...
Alternatively, the DescribeSameAs should be precisely documented.
Simplify migration from 1.4 to 2.0
we would like to, but are lacking resources.
ExchangeItem filter interface
Can be done by adding special arguments. Otherwise it is an idea for an extension to the component.
Make IAdaptedOutput implement IInput
Will be reviewed
Refine IManageState and IByteStateConverter interfaces
This is a general problem for remoting of .Net and java classes, and can/must be solved by the remoting component.
Use DateTime type in ITime interface instead of using double and TimeSpan for duration
Has been discussed many times. No new important arguments. All these methods can be implemented in the SDK (in .NET as extension methods, which will be able to provide the exact same interface as the DateTime).
Component tool interface
Suggested as a component
Generic versions of exchange items and valueset
Cons: It adds complexity to the standard (A standard developer may not have/do not want to have bother about this level of skills), and it is specific to java and .net.
pros: It adds more type safety to the code, and also some performance.
Add missing value definition to IUnit
Discussion where it should be: Quantity/ValueDefinition or Unit. IValueDefinition.MissingDataValue 
.
Add rasterdata support in IElementSet
Suggested as an extension to ElementSet.
Remove Values2D from IValueSet
Refine adapted output factories
Update the IQuality interface
Loop approach
Duplicate - has to do with parallelism
Create more layering in the interfaces
The extension strategy supports this.
Rename IOutput and IInput into IOutputItem and IInputItem
How to make the standard extendable
...