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

[Bug 7969] New: Fragment: clarify behavior of optional xml

From: <bugzilla@wiggum.w3.org>
Date: Mon, 19 Oct 2009 14:45:19 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7969-2780@http.www.w3.org/Bugs/Public/>

           Summary: Fragment: clarify behavior of optional xml
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fragment
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org

WS-Fragment.Put has the following:

    This OPTIONAL element contains the fragment resource representation
corresponding to the subset of the resource identified by the wsf:Expression

It is not clear to what should happen to any optional/missing bits of XML
not included within this Value.  For example, are any snippets of XML
currently present left unchanged?  Removed? Defaulted to some resource-specific

We should follow the pattern established in Transfer, where it says:
Any optional values (elements or attributes) not specified in the Put request
message will be set to a resource-specific default value. 

Add the following sentence to the end of the paragraph referenced above:

When @Mode is 'Insert' or 'Replace', any optional values (element or
within this subset that are not specified in the wsf:Value element will be set
to a 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 Monday, 19 October 2009 14:45:23 UTC

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