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

[Bug 8070] New: Enum: ambiguity around new Enum contexts

From: <bugzilla@wiggum.w3.org>
Date: Mon, 26 Oct 2009 14:08:22 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-8070-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8070

           Summary: Enum: ambiguity around new Enum contexts
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Enumeration
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


Section 3 says:
- - - - - - - - - - - - -
Optionally, the data source MAY return an updated enumeration context in the
Pull response; when present, this new enumeration context SHOULD replace the
old one on the consumer, and SHOULD be passed to the data source in all future
responses until and unless the data source again returns an updated enumeration
context.

Consumers SHOULD NOT reuse old enumeration contexts that have been replaced by
the data source. Using a replaced enumeration context in a Pull response MAY
yield undefined results, including being ignored or generating a fault. 
- - - - - - - - - - - - -
(Note: the word "responses" in the first para should be "requests")

And then in section 3.2 it says:
- - - - - - - - - - - - -
[Body]/wsen:PullResponse/wsen:EnumerationContext

    The OPTIONAL EnumerationContext element, if present, contains a new XML
representation of the current enumeration context. The consumer is required to
replace the prior representation with the contents of this element. 
- - - - - - - - - - - - -

Its not clear how strongly the spec mandates that the new enum context
be used in place of the old one.  The SHOULDs seem to contradict the "required"
in the PullResponse.

Proposal:
remove this ambiguity by mandating that the new Enum Context MUST be used
by changing the text in section 3 with:
- - - - - - - - - - - - -
Optionally, the data source MAY return an updated enumeration context in the
Pull response; when present, this new enumeration context MUST replace the old
one on the consumer, and MUST be passed to the data source in all future
requests until and unless the data source again returns an updated enumeration
context.

Consumers MUST NOT reuse old enumeration contexts that have been replaced by
the data source. Using a replaced enumeration context in a Pull response might
yield undefined results, including being ignored or generating a fault. 
- - - - - - - - - - - - -

and replace the text in the PullResponse with:
The consumer MUST replace the prior representation with the contents of this
element.


-- 
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, 26 October 2009 14:08:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 26 October 2009 14:08:26 GMT