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

[Bug 8283] New: fault descriptions/semantics are inconsistent

From: <bugzilla@wiggum.w3.org>
Date: Fri, 13 Nov 2009 20:05:08 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-8283-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283

           Summary: fault descriptions/semantics are inconsistent
           Product: WS-Resource Access
           Version: PR
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


WS-Eventing defines a number of faults in Section 6. Most of these faults are
described by text with the pattern "This fault is generated when . . .". Two of
these faults (EmptyFilter and UnusableEPR) are described by text with the
pattern "This fault MAY be generated when . . ."

1.) Why do some descriptions use the RFC 2119 "MAY" and others do not?

2.) Since the term "generated" means "do something internal and OPTIONALLY
transmit the fault", the phrase "MAY be generated" is redundant.

Proposal: Change the descriptions of the faults to use the pattern "This fault
MUST be generated when . . ."


-- 
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 Friday, 13 November 2009 20:05:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:36 UTC