W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > March 2009

issue 6673: proposal

From: Doug Davis <dug@us.ibm.com>
Date: Wed, 11 Mar 2009 22:04:39 -0400
To: public-ws-resource-access@w3.org
Message-ID: <OF1F41BA70.1777EA44-ON85257577.000A5E7D-85257577.000B6A82@us.ibm.com>
Change:
/s:Envelope/s:Body/Create
If this REQUIRED element contains children then the first child MUST be 
the literal resource representation, a representation of the constructor 
for the resource, or other instructions for creating the resource. All 
other children SHOULD be ignored by the service. If this element does not 
contain any children then the resource will be created using default 
values. 
to:
/s:Envelope/s:Body/Create
If this REQUIRED element contains children then the first child MUST be 
the literal resource representation, a representation of the constructor 
for the resource, or other instructions for creating the resource. Unless 
additional semantics are defined by an extension specification, this 
element MUST NOT contain any additional child elements. <del>All other 
children SHOULD be ignored by the service. </del> If this element does not 
contain any children then the resource will be created using default 
values. 

Change:
/s:Envelope/wst:CreateResponse
This REQUIRED element MUST contain, at a minimum, a resource reference 
(wst:ResourceCreated element) to the newly created resource. 
By default, a service MUST also return the current representation of the 
new resource as the second child of the wst:CreateResponse element if the 
created representation logically differs from the representation sent in 
the Create request message. That is, the initial representation is 
returned if one or more values present in Create message was specifically 
overridden with a different value during resource creation. If default 
values are used to complete a resource creation which were not present in 
the Create message, then this does not constitute a logical difference. 
The presence of additional child elements which contain other information 
pertaining to the result of the Create operation is service-specific. 
to:
/s:Envelope/wst:CreateResponse
This REQUIRED element MUST contain, at a minimum, a resource reference 
(wst:ResourceCreated element) to the newly created resource. 
By default, a service MUST also return the current representation of the 
new resource as the second child of the wst:CreateResponse element if the 
created representation logically differs from the representation sent in 
the Create request message. That is, the initial representation is 
returned if one or more values present in Create message was specifically 
overridden with a different value during resource creation. If default 
values are used to complete a resource creation which were not present in 
the Create message, then this does not constitute a logical difference. 
Unless additional semantics are defined by an extension specification, 
this element MUST NOT contain any additional child elements.<del> The 
presence of additional child elements which contain other information 
pertaining to the result of the Create operation is service-specific.  
</del>

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
Received on Thursday, 12 March 2009 02:19:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:17:51 GMT