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 8298 - Transfer: misuse of RFC2119 terms
Summary: Transfer: misuse of RFC2119 terms
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (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 02:59 UTC by Gilbert Pilz
Modified: 2010-03-17 10:57 UTC (History)
1 user (show)

See Also:


Attachments

Description Gilbert Pilz 2009-11-14 02:59:38 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-Transfer contains a number of cases where RFC 2119 keywords are
misused. A changebar copy of WS-Transfer will be sent to the mailing list and
linked in the comments below.
Comment 2 Robert Freund 2010-02-09 21:00:39 UTC
Resolved as proposed in comment #1