- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 18 Aug 2009 19:12:01 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv14814
Modified Files:
wsenum.html wsenum.xml
Log Message:
typo found by Ram
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- wsenum.html 6 Aug 2009 18:42:00 -0000 1.47
+++ wsenum.html 18 Aug 2009 19:11:59 -0000 1.48
@@ -448,7 +448,7 @@
Detecting these errors during Enumerate processing will lessen the chances
of the consumer creating an unusable enumeration. If this check is
performed and a problem is detected then the event source MUST generate
- a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
+ a wsen:UnusableEPR fault rather than returning the EnumerateResponse
message.
</p><p>
Upon successful processing of an Enumerate
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- wsenum.xml 6 Aug 2009 18:42:00 -0000 1.38
+++ wsenum.xml 18 Aug 2009 19:11:59 -0000 1.39
@@ -777,7 +777,7 @@
Detecting these errors during Enumerate processing will lessen the chances
of the consumer creating an unusable enumeration. If this check is
performed and a problem is detected then the event source MUST generate
- a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
+ a wsen:UnusableEPR fault rather than returning the EnumerateResponse
message.
</p>
Received on Tuesday, 18 August 2009 19:12:16 UTC