REC-ws-enumeration-20111213 129 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Enumeration (WS-Enumeration)</title><style type="text/css">
code           { font-family: monospace; }

div.constraint,
div.issue,
div.note,
div.notice     { margin-left: 2em; }

ol.enumar      { list-style-type: decimal; }
ol.enumla      { list-style-type: lower-alpha; }
ol.enumlr      { list-style-type: lower-roman; }
ol.enumua      { list-style-type: upper-alpha; }
ol.enumur      { list-style-type: upper-roman; }


div.exampleInner pre { margin-left: 1em;
                       margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
                  margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
                   border-top-width: 4px;
                   border-top-style: double;
                   border-top-color: #d3d3d3;
                   border-bottom-width: 4px;
                   border-bottom-style: double;
                   border-bottom-color: #d3d3d3;
                   padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
                    margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css" /></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title"></a>Web Services Enumeration (WS-Enumeration)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 13 December 2011</h2><dl><dt>This version:</dt><dd>
   <a href="http://www.w3.org/TR/2011/REC-ws-enumeration-20111213">http://www.w3.org/TR/2011/REC-ws-enumeration-20111213
   </a>
  </dd><dt>Latest version:</dt><dd>
    <a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
   </a>
  </dd><dt>Previous version:</dt><dd>
   <a href="http://www.w3.org/TR/2011/PR-ws-enumeration-20110927">http://www.w3.org/TR/2011/PR-ws-enumeration-20110927
   </a>
  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p>Please refer to the <a href="http://www.w3.org/2002/ws/ra/errata/ws-enumeration-20111213-errata"><strong>errata</strong></a> for this document, which may
      include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-enumeration"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
    This specification describes a general SOAP-based protocol for
    enumerating a sequence of XML elements from a SOAP enabled information
    source.
   </p></div><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>
	    This section describes the status of this document at the time
	    of its publication. Other documents may supersede this document.
	    A list of current W3C publications and the latest revision of
	    this technical report can be found in the
	    <a href="http://www.w3.org/TR/">W3C technical reports index</a>
	    at http://www.w3.org/TR/.
	  </em></p><p>
	  This is the 13 December 2011 Recommendation of the <em>Web Services Enumeration (WS-Enumeration)</em> specification.
          It has been produced by the
          <a href="http://www.w3.org/2002/ws/ra/">Web
          Services Resource Access Working Group</a> (WG), which is part of the
          <a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
          Activity</a>.
        </p><p>
          The public is encouraged to send comments to the Working Group's public mailing list
          <a href="mailto:public-ws-resource-access-comments@w3.org">
          public-ws-resource-access-comments@w3.org</a>
          mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/">public
          archive</a>). See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage guidelines</a>.
        </p><p>No substantive changes were made as a result of the Proposed Recommendation phase (see also <a href="diff-ws-enu.html">diff</a>, <a href="http://www.w3.org/2002/ws/ra/test/scenario.html">test scenario</a> and <a href="http://www.w3.org/2002/ws/ra/test/testResults.html">implementation report</a>).</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>
	  This document was produced by a group operating under the
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
	  February 2004 W3C Patent Policy</a>. W3C maintains a
	  <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/43088/status">public
	  list of any patent disclosures</a> made in connection with the
	  deliverables of the group; that page also includes instructions for
	  disclosing a patent. An individual who has actual knowledge of a
	  patent which the individual believes contains
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
	  Claim(s)</a> must disclose the information in accordance with
	  <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
	  6 of the W3C Patent Policy</a>.
	</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
2 <a href="#intro">Introduction</a><br />
&nbsp;&nbsp;&nbsp;2.1 <a href="#reqs">Requirements</a><br />
3 <a href="#termsNotes">Notations and Terminology</a><br />
&nbsp;&nbsp;&nbsp;3.1 <a href="#conv">Notational Conventions</a><br />
&nbsp;&nbsp;&nbsp;3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br />
&nbsp;&nbsp;&nbsp;3.3 <a href="#terms">Terminology</a><br />
&nbsp;&nbsp;&nbsp;3.4 <a href="#compliance">Compliance</a><br />
&nbsp;&nbsp;&nbsp;3.5 <a href="#namespaces">XML Namespaces</a><br />
4 <a href="#EnumMsgs">Enumeration Messages</a><br />
&nbsp;&nbsp;&nbsp;4.1 <a href="#Enumerate">Enumerate</a><br />
&nbsp;&nbsp;&nbsp;4.2 <a href="#Renew">Renew</a><br />
&nbsp;&nbsp;&nbsp;4.3 <a href="#GetStatus">GetStatus</a><br />
&nbsp;&nbsp;&nbsp;4.4 <a href="#Release">Release</a><br />
&nbsp;&nbsp;&nbsp;4.5 <a href="#EnumerationEnd">EnumerationEnd</a><br />
5 <a href="#Faults">Faults</a><br />
&nbsp;&nbsp;&nbsp;5.1 <a href="#UnsupportedExpirationValue">UnsupportedExpirationValue</a><br />
&nbsp;&nbsp;&nbsp;5.2 <a href="#UnsupportedExpirationType">UnsupportedExpirationType</a><br />
&nbsp;&nbsp;&nbsp;5.3 <a href="#FilteringNotSupported">FilteringNotSupported</a><br />
&nbsp;&nbsp;&nbsp;5.4 <a href="#FilterDialectRequestedUnavailable">FilterDialectRequestedUnavailable</a><br />
&nbsp;&nbsp;&nbsp;5.5 <a href="#CannotProcessFilter">CannotProcessFilter</a><br />
&nbsp;&nbsp;&nbsp;5.6 <a href="#InvalidEnumerationContext">InvalidEnumerationContext</a><br />
&nbsp;&nbsp;&nbsp;5.7 <a href="#UnusableEPR">UnusableEPR</a><br />
&nbsp;&nbsp;&nbsp;5.8 <a href="#EndToNotSupported">EndToNotSupported</a><br />
&nbsp;&nbsp;&nbsp;5.9 <a href="#EmptyFilter">EmptyFilter</a><br />
&nbsp;&nbsp;&nbsp;5.10 <a href="#MaxItemsMustBeZero">MaxItemsMustBeZero</a><br />
6 <a href="#Security">Security Considerations</a><br />
&nbsp;&nbsp;&nbsp;6.1 <a href="#idp1655264">Creating Enumeration Contexts</a><br />
&nbsp;&nbsp;&nbsp;6.2 <a href="#idp1657072">Protecting Enumeration Contexts</a><br />
&nbsp;&nbsp;&nbsp;6.3 <a href="#idp1660016">Endpoint Verification</a><br />
7 <a href="#metadata">WS-Enumeration Metadata</a><br />
&nbsp;&nbsp;&nbsp;7.1 <a href="#idp1666400">Enumeration Assertion</a><br />
8 <a href="#acks">Acknowledgements</a><br />
9 <a href="#refs">References</a><br />
&nbsp;&nbsp;&nbsp;9.1 <a href="#idp1700272">Normative References</a><br />
&nbsp;&nbsp;&nbsp;9.2 <a href="#idp1754816">Informative References</a><br />
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br />
B <a href="#WSDL">WSDL</a><br />
C <a href="#actiontables">Action Tables</a><br />
D <a href="#changelog">Change Log</a><br />
</p></div><hr /><div class="body"><div class="div1">
<h2><a name="composable" id="composable"></a>1 Composable Architecture</h2><p>
    By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
    <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
    extensibility models, the Web service
    specifications (WS-*) are designed to be composed with each other
    to provide a rich set of tools for the Web
    services environment. This specification specifically relies on
    other Web service specifications to provide secure, reliable,
    and/or transacted message delivery and to express Web service and
    client policy.
   </p></div><div class="div1">
<h2><a name="intro" id="intro"></a>2 Introduction</h2><p>
    There are numerous applications for which a
    simple single-request/single-reply metaphor is insufficient for
    transferring large data sets over SOAP. Applications that do not
    fit into this simple paradigm include streaming, traversal, query,
    and enumeration.
   </p><p>
    This specification defines a simple SOAP-based
    protocol for enumeration that allows the data source to provide a
    session abstraction, called an enumeration context, to a consumer
    that represents a logical cursor through a sequence of data items.
    The consumer can then request XML element information items using
    this enumeration context over the span of one or more SOAP
    messages.
   </p><p>
    Somewhere, state MUST be maintained regarding
    the progress of the iteration. This state MAY be maintained between
    requests by the data source being enumerated or by the data
    consumer. WS-Enumeration allows the data source to decide, on a
    request-by-request basis, which party will be responsible for
    maintaining this state for the next request.
   </p><p>
    In its simplest form, WS-Enumeration defines an operation, Enumerate,
    used to establish the creation of an enumeration session or
    which allows a data source, in the context
    of a specific enumeration, to produce a sequence of XML elements in
    the body of a SOAP message. Each subsequent Enumerate operation returns
    the next N elements in the aggregate sequence.
   </p><p>
    A data source MAY provide a custom mechanism for
    starting a new enumeration. For instance, a data source that
    provides access to a SQL database can support a SELECT operation
    that performs a database query and uses an explicit database cursor
    to iterate through the returned rows. In general, however, it is
    simpler if all data sources support a single, standard operation to
    start an enumeration. This specification mandates
    that data sources MUST implement the Enumerate operation for starting a new
    enumeration of a data source.
    Each new enumeration results in a distinct enumeration context,
    each with its own logical cursor/position.
   </p><p>
    Note that different
    enumerations of the same data source can produce different results;
    this can happen even for two enumeration contexts created
    concurrently by a single consumer using identical Enumerate
    requests. The ordering or completeness of the enumeration
    is undefined; the returned data items represent a selection by the
    data source of items it wishes to present to that consumer at that
    time in that order, with no guarantee that every available item is
    returned or that the order in which items is returned has any
    semantic meaning whatsoever (of course, any specific data source
    can provide strong guarantees, if so desired). In particular,
    note that the very act of enumerating the contents of a
    data source can modify the contents of the data source; for
    instance, a queue might be represented as a data source such that
    items that are returned in a Enumerate response are removed from the
    queue.
   </p><div class="div2">
<h3><a name="reqs" id="reqs"></a>2.1 Requirements</h3><p>
     This specification intends to meet the following requirements:
    </p><ul><li><p>
       Support enumeration of data sources
       that cannot practically fit into a single SOAP
       message.
      </p></li><li><p>
       Support both server-side and
       client-side enumeration state maintenance.
      </p></li><li><p>
       Minimize additional mechanism
       beyond the current web service architecture.
      </p></li></ul></div></div><div class="div1">
<h2><a name="termsNotes" id="termsNotes"></a>3 Notations and Terminology</h2><p>
    This section specifies the notations,
    namespaces, and terminology used in this
    specification.
   </p><div class="div2">
