- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 06 Nov 2009 05:22:18 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv31851
Modified Files:
wsenum.html wsenum.xml wsfrag.html
Log Message:
8070, 8071, 8072
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -d -r1.88 -r1.89
--- wsenum.html 6 Nov 2009 05:07:57 -0000 1.88
+++ wsenum.html 6 Nov 2009 05:22:16 -0000 1.89
@@ -67,11 +67,11 @@
4.9 <a href="#UnusableEPR">UnusableEPR</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_1925">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_1922">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2014">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2200">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2011">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2197">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/>
@@ -325,32 +325,41 @@
operation. The consumer then passes that XML data back to the data
source in the Pull request. Optionally, the data source MAY return
an updated enumeration context in the Pull response; when present,
- this new enumeration context SHOULD replace the old one on the
- consumer, and SHOULD be passed to the data source in all future
- responses until and unless the data source again returns an updated
+ this new enumeration context MUST replace the old one on the
+ consumer, and MUST be passed to the data source in all future
+ requests until and unless the data source again returns an updated
enumeration context.
</p><p>
- Consumers SHOULD NOT reuse old enumeration
- contexts that have been replaced by the data source. Using a
- replaced enumeration context in a Pull response MAY yield undefined
- results, including being ignored or generating a
- fault.
- </p><p>
- Once the last element in a sequence has been
- returned, or the enumeration context has expired, the enumeration
- context is considered invalid and the result of subsequent
- operations referencing that context is undefined.
- </p><p>
Callers MAY issue a Release operation against a
valid enumeration context at any time, which causes the enumeration
context to become invalid and allows the data source to free up any
resources it might have allocated to the enumeration. Issuing a
Release operation prior to reaching the end of the sequence of
elements is explicitly allowed; however, no further operations
- SHOULD be issued after a Release.
+ MUST be issued after a Release.
</p><p>
+ An enumeration context can become invalid for any reason including:
+ </p><ol class="enumar"><li><p>
+ Enumeration completed (i.e. an EndOfSequence has been returned in a
+ Pull response)
+ </p></li><li><p> Enumeration released </p></li><li><p> Enumeration expired </p></li><li><p>
+ Enumeration ended (i.e. ended via an EnumerationEnd message from
+ data source
+ </p></li><li><p>
+ Enumeration context replaced in the response to another Pull request
+ </p></li></ol><p>
In addition, the data source MAY invalidate an
enumeration context at any time, as necessary.
+ </p><p>
+ When processing a Pull, Renew, GetStatus or Release operation, a
+ data source MUST generate an wsen:InvalidEnumerationContext fault if
+ it determines that the enumeration context supplied by the consumer
+ in the request is invalid.
+ </p><p>
+ Note that the data source might not be able to determine that an
+ enumeration context is invalid, especially if all of the state
+ associated with the enumeration is kept in the enumeration context
+ and refreshed on every PullResponse or RenewResponse.
</p><div class="div2">
<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
Data sources MUST support the Enumerate operation to start an enumeration.
@@ -540,13 +549,13 @@
or by the data source at any time for reasons such as connection
termination, resource constraints, or system
shut-down.
- </p></dd><dt class="label"><b>[body]</b>/wsen:EnumerateResponse/wsen:EnumerationContext
+ </p></dd><dt class="label"><b>[Body]</b>/wsen:EnumerateResponse/wsen:EnumerationContext
</dt><dd><p>
The required EnumerationContext element
contains the XML representation of the new enumeration context. The
consumer is required to pass this XML data in Pull requests for
- this enumeration context, until and unless a PullResponse message
- updates the enumeration context.
+ this enumeration context, until and unless a PullResponse or
+ RenewResponse message updates the enumeration context.
</p></dd></dl><p><a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
@@ -634,25 +643,6 @@
</p><dl><dt class="label"><b>[Body]</b>/wsen:Pull/wsen:EnumerationContext </dt><dd><p>
This required element contains the XML data
that represents the current enumeration context.
- </p><p>
- The data source MUST fail the request and MUST generate the
- wsen:InvalidEnumerationContext fault if the data source is able to
- determine that the enumeration context is invalid for any reason
- including:</p><ol class="enumar"><li><p>
- Context replaced in the response to another Pull request
- </p></li><li><p>
- Context completed (i.e. an EndOfSequence has been returned in
- a Pull response)
- </p></li><li><p>
- Context released
- </p></li><li><p>
- Context expired
- </p></li></ol><p>
- Note that the data source might not be able to
- determine that an enumeration context is not valid, especially if
- all of the state associated with the enumeration is kept in the
- enumeration context and refreshed on every
- PullResponse.
</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
@@ -743,7 +733,7 @@
</dt><dd><p>
The OPTIONAL EnumerationContext element, if
present, contains a new XML representation of the current
- enumeration context. The consumer is required to replace the prior
+ enumeration context. The consumer MUST replace the prior
representation with the contents of this element.
</p></dd><dt class="label"><b>[Body]</b>/wsen:PullResponse/wsen:Items/<em>xs:any</em></dt><dd><p>
The OPTIONAL Items element contains one or
@@ -751,12 +741,8 @@
returned.
</p></dd><dt class="label"><b>[Body]</b>/wsen:PullResponse/wsen:EndOfSequence </dt><dd><p>
This OPTIONAL element indicates that no more
- elements are available from this enumeration. Additionally, once
- this element is returned in a Pull response message, subsequent
- Pull requests using that enumeration context MUST generate a
- wsen:InvalidEnumerationContext fault message, if the data source
- is able to determine that the enumeration context is no longer
- valid.
+ elements are available from this enumeration and the enumeration
+ context sent by the consumer in the request becomes invalid.
</p></dd></dl><p>
Note that at least one of wsen:Items or
wsen:EndOfSequence MUST appear. It is possible for both to appear
@@ -840,12 +826,6 @@
receipt of a Pull response containing a wsen:EndOfSequence element,
the consumer SHOULD NOT issue a Release operation to signal that
the enumeration context is no longer needed.
- </p><p>
- If the consumer does issue a Pull or Release on
- an invalid enumeration context, the result is undefined: the data
- source MAY ignore the request or MAY return a
- wsen:InvalidEnumerationContext fault or MAY
- take some other action.
</p></div><div class="div2">
<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
Data sources MUST support requests to renew
@@ -873,15 +853,6 @@
</p><dl><dt class="label"><b>[Body]</b>/wsen:Renew/wsen:EnumerationContext </dt><dd><p>
This required element contains the XML data
that represents the current enumeration context.
- </p><p>
- If the enumeration context is not valid,
- either because it has been replaced in the response to another Pull
- request, or because it has completed (EndOfSequence has been
- returned in a Pull response), or because it has been Released, or
- because it has expired, or because the data source has had to
- invalidate the context, then the data source SHOULD fail the
- request, and if so, MUST generate a wsen:InvalidEnumerationContext
- fault.
</p></dd></dl><p>
Other components of the outline above are not
further constrained by this specification.
@@ -932,9 +903,8 @@
(see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are
not further constrained by this specification.
</p><p>
- If the enumeration is valid and has not expired,
- the data source MUST reply with a response of the following
- form:
+ If the enumeration is valid the data source MUST reply with a
+ response of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2009/09/ws-enu/GetStatusResponse
@@ -1181,8 +1151,8 @@
if no additional information is available.
</em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="TimedOut" id="TimedOut"/>4.8 TimedOut</h3><p>
- This fault is generated if the data source times out is the
- wsen:MaxTime is reached.
+ This fault is generated if the data source times out during the
+ processing of a Pull operation, if the wsen:MaxTime is reached.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Receiver </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:TimedOut </td></tr><tr><td><b>[Reason]</b></td><td> Timeout. </td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
<h3><a name="UnusableEPR" id="UnusableEPR"/>4.9 UnusableEPR</h3><p>
This fault MAY be generated when a data source detects
@@ -1296,7 +1266,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_1925" id="iddiv2_1_1925"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1922" id="iddiv2_1_1922"/>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 -
@@ -1388,7 +1358,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_2014" id="iddiv2_1_2014"/>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_2011" id="iddiv2_1_2011"/>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.
@@ -1460,7 +1430,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_2200" id="iddiv2_1_2200"/>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_2197" id="iddiv2_1_2197"/>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>
@@ -1968,4 +1938,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8075">8075</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8069">8069</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076">8076</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</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=7912">7912</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issues
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8070">8070</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8071">8071</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8072">8072</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.80
retrieving revision 1.81
diff -u -d -r1.80 -r1.81
--- wsenum.xml 6 Nov 2009 05:07:57 -0000 1.80
+++ wsenum.xml 6 Nov 2009 05:22:16 -0000 1.81
@@ -562,6 +562,7 @@
is abandoning an enumeration context before it has completed the
enumeration.
</p>
+
<p>
Enumeration contexts are represented as XML data
that is opaque to the consumer. Initially, the consumer gets an
@@ -569,24 +570,12 @@
operation. The consumer then passes that XML data back to the data
source in the Pull request. Optionally, the data source MAY return
an updated enumeration context in the Pull response; when present,
- this new enumeration context SHOULD replace the old one on the
- consumer, and SHOULD be passed to the data source in all future
- responses until and unless the data source again returns an updated
+ this new enumeration context MUST replace the old one on the
+ consumer, and MUST be passed to the data source in all future
+ requests until and unless the data source again returns an updated
enumeration context.
</p>
- <p>
- Consumers SHOULD NOT reuse old enumeration
- contexts that have been replaced by the data source. Using a
- replaced enumeration context in a Pull response MAY yield undefined
- results, including being ignored or generating a
- fault.
- </p>
- <p>
- Once the last element in a sequence has been
- returned, or the enumeration context has expired, the enumeration
- context is considered invalid and the result of subsequent
- operations referencing that context is undefined.
- </p>
+
<p>
Callers MAY issue a Release operation against a
valid enumeration context at any time, which causes the enumeration
@@ -594,12 +583,57 @@
resources it might have allocated to the enumeration. Issuing a
Release operation prior to reaching the end of the sequence of
elements is explicitly allowed; however, no further operations
- SHOULD be issued after a Release.
+ MUST be issued after a Release.
</p>
+
+ <p>
+ An enumeration context can become invalid for any reason including:
+ </p>
+
+ <olist>
+ <item>
+ <p>
+ Enumeration completed (i.e. an EndOfSequence has been returned in a
+ Pull response)
+ </p>
+ </item>
+ <item>
+ <p> Enumeration released </p>
+ </item>
+ <item>
+ <p> Enumeration expired </p>
+ </item>
+ <item>
+ <p>
+ Enumeration ended (i.e. ended via an EnumerationEnd message from
+ data source
+ </p>
+ </item>
+ <item>
+ <p>
+ Enumeration context replaced in the response to another Pull request
+ </p>
+ </item>
+ </olist>
+
<p>
In addition, the data source MAY invalidate an
enumeration context at any time, as necessary.
</p>
+
+ <p>
+ When processing a Pull, Renew, GetStatus or Release operation, a
+ data source MUST generate an wsen:InvalidEnumerationContext fault if
+ it determines that the enumeration context supplied by the consumer
+ in the request is invalid.
+ </p>
+
+ <p>
+ Note that the data source might not be able to determine that an
+ enumeration context is invalid, especially if all of the state
+ associated with the enumeration is kept in the enumeration context
+ and refreshed on every PullResponse or RenewResponse.
+ </p>
<div2 id="Enumerate">
<head>Enumerate</head>
@@ -924,15 +958,15 @@
<gitem>
<label>
- <kw>[body]</kw>/wsen:EnumerateResponse/wsen:EnumerationContext
+ <kw>[Body]</kw>/wsen:EnumerateResponse/wsen:EnumerationContext
</label>
<def>
<p>
The required EnumerationContext element
contains the XML representation of the new enumeration context. The
consumer is required to pass this XML data in Pull requests for
- this enumeration context, until and unless a PullResponse message
- updates the enumeration context.
+ this enumeration context, until and unless a PullResponse or
+ RenewResponse message updates the enumeration context.
</p>
</def>
</gitem>
@@ -1060,43 +1094,6 @@
This required element contains the XML data
that represents the current enumeration context.
</p>
-
- <p>
- The data source MUST fail the request and MUST generate the
- wsen:InvalidEnumerationContext fault if the data source is able to
- determine that the enumeration context is invalid for any reason
- including:</p>
- <olist>
- <item>
- <p>
- Context replaced in the response to another Pull request
- </p>
- </item>
- <item>
- <p>
- Context completed (i.e. an EndOfSequence has been returned in
- a Pull response)
- </p>
- </item>
- <item>
- <p>
- Context released
- </p>
- </item>
- <item>
- <p>
- Context expired
- </p>
- </item>
- </olist>
-
- <p>
- Note that the data source might not be able to
- determine that an enumeration context is not valid, especially if
- all of the state associated with the enumeration is kept in the
- enumeration context and refreshed on every
- PullResponse.
- </p>
</def>
</gitem>
@@ -1232,7 +1229,7 @@
<p>
The OPTIONAL EnumerationContext element, if
present, contains a new XML representation of the current
- enumeration context. The consumer is required to replace the prior
+ enumeration context. The consumer MUST replace the prior
representation with the contents of this element.
</p>
</def>
@@ -1256,12 +1253,8 @@
<def>
<p>
This OPTIONAL element indicates that no more
- elements are available from this enumeration. Additionally, once
- this element is returned in a Pull response message, subsequent
- Pull requests using that enumeration context MUST generate a
- wsen:InvalidEnumerationContext fault message, if the data source
- is able to determine that the enumeration context is no longer
- valid.
+ elements are available from this enumeration and the enumeration
+ context sent by the consumer in the request becomes invalid.
</p>
</def>
</gitem>
@@ -1372,14 +1365,6 @@
the consumer SHOULD NOT issue a Release operation to signal that
the enumeration context is no longer needed.
</p>
-
- <p>
- If the consumer does issue a Pull or Release on
- an invalid enumeration context, the result is undefined: the data
- source MAY ignore the request or MAY return a
- wsen:InvalidEnumerationContext fault or MAY
- take some other action.
- </p>
</div2>
<div2 id="Renew">
@@ -1426,17 +1411,6 @@
This required element contains the XML data
that represents the current enumeration context.
</p>
- <p>
- If the enumeration context is not valid,
- either because it has been replaced in the response to another Pull
- request, or because it has completed (EndOfSequence has been
- returned in a Pull response), or because it has been Released, or
- because it has expired, or because the data source has had to
- invalidate the context, then the data source SHOULD fail the
- request, and if so, MUST generate a wsen:InvalidEnumerationContext
- fault.
- </p>
-
</def>
</gitem>
</glist>
@@ -1526,9 +1500,8 @@
</p>
<p>
- If the enumeration is valid and has not expired,
- the data source MUST reply with a response of the following
- form:
+ If the enumeration is valid the data source MUST reply with a
+ response of the following form:
</p>
<example>
@@ -2116,8 +2089,8 @@
<head>TimedOut</head>
<p>
- This fault is generated if the data source times out is the
- wsen:MaxTime is reached.
+ This fault is generated if the data source times out during the
+ processing of a Pull operation, if the wsen:MaxTime is reached.
</p>
<table border="1">
@@ -3517,6 +3490,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issues
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8070">8070</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8071">8071</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8072">8072</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Friday, 6 November 2009 05:22:29 UTC