- From: Katy Warr via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 16 Mar 2009 17:41:20 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv22673
Modified Files:
wsenum.html wsenum.xml
Log Message:
Issue 6587 - Notational Conventions (Use of brackets in msgs)
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- wsenum.html 16 Mar 2009 10:26:21 -0000 1.22
+++ wsenum.html 16 Mar 2009 17:41:06 -0000 1.23
@@ -1,6 +1,7 @@
<?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">
+<!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"><head><title>Web Services Enumeration (WS-Enumeration)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -30,43 +31,43 @@
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/base.css" /></head><body><div class="head">
-<h1><a name="title" id="title"></a>Web Services Enumeration (WS-Enumeration)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
+<h1><a name="title" id="title"/>Web Services Enumeration (WS-Enumeration)</h1>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
</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 class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</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>
+ </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 class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</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"/>Abstract</h2><p>
This specification describes a general
SOAP-based protocol for enumerating a sequence of XML elements that
is suitable for traversing logs, message queues, or other linear
information models.
</p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br />
- 1.1 <a href="#reqs">Requirements</a><br />
-2 <a href="#termsNotes">Notations and Terminology</a><br />
- 2.1 <a href="#conv">Notational Conventions</a><br />
- 2.2 <a href="#namespaces">XML Namespaces</a><br />
- 2.3 <a href="#terms">Terminology</a><br />
- 2.4 <a href="#compliance">Compliance</a><br />
-3 <a href="#EnumMsgs">Enumeration Messages</a><br />
- 3.1 <a href="#Enumerate">Enumerate</a><br />
- 3.2 <a href="#Pull">Pull</a><br />
- 3.3 <a href="#Renew">Renew</a><br />
- 3.4 <a href="#GetStatus">GetStatus</a><br />
- 3.5 <a href="#Release">Release</a><br />
- 3.6 <a href="#EnumerationEnd">EnumerationEnd</a><br />
-4 <a href="#Security">Security Considerations</a><br />
-5 <a href="#acks">Acknowledgements</a><br />
-6 <a href="#refs">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
+ 1.1 <a href="#reqs">Requirements</a><br/>
+2 <a href="#termsNotes">Notations and Terminology</a><br/>
+ 2.1 <a href="#conv">Notational Conventions</a><br/>
+ 2.2 <a href="#namespaces">XML Namespaces</a><br/>
+ 2.3 <a href="#terms">Terminology</a><br/>
+ 2.4 <a href="#compliance">Compliance</a><br/>
+3 <a href="#EnumMsgs">Enumeration Messages</a><br/>
+ 3.1 <a href="#Enumerate">Enumerate</a><br/>
+ 3.2 <a href="#Pull">Pull</a><br/>
+ 3.3 <a href="#Renew">Renew</a><br/>
+ 3.4 <a href="#GetStatus">GetStatus</a><br/>
+ 3.5 <a href="#Release">Release</a><br/>
+ 3.6 <a href="#EnumerationEnd">EnumerationEnd</a><br/>
+4 <a href="#Security">Security Considerations</a><br/>
+5 <a href="#acks">Acknowledgements</a><br/>
+6 <a href="#refs">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="#changelog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
+B <a href="#WSDL">WSDL</a><br/>
+C <a href="#changelog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="intro" id="intro"/>1 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
@@ -125,7 +126,7 @@
items that are returned in a Pull response are removed from the
queue.
</p><div class="div2">
-<h3><a name="reqs" id="reqs"></a>1.1 Requirements</h3><p>
+<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>
This specification intends to meet the following requirements:
</p><ul><li><p>
Support enumeration of data sources
@@ -138,12 +139,12 @@
Minimize additional mechanism
beyond the current web service architecture.
</p></li></ul></div></div><div class="div1">
-<h2><a name="termsNotes" id="termsNotes"></a>2 Notations and Terminology</h2><p>
+<h2><a name="termsNotes" id="termsNotes"/>2 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>2.1 Notational Conventions</h3><p>
+<h3><a name="conv" id="conv"/>2.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
@@ -168,13 +169,14 @@
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.
+ 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>
- An ellipsis (i.e. "...") indicates
- a point of extensibility that allows other child or attribute
- content. Additional children and/or attributes MAY be added at the
+ The characters "[" and "]" are used to call out references and
+ property names.
+ </p></li><li><p>
+ Ellipsis (i.e. "...") indicate points of extensibility.
+ Additional children and/or attributes MAY be added 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
@@ -184,14 +186,14 @@
to indicate the namespace of the element being
defined.
</p></li></ul></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"></a>2.2 XML Namespaces</h3><p>
+<h3><a name="namespaces" id="namespaces"/>2.2 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/2009/02/ws-enu">http://www.w3.org/2009/02/ws-enu</a></pre></div></div><p>
<a href="#xmlnamespaces">Table 2-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 2-1:
+ </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1"><caption>Table 2-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/2009/02/ws-enu">
@@ -240,7 +242,7 @@
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div><div class="div2">
-<h3><a name="terms" id="terms"></a>2.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
+<h3><a name="terms" id="terms"/>2.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>
@@ -253,7 +255,7 @@
items using the Pull operation defined in this
specification
</p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"></a>2.4 Compliance</h3><p>
+<h3><a name="compliance" id="compliance"/>2.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
@@ -265,7 +267,7 @@
precedence over normative outlines, which in turn takes precedence
over the XML Schema and WSDL descriptions.
</p></div></div><div class="div1">
-<h2><a name="EnumMsgs" id="EnumMsgs"></a>3 Enumeration Messages</h2><p>
+<h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
Enumeration contexts represent a specific
traversal through a sequence of XML information items. An Enumerate
operation may be used to establish an enumeration context from a
@@ -312,7 +314,7 @@
to a Web service that is addressable by an EPR
<a href="#WSAddressing">[WS-Addressing]</a>.
</p><div class="div2">
-<h3><a name="Enumerate" id="Enumerate"></a>3.1 Enumerate</h3><p>
+<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
All data sources MUST support some operation
that allows an enumeration to be started. A data source MAY support
the Enumerate operation, or it may provide some other mechanism for
@@ -334,7 +336,7 @@
<s:Body ...>
<wsen:Enumerate ...>
<wsen:EndTo><em>endpoint-reference</em></wsen:EndTo> ?
- <wsen:Expires>[<em>xs:dateTime</em> | <em>xs:duration</em>]</wsen:Expires> ?
+ <wsen:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wsen:Expires> ?
<wsen:Filter Dialect="<em>xs:anyURI</em>"?> <em>xs:any</em> </wsen:Filter> ?
...
</wsen:Enumerate>
@@ -476,7 +478,7 @@
s12:Code/s12:Subcode/s12:Value = wsen:CannotProcessFilter
</p></li><li><p>
s12:Reason/s12:Text = e.g., "cannot filter as requested"
- </p></li></ul></dd><dt class="label"><a name="Dialect" id="Dialect"></a> /s:Envelope/s:Body/*/wsen:Filter/@Dialect </dt><dd><p>
+ </p></li></ul></dd><dt class="label"><a name="Dialect" id="Dialect"/> /s:Envelope/s:Body/*/wsen:Filter/@Dialect </dt><dd><p>
Implied value is
"http://www.w3.org/TR/1999/REC-xpath-19991116".
</p><p>
@@ -522,7 +524,7 @@
</s:Header>
<s:Body ...>
<wsen:EnumerateResponse ...>
- <wsen:Expires>[<em>xs:dateTime</em> | <em>xs:duration</em>]</wsen:Expires> ?
+ <wsen:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wsen:Expires> ?
<wsen:EnumerationContext>...</wsen:EnumerationContext>
...
</wsen:EnumerateResponse>
@@ -559,7 +561,7 @@
</p></dd></dl><p>
<a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumReq" id="enumReq"></a>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:wsen="http://www.w3.org/2009/02/ws-enu">
(04) <s:Header>
@@ -595,7 +597,7 @@
<a href="#enumRes">Example 3-2</a> lists a response to the request in
<a href="#enumReq">Example 3-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumRes" id="enumRes"></a>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
+<div class="exampleHeader"><a name="enumRes" id="enumRes"/>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
(02) xmlns:wsen='http://www.w3.org/2009/02/ws-enu'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
(04) >
@@ -626,7 +628,7 @@
enumeration context that supports the Pull operation defined
below.
</p></div><div class="div2">
-<h3><a name="Pull" id="Pull"></a>3.2 Pull</h3><p>
+<h3><a name="Pull" id="Pull"/>3.2 Pull</h3><p>
The Pull operation is initiated by sending a
Pull request message to the data source. The Pull request message
MUST be of the following form:
@@ -826,7 +828,7 @@
</p><p>
<a href="#pullReq">Example 3-3</a> lists a Pull request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullReq" id="pullReq"></a>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullReq" id="pullReq"/>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) <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/2009/02/ws-enu">
(04) <s:Header>
@@ -862,7 +864,7 @@
<a href="#pullRes">Example 3-4</a> lists a response to the request in
<a href="#pullReq">Example 3-3</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullRes" id="pullRes"></a>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullRes" id="pullRes"/>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsen="http://www.w3.org/2009/02/ws-enu"
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(04) >
@@ -909,7 +911,7 @@
wsen:InvalidEnumerationContext fault, as described above, or MAY
take some other action.
</p></div><div class="div2">
-<h3><a name="Renew" id="Renew"></a>3.3 Renew</h3><p>
+<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
Data sources MUST support requests to renew
enumerations.
</p><p>
@@ -929,7 +931,7 @@
<s:Body ...>
<wsen:Renew ...>
<wsen:EnumerationContext>...</wsen:EnumerationContext>
- <wsen:Expires>[<em>xs:dateTime</em> | <em>xs:duration</em>]</wsen:Expires> ?
+ <wsen:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wsen:Expires> ?
...
</wsen:Renew>
</s:Body>
@@ -987,7 +989,7 @@
</s:Header>
<s:Body ...>
<wsen:RenewResponse ...>
- <wsen:Expires>[<em>xs:dateTime</em> | <em>xs:duration</em>]</wsen:Expires> ?
+ <wsen:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wsen:Expires> ?
<wsen:EnumerationContext>...</wsen:EnumerationContext> ?
...
</wsen:RenewResponse>
@@ -1031,7 +1033,7 @@
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>3.4 GetStatus</h3><p>
+<h3><a name="GetStatus" id="GetStatus"/>3.4 GetStatus</h3><p>
To get the status of an enumeration, the
subscriber sends a request of the following form to the data
source:
@@ -1072,7 +1074,7 @@
</s:Header>
<s:Body ...>
<wsen:GetStatusResponse ...>
- <wsen:Expires>[<em>xs:dateTime</em> | <em>xs:duration</em>]</wsen:Expires> ?
+ <wsen:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wsen:Expires> ?
...
</wsen:GetStatusResponse>
</s:Body>
@@ -1082,7 +1084,7 @@
(see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are
not further constrained by this specification.
</p></div><div class="div2">
-<h3><a name="Release" id="Release"></a>3.5 Release</h3><p>
+<h3><a name="Release" id="Release"/>3.5 Release</h3><p>
The Release operation is initiated by sending a
Release request message to the data source. The Release request
message MUST be of the following form:
@@ -1144,7 +1146,7 @@
</p></dd></dl><p>
<a href="#releaseReq">Example 3-5</a> lists a Release request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseReq" id="releaseReq"></a>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseReq" id="releaseReq"/>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) <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/2009/02/ws-enu">
(04) <s:Header>
@@ -1175,7 +1177,7 @@
<a href="#releaseRes">Example 3-6</a> lists a response to the request in
<a href="#releaseReq">Example 3-5</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseRes" id="releaseRes"></a>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseRes" id="releaseRes"/>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsen="http://www.w3.org/2009/02/ws-enu"
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(04) >
@@ -1195,7 +1197,7 @@
Lines (06-08) in <a href="#releaseRes">Example 3-6</a> indicate this message
is a Release response message.
</p></div><div class="div2">
-<h3><a name="EnumerationEnd" id="EnumerationEnd"></a>3.6 EnumerationEnd</h3><p>
+<h3><a name="EnumerationEnd" id="EnumerationEnd"/>3.6 EnumerationEnd</h3><p>
If the data source terminates an enumeration
unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
message to the endpoint reference indicated when the enumeration
@@ -1213,10 +1215,10 @@
<wsen:EnumerationEnd ...>
<wsen:EnumerationContext>...</wsen:EnumerationContext>
<wsen:Code>
- [
+ (
http://www.w3.org/2009/02/ws-enu/SourceShuttingDown
| http://www.w3.org/2009/02/ws-enu/SourceCancelling
- ]
+ )
</wsen:Code>
<wsen:Reason xml:lang="<em>language identifier</em>" >
<em>xs:string</em>
@@ -1255,7 +1257,7 @@
Other components of the outline above are not
further constrained by this specification.
</p></div></div><div class="div1">
-<h2><a name="Security" id="Security"></a>4 Security Considerations</h2><p>
+<h2><a name="Security" id="Security"/>4 Security Considerations</h2><p>
It is strongly recommended that the
communication between services be secured using the mechanisms
described in <a href="#WSSecurity">[WS-Security]</a>.
@@ -1356,7 +1358,7 @@
taken to ensure that minimal state is saved prior to any
authenticating sequences.
</p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"></a>5 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>5 Acknowledgements</h2><p>
This specification has been developed as a
result of joint work with many individuals and teams,
including:
@@ -1379,75 +1381,75 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C)
</p></div><div class="div1">
-<h2><a name="refs" id="refs"></a>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC2119</dt><dd>
+<h2><a name="refs" id="refs"/>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</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, March 1997.
- (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP11</dt><dd>
+ (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd>
<a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
Simple Object Access Protocol (SOAP) 1.1
</cite></a>
, D. Box, et al, May 2000.
- (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"></a>SOAP12</dt><dd>
+ (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd>
<a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
SOAP Version 1.2 Part 1: Messaging Framework
</cite></a>
, M. Gudgin, et al, June 2003.
- (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"></a>WS-Addressing</dt><dd>
+ (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"/>WS-Addressing</dt><dd>
<a href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/"><cite>
Web Services Addressing (WS-Addressing)
</cite></a>
,D. Box, et al, August 2004.
- (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
+ (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd>
<a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
Web Services Policy Framework (WS-Policy)
</cite></a>
, S. Bajaj, et al, September 2004.
- (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"></a>WS-SecureConversation</dt><dd>
+ (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd>
<a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
Web Services Secure Conversation Language (WS-SecureConversation)
</cite></a>
, S. Anderson, et al, February 2005.
- (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"></a>WS-Security</dt><dd>
+ (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd>
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
Web Services Security: SOAP Message Security 1.0
</cite></a>
, A. Nadalin, et al, March 2004.
- (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"></a>WS-SecurityPolicy</dt><dd>
+ (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd>
<a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
Web Services Security Policy Language (WS-SecurityPolicy), , Version 1.1
</cite></a>
, G. Della-Libera, et al, July 2005.
- (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL11</dt><dd>
+ (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd>
<a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
Web Services Description Language (WSDL) 1.1
</cite></a>
, E. Christensen, et al, March 2001.
- (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
+ (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd>
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
XML Information Set
</cite></a>
, J. Cowan, et al, February 2004.
- (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XMLSchema - Part 1</dt><dd>
+ (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd>
<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
XML Schema Part 1: Structures
</cite></a>
, H. Thompson, et al, October 2004.
- (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XMLSchema - Part 2</dt><dd>
+ (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd>
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
XML Schema Part 2: Datatypes
</cite></a>
, P. Biron, et al, October 2004.
- (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"></a>XPath1.0</dt><dd>
+ (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"/>XPath1.0</dt><dd>
<a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
XML Path Language (XPath) Version 1.0
</cite></a>
, J. Clark, et al, November 1999.
(See http://www.w3.org/TR/1999/REC-xpath-19991116.)</dd></dl></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="#">[Schema1]</a>,
- <a href="#">[Schema2]</a> description for this specification may be
+<h2><a name="schema" id="schema"/>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 may be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-enu/enumeration.xsd">http://www.w3.org/2009/02/ws-enu/enumeration.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for convenience.
@@ -1690,7 +1692,7 @@
<xs:union memberTypes="tns:EnumerationEndCodeType xs:anyURI" />
</xs:simpleType>
</xs:schema></pre></div></div></div><div class="div1">
-<h2><a name="WSDL" id="WSDL"></a>B WSDL</h2><p>
+<h2><a name="WSDL" id="WSDL"/>B WSDL</h2><p>
A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a>
description for this specification may be retrieved from the
following address:
@@ -1806,7 +1808,7 @@
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"></a>C 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
+<h2><a name="changelog" id="changelog"/>C 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>
@@ -1814,4 +1816,6 @@
<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></tbody></table></div></div></body></html>
+ </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></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- wsenum.xml 12 Mar 2009 13:22:10 -0000 1.14
+++ wsenum.xml 16 Mar 2009 17:41:06 -0000 1.15
@@ -246,16 +246,20 @@
</item>
<item>
<p>
- The characters "[" and "]" are used
- to indicate that contained items are to be treated as a group with
- respect to cardinality or choice.
+ The characters "(" and ")" are used to indicate that contained items
+ are to be treated as a group with respect to cardinality or choice.
+ </p>
+ </item>
+ <item>
+ <p>
+ The characters "[" and "]" are used to call out references and
+ property names.
</p>
</item>
<item>
<p>
- An ellipsis (i.e. "...") indicates
- a point of extensibility that allows other child or attribute
- content. Additional children and/or attributes MAY be added at the
+ Ellipsis (i.e. "...") indicate points of extensibility.
+ Additional children and/or attributes MAY be added 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
@@ -534,7 +538,7 @@
<s:Body ...>
<wsen:Enumerate ...>
<wsen:EndTo><emph>endpoint-reference</emph></wsen:EndTo> ?
- <wsen:Expires>[<emph>xs:dateTime</emph> | <emph>xs:duration</emph>]</wsen:Expires> ?
+ <wsen:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wsen:Expires> ?
<wsen:Filter Dialect="<emph>xs:anyURI</emph>"?> <emph>xs:any</emph> </wsen:Filter> ?
...
</wsen:Enumerate>
@@ -943,7 +947,7 @@
</s:Header>
<s:Body ...>
<wsen:EnumerateResponse ...>
- <wsen:Expires>[<emph>xs:dateTime</emph> | <emph>xs:duration</emph>]</wsen:Expires> ?
+ <wsen:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wsen:Expires> ?
<wsen:EnumerationContext>...</wsen:EnumerationContext>
...
</wsen:EnumerateResponse>
@@ -1575,7 +1579,7 @@
<s:Body ...>
<wsen:Renew ...>
<wsen:EnumerationContext>...</wsen:EnumerationContext>
- <wsen:Expires>[<emph>xs:dateTime</emph> | <emph>xs:duration</emph>]</wsen:Expires> ?
+ <wsen:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wsen:Expires> ?
...
</wsen:Renew>
</s:Body>
@@ -1681,7 +1685,7 @@
</s:Header>
<s:Body ...>
<wsen:RenewResponse ...>
- <wsen:Expires>[<emph>xs:dateTime</emph> | <emph>xs:duration</emph>]</wsen:Expires> ?
+ <wsen:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wsen:Expires> ?
<wsen:EnumerationContext>...</wsen:EnumerationContext> ?
...
</wsen:RenewResponse>
@@ -1833,7 +1837,7 @@
</s:Header>
<s:Body ...>
<wsen:GetStatusResponse ...>
- <wsen:Expires>[<emph>xs:dateTime</emph> | <emph>xs:duration</emph>]</wsen:Expires> ?
+ <wsen:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wsen:Expires> ?
...
</wsen:GetStatusResponse>
</s:Body>
@@ -2048,10 +2052,10 @@
<wsen:EnumerationEnd ...>
<wsen:EnumerationContext>...</wsen:EnumerationContext>
<wsen:Code>
- [
+ (
http://www.w3.org/2009/02/ws-enu/SourceShuttingDown
| http://www.w3.org/2009/02/ws-enu/SourceCancelling
- ]
+ )
</wsen:Code>
<wsen:Reason xml:lang="<emph>language identifier</emph>" >
<emph>xs:string</emph>
@@ -2423,8 +2427,8 @@
<head>XML Schema</head>
<p>
- A normative copy of the XML Schema <bibref ref='Schema1'/>,
- <bibref ref='Schema2'/> description for this specification may be
+ A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
+ <bibref ref='XMLSchema2'/> description for this specification may be
retrieved from the following address:
</p>
@@ -2853,6 +2857,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/03/16 </td>
+ <td> KW </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Monday, 16 March 2009 18:27:29 UTC