<h3><a name="conv" id="conv"></a>3.1 Notational Conventions</h3><p>
     The keywords "MUST", "MUST NOT", "REQUIRED",
     "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
     and "OPTIONAL" in this document are to be interpreted as described
     in RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.
    </p><p>
     This specification uses the following syntax to
     define normative outlines for messages:
    </p><ul><li><p>
       The syntax appears as an XML
       instance, but values in italics indicate data types instead of
       values.
      </p></li><li><p>
       Characters are appended to elements
       and attributes to indicate cardinality:
      </p></li><li><p>
       "?" (0 or 1)
      </p></li><li><p>
       "*" (0 or more)
      </p></li><li><p>
       "+" (1 or more)
      </p></li><li><p>
       The character "|" is used to
       indicate a choice between alternatives.
      </p></li><li><p>
       The characters "(" and ")" are used to indicate that contained items
       are to be treated as a group with respect to cardinality or choice.
      </p></li><li><p>
       The characters "[" and "]" are used to call out references and
       property names.
      </p></li><li><p>
       Ellipsis (i.e. "...") indicate points of extensibility.
      </p></li><li><p>
       XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
       to indicate the namespace of the element being
       defined.
      </p></li></ul><p>
     In addition to Message Information Header properties
     <a href="#AddrCore">[WS-Addressing]</a>,
     this specification uses the following properties to define messages:
    </p><dl><dt class="label"> <b>[Headers]</b> </dt><dd><p> Unordered message headers. </p></dd><dt class="label"> <b>[Action]</b> </dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"> <b>[Body]</b> </dt><dd><p> A message body. </p></dd></dl><p>
     These properties bind to a SOAP Envelope as follows:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
  &lt;s:Header&gt;
    <b>[Headers]</b>
    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
    ...
  &lt;/s:Header&gt;
  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
&lt;/s:Envelope&gt;</pre></div></div><p>
     This specification can be used in terms of XML Information Set (Infoset)
     <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
     terminology. Valid Infoset for this specification is the one
     serializable in XML 1.0, hence the use of XML 1.0.
    </p><p>
     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.
    </p></div><div class="div2">
<h3><a name="extensions" id="extensions"></a>3.2 Considerations on the Use of Extensibility Points</h3><p>
     The elements defined in this specification MAY be extended at the
     points indicated by their outlines and schema. Implementations MAY
     add child elements and/or attributes at the indicated extension
     points but MUST NOT contradict the semantics of the parent and/or
     owner, respectively. If a receiver does not recognize an extension,
     the receiver SHOULD ignore that extension. Senders MAY indicate
     the presence of an extension that has to be understood through the use
     of a corresponding SOAP Header with a soap:mustUnderstand attribute
     with the value "1".
    </p><p>
     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
     specify how the extension that appears in the response correlates
     with that in the corresponding request.
    </p><p>
     Extension elements and attributes MUST NOT use the Web Services
     Enumeration namespace URI.
    </p></div><div class="div2">
<h3><a name="terms" id="terms"></a>3.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
        The Web service that is requesting the data
        enumeration from the data source
       </p></dd><dt class="label"> Data Source </dt><dd><p>
        A Web service that supports traversal using
        enumeration contexts via the Enumerate operation defined in this
        specification
       </p></dd><dt class="label"> Enumeration context </dt><dd><p>
        A session context that represents a specific
        traversal through a logical sequence of XML element information
        items using the Enumerate operation defined in this
        specification
       </p></dd></dl></div><div class="div2">
<h3><a name="compliance" id="compliance"></a>3.4 Compliance</h3><p>
     An implementation is not compliant with this specification if it fails to
     satisfy one or more of the MUST or REQUIRED level requirements defined
     herein.  A SOAP Node MUST NOT use the XML namespace identifier for this
     specification (listed in <a href="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP
     Envelopes unless it is compliant with this specification.
    </p><p>
     Normative text within this specification takes precedence over the XML
     Schema and WSDL descriptions, which in turn take precedence over
     outlines, which in turn take precedence over examples.
    </p><p>
     All messages defined by this specification MUST conform to the
     WS-Addressing specifications and be sent to a Web service that
     is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
    </p><p>
     Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
     MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
    </p><p>
     For any message defined by this specification, any OPTIONAL elements
     or attributes in the message MAY be used by senders of the message;
     however receivers of those messages MUST support those OPTIONAL
     elements and attributes, unless other behavior is explicitly defined
     by this specification.
    </p><p>
     Implementations are expected to support both UTF-8 and UTF-16 as
     described in XML 1.0.
    </p><p>
     Implementations of this specification MUST conform to the corrected
     version of WSDL as defined by the 'WSDL Correction' sections of WS-I
     Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
     <a href="#BP20">[BP20]</a>.
    </p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"></a>3.5 XML Namespaces</h3><p>
     The XML namespace URI that MUST be used by
     implementations of this specification is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-enu">http://www.w3.org/2011/03/ws-enu</a></pre></div></div><p>
     <a href="#xmlnamespaces">Table 3-1</a> lists XML namespaces that are used in
     this specification. The choice of any namespace prefix is arbitrary
     and not semantically significant.
    </p><a name="xmlnamespaces" id="xmlnamespaces"></a><table border="1"><caption>Table 3-1:
      Prefixes and XML namespaces used in this specification
     </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td>
        <a href="http://www.w3.org/2011/03/ws-enu">
         http://www.w3.org/2011/03/ws-enu
        </a>
       </td><td> This specification </td></tr><tr><td> s </td><td>
        <a href="http://www.w3.org/2003/05/soap-envelope">
         http://www.w3.org/2003/05/soap-envelope
        </a>
       </td><td> SOAP 1.2 <a href="#SOAP12">[SOAP12]</a> </td></tr><tr><td> s11 </td><td>
        <a href="http://schemas.xmlsoap.org/soap/envelope/">
         http://schemas.xmlsoap.org/soap/envelope/
        </a>
       </td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a> </td></tr><tr><td> wsa </td><td>
        <a href="http://www.w3.org/2005/08/addressing">
         http://www.w3.org/2005/08/addressing
        </a>
       </td><td> WS-Addressing <a href="#AddrCore">[WS-Addressing]</a> </td></tr><tr><td> wsp </td><td>
        <a href="http://www.w3.org/ns/ws-policy">
         http://www.w3.org/ns/ws-policy
        </a>
       </td><td> WS-Policy <a href="#wspolicy">[WS-Policy]</a> </td></tr><tr><td> xs </td><td>
        <a href="http://www.w3.org/2001/XMLSchema">
         http://www.w3.org/2001/XMLSchema
        </a>
       </td><td>
        XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
       </td></tr><tr><td> wsdl </td><td>
        <a href="http://schemas.xmlsoap.org/wsdl">
         http://schemas.xmlsoap.org/wsdl
        </a>
       </td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a> </td></tr></tbody></table><p>
     The working group intends to update the value of the Web Services
     Enumeration namespace URI each time a new version of this document is
     published until such time that the document reaches Candidate
     Recommendation status. Once it has reached Candidate Recommendation
     status, the working group intends to maintain the value of the
     Web Services Enumeration namespace URI that was assigned in the
     Candidate Recommendation unless significant changes are made that
     impact the implementation or break post-CR implementations of the
     specification. Also see
     <a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
      http://www.w3.org/2001/tag/doc/namespaceState.html
     </a> and
     <a href="http://www.w3.org/2005/07/13-nsuri">
      http://www.w3.org/2005/07/13-nsuri
     </a>.
    </p></div></div><div class="div1">
<h2><a name="EnumMsgs" id="EnumMsgs"></a>4 Enumeration Messages</h2><p>
    Enumeration contexts represent a specific
    traversal through a sequence of XML information items. A Enumerate
    operation can be used to establish an enumeration context from a
    data source. A subsequent Enumerate operation is used to fetch information
    items from a data source according to a specific enumeration context. A
    Release operation is used to tell a data source that the consumer
    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
    enumeration context from the data source by means of a Enumerate
    operation. The consumer then passes that XML data back to the data
    source in subsequent Enumerate requests. Optionally, the data source MAY
    return an updated enumeration context in the Enumerate response; when
    present, 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>
    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
    items is explicitly allowed; however, no further operations
    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
      Enumerate response)
     </p></li><li><p> Enumeration released </p></li><li><p> Enumeration expired </p></li><li><p>
      Enumeration context replaced in the response to another Enumerate request
     </p></li><li><p>
      Enumeration ended (i.e. as indicated via an EnumerationEnd message from
      data source)
     </p></li></ol><p>
    As the last item indicates, the data source MAY invalidate an
    enumeration context at any time.
   </p><p>
    When processing a Enumerate, 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 EnumerateResponse or RenewResponse.
   </p><p>
    Once a consumer determines that an enumeration context is invalid, it
    MUST NOT issue any more WS-Enumeration request messages referencing
    that enumeration context.
   </p><div class="div2">
<h3><a name="Enumerate" id="Enumerate"></a>4.1 Enumerate</h3><p>
     The Enumerate operation is initiated by sending a Enumerate request
     message to the data source.
     This operation MUST be supported by compliant data sources.
     The Enumerate request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/Enumerate

