- From: <bugzilla@jessica.w3.org>
- Date: Fri, 23 Apr 2010 23:01:23 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588
Summary: All: Changes to definition of term 'generate'
Product: WS-Resource Access
Version: PR
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: All
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: ram.jeyaraman@microsoft.com
QAContact: public-ws-resource-access-notifications@w3.org
All the WS-RA specs define the term "generate" as follows [1].
I like to suggest two changes as proposed in [2]:
1. Editorial spelling - Change "futher" to "further".
2. The term "MAY NOT" is not generally used. I have suggested a different
phrase.
Both the changes are highlighted within **.
[1] The term "generate" is used in relation to the various faults defined by
this specification to imply that a fault is produced and no futher processing
SHOULD be performed. In these cases the fault SHOULD be transmitted. However,
there might be reasons when a compliant implementation can choose not to
transmit the fault - for example, security concerns - in these situations the
fault MAY NOT be transmitted.
[2] The term "generate" is used in relation to the various faults defined by
this specification to imply that a fault is produced and no *further*
processing SHOULD be performed. In these cases the fault SHOULD be transmitted.
However, there might be reasons when a compliant implementation can choose not
to transmit the fault - for example, security concerns - in these situations
the *service MAY choose not to transmit the fault*.
--
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, 23 April 2010 23:01:50 UTC