This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6712 - Transfer: Create is ambiguous
Summary: Transfer: Create is ambiguous
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-03-17 15:21 UTC by Doug Davis
Modified: 2009-08-18 21:15 UTC (History)
0 users

See Also:


Attachments

Description Doug Davis 2009-03-17 15:21:57 UTC
Current Transfer.Create states:
- - - - - -
/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. 
- - - - - -
This is a bit ambiguous because its not clear how the service knows whether
or not the child of Create is the actual representation, a list of
instructions or something else.  There needs to be a very clear flag
to indicate what's in the Create element.

Proposal:
Add a 'Dialect' attribute - not unlike the Mode attribute that we
see on the Delivery element in eventing - that explicitly tells the
service how to interpret the children of the Create element.

<wst:Create Dialect="xs:anyURI"? ...>
  xs:any *
</wst:Create>

Define a "http://.../ws-t/XMLRepresentation" dialect/uri and make
the absence of a Dialect attribute default to this.
Comment 1 Robert Freund 2009-04-21 20:08:00 UTC
discussed on 2009-04-21 (Action-59)
Comment 4 Robert Freund 2009-06-09 19:00:33 UTC
OPTIONAL Hint that describes the content, CONTENT DESCRIPTION. If the service needs a hint and the CONTENT DESCRIPTION is not known, then service MUST generate a fault (to be defined). If the service does not need a hint then may ignore the CONTENT DESCRIPTION and MAY NOT generate a fault. Type(CONTENT DESCRIPTION) = xs:anyURI

resolved as a directional decision on 2009-06-09
Comment 6 Robert Freund 2009-06-10 20:30:08 UTC
When this OPTIONAL attribute is present it conveys additional information that can be used by the service to process this message. If the service can determine how to process the message it MAY choose to ignore this attribute, even if the URI provided is not known. However, if the service needs this information, for example to determine if the child elements of the wst:Create are the literal resource representation or an instruction, but the attribute is not present or the URI is not known, then the service MUST generate an invalidContentDescription fault. There is no default value.

n.b.
modify fault to correspond with this language