WS-Transfer empty resource feature at risk

Hi Bob,

We touched upon this during our previous meeting - WS-Transfer and WS-Fragment have this notion of an empty representation.

[Body]/wst:Create/wst:Representation
This OPTIONAL element acts as a container for the full representation of the resource. If this element is not present the resource MUST be created using default values (equivalent to a null constructor). This element MAY have no children, in which case the resource MUST be created with an empty representation (equivalent to an empty constructor).
During interoperation testing, Microsoft does not plan to test the empty representation case. That would leave that feature with likely just one implementation.

Hence, I suggest marking the empty representation case as a feature at risk during CR.

Thanks.