- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 18 Aug 2009 17:12:25 -0400
- To: public-ws-resource-access@w3.org
- Message-ID: <OFB4706659.48F35C06-ON85257616.00745B48-85257616.00747F6F@us.ibm.com>
As I was doing 7206 I noticed that the words "recommended" and "should"
appear in the new text we added. It seemed clear to me that these did
intent to be RFC2119 terms so I made them uppercase. If there are any
concerns with this please let me know and we'll open an issue to discuss.
thanks
-Doug
______________________________________________________
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com
The more I'm around some people, the more I like my dog.
----- Forwarded by Doug Davis/Raleigh/IBM on 08/18/2009 05:10 PM -----
Doug Davis via cvs-syncmail <cvsmail@w3.org>
Sent by: public-ws-resource-access-notifications-request@w3.org
08/18/2009 05:10 PM
To
public-ws-resource-access-notifications@w3.org
cc
Subject
WWW/2002/ws/ra/edcopies wsenum.xml,1.40,1.41 wseventing.xml,1.63,1.64
wsfrag.xml,1.5,1.6 wsmex.xml,1.37,1.38 wsrt.xml,1.30,1.31
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv28591
Modified Files:
wsenum.xml wseventing.xml wsfrag.xml wsmex.xml wsrt.xml
Log Message:
s/should/SHOULD
s/recommended/RECOMMENDED
for 7206
Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- wsrt.xml 18 Aug 2009 20:54:31 -0000 1.30
+++ wsrt.xml 18 Aug 2009 21:10:01 -0000 1.31
@@ -654,8 +654,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that
extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should
clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD
clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- wsmex.xml 18 Aug 2009 20:54:31 -0000 1.37
+++ wsmex.xml 18 Aug 2009 21:10:01 -0000 1.38
@@ -675,8 +675,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that
extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should
clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD
clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p>
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- wsfrag.xml 18 Aug 2009 20:54:31 -0000 1.5
+++ wsfrag.xml 18 Aug 2009 21:10:01 -0000 1.6
@@ -421,8 +421,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that
extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should
clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD
clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p>
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- wsenum.xml 18 Aug 2009 20:54:30 -0000 1.40
+++ wsenum.xml 18 Aug 2009 21:10:01 -0000 1.41
@@ -334,8 +334,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that
extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should
clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD
clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- wseventing.xml 18 Aug 2009 20:54:30 -0000 1.63
+++ wseventing.xml 18 Aug 2009 21:10:01 -0000 1.64
@@ -547,8 +547,8 @@
In cases where it is either desirable or necessary for the receiver
of a request that has been extended to indicate that it has
recognized and accepted the semantics associated with that
extension,
- it is recommended that the receiver add a corresponding extension
- to the response message. The definition of an extension should
clearly
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD
clearly
specify how the extension that appears in the response correlates
with that in the corresponding request.
</p>
Received on Tuesday, 18 August 2009 21:13:08 UTC