This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8070 - Enum: ambiguity around new Enum contexts
Summary: Enum: ambiguity around new Enum contexts
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-26 14:08 UTC by Doug Davis
Modified: 2009-12-08 22:09 UTC (History)
0 users

See Also:


Attachments
latest proposal (271.50 KB, application/doc)
2009-11-06 00:32 UTC, Doug Davis
Details
even newer one (271.50 KB, application/doc)
2009-11-06 00:44 UTC, Doug Davis
Details

Description Doug Davis 2009-10-26 14:08:22 UTC
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.
Comment 1 Doug Davis 2009-11-04 16:50:48 UTC
Joint proposal for 8070, 8071, 8072:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0025.html
Comment 2 Doug Davis 2009-11-06 00:32:06 UTC
Created attachment 780 [details]
latest proposal
Comment 3 Doug Davis 2009-11-06 00:44:03 UTC
Created attachment 781 [details]
even newer one
Comment 4 Doug Davis 2009-11-06 05:23:27 UTC
Agreed with proposal:
http://www.w3.org/Bugs/Public/attachment.cgi?id=781