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

[Bug 7486] New: Transfer: clear up confusion around missing Put values

From: <bugzilla@wiggum.w3.org>
Date: Thu, 03 Sep 2009 13:58:01 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7486-2780@http.www.w3.org/Bugs/Public/>

           Summary: Transfer: clear up confusion around missing Put values
           Product: WS-Resource Access
           Version: PR
          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

There's an ongoing discussion in WSMan about what to do during a
Put when there are optional properties of a resource.  Here's the
- do a T.Create() that includes some optional (minOccurs=0) elements in the
- do a T.Put() but this time do not include those optional elements.

Question: are those optional elements reset to their default values (eg. null)
or do they retain the values specified during the t.Create()?

The Transfer spec currently says things like:
"This specification defines one Web service operation (Put) for updating a
resource by providing a replacement representation."
"A Put request MUST be targeted at the resource whose representation is desired
to be replaced, ..."

These, to me, seem to push for a total replacement - meaning the values
would go back to their defaults.

The WSMan spec added some text that reinforces this notion:
"To delete individual property values within an object that, itself, is not to
be deleted, either the client can perform a Put operation with those properties
removed, or the service can support fragment-level access."

The Transfer spec itself should make this clear by being more explicit about

To the end of the first paragraph of the Put section, add the following text:

This operation will replace the entire XML representation of the resource. Any
optional values (elements or attributes) not specified in the Put request
message will be set to some resource specific default value.

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 Thursday, 3 September 2009 13:58:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:35 UTC