- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 23 Feb 2010 22:51:00 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1657
Modified Files:
wsenum.html wsenum.xml
Log Message:
8306
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -d -r1.115 -r1.116
--- wsenum.html 23 Feb 2010 16:18:18 -0000 1.115
+++ wsenum.html 23 Feb 2010 22:50:57 -0000 1.116
@@ -69,11 +69,11 @@
4.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_2019">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_2017">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2114">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2300">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2112">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2298">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -677,13 +677,16 @@
that represents the current enumeration context.
</p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxTime </dt><dd><p>
This OPTIONAL element (of type xs:duration)
- indicates the maximum amount of time the initiator is willing to
+ indicates the maximum amount of time the consumer is willing to
allow the data source to assemble the Pull response. When this
element is absent, the data source is NOT REQUIRED to limit the
amount of time it takes to assemble the Pull
response. The data source MUST recognize the wsen:MaxTime
element and return a wsen:TimedOut fault if no elements
are available prior to the request message's deadline.
+ However, this fault MUST NOT cause the enumeration context to
+ become invalid and the consumer can issue additional Pull requests
+ using this enumeration context after receiving this fault.
</p><p>
This is useful with data sources that
accumulate elements over time and package them into a single Pull
@@ -700,7 +703,7 @@
</p></dd><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:MaxCharacters </dt><dd><p>
This OPTIONAL element (of type xs:long)
indicates the maximum size of the returned elements, in Unicode
- characters, that the initiator is willing to accept. When this
+ characters, that the consumer is willing to accept. When this
element is absent, the data source is NOT REQUIRED to limit the
number of characters in the Pull response.
Implementations MUST NOT
@@ -732,20 +735,6 @@
Other components of the outline above are not
further constrained by this specification.
</p><p>
- Upon receipt of a Pull request message, the
- data source MAY wait as long as it deems necessary (but not longer
- than the value of the wsen:MaxTime element, if present) to produce
- a message for delivery to the consumer. The data source MUST
- recognize the wsen:MaxTime element and return a
- wsen:TimedOut fault if no elements are available prior to the
- request message's deadline.
-
- Note, however, that this fault SHOULD NOT cause
- the enumeration context to become invalid (of course, the data
- source MAY invalidate the enumeration context for other reasons).
- That is, the requestor can issue additional Pull
- requests using this enumeration context after receiving this fault.
- </p><p>
Upon successful processing of a Pull request
message, a data source MUST return a Pull response
message of the following form:
@@ -955,7 +944,7 @@
not further constrained by this specification.
</p><p>
This operation is safe; it will not result in any side effect
- imputable to the requester. This means that in case of an underlying
+ imputable to the consumer. This means that in case of an underlying
protocol error that might get unnoticed, resending the same request
can be done automatically.
</p></div><div class="div2">
@@ -1216,7 +1205,7 @@
in references need to be signed along with the body in order to
"bind" them together and prevent certain types of attacks.
</p><p>
- If a requestor is issuing multiple messages to a
+ If a consumer is issuing multiple messages to a
Web service, such as when a consumer is enumerating a data source,
it is RECOMMENDED that a security context be established using the
mechanisms described in <a href="#WSSecureConversation">[WS-SecureConversation]</a>. It is often
@@ -1311,7 +1300,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2019" id="iddiv2_1_2019"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_2017" id="iddiv2_1_2017"/>6.1 Enumeration Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Enumeration specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1414,7 +1403,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2114" id="iddiv2_1_2114"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2112" id="iddiv2_1_2112"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1486,7 +1475,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2300" id="iddiv2_1_2300"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2298" id="iddiv2_1_2298"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -2090,4 +2079,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436">6436</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</a></td></tr><tr><td> 2010/02/23 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306">8306</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -d -r1.107 -r1.108
--- wsenum.xml 23 Feb 2010 16:18:18 -0000 1.107
+++ wsenum.xml 23 Feb 2010 22:50:58 -0000 1.108
@@ -1139,13 +1139,16 @@
<def>
<p>
This OPTIONAL element (of type xs:duration)
- indicates the maximum amount of time the initiator is willing to
+ indicates the maximum amount of time the consumer is willing to
allow the data source to assemble the Pull response. When this
element is absent, the data source is NOT REQUIRED to limit the
amount of time it takes to assemble the Pull
response. The data source MUST recognize the wsen:MaxTime
element and return a wsen:TimedOut fault if no elements
are available prior to the request message's deadline.
+ However, this fault MUST NOT cause the enumeration context to
+ become invalid and the consumer can issue additional Pull requests
+ using this enumeration context after receiving this fault.
</p>
<p>
This is useful with data sources that
@@ -1177,7 +1180,7 @@
<p>
This OPTIONAL element (of type xs:long)
indicates the maximum size of the returned elements, in Unicode
- characters, that the initiator is willing to accept. When this
+ characters, that the consumer is willing to accept. When this
element is absent, the data source is NOT REQUIRED to limit the
number of characters in the Pull response.
Implementations MUST NOT
@@ -1218,22 +1221,6 @@
</p>
<p>
- Upon receipt of a Pull request message, the
- data source MAY wait as long as it deems necessary (but not longer
- than the value of the wsen:MaxTime element, if present) to produce
- a message for delivery to the consumer. The data source MUST
- recognize the wsen:MaxTime element and return a
- wsen:TimedOut fault if no elements are available prior to the
- request message's deadline.
-
- Note, however, that this fault SHOULD NOT cause
- the enumeration context to become invalid (of course, the data
- source MAY invalidate the enumeration context for other reasons).
- That is, the requestor can issue additional Pull
- requests using this enumeration context after receiving this fault.
- </p>
-
- <p>
Upon successful processing of a Pull request
message, a data source MUST return a Pull response
message of the following form:
@@ -1563,7 +1550,7 @@
<p>
This operation is safe; it will not result in any side effect
- imputable to the requester. This means that in case of an underlying
+ imputable to the consumer. This means that in case of an underlying
protocol error that might get unnoticed, resending the same request
can be done automatically.
</p>
@@ -2280,7 +2267,7 @@
"bind" them together and prevent certain types of attacks.
</p>
<p>
- If a requestor is issuing multiple messages to a
+ If a consumer is issuing multiple messages to a
Web service, such as when a consumer is enumerating a data source,
it is RECOMMENDED that a security context be established using the
mechanisms described in <bibref ref="WSSecureConversation"/>. It is often
@@ -3934,6 +3921,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/23 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306">8306</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 23 February 2010 22:51:01 UTC