[Bug 6712] New: Transfer: Create is ambiguous

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6712

           Summary: Transfer: Create is ambiguous
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Transfer
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Tuesday, 17 March 2009 15:22:06 UTC