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 8072 - Enum: inconsistency around invalid EnumContext
Summary: Enum: inconsistency around invalid EnumContext
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: hasProposal
Depends on:
Blocks:
 
Reported: 2009-10-26 14:28 UTC by Doug Davis
Modified: 2009-12-08 22:09 UTC (History)
0 users

See Also:


Attachments

Description Doug Davis 2009-10-26 14:28:17 UTC
The Pull section says:
- - - - - - -
 The data source MUST fail the request and MUST generate the wsen:InvalidEnumerationContext fault if the data source is able to determine that the enumeration context is invalid for any reason including:

   1. Context replaced in the response to another Pull request
   2. Context completed (i.e. an EndOfSequence has been returned in a Pull response)
   3. Context released
   4. Context expired 
- - - - - - -

Which is sort of ok.  However, later on the spec we talk about how data sources 
SHOULD fault requests messages that use an invalid Enum Context 
(See Renew for an example).

Proposal:
Modify any occurrence of the SHOULD with a MUST, in particular change:
- - - - - - -
If the enumeration context is not valid, either because it has been replaced in the response to another Pull request, or because it has completed (EndOfSequence has been returned in a Pull response), or because it has been Released, or because it has expired, or because the data source has had to invalidate the context, then the data source SHOULD fail the request, and if so, MUST generate a wsen:InvalidEnumerationContext fault. 
- - - - - - -

to a much less annoying verbose paragraph:
- - - - - - -
If the enumeration context is not valid then the data source MUST generate 
a wsen:InvalidEnumerationContext fault.
- - - - - - -

At the same time I'd like to remove the reference in the Pull operation to
"failing requests". It is an impl choice whether to send the fault so to
be consistent with other specs we should just say what fault MUST be generated
and leave it at that.

So, change:
The data source MUST fail the request and MUST generate the wsen:InvalidEnumerationContext fault...

to:
The data source MUST generate a wsen:InvalidEnumerationContext fault...
Comment 1 Doug Davis 2009-11-03 20:21:14 UTC
Related to this, I came across text like this:
--
 If the consumer does issue a Pull or Release on an invalid enumeration context, the result is undefined: the data source MAY ignore the request or MAY return a wsen:InvalidEnumerationContext fault or MAY take some other action. 
--

we should remove this text as my proposed text clears this up.
Comment 2 Doug Davis 2009-11-04 16:50:53 UTC
Joint proposal for 8070, 8071, 8072:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0025.html
Comment 3 Doug Davis 2009-11-06 05:09:54 UTC
agreed proposal from 8070:
http://www.w3.org/Bugs/Public/attachment.cgi?id=781