RE: [Bug 8181] New: desription of fragment put is confusing

> "This element identifies the fragment in the resource as it appears after successfully processing the Put request."

This cannot be guaranteed since depending on the nature of update, it is possible that the fragment may not be present (for example, delete). 

Proposal: Suggest removing this sentence.

-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org [mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
Sent: Wednesday, November 04, 2009 10:20 AM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 8181] New: desription of fragment put is confusing

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

           Summary: desription of fragment put is confusing
           Product: WS-Resource Access
           Version: PR
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fragment
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


Section 3.2 of WS-Fragment contains the following sentence in the description of /wst:Put/wsf:Fragment/wsf:Expression:

"This element identifies which fragment in the resource this operation applies to. If the value of this element does not conform to the syntax of the language specified in the Language attribute, or is semantically invalid, a wsf:InvalidExpression fault MUST be generated. 

This element identifies the fragment in the resource as it appears after successfully processing the Put request."

The statements "this element identifies which fragment in the resource this operation applies to" and "this element identifies the fragment in the resource as it appears after successfully processing the Put request" are contradictory.


--
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 Friday, 22 January 2010 21:32:28 UTC