<b>[Body]</b>
  &lt;wsen:Enumerate ...&gt;
    ( &lt;wsen:NewContext ...&gt;
        &lt;wsen:EndTo&gt;<em>endpoint-reference</em>&lt;/wsen:EndTo&gt; ?
        &lt;wsen:Expires BestEffort="<em>xs:boolean</em>"? ...&gt;
          (<em>xs:dateTime</em> | <em>xs:duration</em>)
        &lt;/wsen:Expires&gt; ?
        &lt;wsen:Filter Dialect="<em>xs:anyURI</em>"?&gt; <em>xs:any</em> &lt;/wsen:Filter&gt; ?
        <em>xs:any</em>*
      &lt;/wsen:NewContext&gt; |
      &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt; )
    &lt;wsen:MaxTime&gt;<em>xs:duration</em>&lt;/wsen:MaxTime&gt; ?
    &lt;wsen:MaxItems&gt;<em>xs:long</em>&lt;/wsen:MaxItems&gt; ?
    &lt;wsen:MaxCharacters&gt;<em>xs:long</em>&lt;/wsen:MaxCharacters&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:Enumerate&gt;</pre></div></div><p>
     The following describes additional, normative
     constraints on the outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext </dt><dd><p>
        This OPTIONAL element contains the information necessary to create
        a new Enumeration.
        Note, a Enumerate request MUST have either a wsen:EnumerationContext
        element or a wsen:NewContext element.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:EndTo </dt><dd><p>
        This OPTIONAL element denotes where to send
        an EnumerationEnd message if the enumeration is terminated
        unexpectedly
        (see <a href="#EnumerationEnd"><b>4.5 EnumerationEnd</b></a>).
        If present, this element MUST
        be of type wsa:EndpointReferenceType. Default is to not send this
        message.  The endpoint to which the EndTo EPR
        refers MUST support the EnumerationEndPortType portType.
        Unless some mechanism is used to indicate otherwise, the messages
        sent to this endpoint MUST use the same version of SOAP that was
        used for the Enumerate message.
       </p><p>
        If the data source does not support the use of the EndTo EPR,
        the data source MUST generate a wsen:EndToNotSupported fault.
       </p><p>
        If included within the Enumerate request message, the
        wsen:EndTo SHOULD have some cursory validity checking performed before
        the Enumerate response is returned. While not all errors can be detected
        prior to sending a message to that EPR, some obvious ones can be
        detected.  For example, an unsupported transport specified within the
        wsa:Address IRI.
        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 data source
        MUST generate a wsen:UnusableEPR fault rather than returning the
        EnumerateResponse
        message.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Expires </dt><dd><p>
        This OPTIONAL element can be used by the consumer to indicate the
        expiration time of the requested enumeration.
        A value of PT0S indicates a request for an infinite expiration time
        (i.e. an enumeration that never expires).
       </p><p>
        The absence of the wsen:Expires element indicates that the expiration
        value will be chosen by the data source.
        This value is communicated via the wsen:GrantedExpires element
        (see below).
       </p><p>
        If the wsen:Expires element is present and the data source is not
        able to grant an expiration time that matches the specified value
        then it MUST generate a wsen:UnsupportedExpirationValue fault.
       </p><p>
        The value of the wsen:Expires element MAY be either a duration
        (xs:duration) or a specific time (xs:dateTime). Data sources
        MUST accept duration values and MAY
        accept specific time values. Upon receiving a request that
        contains specific time values, a data source
        that does not support such value types MUST fail the
        request and generate a wsen:UnsupportedExpirationType fault.
       </p><p>
        If a consumer chooses to use specific time values in a request,
        it is RECOMMENDED that these values include a time zone component.
        Specific time values that lack a time zone MUST be interpreted in
        the local time zone of the receiver.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Expires@BestEffort </dt><dd><p>
        This OPTIONAL attribute, when present with a value of 'true',
        indicates that the data source MUST grant an expiration time that
        is its best effort to match the requested
        expiration time. Default value of this attribute is "false" in
        which case the data source MUST grant the requested expiration time
        or fault the enumeration request as defined above.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter </dt><dd><p>
        This OPTIONAL element contains a Boolean
        predicate in some dialect (see <b>[<a href="#Dialect"> [Body]/wsen:Enumerate/wsen:NewContext/wsen:Filter/@Dialect </a>]</b>)
        that all items of
        interest MUST satisfy. The resultant enumeration context MUST NOT
        return items for which this predicate expression evaluates to
        the value false. If this element is absent, then the implied value
        is the expression true(), indicating that no filtering is
        desired.
       </p><p>
        If the data source does not support
        filtering, the request MUST fail, and the data source MUST generate
        a wsen:FilteringNotSupported fault.
       </p><p>
        If the data source supports filtering but
        cannot honor the requested filter dialect, the request MUST fail,
        and the data source MUST generate a
        wsen:FilterDialectRequestedUnavailable fault.
       </p><p>
        If the data source supports filtering and the
        requested dialect but cannot process the requested filter content,
        the request MUST fail, and the data source MUST generate a
        wsen:CannotProcessFilter fault.
       </p><p>
        It is possible for a Enumerate request to contain a filter that
        will never evaluate to true for the lifetime of the enumeration.
        If a data source detects this condition during the processing
        of the Enumerate request it MUST generate a
        wsen:EmptyFilter fault in response to the Enumerate request message.
        If, after the EnumerateResponse message has been sent, the
        data source determines that the filter will never evaluate to true
        for the lifetime of the enumeration, or if there is an error within
        the filter expression, the enumeration MUST be terminated. In this
        case if an EndTo was provided, then a EnumerationEnd message MUST
        be sent with a Reason value of
        "http://www.w3.org/2011/03/ws-evt/SourceCancelling".

       </p></dd><dt class="label"><a name="Dialect" id="Dialect"></a> <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter/@Dialect </dt><dd><p>
        Implied value is
        "http://www.w3.org/2011/03/ws-enu/Dialects/XPath10".
       </p><p>
        If filtering is supported, then support for the XPath 1.0 dialect
        (described below) is RECOMMENDED.
        Alternate filter dialects can be defined.
        Such dialect definitions MUST include sufficient information for
        proper application. For example, it would need to define the context
        (which data) over which the filter operates.
       </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter/@Dialect="<a href="http://www.w3.org/2011/03/ws-enu/Dialects/XPath10">
        http://www.w3.org/2011/03/ws-enu/Dialects/XPath10
       </a>
      </dt><dd><p>
        Value of <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter is
        an XPath <a href="#XPath1">[XPath1.0]</a>
        predicate expression (PredicateExpr); the context
        of the expression is:
       </p><ul><li><p>
          Context Node: any XML element that
          could be returned as a direct child of the wsen:Items
          element.
         </p></li><li><p>
          Context Position: 1.
         </p></li><li><p>
          Context Size: 1.
         </p></li><li><p>
          Variable Bindings: None.
         </p></li><li><p>
          Function Libraries: Core Function
          Library <a href="#XPath1">[XPath1.0]</a>.
         </p></li><li><p>
          Namespace Declarations: The
          [in-scope namespaces] property <a href="#XMLInfoset">[XML Infoset]</a>
          of <b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter.
         </p></li></ul><p>
        The namespace bindings are evaluated against any namespace
        declarations that are in scope where the XPath expression appears
        within the SOAP message.
        Note that the evaluation of expressions that rely on such context
        dependent bindings is fragile in the face of transformations that alter
        namespace prefixes. Such transformations might occur during the
        transmission, processing, storage, or retrieval of a request. Clients
        that wish to isolate expressions from the effects of any changes to the
        namespace prefixes in the containing SOAP message are advised to
        construct expressions in a manner that avoids the use of namespace
        prefixes. For example, use an expression such as
        "/*[local-name()='a' and namespace-uri()='http://www.example.com']"
        not "/ns1:a".
       </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter/@Dialect="<a href="http://www.w3.org/2011/03/ws-enu/Dialects/XPath20">
        http://www.w3.org/2011/03/ws-enu/Dialects/XPath20
       </a>
      </dt><dd><p>
        This filter dialect is the same as the XPath 1.0 filter dialect
        except that it uses <a href="#XPath2">[XPath2.0]</a> instead of XPath 1.0
        as the expression language.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:EnumerationContext </dt><dd><p>
        This OPTIONAL element contains the XML data
        that represents the current enumeration context.
        Note, a Enumerate request MUST have either a wsen:EnumerationContext
        element or a wsen:NewContext element.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:MaxTime </dt><dd><p>
        This OPTIONAL element (of type xs:duration)
        indicates the maximum amount of time the consumer is willing to
        allow the data source to assemble the Enumerate response. When this
        element is absent, the data source is NOT REQUIRED to limit the
        amount of time it takes to assemble the Enumerate
        response. The data source MUST recognize the wsen:MaxTime
        element. If no items
        are available prior to the request message's deadline,
        the data source MUST return an EnumerationResponse message
        that contains a wsen:Items element with no child elements present.
       </p><p>
        This is useful with data sources that
        accumulate items over time and package them into a single Enumerate
        response.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:MaxItems </dt><dd><p>
        This OPTIONAL element (of type xs:long)
        indicates the number of items (child elements of wsen:Items in the
        Enumerate response) the consumer is willing to accept. When this element
        is absent, its implied value is 1. Implementations MUST NOT return
        more than this number of items in the Enumerate response message.
        Implementations MAY return fewer than this number based on either
        the wsen:MaxTime timeout, the wsen:MaxCharacters size limit, or
        implementation-specific constraints.
       </p><p>
        Note that a value of zero MAY, along with a wsen:NewContext element,
        be used to create a new enumeration without retrieving any of
        the data items.
       </p><p>
        If the data source does not support returning items in response
        to a Enumerate request that also created a new enumeration, and the
        Enumerate request did not include a wsen:MaxItems with a
        value of zero, then the data source MUST generate a
        wsen:MaxItemsMustBeZero fault.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:Enumerate/wsen:MaxCharacters </dt><dd><p>
        This OPTIONAL element (of type xs:long)
        indicates the maximum size of the returned items, in Unicode
        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 Enumerate response.
        Implementations MUST NOT
        return a Enumerate response message whose wsen:Items element, and
        all of its children, is larger than MaxCharacters.
        Implementations MAY return a smaller message
        based on the wsen:MaxTime timeout, the wsen:MaxItems limit, or
        implementation-specific constraints.
       </p><p>
        Even if a Enumerate request contains a
        MaxCharacters element, the consumer MUST be prepared to receive a
        Enumerate response that contains more data characters than specified, as
        XML canonicalization or alternate XML serialization algorithms can
        change the size of the representation.
       </p><p>
        When compiling the list of items to return, if the next item would
        cause the wsen:Items array to be larger than the MaxCharacters
        value and the wsen:Items array is not empty then the data source
        MUST return the current list of items back to the client, saving
        that next item for a subsequent enumerate request. If, however,
        the wsen:Items array is empty the data source MUST skip the item
        and MUST NOT return it as part of the enumeration.
       </p></dd></dl><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p><p>
     Upon successful processing of a Enumerate request
     message, a data source MUST return a Enumerate response
     message of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/EnumerateResponse

<b>[Body]</b>
  &lt;wsen:EnumerateResponse ...&gt;
    &lt;wsen:GrantedExpires ...&gt;
      (<em>xs:dateTime</em> | <em>xs:duration</em>)
    &lt;/wsen:GrantedExpires&gt;
    &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt; ?
    &lt;wsen:Items Reason="<em>xs:anyURI</em>"?&gt;
      &lt;xs:any&gt; enumeration-specific element &lt;/xs:any&gt; *
    &lt;/wsen:Items&gt; ?
    &lt;wsen:EndOfSequence/&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:EnumerateResponse&gt;</pre></div></div><p>
     The following describes additional, normative
     constraints on the outline listed above:
    </p><dl><dt class="label"> <b>[Body]</b>/wsen:EnumerateResponse/wsen:GrantedExpires </dt><dd><p>
        This element is the expiration time assigned by the data source. The
        expiration time MAY be either a specific time or a duration
        but MUST be of the same type as the wsen:Expires element of
        the corresponding request. If the corresponding request
        did not contain a wsen:Expires element, this element MUST be
        a duration (xs:duration).
       </p><p>
        When expressed as a duration, the wse:GrantedExpires element
        designates the amount of time remaining on this enumeration
        as measured from the moment the request message was processed.
        Although this specification cannot dictate when, during the
        processing of a request message a enumeration's remaining time
        is determined, the data source MUST measure the expiration
        duration from  a time that is at or before the transmission of
        the response message.
       </p><p>
        A wsen:GrantedExpires value of PT0S indicates that the enumeration will
        never expire.
        It will terminate when the end of the
        enumeration is reached, or if the consumer sends a Release request,
        or by the data source at any time for reasons such as connection
        termination, resource constraints, or system
        shut-down.
       </p><p>
        Note that a wsen:GrantedExpires element MUST only appear in a
        EnumerateResponse message if the corresponding Enumerate request
        message included a wsen:NewContext element.
       </p></dd><dt class="label">
       <b>[Body]</b>/wsen:EnumerateResponse/wsen:EnumerationContext
      </dt><dd><p>
        The OPTIONAL EnumerationContext element, if
        present, contains a XML representation of the
        enumeration context. The consumer MUST replace the prior
        representation, if any, with the contents of this element.
       </p></dd><dt class="label">
       <b>[Body]</b>/wsen:EnumerateResponse/wsen:Items/<em>xs:any</em>
      </dt><dd><p>
        The OPTIONAL Items element contains zero or
        more enumeration-specific elements, one for each item being
        returned.
       </p></dd><dt class="label">
       <b>[Body]</b>/wsen:EnumerateResponse/wsen:Items/@Reason
      </dt><dd><p>
        Implied value is "http://www.w3.org/2011/03/ws-enu/TimedOut".
       </p><p>
        The OPTIONAL Reason attribute indicates the reason that the
        wsen:Items element has no child elements.  Alternate Reason
        values can be defined. The Reason attribute MUST NOT be present
        if the wsen:Items element has one or more child elements.
       </p></dd><dt class="label">
       <b>[Body]</b>/wsen:EnumerateResponse/wsen:Items/@Reason="http://www.w3.org/2011/03/ws-enu/TimedOut"
      </dt><dd><p>
        This value MUST be used if no items are available prior to the
        Enumeration request message's deadline.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:EnumerateResponse/wsen:EndOfSequence </dt><dd><p>
        This OPTIONAL element indicates that no more
        items 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
     if items are returned and the sequence is exhausted. Similarly,
     wsen:EnumerationContext and wsen:EndOfSequence MUST NOT both
     appear; neither can appear, or one without the other, but not both
     in the same EnumerateResponse.
    </p><p>
     <a href="#enumReq">Example 4-1</a> lists a sample Enumerate request that
     establishes a new context.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="enumReq" id="enumReq"></a>Example 4-1: Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03)    xmlns:wsen="http://www.w3.org/2011/03/ws-enu"&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/Enumerate
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:MessageID&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:MessageID&gt;
(11)     &lt;wsa:To&gt;http://www.example.com/relayAgent/enum19&lt;/wsa:To&gt;
(12)     &lt;wsa:ReplyTo&gt;
(13)       &lt;wsa:Address&gt;
(14)         http://www.w3.org/2005/08/addressing/anonymous
(15)       &lt;/wsa:Address&gt;
(16)     &lt;/wsa:ReplyTo&gt;
(17)   &lt;/s:Header&gt;
(18)   &lt;s:Body&gt;
(19)     &lt;wsen:Enumerate&gt;
(20)       &lt;wsen:NewContext&gt;
(21)         &lt;wsen:Expires&gt; PT10M &lt;/wsen:Expires&gt;
(22)       &lt;/wsen:NewContext&gt;
(23)       &lt;wsen:MaxItems&gt; 0 &lt;/wsen:MaxItems&gt;
(24)     &lt;/wsen:Enumerate&gt;
(25)   &lt;/s:Body&gt;
(26) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#enumReq">Example 4-1</a> indicate this message
     is a Enumerate request and that the data source is expected to
     respond with a Enumerate response message. The wsen:Expires
     element on line (21) indicates that the consumer would like an
     enumeration context that will be good for 10 minutes.
     No wsen:Filter element is present, so the resultant
     enumeration context is expected to return all available
     items. Line (23) indicates that the Enumerate response
     is not to include any items from the enumeration - this operation
     is just estalishing the enumeration context.
    </p><p>
     <a href="#enumRes">Example 4-2</a> lists a response to the request in
     <a href="#enumReq">Example 4-1</a>.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="enumRes" id="enumRes"></a>Example 4-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
