8304 – Enum: misuse of RFC2119 terms

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 8304 - Enum: misuse of RFC2119 terms
Summary: Enum: misuse of RFC2119 terms
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-11-14 03:43 UTC by Gilbert Pilz
Modified: 2010-03-17 10:51 UTC (History)
1 user (show)

See Also:

Attachments

Description Gilbert Pilz 2009-11-14 03:43:51 UTC 
The RFC 2119 terms "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" are meant to
apply to specific requirements and behaviors within the context of a
specification. They are *not* meant to refer to general concepts and actions.

To quote RFC 2119: "Imperatives of the type defined in this memo must be used
with care and sparingly.  In particular, they MUST only be used where it is
actually required for interoperation or to limit behavior which has potential
for causing harm (e.g., limiting retransmisssions)"

WS-Enumeration contains a number of cases where RFC 2119 keywords are
misused. A changebar copy of WS-Enumeration will be sent to the mailing list and
linked in the comments below.
Comment 2 Robert Freund 2010-02-09 21:07:41 UTC 
partial change to proposal in comment 1 to
The ordering or completeness of the enumeration is undefined; the returned data items represent a selection by the data source of items it wishes to present to that consumer at that time in that order, with no guarantee that every available item is returned or that the order in which items is returned has any semantic meaning whatsoever (of course, any specific data source can provide strong guarantees, if so desired).
Comment 3 Robert Freund 2010-02-09 21:18:18 UTC 
partial change additional to above to proposal in comment 1
The consumer MUST NOT issue additional Pull request messages after a Pull response containing a wsen:EndOfSequence element has been received.
Comment 4 Robert Freund 2010-02-09 21:22:59 UTC 
Additional modifications to the proposal in comment #1

Upon successful processing of a Pull request message, a data source MUST return a Pull response message of the following form:

Upon successful processing of a Release request message, a data source MUST return a Release response message of the following form:
Comment 5 Robert Freund 2010-02-09 21:26:02 UTC 
additional change to the proposal in section 3 in the proposal contained in comment #1

Upon successful processing of an Enumerate request message, a data source MUST create an enumeration context and return that context in an Enumerate response message of the following form:
Comment 6 Robert Freund 2010-02-09 21:27:06 UTC 
resolved with comments 1-5