Re: WS-Transfer empty resource feature at risk

Ram,
  during the meeting we agreed that his was akin to more like schema 
testing which isn't really testing the transfer spec itself - so we remove 
that as a stand-alone feature.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Ram Jeyaraman <Ram.Jeyaraman@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
01/13/2011 07:11 PM

To
"Bob Freund (bob.freund@hitachisoftware.com)" 
<bob.freund@hitachisoftware.com>
cc
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Subject
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.