(02)     xmlns:wsen='http://www.w3.org/2011/03/ws-enu'
(03)     xmlns:wsa='http://www.w3.org/2005/08/addressing'&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/EnumerateResponse
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:RelatesTo&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:RelatesTo&gt;
(11)     &lt;wsa:To&gt;
(12)       http://www.w3.org/2005/08/addressing/anonymous
(13)     &lt;wsa:To&gt;
(14)   &lt;/s:Header&gt;
(15)   &lt;s:Body&gt;
(16)     &lt;wsen:EnumerateResponse&gt;
(17)       &lt;wsen:GrantedExpires&gt; PT10M &lt;/wsen:GrantedExpires&gt;
(18)       &lt;wsen:EnumerationContext&gt;
(19)         123
(20)       &lt;/wsen:EnumerationContext&gt;
(21)     &lt;/wsen:EnumerateResponse&gt;
(22)    &lt;/s:Body&gt;
(23) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#enumRes">Example 4-2</a> indicate this message
     is a Enumerate response message. Line (17) indicates that the data
     source has created an enumeration context with a lifetime
     of 10 minutes. Lines (18-20) are the XML representation of the
     enumeration context that supports the Enumerate operation defined
     below.
    </p><p>
     <a href="#EnumerateReq">Example 4-3</a> lists a Enumerate request that uses the
     enumeration context established in the previous example.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="EnumerateReq" id="EnumerateReq"></a>Example 4-3: Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03)    xmlns:wsen="http://www.w3.org/2011/03/ws-enu"&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/Enumerate
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:MessageID&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:MessageID&gt;
(11)     &lt;wsa:To&gt;http://www.example.com/relayAgent&lt;/wsa:To&gt;
(12)     &lt;wsa:ReplyTo&gt;
(13)       &lt;wsa:Address&gt;
(14)         http://www.w3.org/2005/08/addressing/anonymous
(15)       &lt;/wsa:Address&gt;
(16)     &lt;/wsa:ReplyTo&gt;
(17)   &lt;/s:Header&gt;
(18)   &lt;s:Body&gt;
(19)     &lt;wsen:Enumerate&gt;
(20)       &lt;wsen:EnumerationContext&gt;123&lt;/wsen:EnumerationContext&gt;
(21)       &lt;wsen:MaxTime&gt;P30S&lt;/wsen:MaxTime&gt;
(22)       &lt;wsen:MaxItems&gt;10&lt;/wsen:MaxItems&gt;
(23)     &lt;/wsen:Enumerate&gt;
(24)   &lt;/s:Body&gt;
(25) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#EnumerateReq">Example 4-3</a> indicate this message
     is a Enumerate request and that the data source is expected to respond
     with a Enumerate response message. Line (21) indicates that the response
     message SHOULD be generated no more than 30 seconds after receipt
     of the Enumerate request message. Line (22) indicates that no more than
     10 items can be returned in the body of the Enumerate response
     message.
    </p><p>
     <a href="#EnumerateRes">Example 4-4</a> lists a response to the request in
     <a href="#EnumerateReq">Example 4-3</a>.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="EnumerateRes" id="EnumerateRes"></a>Example 4-4: Response to Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02)     xmlns:wsen="http://www.w3.org/2011/03/ws-enu"
(03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/EnumerateResponse
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:RelatesTo&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:RelatesTo&gt;
(11)     &lt;wsa:To&gt;
(12)       http://www.w3.org/2005/08/addressing/anonymous
(13)     &lt;wsa:To&gt;
(14)   &lt;/s:Header&gt;
(15)   &lt;s:Body&gt;
(16)     &lt;wsen:EnumerateResponse&gt;
(17)       &lt;wsen:Items xmlns:xx="http://fabrikam123.example.com/schema/log"&gt;
(18)         &lt;xx:LogEntry id="1"&gt;System booted&lt;/xx:LogEntry&gt;
(19)         &lt;xx:LogEntry id="2"&gt;AppX started&lt;/xx:LogEntry&gt;
(20)         &lt;xx:LogEntry id="3"&gt;John Smith logged on&lt;/xx:LogEntry&gt;
(21)         &lt;xx:LogEntry id="4"&gt;AppY started&lt;/xx:LogEntry&gt;
(22)         &lt;xx:LogEntry id="5"&gt;AppX crashed&lt;/xx:LogEntry&gt;
(23)       &lt;/wsen:Items&gt;
(24)       &lt;wsen:EndOfSequence/&gt;
(25)      &lt;/wsen:EnumerateResponse&gt;
(26)    &lt;/s:Body&gt;
(27) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#EnumerateRes">Example 4-4</a> indicate this message
     is a Enumerate response message. Lines (18-22) are the five items
     returned by this Enumerate request. The presence of a wsen:EndOfSequence
     element (line (24)) indicates that no more items are available
     and that the enumeration context is now invalid.
    </p></div><div class="div2">
<h3><a name="Renew" id="Renew"></a>4.2 Renew</h3><p>
     To update, or renew, the expiration for an enumeration, a Renew
     request message is sent to the data source.
     This operation MUST be supported by compliant data sources.
     The Renew request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/Renew

<b>[Body]</b>
  &lt;wsen:Renew ...&gt;
    &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt;
    &lt;wsen:Expires BestEffort="<em>xs:boolean</em>"? ...&gt;
      (<em>xs:dateTime</em> | <em>xs:duration</em>)
    &lt;/wsen:Expires&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:Renew&gt;</pre></div></div><p>
     Components of the outline listed above are
     additionally constrained as for a request to create an enumeration
     (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>) with the following
     addition(s):
    </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></dd></dl><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p><p>
     If the data source accepts a request to renew an
     enumeration, it MUST reply with a response of the following
     form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/RenewResponse

<b>[Body]</b>
  &lt;wsen:RenewResponse ...&gt;
    &lt;wsen:GrantedExpires ...&gt;
      (<em>xs:dateTime</em> | <em>xs:duration</em>)
    &lt;/wsen:GrantedExpires&gt; ?
    &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:RenewResponse&gt;</pre></div></div><p>
     Components of the outline listed above are
     constrained as for a response to a Enumerate request
     (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>) with the following addition:
    </p><dl><dt class="label">
       <b>[Body]</b>/wsen:RenewResponse/wsen:EnumerationContext
      </dt><dd><p>
        This element is OPTIONAL in this response.
       </p></dd></dl><p>
     If the data source chooses not to renew this enumeration, the request
     MUST fail, and the data source MUST generate a SOAP 1.1 Server fault
     or a SOAP 1.2 Receiver fault indicating that the renewal was not
     accepted.
    </p><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p></div><div class="div2">
<h3><a name="GetStatus" id="GetStatus"></a>4.3 GetStatus</h3><p>
     To get the status of an enumeration, the
     consumer sends a GetStatus request message to the data source.
     This operation MUST be supported by compliant data sources.
     The message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/GetStatus

<b>[Body]</b>
  &lt;wsen:GetStatus ...&gt;
    &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt;
    <em>xs:any</em>*
  &lt;/wsen:GetStatus&gt;</pre></div></div><p>
     Components of the outline listed above are
     additionally constrained as for a request to renew an enumeration
     (see <a href="#Renew"><b>4.2 Renew</b></a>). Other components of the outline above are
     not further constrained by this specification.
    </p><p>
     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/2011/03/ws-enu/GetStatusResponse

<b>[Body]</b>
  &lt;wsen:GetStatusResponse ...&gt;
    &lt;wsen:GrantedExpires ...&gt;
      (<em>xs:dateTime</em> | <em>xs:duration</em>)
    &lt;/wsen:GrantedExpires&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:GetStatusResponse&gt;</pre></div></div><p>
     Components of the outline listed above are
     constrained as for a response to a renew request
     (see <a href="#Renew"><b>4.2 Renew</b></a>). Other components of the outline above are
     not further constrained by this specification.
    </p><p>
     This operation is safe; it will not result in any side effect
     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">
<h3><a name="Release" id="Release"></a>4.4 Release</h3><p>
     The Release operation is initiated by sending a
     Release request message to the data source.
     This operation MUST be supported by compliant data sources.
     The Release request message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/Release

<b>[Body]</b>
  &lt;wsen:Release ...&gt;
    &lt;wsen:EnumerationContext ...&gt;...&lt;/wsen:EnumerationContext&gt;
    <em>xs:any</em>*
  &lt;/wsen:Release&gt;</pre></div></div><p>
     The following describes additional, normative
     constraints on the outline listed above:
    </p><dl><dt class="label">
       <b>[Body]</b>/wsen:Release/wsen:EnumerationContext
      </dt><dd><p>
        This REQUIRED element contains the XML data
        that represents the enumeration context being
        abandoned.
       </p></dd></dl><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p><p>
     Upon successful processing of a Release request
     message, a data source MUST return a Release response
     message of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/ReleaseResponse

<b>[Body]</b>
  &lt;wsen:ReleaseResponse ...&gt;
    <em>xs:any</em>*
  &lt;/wsen:ReleaseResponse&gt;</pre></div></div><p>
     <a href="#releaseReq">Example 4-5</a> lists a Release request.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="releaseReq" id="releaseReq"></a>Example 4-5: Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03)    xmlns:wsen="http://www.w3.org/2011/03/ws-enu"&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/Release
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:MessageID&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:MessageID&gt;
(11)     &lt;wsa:To&gt;http://www.example.com/relayAgent&lt;/wsa:To&gt;
(12)     &lt;wsa:ReplyTo&gt;
(13)       &lt;wsa:Address&gt;
(14)         http://www.w3.org/2005/08/addressing/anonymous
(15)       &lt;/wsa:Address&gt;
(16)     &lt;/wsa:ReplyTo&gt;
(17)   &lt;/s:Header&gt;
(18)   &lt;s:Body&gt;
(19)     &lt;wsen:Release&gt;
(20)       &lt;wsen:EnumerationContext&gt;123&lt;/wsen:EnumerationContext&gt;
(21)     &lt;/wsen:Release&gt;
(22)   &lt;/s:Body&gt;
(23) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#releaseReq">Example 4-5</a> indicate this message
     is a Release request.
     Line (20) identifies the enumeration context to be released.
    </p><p>
     <a href="#releaseRes">Example 4-6</a> lists a response to the request in
     <a href="#releaseReq">Example 4-5</a>.
    </p><div class="exampleOuter">
<div class="exampleHeader"><a name="releaseRes" id="releaseRes"></a>Example 4-6: Response to Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02)     xmlns:wsen="http://www.w3.org/2011/03/ws-enu"
(03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"&gt;
(04)   &lt;s:Header&gt;
(05)     &lt;wsa:Action&gt;
(06)       http://www.w3.org/2011/03/ws-enu/ReleaseResponse
(07)     &lt;/wsa:Action&gt;
(08)     &lt;wsa:RelatesTo&gt;
(09)       urn:uuid:e7c5726b-de29-4313-b4d4-b3425b200839
(10)     &lt;/wsa:RelatesTo&gt;
(11)     &lt;wsa:To&gt;
(12)       http://www.w3.org/2005/08/addressing/anonymous
(13)     &lt;wsa:To&gt;
(14)   &lt;/s:Header&gt;
(15)   &lt;s:Body&gt;
(16)     &lt;wsen:ReleaseResponse/&gt;
(17)   &lt;/s:Body&gt;
(18) &lt;/s:Envelope&gt;</pre></div></div><p>
     Lines (05-07) in <a href="#releaseRes">Example 4-6</a> indicate this message
     is a Release response message.
    </p></div><div class="div2">
<h3><a name="EnumerationEnd" id="EnumerationEnd"></a>4.5 EnumerationEnd</h3><p>
     If the data source terminates an enumeration unexpectedly, and it
     supports the use of the EndTo EPR, and the EndTo EPR was present in the
     Enumerate message for that enumeration (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>),
     the EnumerationEnd message MUST be sent to the endpoint reference
     indicated by that EPR.
    </p><p>
     Note, a enumeration context expiring as expected is not considered to
     be an unexpected termination, therefore a EnumerationEnd message MUST NOT
     be sent in this case.
    </p><p>
     The message MUST be of the following form:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
  http://www.w3.org/2011/03/ws-enu/EnumerationEnd

<b>[Body]</b>
  &lt;wsen:EnumerationEnd ...&gt;
    &lt;wsen:Code&gt;
      ( http://www.w3.org/2011/03/ws-enu/SourceShuttingDown |
        http://www.w3.org/2011/03/ws-enu/SourceCancelling |
        <em>xs:anyURI</em> )
    &lt;/wsen:Code&gt;
    &lt;wsen:Reason xml:lang="<em>language identifier</em>" &gt;
      <em>xs:string</em>
    &lt;/wsen:Reason&gt; ?
    <em>xs:any</em>*
  &lt;/wsen:EnumerationEnd&gt;</pre></div></div><p>
     The following describes additional, normative
     constraints on the outline listed above:
    </p><dl><dt class="label">
       <b>[Body]</b>/wsen:EnumerationEnd/wsen:Code =
       "http://www.w3.org/2011/03/ws-enu/SourceShuttingDown"
      </dt><dd><p>
        This value MUST be used if the data source
        terminated the enumeration because the source is being shut down in
        a controlled manner; that is, if the data source is being shut down
        but has the opportunity to send an EnumerationEnd message before it
        exits.
       </p></dd><dt class="label">
       <b>[Body]</b>/wsen:EnumerationEnd/wsen:Code =
       "http://www.w3.org/2011/03/ws-enu/SourceCancelling"
      </dt><dd><p>
        This value MUST be used if the data source
        terminated the enumeration for some other reason before it
        expired.
       </p></dd><dt class="label"> <b>[Body]</b>/wsen:EnumerationEnd/wsen:Reason </dt><dd><p>
        This OPTIONAL element contains text, in the
        language specified by the @xml:lang attribute, describing the
        reason for the unexpected enumeration termination.
       </p></dd></dl><p>
     Other components of the outline above are not
     further constrained by this specification.
    </p></div></div><div class="div1">
<h2><a name="Faults" id="Faults"></a>5 Faults</h2><p>
    All fault messages defined in this specification MUST be sent
    according to the rules and usage described in
    <a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
    Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
    The <b>[Action]</b> property below MUST be used for faults
    defined in this specification:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-enu/fault">http://www.w3.org/2011/03/ws-enu/fault</a></pre></div></div><p>
    The definitions of faults in this section use the following properties:
   </p><p>
    <b>[Code]</b> The fault code.<br />
    <b>[Subcode]</b> The fault subcode.<br />
    <b>[Reason]</b> The English language reason element.<br />
    <b>[Detail]</b> The detail element. If absent, no detail element
    is defined for the fault.<br />
   </p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s12:Body&gt;
    &lt;s12:Fault&gt;
      &lt;s12:Code&gt;
        &lt;s12:Value&gt;<b>[Code]</b>&lt;/s12:Value&gt;
        &lt;s12:Subcode&gt;
          &lt;s12:Value&gt;<b>[Subcode]</b>&lt;/s12:Value&gt;
        &lt;/s12:Subcode&gt;
      &lt;/s12:Code&gt;
      &lt;s12:Reason&gt;
        &lt;s12:Text xml:lang="en"&gt;<b>[Reason]</b>&lt;/s12:Text&gt;
      &lt;/s12:Reason&gt;
      &lt;s12:Detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/s12:Detail&gt;
    &lt;/s12:Fault&gt;
  &lt;/s12:Body&gt;
&lt;/s12:Envelope&gt;</pre></div></div><p>The properties bind to a SOAP 1.1 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s11:Envelope&gt;
  &lt;s12:Header&gt;
    &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
    &lt;!-- Headers elided for brevity. --&gt;
  &lt;/s12:Header&gt;
  &lt;s11:Body&gt;
    &lt;s11:Fault&gt;
      &lt;faultcode&gt;<b>[Subcode]</b>&lt;/faultcode&gt;
      &lt;faultstring xml:lang="en"&gt;<b>[Reason]</b>&lt;/faultstring&gt;
      &lt;detail&gt;
        <b>[Detail]</b>
        ...
      &lt;/detail&gt;
    &lt;/s11:Fault&gt;
  &lt;/s11:Body&gt;
&lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
<h3><a name="UnsupportedExpirationValue" id="UnsupportedExpirationValue"></a>5.1 UnsupportedExpirationValue</h3><p>
     This fault MUST be generated when a request specifies an
     expiration that is not within the min/max range.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:UnsupportedExpirationValue </td></tr><tr><td> <b>[Reason]</b> </td><td>
        The expiration time requested is not within the min/max range.
       </td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"></a>5.2 UnsupportedExpirationType</h3><p>
     This fault MUST be generated when a request specifies an
     expiration time and the data source is only capable of accepting
     expiration durations; for instance, if the data source does not
     have access to absolute time.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:UnsupportedExpirationType </td></tr><tr><td> <b>[Reason]</b> </td><td> Only expiration durations are supported.  </td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div><div class="div2">
<h3><a name="FilteringNotSupported" id="FilteringNotSupported"></a>5.3 FilteringNotSupported</h3><p>
     This fault MUST generated when the data source does not support filters.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:FilteringNotSupported </td></tr><tr><td> <b>[Reason]</b> </td><td>
        Filtering not supported.
       </td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div><div class="div2">
<h3><a name="FilterDialectRequestedUnavailable" id="FilterDialectRequestedUnavailable"></a>5.4 FilterDialectRequestedUnavailable</h3><p>
     This fault MUST be generated when the data source does not support
     the requested filter dialect.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:FilterDialectRequestedUnavailable </td></tr><tr><td> <b>[Reason]</b> </td><td>
        Filter dialect requested unavailable.
       </td></tr><tr><td> <b>[Detail]</b> </td><td>
        &lt;wsen:SupportedDialect&gt; +
        <br />
        <em>OPTIONAL; repeating; one per filter dialect supported by the
        receiver</em>
       </td></tr></tbody></table></div><div class="div2">
<h3><a name="CannotProcessFilter" id="CannotProcessFilter"></a>5.5 CannotProcessFilter</h3><p>
     This fault MUST be generated when the data source can not process the
     filter content.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:CannotProcessFilter </td></tr><tr><td> <b>[Reason]</b> </td><td>
        Cannot filter as requested.
       </td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div><div class="div2">
<h3><a name="InvalidEnumerationContext" id="InvalidEnumerationContext"></a>5.6 InvalidEnumerationContext</h3><p>
     This fault MUST be generated when the enumeration context is invalid.
    </p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Receiver </td></tr><tr><td> <b>[Subcode]</b> </td><td> wsen:InvalidEnumerationContext </td></tr><tr><td> <b>[Reason]</b> </td><td>
        <em>
         Text explaining why the enumeration context is no longer valid, or
        </em>
        "Invalid enumeration context"
        <em>
         if no additional information is available.
        </em>
       </td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div><div class="div2">
<h3><a name="UnusableEPR" id="UnusableEPR"></a>5.7 UnusableEPR</h3><p>
     This fault MUST be generated when a data source detects
     that the wsen:EndTo EPR is unusable.
    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:EndTo EPR is unusable.</td></tr><tr><td><b>[Detail]</b></td><td>
        <em> Details as to why the EPR is unusable. </em>
       </td></tr></tbody></table></div><div class="div2">
<h3><a name="EndToNotSupported" id="EndToNotSupported"></a>5.8 EndToNotSupported</h3><p>
     This fault MUST be generated by a data source that does not support
     /wsen:Enumerate/wsen:NewContext/wsen:EndTo semantics, in response to
     a Enumerate request that contains a wsen:EndTo element.
    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wsen:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
        <em>none</em>
       </td></tr></tbody></table></div><div class="div2">
<h3><a name="EmptyFilter" id="EmptyFilter"></a>5.9 EmptyFilter</h3><p>
     This fault MUST be generated when a data source detects a
     Enumerate request containing a filter that, for whatever
     reason, will never evaluate to true.
    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:Filter would result in zero data items.</td></tr><tr><td><b>[Detail]</b></td><td>
        <em> The wsen:Filter value. </em>
       </td></tr></tbody></table></div><div class="div2">
<h3><a name="MaxItemsMustBeZero" id="MaxItemsMustBeZero"></a>5.10 MaxItemsMustBeZero</h3><p>
     This fault MUST be generated by a data source that does not support
     returning items in a Enumerate response and the Enumerate request
     did not include a wsen:MaxItems with a value of zero.
    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:MaxItemsMustBeZero</td></tr><tr><td><b>[Reason]</b></td><td>wsen:MaxItems must be zero when creating a new enumeration.</td></tr><tr><td><b>[Detail]</b></td><td>
        <em>none</em>
       </td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security" id="Security"></a>6 Security Considerations</h2><p>
    This specification considers two sets of security requirements, those
    of the applications that use the WS-Enumeration protocol and those of
    the protocol itself.
   </p><p>
    This specification makes no assumptions about the security requirements
    of the applications that use WS-Enumeration. However, once those
    requirements have been satisfied within a given operational context,
    the addition of WS-Enumeration to this operational context can not
    undermine the fulfillment of those requirements; the use of
    WS-Enumeration SHOULD NOT create additional attack vectors within
    an otherwise secure system.
   </p><p>
    The material below is not a "check list". There are many other security
    concerns that need to be considered when implementing or using this
    protocol. Implementers and users of this protocol are urged to perform
    a security analysis to determine their particular threat profile and
    the appropriate responses to those threats.
   </p><div class="div2">
<h3><a name="idp1655264" id="idp1655264"></a>6.1 Creating Enumeration Contexts</h3><p>
     An enumeration represents a logical cursor through a sequence of
     data items. If the information in these items is sensitive, it is
     advisable to for Data Sources to authenticate and authorize Consumers
     as part of the processing of the Enumerate request. Note that a
     Data Source might authorize retrievals on a per-item basis after the
     enumeration has been created. This might be necessary in cases where
     the sensitivity of the information requested might not be known at
     the time the Enumerate request is processed or varies during the
     lifetime of the enumeration.
    </p></div><div class="div2">
<h3><a name="idp1657072" id="idp1657072"></a>6.2 Protecting Enumeration Contexts</h3><p>
     Once created, it is advisable to treat Enumeration Contexts as
     protected resources. Renew, GetStatus, and Release requests ought to
     be authenticated and authorized (for example, the identity of the
     requester ought to be checked against the identity of the entity
     that performed the original Enumerate request). Likewise
     EnumerationEnd messages ought to be authenticated and authorized
     (for example, the identity of the sender ought to be checked against
     the identity the entity that sent the original EnumerateResponse message).
     Note that authentication and authorization policies (i.e. the rules
     that define which entities are allowed to perform which requests and
     the mechanisms by which the identities of these entities are
     discovered and verified) are particular to individual deployments.
    </p><p>
     Enumeration Contexts are also sensitive because of the way they are
     used to maintain or reference the state of active Enumerations.
     Attackers able to snoop or guess the value of an Enumeration Context
     could use this information to Enumerate data items in that Enumeration.
     To defend against the misuse of snooped/guessed Enumeration Contexts,
     Data Sources are advised to authenticate and authorize clients
     sending Enumerate requests.
    </p></div><div class="div2">
<h3><a name="idp1660016" id="idp1660016"></a>6.3 Endpoint Verification</h3><p>
     Data Source implementations that perform validity checks on the
     EndTo EPR used in the Enumerate request are advised that such checks
     can be misused to obtain information about a target network. For
     example, suppose a Data Source implementation verifies the address
     of EndTo EPRs by attempting to create a connection to this EPR's
     address and faulting the Enumerate request if a connection cannot
     be created. When deployed within a DMZ, such a Data Source could be
     exploited by a malicious Consumer to probe for other, non-visible
     hosts by guessing target addresses and using them in Enumerate requests.
     Note that, even if the returned fault does not provide connection
     information, the time the Data Source spends processing the
     Enumerate request might betray the existence or non-existence of a
     host at the target address.
    </p><p>
     Implementations that perform validity checks on the EndTo EPR are
     advised to provide a means to disable such checks in environments
     where these types of attacks are an issue.
    </p></div></div><div class="div1">
<h2><a name="metadata" id="metadata"></a>7 WS-Enumeration Metadata</h2><p>
    An endpoint MAY indicate its support of WS-Enumeration, or its features,
    by including the WS-Enumeration DataSource Policy assertion within its
    WSDL. By
    doing so the endpoint is indicating that the corresponding WS-Enumeration
    operations are supported by that endpoint even though they are implicit
    and do not explicitly appear in its WSDL
    (i.e. the WS-Enumeration operations do not appear in the WSDL that MAY
    be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
   </p><p>
    The WS-Enumeration WSDL containing the operations indicated by the
    Enumeration Assertion MAY be exposed by including the WSDL as a child
    of the DataSource Policy assertion or by including a reference to it
    using the mex:Location or mex:Reference element (as described in
    WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
   </p><p>
    This WS-Enumeration WSDL can be annotated to indicate any endpoint
    specific metadata that might be needed by clients interacting with
    the WS-Enumeration operations.   For example, the WSDL MAY
    have policy assertions
    that indicate a particular security mechanism used to protect
    the WS-Enumeration operations supported by this endpoint.
   </p><div class="div2">
<h3><a name="idp1666400" id="idp1666400"></a>7.1 Enumeration Assertion</h3><p>
     Services indicate support for the WS-Enumeration's definition of a
     data source through the use of the Web Services
     Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
     Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
    </p><p>
     This specification defines a policy assertion (wsen:DataSource).
     The normative outline of this assertion is:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsen:DataSource ...&gt;
  &lt;wsen:FilterDialect URI="<em>xs:anyURI</em>" ...&gt;
    <em>xs:any</em>*
  &lt;/wsen:FilterDialect&gt; *
  &lt;wsen:DateTimeSupported .../&gt; ?
  &lt;wsen:Expires min="<em>xs:duration</em>"? max="<em>xs:duration</em>"? .../&gt; ?
  &lt;wsen:MaxTime ...&gt; <em>xs:duration</em> &lt;/wsen:MaxTime&gt; ?
  &lt;wsen:MaxItems ...&gt; <em>xs:long</em> &lt;/wsen:MaxItems&gt; ?
  &lt;wsen:MaxCharacters ...&gt; <em>xs:long</em> &lt;/wsen:MaxCharacters&gt; ?
  &lt;wsen:EndToSupported .../&gt; ?
  &lt;wsen:ItemsOnNewContextSupported .../&gt; ?
  <em>xs:any</em>*
&lt;/wsen:DataSource&gt;</pre></div></div><p>
     The following describes additional, normative constraints on the
     outline listed above:
    </p><dl><dt class="label"> /wsen:DataSource </dt><dd><p>
         This policy assertion has Endpoint Policy Subject. When present in a
         policy alternative, it indicates that the subject is a data source
         and the WS-Enumeration protocol MUST
         be used when communicating with this endpoint.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:FilterDialect </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the
         specified Filter Dialect IRI.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:FilterDialect/xs:any </dt><dd><p>
         This extensibility point allows for additional FilterDialect
         specific metadata to be included within the policy assertion. Any
         metadata that appears is scoped to the use of the specified
         FilterDialect URI.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:DateTimeSupported </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for
         expiration time expressed as specific time (rather than duration).
        </p></dd><dt class="label"> /wsen:DataSource/wsen:Expires </dt><dd><p>
         When present, this OPTIONAL parameter indicates the minimum and
         maximum enumeration expiration times that this endpoint will support.
         When the OPTIONAL 'min' attribute is absent then the data source
         MUST not impose a lower bound on the accepted Expires values. The
         implied default value for the OPTIONAL 'max' attribute is
         infinite (or PT0S). In all cases, the 'min' value MUST be less
         than or equal to the 'max' value.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:MaxTime </dt><dd><p>
         When present, this OPTIONAL parameter indicates the maximum MaxTime
         value supported by this endpoint.
         The implied default is infinite.
         Note: a value of "PT0S" indicates that this endpoint supports any
         duration value.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:MaxItems </dt><dd><p>
         When present, this OPTIONAL parameter indicates the maximum
         MaxItems value supported by this endpoint. The value specified
         MUST be greater than zero.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:MaxCharacters </dt><dd><p>
         When present, this OPTIONAL parameter indicates the maximum
         MaxCharacters value supported by this endpoint. The value specified
         MUST be greater than zero.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:EndToSupported </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the
         /wsen:Enumerate/wsen:NewContext/wsen:EndTo semantics. That is, when a
         Enumerate request contains a wsen:EndTo element, a EnumerationEnd
         message will be sent to the EPR contained in the wsen:EndTo element,
         if the enumeration terminates unexpectedly.
        </p></dd><dt class="label"> /wsen:DataSource/wsen:ItemsOnNewContextSupported </dt><dd><p>
         When present, this OPTIONAL parameter indicates support for the
         Enumerate operation creating a new enumeration context and
         returning an initial set of items in the Enumerate response
         message.  When a data source does not support this feature,
         all consumers MUST include a wsen:MaxItems with
         a value of zero in Enumerate requests that create new
         enumeration contexts.
        </p></dd><dt class="label"> /wsen:DataSource/xs:any </dt><dd><p>
         This extensibility point allows for additional WS-Enumeration
         specific metadata to be included within the policy assertion -
         e.g. WS-Enumeration WSDL, or nested policy assertions related to
         the WS-Enumeration message exchanges. Any metadata that appears
         is scoped to the operations and features of the WS-Enumeration
         specification.
        </p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"></a>8 Acknowledgements</h2><p>
    This specification has been developed as a
    result of joint work with many individuals and teams,
    including:
     Alessio Soldano (Red Hat),
     Ashok Malhotra (Oracle Corp.),
     Asir Vedamuthu (Microsoft Corp.),
     Bob Freund (Hitachi, Ltd.),
     Bob Natale (MITRE Corp.),
     David Snelling (Fujitsu, Ltd.),
     Doug Davis (IBM),
     Fred Maciel (Hitachi, Ltd.),
     Geoff Bullen (Microsoft Corp.),
     Gilbert Pilz (Oracle Corp.),
     Greg Carpenter (Microsoft Corp.),
     Jeff Mischkinsky (Oracle Corp.),
     Katy Warr (IBM),
     Li Li (Avaya Communications),
     Mark Little (Red Hat),
     Martin Chapman (Oracle Corp.),
     Paul Fremantle (WSO2),
     Paul Nolan (IBM),
     Prasad Yendluri (Software AG),
     Ram Jeyaraman (Microsoft Corp.),
     Sreedhara Narayanaswamy (CA),
     Sumeet Vij (Software AG),
     Tom Rutt (Fujitsu, Ltd.),
     Vikas Varma (Software AG),
     Wu Chou (Avaya Communications),
     Yves Lafon (W3C/ERCIM).
   </p></div><div class="div1">
<h2><a name="refs" id="refs"></a>9 References</h2><div class="div2">
<h3><a name="idp1700272" id="idp1700272"></a>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"></a>BP12</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 1.2
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"></a>BP20</dt><dd>
        <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
         WS-I Profile, Basic Profile Version 2.0
        </cite></a>
        , R. Chumbley, et al, Editors.
        Web Services Interoperability Organization (WS-I), 9 November 2010.
      Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>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.
       Internet Engineering Task Force, March 1997.
      Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"></a>RFC 3987</dt><dd>
       <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
        Internationalized Resource Identifiers (IRIs)
       </cite></a>
       , M. Duerst and M. Suignard, Authors.
       Internet Engineering Task Force, January 2005.
      Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP11</dt><dd>
       <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
        W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
       </cite></a>
       , D. Box, et al, Editors.
       World Wide Web Consortium (W3C), 8 May 2000.
      Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"></a>SOAP12</dt><dd>
       <a href="http://www.w3.org/TR/soap12-part1/"><cite>
        W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
       </cite></a>
       , M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
        Editors.
       World Wide Web Consortium (W3C), 27 April 2007.
      Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"></a>WS-Addressing</dt><dd>
       <a href="http://www.w3.org/TR/ws-addr-core"><cite>
        W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </cite></a>
       , M. Gudgin, M. Hadley, T. Rogers, Editors.
       World Wide Web Consortium (W3C), 9 May 2006.
      Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="WSABinding" id="WSABinding"></a>WS-Addressing 1.0 SOAP Binding</dt><dd>
       <a href="http://www.w3.org/TR/ws-addr-soap"><cite>
        W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
       </cite></a>
       , M. Gudgin, M. Hadley, T. Rogers, Editors.
       World Wide Web Consortium (W3C), 9 May 2006.
      Available at <a href="http://www.w3.org/TR/ws-addr-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
       <a href="http://www.w3.org/TR/ws-policy/"><cite>
        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
       </cite></a>
       , A. Vedamuthu, et al., Editors.
       World Wide Web Consortium (W3C), 4 September 2007.
      Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="wspolicyattach" id="wspolicyattach"></a>WS-Policy Attachment</dt><dd>
       <a href="http://www.w3.org/TR/ws-policy-attach"><cite>
        W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
       </cite></a>
       , A. Vedamuthu, et al., Editors.
       World Wide Web Consortium (W3C), 4 September 2007.
      Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL11</dt><dd>
       <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
        W3C Note, "Web Services Description Language (WSDL) 1.1"
       </cite></a>
       , E. Christensen, et al., Editors.
       World Wide Web Consortium (W3C), 15 March 2001
      Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
       <a href="http://www.w3.org/TR/xml-infoset"><cite>
        W3C Recommendation, "XML Information Set (Second Edition)"
       </cite></a>
       , J. Cowan, R. Tobin, Editors.
       World Wide Web Consortium (W3C), 4 February 2004.
      Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XMLSchema - Part 1</dt><dd>
       <a href="http://www.w3.org/TR/xmlschema-1/"><cite>
        W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
       </cite></a>
       , H. Thompson, et al., Editors.
       World Wide Web Consortium (W3C), 28 October 2004.
      Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XMLSchema - Part 2</dt><dd>
       <a href="http://www.w3.org/TR/xmlschema-2/"><cite>
        W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
       </cite></a>
       , P. Biron, A. Malhotra, Editors.
       World Wide Web Consortium (W3C), 28 October 2004.
      Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd><dt class="label"><a name="XPath1" id="XPath1"></a>XPath1.0</dt><dd>
       <a href="http://www.w3.org/TR/xpath"><cite>
        W3C Recommendation, "XML Path Language (XPath) Version 1.0"
       </cite></a>
       , 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><dt class="label"><a name="XPath2" id="XPath2"></a>XPath2.0</dt><dd>
       <a href="http://www.w3.org/TR/xpath20/"><cite>
        W3C Recommendation, "XML Path Language (XPath) 2.0"
       </cite></a>
       , A. Berglund, et al., Editors.
       World Wide Web Consortium (W3C), 23 January 2007.
      Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div><div class="div2">
<h3><a name="idp1754816" id="idp1754816"></a>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"></a>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>
       , D. Davis, et al., Editors.
       World Wide Web Consortium (W3C), 15 September 2009.
      Available at <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="schema" id="schema"></a>A XML Schema</h2><p>
    A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
    <a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
    retrieved from the following address:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-enu/enumeration.xsd">http://www.w3.org/2011/03/ws-enu/enumeration.xsd</a></pre></div></div><p>
    A non-normative copy of the XML schema is listed below for convenience.
   </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;xs:schema
    targetNamespace='http://www.w3.org/2011/03/ws-enu'
    xmlns:tns='http://www.w3.org/2011/03/ws-enu'
    xmlns:wsa='http://www.w3.org/2005/08/addressing'
    xmlns:xs='http://www.w3.org/2001/XMLSchema'
    elementFormDefault='qualified'
    blockDefault='#all'&gt;

  &lt;xs:import namespace='http://www.w3.org/XML/1998/namespace'
     schemaLocation='http://www.w3.org/2001/xml.xsd' /&gt;
  &lt;xs:import
    namespace='http://www.w3.org/2005/08/addressing'
    schemaLocation='http://www.w3.org/2006/03/addressing/ws-addr.xsd' /&gt;

  &lt;!-- Types and global elements --&gt;
  &lt;xs:complexType name='FilterType' mixed='true'&gt;
    &lt;xs:sequence&gt;
      &lt;xs:any namespace='##other' processContents='lax'
              minOccurs='0' maxOccurs='unbounded' /&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:attribute name='Dialect' type='xs:anyURI' use='optional'
                  default='http://www.w3.org/2011/03/ws-enu/Dialects/XPath10'/&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:simpleType name='PositiveDurationType'&gt;
    &lt;xs:restriction base='xs:duration'&gt;
      &lt;xs:minExclusive value='P0Y0M0DT0H0M0S' /&gt;
    &lt;/xs:restriction&gt;
  &lt;/xs:simpleType&gt;

  &lt;xs:simpleType name='NonNegativeDurationType'&gt;
    &lt;xs:restriction base='xs:duration'&gt;
      &lt;xs:minInclusive value='P0Y0M0DT0H0M0S' /&gt;
    &lt;/xs:restriction&gt;
  &lt;/xs:simpleType&gt;

  &lt;xs:simpleType name='DurationDateTime'&gt;
      &lt;xs:union memberTypes='xs:dateTime tns:NonNegativeDurationType' /&gt;
  &lt;/xs:simpleType&gt;

  &lt;xs:complexType name='MiniExpirationType'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='tns:DurationDateTime'&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='ExpirationType'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='tns:MiniExpirationType'&gt;
        &lt;xs:attribute name='BestEffort' type='xs:boolean' use='optional'/&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='EnumerationContextType'&gt;
    &lt;xs:complexContent mixed='true'&gt;
      &lt;xs:restriction base='xs:anyType'&gt;
        &lt;xs:sequence&gt;
          &lt;xs:any namespace='##other' processContents='lax'
                  minOccurs='0' maxOccurs='unbounded' /&gt;
        &lt;/xs:sequence&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
      &lt;/xs:restriction&gt;
    &lt;/xs:complexContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='ItemListType'&gt;
    &lt;xs:sequence maxOccurs='unbounded'&gt;
      &lt;xs:any namespace='##other' processContents='lax'
              minOccurs='0' maxOccurs='unbounded' /&gt;
    &lt;/xs:sequence&gt;
    &lt;xs:attribute name='Reason' type='xs:anyURI' use='optional'/&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='LanguageSpecificStringType'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:string'&gt;
        &lt;xs:attribute ref='xml:lang' /&gt;
        &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;!-- Used for a fault response --&gt;
  &lt;xs:element name='SupportedDialect' type='xs:anyURI' /&gt;

  &lt;!-- Enumerate request --&gt;
  &lt;xs:element name='Enumerate'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:choice&gt;
          &lt;xs:element name='NewContext'&gt;
            &lt;xs:complexType&gt;
              &lt;xs:sequence&gt;
                &lt;xs:element name='EndTo' type='wsa:EndpointReferenceType'
                            minOccurs='0' /&gt;
                &lt;xs:element name='Expires' type='tns:ExpirationType'
                            minOccurs='0' /&gt;
                &lt;xs:element name='Filter' type='tns:FilterType'
                            minOccurs='0' /&gt;
                &lt;xs:any namespace='##other' processContents='lax'
                        minOccurs='0' maxOccurs='unbounded' /&gt;
              &lt;/xs:sequence&gt;
              &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
            &lt;/xs:complexType&gt;
          &lt;/xs:element&gt;
          &lt;xs:element name='EnumerationContext'
                      type='tns:EnumerationContextType' /&gt;
        &lt;/xs:choice&gt;
        &lt;xs:element name='MaxTime' type='tns:PositiveDurationType'
                    minOccurs='0' /&gt;
        &lt;xs:element name='MaxItems' type='xs:positiveInteger'
                    minOccurs='0' /&gt;
        &lt;xs:element name='MaxCharacters' type='xs:positiveInteger'
                    minOccurs='0' /&gt;
        &lt;xs:element name='EndToSupported' type='tns:Empty' minOccurs='0' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Enumerate response --&gt;
  &lt;xs:element name='EnumerateResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='GrantedExpires' type='tns:MiniExpirationType' /&gt;
        &lt;xs:element name='EnumerationContext'
                    type='tns:EnumerationContextType'
                    minOccurs='0' /&gt;
        &lt;xs:element name='Items' type='tns:ItemListType'
                    minOccurs='0' /&gt;
        &lt;xs:element name='EndOfSequence' minOccurs='0' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Renew request --&gt;
  &lt;xs:element name='Renew'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='EnumerationContext'
                    type='tns:EnumerationContextType' /&gt;
        &lt;xs:element name='Expires' type='tns:ExpirationType'
                    minOccurs='0' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Renew response --&gt;
  &lt;xs:element name='RenewResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='GrantedExpires' type='tns:MiniExpirationType' /&gt;
        &lt;xs:element name='EnumerationContext'
                    type='tns:EnumerationContextType'
                    minOccurs='0' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- GetStatus request --&gt;
  &lt;xs:element name='GetStatus'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='EnumerationContext'
                    type='tns:EnumerationContextType' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- GetStatus response --&gt;
  &lt;xs:element name='GetStatusResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='GrantedExpires' type='tns:MiniExpirationType' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Release request --&gt;
  &lt;xs:element name='Release'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='EnumerationContext'
                    type='tns:EnumerationContextType' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- Release response --&gt;
  &lt;xs:element name='ReleaseResponse'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;!-- EnumerationEnd message --&gt;
  &lt;xs:element name='EnumerationEnd'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='Code' type='tns:OpenEnumerationEndCodeType' /&gt;
        &lt;xs:element name='Reason' type='tns:LanguageSpecificStringType'
                    minOccurs='0' maxOccurs='unbounded' /&gt;
        &lt;xs:any namespace='##other' processContents='lax'
                minOccurs='0' maxOccurs='unbounded' /&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

  &lt;xs:simpleType name='EnumerationEndCodeType'&gt;
    &lt;xs:restriction base='xs:anyURI'&gt;
      &lt;xs:enumeration value=
        'http://www.w3.org/2011/03/ws-enu/SourceShuttingDown' /&gt;
      &lt;xs:enumeration value=
        'http://www.w3.org/2011/03/ws-enu/SourceCancelling' /&gt;
    &lt;/xs:restriction&gt;
  &lt;/xs:simpleType&gt;

  &lt;xs:simpleType name='OpenEnumerationEndCodeType'&gt;
    &lt;xs:union memberTypes='tns:EnumerationEndCodeType xs:anyURI' /&gt;
  &lt;/xs:simpleType&gt;

  &lt;!-- Policy --&gt;
  &lt;xs:complexType name='Duration'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='tns:NonNegativeDurationType'&gt;
       &lt;xs:anyAttribute namespace='##other'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='URI'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:anyURI'&gt;
        &lt;xs:anyAttribute namespace='##other'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='Long'&gt;
    &lt;xs:simpleContent&gt;
      &lt;xs:extension base='xs:long'&gt;
        &lt;xs:anyAttribute namespace='##other'/&gt;
      &lt;/xs:extension&gt;
    &lt;/xs:simpleContent&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:complexType name='Empty'&gt;
    &lt;xs:sequence/&gt;
    &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
  &lt;/xs:complexType&gt;

  &lt;xs:element name='DataSource'&gt;
    &lt;xs:complexType&gt;
      &lt;xs:sequence&gt;
        &lt;xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'&gt;
          &lt;xs:complexType&gt;
            &lt;xs:sequence&gt;
              &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                          maxOccurs='0'/&gt;
            &lt;/xs:sequence&gt;
            &lt;xs:attribute name='URI' type='xs:anyURI' use='required' /&gt;
            &lt;xs:anyAttribute namespace="##other" processContents='lax'/&gt;
          &lt;/xs:complexType&gt;
        &lt;/xs:element&gt;
        &lt;xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/&gt;
        &lt;xs:element name='Expires' minOccurs='0'&gt;
          &lt;xs:complexType&gt;
            &lt;xs:attribute name='min' type='xs:duration' use='optional'/&gt;
            &lt;xs:attribute name='max' type='xs:duration' use='optional'/&gt;
          &lt;/xs:complexType&gt;
        &lt;/xs:element&gt;
        &lt;xs:element name='MaxTime' type='tns:Duration' minOccurs='0'/&gt;
        &lt;xs:element name='MaxItems' type='tns:Long' minOccurs='0'/&gt;
        &lt;xs:element name='MaxCharacters' type='tns:Long' minOccurs='0'/&gt;
        &lt;xs:any namespace='##other' processContents='lax' minOccurs='0'
                                    maxOccurs='unbounded'/&gt;
      &lt;/xs:sequence&gt;
      &lt;xs:anyAttribute namespace='##other' processContents='lax' /&gt;
    &lt;/xs:complexType&gt;
  &lt;/xs:element&gt;

&lt;/xs:schema&gt;</pre></div></div></div><div class="div1">
<h2><a name="WSDL" id="WSDL"></a>B WSDL</h2><p>
    A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a>
    description for this specification can be retrieved from the
    following address:
   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-enu/enumeration.wsdl">http://www.w3.org/2011/03/ws-enu/enumeration.wsdl</a></pre></div></div><p>
    A non-normative copy of the WSDL description is
    listed below for convenience.
   </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsdl:definitions
    targetNamespace='http://www.w3.org/2011/03/ws-enu'
    xmlns:wsa='http://www.w3.org/2005/08/addressing'
    xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
    xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
    xmlns:wsen='http://www.w3.org/2011/03/ws-enu'
    xmlns:xs='http://www.w3.org/2001/XMLSchema' &gt;

  &lt;wsdl:types&gt;
    &lt;xs:schema&gt;
      &lt;xs:import
        namespace='http://www.w3.org/2011/03/ws-enu'
        schemaLocation='http://www.w3.org/2011/03/ws-enu/enumeration.xsd' /&gt;
    &lt;/xs:schema&gt;
  &lt;/wsdl:types&gt;

  &lt;wsdl:message name='EnumerateMessage'&gt;
    &lt;wsdl:part name='Body' element='wsen:Enumerate' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='EnumerateResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='wsen:EnumerateResponse' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='RenewMessage' &gt;
    &lt;wsdl:part name='Body' element='wsen:Renew' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='RenewResponseMessage' &gt;
    &lt;wsdl:part name='Body' element='wsen:RenewResponse' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='GetStatusMessage' &gt;
    &lt;wsdl:part name='Body' element='wsen:GetStatus' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='GetStatusResponseMessage' &gt;
    &lt;wsdl:part name='Body' element='wsen:GetStatusResponse' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='ReleaseMessage'&gt;
    &lt;wsdl:part name='Body' element='wsen:Release' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='ReleaseResponseMessage'&gt;
    &lt;wsdl:part name='Body' element='wsen:ReleaseResponse' /&gt;
  &lt;/wsdl:message&gt;
  &lt;wsdl:message name='EnumerationEndMessage' &gt;
    &lt;wsdl:part name='Body' element='wsen:EnumerationEnd' /&gt;
  &lt;/wsdl:message&gt;

  &lt;wsdl:portType name='DataSource'&gt;
    &lt;wsdl:operation name='EnumerateOp'&gt;
      &lt;wsdl:input
        message='wsen:EnumerateMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/Enumerate' /&gt;
      &lt;wsdl:output
        message='wsen:EnumerateResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/EnumerateResponse' /&gt;
    &lt;/wsdl:operation&gt;
    &lt;wsdl:operation name='RenewOp' &gt;
      &lt;wsdl:input
        message='wsen:RenewMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/Renew' /&gt;
      &lt;wsdl:output
        message='wsen:RenewResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/RenewResponse' /&gt;
    &lt;/wsdl:operation&gt;
    &lt;wsdl:operation name='GetStatusOp' &gt;
      &lt;wsdl:input
        message='wsen:GetStatusMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/GetStatus' /&gt;
      &lt;wsdl:output
        message='wsen:GetStatusResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/GetStatusResponse' /&gt;
    &lt;/wsdl:operation&gt;
    &lt;wsdl:operation name='ReleaseOp'&gt;
      &lt;wsdl:input
        message='wsen:ReleaseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/Release' /&gt;
      &lt;wsdl:output
        message='wsen:ReleaseResponseMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/ReleaseResponse' /&gt;
    &lt;/wsdl:operation&gt;
  &lt;/wsdl:portType&gt;

  &lt;wsdl:portType name='EnumerationEndPortType'&gt;
    &lt;wsdl:operation name='EnumerationEndOp' &gt;
      &lt;wsdl:input
        message='wsen:EnumerationEndMessage'
        wsam:Action='http://www.w3.org/2011/03/ws-enu/EnumerationEnd' /&gt;
    &lt;/wsdl:operation&gt;
  &lt;/wsdl:portType&gt;

&lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
<h2><a name="actiontables" id="actiontables"></a>C Action Tables</h2><p>
    The purpose of the action tables is to illustrate, via a separate means
    from the normative text, the allowable order and interactions of various
    messages and activities. The action tables are not intended to constrain
    implementations beyond those necessary to insure this ordering.
   </p><ul><li><p>
      Actions are represented as columns.
     </p></li><li><p>
      Triggers (messages, application actions, timer events) are represented
      as rows. Triggers are annotated by their type;
      "[app]" - represents an application action (e.g. a user selecting a
      "Enumerate" menu item);
      "[msg]" - represents an incoming, WS-Enumeration defined, message;
      "[timer]" - represents an internal timer event.
     </p></li><li><p>
      Each cell describes the appropriate action for a given state and
      trigger.
      Where the
      action is dependent upon other factors than the state
      and trigger (e.g. the value of a fault message), the activity is
      described in pseudo-code. The section of the specification that
      describes these activities is displayed in curly
      brackets (e.g. "{4.2}").
     </p></li><li><p>
      Empty box indicates that the spec is silent for the specified
      trigger/action pair.
     </p></li></ul><table border="1"><caption>Table C-1: Data Source Action Table</caption><tbody><tr><td rowspan="2" valign="bottom"> <b>Trigger</b> </td><td colspan="3" align="center"> <b>Action</b> </td></tr><tr><td> <b>Trigger has no context</b> </td><td> <b>Trigger has valid context</b> </td><td> <b>Trigger has invalid context</b> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Enumerate Request <br />
       [msg]</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Create new context<br />
       If (end of sequence) {<br />
           include EndOfSequence <br />
           invalidate context<br />
       } <br />
       Send EnumerateResponse  <br />
       {<a href="#Enumerate"><b>4.1</b></a>}</code>
      </td><td valign="top" nowrap="nowrap"><code>
       If (end of sequence) {<br />
           include EndOfSequence <br />
           invalidate context<br />
       } <br />
       Send EnumerateResponse  <br />
       {<a href="#Enumerate"><b>4.1</b></a>}</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Generate <br />
           InvalidEnumerationContext <br />
           Fault<br />
       {<a href="#EnumMsgs"><b>4</b></a>}</code>
      </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Renew Request <br />
       [msg] </code>
      </td><td> </td><td valign="top" nowrap="nowrap"><code>
       Update expiration timer<br />
       Send RenewReponse<br />
       {<a href="#Renew"><b>4.2</b></a>}</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Generate <br />
           InvalidEnumerationContext <br />
           Fault<br />
       {<a href="#EnumMsgs"><b>4</b></a>}</code>
      </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       GetStatus Request <br />
       [msg] </code>
      </td><td> </td><td valign="top" nowrap="nowrap"><code>
       Send GetStatusResponse <br />
       {<a href="#GetStatus"><b>4.3</b></a>}</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Generate <br />
           InvalidEnumerationContext <br />
           Fault<br />
       {<a href="#EnumMsgs"><b>4</b></a>}</code>
      </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Release Request <br />
       [msg] </code>
      </td><td> </td><td valign="top" nowrap="nowrap"><code>
       Send wse:ReleaseResponse<br />
       Invalidate context<br />
       {<a href="#Release"><b>4.4</b></a>}</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Generate <br />
           InvalidEnumerationContext <br />
           Fault<br />
       {<a href="#EnumMsgs"><b>4</b></a>}</code>
      </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Expiration <br />
       [timer] </code>
      </td><td> </td><td valign="top" nowrap="nowrap"><code>
       Invalidate context<br />
       {<a href="#Enumerate"><b>4.1</b></a>}</code>
      </td><td> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Shutdown/Error <br />
       [app] </code>
      </td><td> </td><td valign="top" nowrap="nowrap"><code>
       if (EndTo engaged) <br />
           send EnumerationEnd <br />
       Invalidate context <br />
       {<a href="#EnumerationEnd"><b>4.5</b></a>}</code>
      </td><td> </td></tr></tbody></table><p></p><table border="1"><caption>Table C-2: Consumer Action Table</caption><tbody><tr><td valign="bottom"> <b>Trigger</b> </td><td align="center"> <b>Action</b> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       Expiration<br />
       [timer] </code>
      </td><td valign="top" nowrap="nowrap"><code>
       Invalidate context<br />
       {<a href="#Enumerate"><b>4.1</b></a>}</code>
      </td></tr><tr><td valign="top" nowrap="nowrap"><code>
       EnumerationEnd<br />
       [msg]</code>
      </td><td valign="top" nowrap="nowrap"><code>
       Invalidate context<br />
       {<a href="#EnumerationEnd"><b>4.5</b></a>}</code>
      </td></tr></tbody></table></div><div class="div1">
<h2><a name="changelog" id="changelog"></a>D Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
      </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a>
      </td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</a>
      </td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a>
      </td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a>
      </td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6499">6499</a>
      </td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6726">6726</a>
      </td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a>
      </td></tr><tr><td> 2009/04/28 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6787">6787</a>
      </td></tr><tr><td> 2009/05/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6860">6860</a>
      </td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</a>
      </td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a>
      </td></tr><tr><td> 2009/05/26 </td><td> KW </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6920">6920</a>
      </td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a>
      </td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</a>
      </td></tr><tr><td> 2009/06/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6956">6956</a>
      </td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a>
      </td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7192">7192</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a>
      </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7193">7193</a>
      </td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a>
      </td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a>
      </td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235">7235</a>
      </td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a>
      </td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6701">6701</a>
      </td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7430">7430</a>
      </td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a>
      </td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a>
      </td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6568">6568</a>
      </td></tr><tr><td> 2009/09/30 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7716">7716</a>
      </td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a>
      </td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6403">6403</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a>
      </td></tr><tr><td> 2009/10/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7587">7587</a>
      </td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7811">7811</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a>
      </td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issues
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</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=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><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><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8158">8158</a>
      </td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a>
      </td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a>
      </td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a>
      </td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8305">8305</a>
      </td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159">8159</a>
      </td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161">8161</a>
      </td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</a>
      </td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a>
      </td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157">8157</a>
      </td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a>
      </td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
       <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><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><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a>
      </td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a>
      </td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</a>
      </td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a>
      </td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9543">9543</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</a>
      </td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9568">9568</a>
      </td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a>
      </td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</a>
      </td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702">9702</a>
      </td></tr><tr><td> 2010/06/29 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9609">9609</a>
      </td></tr><tr><td> 2010/08/17 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</a>
      </td></tr><tr><td> 2010/11/16 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960">10960</a>
      </td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a>
      </td></tr><tr><td> 2011/01/11 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11696">11696</a>
      </td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a>
      </td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12051">12051</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894">11894</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11990">11990</a>
      </td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</a>
      </td></tr><tr><td> 2011/03/22 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12112">12112</a>
      </td></tr><tr><td> 2011/03/22 </td><td> DD </td><td> Added resolution of issue
       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11776">11776</a>
      </td></tr></tbody></table></div></div></body></html>