- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 21 Apr 2010 03:10:06 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv30812
Modified Files:
wsenum.html wsenum.xml wsevd.html wsevd.xml wseventing.html
wseventing.xml wsfrag.html wsfrag.xml wsmex.html wsmex.xml
wssa.html wssa.xml wst.html wst.xml
Log Message:
Apply 9266 to ws-frag and wssa
Align all of the spec's "Terminology and Notation" sections
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- wst.xml 30 Mar 2010 23:39:58 -0000 1.112
+++ wst.xml 21 Apr 2010 03:10:04 -0000 1.113
@@ -182,134 +182,7 @@
</div1>
<div1 id="Notations_and_Terminology">
<head>Terminology and Notation</head>
- <div2 id="terminology">
- <head>Terminology</head>
- <glist>
- <gitem>
- <label>Resource</label>
- <def>
- <p>
- A Web service that is addressable using an endpoint reference
- and can be represented by an XML Information Set.
- The representation can be retrieved using the Get operation
- and can be manipulated using the Put and Delete operations.
- </p>
- </def>
- </gitem>
- <gitem>
- <label>Resource Factory</label>
- <def>
- <p>A Web service that is capable of creating new resources using the
- Create operation defined in this specification.</p>
- </def>
- </gitem>
- </glist>
- </div2>
- <div2 id="namespaces">
- <head>XML Namespaces</head>
- <p>
- The XML Namespace URI that MUST be used by implementations of this
- specification is:
- </p>
- <example>
- <eg><loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc></eg>
- </example>
- <p>
- <specref ref="xmlnamespaces"/> lists XML namespaces that are
- used in this specification. The
- choice of any namespace prefix is arbitrary and not semantically
- significant.
- </p>
- <table id="xmlnamespaces" border="1" cellpadding="5">
- <caption>
- 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> wst </td>
- <td>
- <loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc>
- </td>
- <td>
- This specification
- </td>
- </tr>
- <tr>
- <td> s </td>
- <td> Either SOAP 1.1 or 1.2 </td>
- <td> SOAP </td>
- </tr>
- <tr>
- <td> s11 </td>
- <td>
- <loc href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</loc>
- </td>
- <td>
- <bibref ref="SOAP11"/>
- </td>
- </tr>
- <tr>
- <td> s12 </td>
- <td>
- <loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
- </td>
- <td>
- <bibref ref="SOAP121"/>
- </td>
- </tr>
- <tr>
- <td> wsa </td>
- <td>
- <loc href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</loc>
- </td>
- <td>
- <bibref ref="AddrCore"/>
- </td>
- </tr>
- <tr>
- <td> wsdl </td>
- <td>
- <loc href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</loc>
- </td>
- <td>
- <bibref ref="WSDL11"/>
- </td>
- </tr>
- <tr>
- <td> xs </td>
- <td>
- <loc href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</loc>
- </td>
- <td>
- XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
- </td>
- </tr>
- </tbody>
- </table>
- <p>
- The working group intends to update the value of the Web Services
- Transfer 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 Transfer 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
- <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
- http://www.w3.org/2001/tag/doc/namespaceState.html
- </loc> and
- <loc href="http://www.w3.org/2005/07/13-nsuri">
- http://www.w3.org/2005/07/13-nsuri
- </loc>.
- </p>
- </div2>
<div2 id="conven">
<head>Notational Conventions</head>
<p>
@@ -474,6 +347,30 @@
</p>
</div2>
+ <div2 id="terminology">
+ <head>Terminology</head>
+ <glist>
+ <gitem>
+ <label>Resource</label>
+ <def>
+ <p>
+ A Web service that is addressable using an endpoint reference
+ and can be represented by an XML Information Set.
+ The representation can be retrieved using the Get operation
+ and can be manipulated using the Put and Delete operations.
+ </p>
+ </def>
+ </gitem>
+ <gitem>
+ <label>Resource Factory</label>
+ <def>
+ <p>A Web service that is capable of creating new resources using the
+ Create operation defined in this specification.</p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
+
<div2 id="compliance">
<head>Compliance</head>
@@ -510,6 +407,113 @@
</p>
</div2>
+
+ <div2 id="namespaces">
+ <head>XML Namespaces</head>
+ <p>
+ The XML Namespace URI that MUST be used by implementations of this
+ specification is:
+ </p>
+ <example>
+ <eg><loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc></eg>
+ </example>
+ <p>
+ <specref ref="xmlnamespaces"/> lists XML namespaces that are
+ used in this specification. The
+ choice of any namespace prefix is arbitrary and not semantically
+ significant.
+ </p>
+ <table id="xmlnamespaces" border="1" cellpadding="5">
+ <caption>
+ 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> wst </td>
+ <td>
+ <loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc>
+ </td>
+ <td>
+ This specification
+ </td>
+ </tr>
+ <tr>
+ <td> s </td>
+ <td> Either SOAP 1.1 or 1.2 </td>
+ <td> SOAP </td>
+ </tr>
+ <tr>
+ <td> s11 </td>
+ <td>
+ <loc href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</loc>
+ </td>
+ <td>
+ <bibref ref="SOAP11"/>
+ </td>
+ </tr>
+ <tr>
+ <td> s12 </td>
+ <td>
+ <loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
+ </td>
+ <td>
+ <bibref ref="SOAP121"/>
+ </td>
+ </tr>
+ <tr>
+ <td> wsa </td>
+ <td>
+ <loc href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</loc>
+ </td>
+ <td>
+ <bibref ref="AddrCore"/>
+ </td>
+ </tr>
+ <tr>
+ <td> wsdl </td>
+ <td>
+ <loc href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</loc>
+ </td>
+ <td>
+ <bibref ref="WSDL11"/>
+ </td>
+ </tr>
+ <tr>
+ <td> xs </td>
+ <td>
+ <loc href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</loc>
+ </td>
+ <td>
+ XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The working group intends to update the value of the Web Services
+ Transfer 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 Transfer 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
+ <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
+ http://www.w3.org/2001/tag/doc/namespaceState.html
+ </loc> and
+ <loc href="http://www.w3.org/2005/07/13-nsuri">
+ http://www.w3.org/2005/07/13-nsuri
+ </loc>.
+ </p>
+ </div2>
+
</div1>
<div1 id="resourceOperations">
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.177
retrieving revision 1.178
diff -u -d -r1.177 -r1.178
--- wseventing.html 21 Apr 2010 00:38:51 -0000 1.177
+++ wseventing.html 21 Apr 2010 03:10:03 -0000 1.178
@@ -49,9 +49,9 @@
3 <a href="#notterms">Notations and Terminology</a><br/>
3.1 <a href="#conventions">Notational Conventions</a><br/>
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 3.3 <a href="#namespaces">XML Namespaces</a><br/>
- 3.4 <a href="#terms">Terminology</a><br/>
- 3.5 <a href="#compliance">Compliance</a><br/>
+ 3.3 <a href="#terms">Terminology</a><br/>
+ 3.4 <a href="#compliance">Compliance</a><br/>
+ 3.5 <a href="#namespaces">XML Namespaces</a><br/>
4 <a href="#SubMsgs">Subscription Messages</a><br/>
4.1 <a href="#Subscribe">Subscribe</a><br/>
4.2 <a href="#Renew">Renew</a><br/>
@@ -385,43 +385,7 @@
Extension elements and attributes MUST NOT use the Web Services
Eventing namespace URI.
</p></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"/>3.3 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/2002/ws/ra/edcopies/ws-evt">http://www.w3.org/2002/ws/ra/edcopies/ws-evt</a></pre></div></div><p><a href="#Table3">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="Table3" id="Table3"/><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>s</td><td>(Either SOAP 1.1 or 1.2)</td><td>(Either SOAP 1.1 or 1.2)</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>s12</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="#SOAP121">[SOAP12]</a></td></tr><tr><td>wsdl</td><td><a href="http://schemas.xmlsoap.org/wsdl/">
- http://schemas.xmlsoap.org/wsdl/
- </a></td><td>WSDL <a href="#WSDL11">[WSDL11]</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>wse</td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt">
- http://www.w3.org/2002/ws/ra/edcopies/ws-evt
- </a></td><td>This specification</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></tbody></table><p>
- The working group intends to update the value of the Web Services
- Eventing 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 Eventing 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 class="div2">
-<h3><a name="terms" id="terms"/>3.4 Terminology</h3><dl><dt class="label"> Event Source </dt><dd><p>
+<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Event Source </dt><dd><p>
A Web service that accepts requests to create subscriptions.
Notifications MAY be sent by any endpoint including the event source.
</p></dd><dt class="label"> Event Sink </dt><dd><p>
@@ -440,11 +404,11 @@
A Web service that accepts requests to manage, get the status of,
renew, and/or delete subscriptions on behalf of an event source.
</p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>3.5 Compliance</h3><p>
+<h3><a name="compliance" id="compliance"/>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.3 XML Namespaces</b></a>) within SOAP
+ 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
@@ -462,6 +426,42 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>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/2002/ws/ra/edcopies/ws-evt">http://www.w3.org/2002/ws/ra/edcopies/ws-evt</a></pre></div></div><p><a href="#Table3">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="Table3" id="Table3"/><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>s</td><td>(Either SOAP 1.1 or 1.2)</td><td>(Either SOAP 1.1 or 1.2)</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>s12</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="#SOAP121">[SOAP12]</a></td></tr><tr><td>wsdl</td><td><a href="http://schemas.xmlsoap.org/wsdl/">
+ http://schemas.xmlsoap.org/wsdl/
+ </a></td><td>WSDL <a href="#WSDL11">[WSDL11]</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>wse</td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt">
+ http://www.w3.org/2002/ws/ra/edcopies/ws-evt
+ </a></td><td>This specification</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></tbody></table><p>
+ The working group intends to update the value of the Web Services
+ Eventing 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 Eventing 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="SubMsgs" id="SubMsgs"/>4 Subscription Messages</h2><p>
To create, renew, and delete subscriptions, subscribers send
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -d -r1.118 -r1.119
--- wsenum.xml 21 Apr 2010 00:36:31 -0000 1.118
+++ wsenum.xml 21 Apr 2010 03:10:03 -0000 1.119
@@ -363,6 +363,82 @@
</p>
</div2>
+ <div2 id="terms">
+ <head>Terminology</head>
+
+ <glist>
+ <gitem>
+ <label> Consumer </label>
+ <def>
+ <p>
+ The Web service that is requesting the data
+ enumeration from the data source
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Data Source </label>
+ <def>
+ <p>
+ A Web service that supports traversal using
+ enumeration contexts via the Enumerate operation defined in this
+ specification
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Enumeration context </label>
+ <def>
+ <p>
+ A session context that represents a specific
+ traversal through a logical sequence of XML element information
+ items using the Pull operation defined in this
+ specification
+ </p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
+
+ <div2 id="compliance">
+ <head>Compliance</head>
+
+ <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 <specref ref="namespaces"/>) 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 be sent to a Web service
+ that is addressable by an EPR (see <bibref ref="AddrCore"/>).
+ </p>
+
+ <p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> 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>
+
+ </div2>
+
<div2 id="namespaces">
<head>XML Namespaces</head>
@@ -471,82 +547,6 @@
</div2>
- <div2 id="terms">
- <head>Terminology</head>
-
- <glist>
- <gitem>
- <label> Consumer </label>
- <def>
- <p>
- The Web service that is requesting the data
- enumeration from the data source
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Data Source </label>
- <def>
- <p>
- A Web service that supports traversal using
- enumeration contexts via the Enumerate operation defined in this
- specification
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Enumeration context </label>
- <def>
- <p>
- A session context that represents a specific
- traversal through a logical sequence of XML element information
- items using the Pull operation defined in this
- specification
- </p>
- </def>
- </gitem>
- </glist>
- </div2>
-
- <div2 id="compliance">
- <head>Compliance</head>
-
- <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 <specref ref="namespaces"/>) 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 be sent to a Web service
- that is addressable by an EPR (see <bibref ref="AddrCore"/>).
- </p>
-
- <p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <bibref ref="RFC3987"/> 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>
-
- </div2>
-
</div1>
<div1 id="EnumMsgs">
Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- wsevd.xml 20 Apr 2010 21:46:46 -0000 1.9
+++ wsevd.xml 21 Apr 2010 03:10:03 -0000 1.10
@@ -246,6 +246,45 @@
</p>
</div2>
+ <div2 id="terms">
+ <head>Terminology</head>
+
+ <glist>
+ <gitem>
+ <label> Notification </label>
+ <def>
+ <p>
+ A message sent to indicate that an event, or events, have occurred.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
+
+ <div2 id="compliance">
+ <head>Compliance</head>
+
+ <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 <specref ref="namespaces"/>) within SOAP
+ Envelopes unless it is compliant with this specification.
+ </p>
+
+ <p>
+ Normative text within this specification takes precedence over the XML
+ Schema, which in turn take precedence over
+ outlines, which in turn take precedence over examples.
+ </p>
+
+ <p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
+ </p>
+
+ </div2>
+
<div2 id="namespaces">
<head>XML Namespaces</head>
@@ -356,44 +395,6 @@
</p>
</div2>
- <div2 id="terms">
- <head>Terminology</head>
-
- <glist>
- <gitem>
- <label> Notification </label>
- <def>
- <p>
- A message sent to indicate that an event, or events, have occurred.
- </p>
- </def>
- </gitem>
- </glist>
- </div2>
-
- <div2 id="compliance">
- <head>Compliance</head>
-
- <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 <specref ref="namespaces"/>) within SOAP
- Envelopes unless it is compliant with this specification.
- </p>
-
- <p>
- Normative text within this specification takes precedence over the XML
- Schema, which in turn take precedence over
- outlines, which in turn take precedence over examples.
- </p>
-
- <p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
- </p>
-
- </div2>
</div1>
<div1 id="Advertising">
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- wsfrag.xml 19 Mar 2010 18:52:27 -0000 1.60
+++ wsfrag.xml 21 Apr 2010 03:10:03 -0000 1.61
@@ -148,139 +148,6 @@
<div1 id="Notations_and_Terminology">
<head>Terminology and Notation</head>
- <div2 id="terminology">
- <head>Terminology</head>
- <glist>
- <gitem>
- <label>Expression</label>
- <def>
- <p>
- A Language specific set of tokens that resolves to a location
- in a resource that contains a subset of the resource.
- </p>
- </def>
- </gitem>
- <gitem>
- <label>Fragment</label>
- <def>
- <p>
- A subset of a resource.
- </p>
- </def>
- </gitem>
- </glist>
- </div2>
-
- <div2 id="namespaces">
- <head>XML Namespaces</head>
- <p>
- The XML Namespace URI that MUST be used by implementations of this
- specification is:
- </p>
-
- <example>
- <eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra">http://www.w3.org/&wsfra.nsprefix;/ws-fra</loc></eg>
- </example>
-
- <p>
- <specref ref="xmlnamespaces"/> lists XML namespaces that are
- used in this specification. The
- choice of any namespace prefix is arbitrary and not semantically
- significant.
- </p>
-
- <table id="xmlnamespaces" border="1" cellpadding="5">
- <caption>
- 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> wsf </td>
- <td>
- <loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra">http://www.w3.org/&wsfra.nsprefix;/ws-fra</loc>
- </td>
- <td>
- This specification
- </td>
- </tr>
- <tr>
- <td> s </td>
- <td> Either SOAP 1.1 or 1.2 </td>
- <td> SOAP </td>
- </tr>
- <tr>
- <td> s11 </td>
- <td>
- <loc href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</loc>
- </td>
- <td>
- <bibref ref="SOAP11"/>
- </td>
- </tr>
- <tr>
- <td> s12 </td>
- <td>
- <loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
- </td>
- <td>
- <bibref ref="SOAP121"/>
- </td>
- </tr>
- <tr>
- <td> wsa </td>
- <td>
- <loc href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</loc>
- </td>
- <td>
- <bibref ref="AddrCore"/>
- </td>
- </tr>
- <tr>
- <td> xs </td>
- <td>
- <loc href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</loc>
- </td>
- <td>
- XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
- </td>
- </tr>
- <tr>
- <td> wst </td>
- <td>
- <loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc>
- </td>
- <td>
- <bibref ref="WsTransfer"/>
- </td>
- </tr>
- </tbody>
- </table>
-
- <p>
- The working group intends to update the value of the Web Services
- Fragment 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 Fragment 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
- <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
- http://www.w3.org/2001/tag/doc/namespaceState.html
- </loc> and
- <loc href="http://www.w3.org/2005/07/13-nsuri">
- http://www.w3.org/2005/07/13-nsuri
- </loc>.
- </p>
- </div2>
-
<div2 id="conven">
<head>Notational Conventions</head>
<p>
@@ -451,6 +318,29 @@
</p>
</div2>
+ <div2 id="terminology">
+ <head>Terminology</head>
+ <glist>
+ <gitem>
+ <label>Expression</label>
+ <def>
+ <p>
+ A Language specific set of tokens that resolves to a location
+ in a resource that contains a subset of the resource.
+ </p>
+ </def>
+ </gitem>
+ <gitem>
+ <label>Fragment</label>
+ <def>
+ <p>
+ A subset of a resource.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
+
<div2 id="compliance">
<head>Compliance</head>
@@ -487,6 +377,117 @@
</p>
</div2>
+
+ <div2 id="namespaces">
+ <head>XML Namespaces</head>
+ <p>
+ The XML Namespace URI that MUST be used by implementations of this
+ specification is:
+ </p>
+
+ <example>
+ <eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra">http://www.w3.org/&wsfra.nsprefix;/ws-fra</loc></eg>
+ </example>
+
+ <p>
+ <specref ref="xmlnamespaces"/> lists XML namespaces that are
+ used in this specification. The
+ choice of any namespace prefix is arbitrary and not semantically
+ significant.
+ </p>
+
+ <table id="xmlnamespaces" border="1" cellpadding="5">
+ <caption>
+ 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> wsf </td>
+ <td>
+ <loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra">http://www.w3.org/&wsfra.nsprefix;/ws-fra</loc>
+ </td>
+ <td>
+ This specification
+ </td>
+ </tr>
+ <tr>
+ <td> s </td>
+ <td> Either SOAP 1.1 or 1.2 </td>
+ <td> SOAP </td>
+ </tr>
+ <tr>
+ <td> s11 </td>
+ <td>
+ <loc href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</loc>
+ </td>
+ <td>
+ <bibref ref="SOAP11"/>
+ </td>
+ </tr>
+ <tr>
+ <td> s12 </td>
+ <td>
+ <loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
+ </td>
+ <td>
+ <bibref ref="SOAP121"/>
+ </td>
+ </tr>
+ <tr>
+ <td> wsa </td>
+ <td>
+ <loc href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</loc>
+ </td>
+ <td>
+ <bibref ref="AddrCore"/>
+ </td>
+ </tr>
+ <tr>
+ <td> xs </td>
+ <td>
+ <loc href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</loc>
+ </td>
+ <td>
+ XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
+ </td>
+ </tr>
+ <tr>
+ <td> wst </td>
+ <td>
+ <loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra">http://www.w3.org/&wstra.nsprefix;/ws-tra</loc>
+ </td>
+ <td>
+ <bibref ref="WsTransfer"/>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The working group intends to update the value of the Web Services
+ Fragment 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 Fragment 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
+ <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
+ http://www.w3.org/2001/tag/doc/namespaceState.html
+ </loc> and
+ <loc href="http://www.w3.org/2005/07/13-nsuri">
+ http://www.w3.org/2005/07/13-nsuri
+ </loc>.
+ </p>
+ </div2>
+
</div1>
<div1 id="fragments">
@@ -1942,7 +1943,7 @@
<head>WS-Fragment Metadata</head>
<p>
- An endpoint MAY indicate that it supports WS-Fragment, or its features,
+ An endpoint MAY indicate its support of WS-Fragment, or its features,
by including the WS-Fragment FragmentAssertion Policy assertion within its
WSDL. By
doing so the endpoint is indicating that the corresponding WS-Fragment
@@ -1953,7 +1954,7 @@
<head>Fragment Assertion</head>
<p>
- Services indicate support for the WS-Fragment specification through
+ Services indicate their support for the WS-Fragment specification through
the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
@@ -1961,34 +1962,6 @@
<p>
This specification defines a policy assertion (wsf:FragmentAssertion).
- The wsf:FragmentAssertion policy assertion applies to the endpoint policy
- subject.
- </p>
-
- <p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
- wsdl11:port or wsdl11:binding.
- For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
- wsdl20:binding.
- </p>
-
- <p>
- The meaning of this assertion, when present in a policy
- alternative, is that WS-Fragment is REQUIRED to communicate with the
- subject and that the subject is a WS-Transfer Resource.
- </p>
-
- <p>
- In order to indicate that the subject supports WS-Fragment
- but does not require its use, an additional policy alternative SHOULD
- be provided which does not contain this assertion. The compact
- authoring style for an OPTIONAL policy assertion (the wsp:Optional
- attribute) provided by WS-Policy MAY be used to indicate two policy
- alternatives, one which contains the policy assertion, and another
- which does not.
- </p>
-
- <p>
The normative outline of this assertion is:
</p>
@@ -2012,9 +1985,9 @@
<label> /wsf:FragmentAssertion </label>
<def>
<p>
- A policy assertion that specifies that WS-Fragment protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When present
+ in a policy alternative, it indicates that the WS-Fragment
+ protocol MUST be used when communicating with this endpoint.
</p>
</def>
</gitem>
@@ -2530,7 +2503,7 @@
<tr>
<td> 2010/03/02 </td>
<td> DD </td>
- <td> Added resolution of issue
+ <td> Added resolution of issues
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185">8185</loc>,
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193">8193</loc>
</td>
@@ -2538,12 +2511,19 @@
<tr>
<td> 2010/03/09 </td>
<td> DD </td>
- <td> Added resolution of issue
+ <td> Added resolution of issues
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</loc>,
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/04/20 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- wsfrag.html 20 Mar 2010 01:25:54 -0000 1.62
+++ wsfrag.html 21 Apr 2010 03:10:03 -0000 1.63
@@ -43,11 +43,11 @@
<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="#Notations_and_Terminology">Terminology and Notation</a><br/>
- 2.1 <a href="#terminology">Terminology</a><br/>
- 2.2 <a href="#namespaces">XML Namespaces</a><br/>
- 2.3 <a href="#conven">Notational Conventions</a><br/>
- 2.4 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 2.5 <a href="#compliance">Compliance</a><br/>
+ 2.1 <a href="#conven">Notational Conventions</a><br/>
+ 2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
+ 2.3 <a href="#terminology">Terminology</a><br/>
+ 2.4 <a href="#compliance">Compliance</a><br/>
+ 2.5 <a href="#namespaces">XML Namespaces</a><br/>
3 <a href="#fragments">Fragment WS-Transfer Dialect</a><br/>
3.1 <a href="#IdResSubset">Identification of a Resource Subset</a><br/>
3.2 <a href="#FragSer">Fragment Serialization</a><br/>
@@ -68,7 +68,7 @@
9.1 <a href="#iddiv2_1_1939">Fragment Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2010">Normative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2002">Normative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#changelog">Change Log</a><br/>
@@ -108,42 +108,7 @@
can leverage.
</p></li></ul></div></div><div class="div1">
<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>2 Terminology and Notation</h2><div class="div2">
-<h3><a name="terminology" id="terminology"/>2.1 Terminology</h3><dl><dt class="label">Expression</dt><dd><p>
- A Language specific set of tokens that resolves to a location
- in a resource that contains a subset of the resource.
- </p></dd><dt class="label">Fragment</dt><dd><p>
- A subset of a resource.
- </p></dd></dl></div><div class="div2">
-<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/2002/ws/ra/edcopies/ws-fra">http://www.w3.org/2002/ws/ra/edcopies/ws-fra</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"/><table border="1" cellpadding="5"><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> wsf </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra">http://www.w3.org/2002/ws/ra/edcopies/ws-fra</a></td><td>
- This specification
- </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</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><a href="#AddrCore">[WS-Addressing]</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> wst </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</a></td><td><a href="#WsTransfer">[WS-Transfer]</a></td></tr></tbody></table><p>
- The working group intends to update the value of the Web Services
- Fragment 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 Fragment 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 class="div2">
-<h3><a name="conven" id="conven"/>2.3 Notational Conventions</h3><p>
+<h3><a name="conven" id="conven"/>2.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",
@@ -205,7 +170,7 @@
of the message that are defined as part of this specification and
are extensions to the WS-Transfer messages.
</p></div><div class="div2">
-<h3><a name="extensions" id="extensions"/>2.4 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>2.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
@@ -227,11 +192,17 @@
Extension elements and attributes MUST NOT use the Web Services
Fragment namespace URI.
</p></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>2.5 Compliance</h3><p>
+<h3><a name="terminology" id="terminology"/>2.3 Terminology</h3><dl><dt class="label">Expression</dt><dd><p>
+ A Language specific set of tokens that resolves to a location
+ in a resource that contains a subset of the resource.
+ </p></dd><dt class="label">Fragment</dt><dd><p>
+ A subset of a resource.
+ </p></dd></dl></div><div class="div2">
+<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 use the XML namespace identifier for this
- specification (listed in <a href="#namespaces"><b>2.2 XML Namespaces</b></a>) within SOAP
+ specification (listed in <a href="#namespaces"><b>2.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
@@ -249,6 +220,35 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>2.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/2002/ws/ra/edcopies/ws-fra">http://www.w3.org/2002/ws/ra/edcopies/ws-fra</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"/><table border="1" cellpadding="5"><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> wsf </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra">http://www.w3.org/2002/ws/ra/edcopies/ws-fra</a></td><td>
+ This specification
+ </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</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><a href="#AddrCore">[WS-Addressing]</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> wst </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</a></td><td><a href="#WsTransfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+ The working group intends to update the value of the Web Services
+ Fragment 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 Fragment 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="fragments" id="fragments"/>3 Fragment WS-Transfer Dialect</h2><p>
This section defines the fragment transfer mechanism that the expression
@@ -918,39 +918,19 @@
The specified mode is not supported.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Mode.</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="metadata" id="metadata"/>9 WS-Fragment Metadata</h2><p>
- An endpoint MAY indicate that it supports WS-Fragment, or its features,
+ An endpoint MAY indicate its support of WS-Fragment, or its features,
by including the WS-Fragment FragmentAssertion Policy assertion within its
WSDL. By
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
<h3><a name="iddiv2_1_1939" id="iddiv2_1_1939"/>9.1 Fragment Assertion</h3><p>
- Services indicate support for the WS-Fragment specification through
+ Services indicate their support for the WS-Fragment specification 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 (wsf:FragmentAssertion).
- The wsf:FragmentAssertion policy assertion applies to the endpoint policy
- subject.
- </p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
- wsdl11:port or wsdl11:binding.
- For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
- wsdl20:binding.
- </p><p>
- The meaning of this assertion, when present in a policy
- alternative, is that WS-Fragment is REQUIRED to communicate with the
- subject and that the subject is a WS-Transfer Resource.
- </p><p>
- In order to indicate that the subject supports WS-Fragment
- but does not require its use, an additional policy alternative SHOULD
- be provided which does not contain this assertion. The compact
- authoring style for an OPTIONAL policy assertion (the wsp:Optional
- attribute) provided by WS-Policy MAY be used to indicate two policy
- alternatives, one which contains the policy assertion, and another
- which does not.
- </p><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsf:FragmentAssertion ...>
<wsf:Language URI="<em>xs:anyURI</em> ...>
@@ -961,9 +941,9 @@
The following describes additional, normative constraints on the
outline listed above:
</p><dl><dt class="label"> /wsf:FragmentAssertion </dt><dd><p>
- A policy assertion that specifies that WS-Fragment protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When present
+ in a policy alternative, it indicates that the WS-Fragment
+ protocol MUST be used when communicating with this endpoint.
</p></dd><dt class="label"> /wsf:FragmentAssertion/wsf:Language </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified Language IRI.
@@ -1008,7 +988,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2010" id="iddiv2_1_2010"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2002" id="iddiv2_1_2002"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1185,9 +1165,10 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191">8191</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/10 </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/10 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a></td></tr><tr><td> 2010/03/02 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a></td></tr><tr><td> 2010/03/02 </td><td> DD </td><td> Added resolution of issues
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185">8185</a>,
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193">8193</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=8193">8193</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issues
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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=9266">9266</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wssa.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- wssa.xml 21 Apr 2010 01:49:57 -0000 1.1
+++ wssa.xml 21 Apr 2010 03:10:03 -0000 1.2
@@ -227,6 +227,25 @@
</p>
</div2>
+ <div2 id="Compliance">
+ <head>Compliance</head>
+
+ <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 <specref ref="namespaces"/>) 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>
+
+ </div2>
+
<div2 id="namespaces">
<head>XML Namespaces</head>
@@ -311,24 +330,6 @@
</p>
</div2>
- <div2 id="Compliance">
- <head>Compliance</head>
-
- <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 <specref ref="namespaces"/>) 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>
-
- </div2>
</div1>
<div1 id='SOAPAssertions'>
@@ -337,20 +338,7 @@
<p>
An endpoint MAY indicate that it requires the use of a certain version
of SOAP by using the following policy assertions with its policy
- alternatives. These policy assertions apply to the endpoint policy
- subject. For WSDL 1.1, these assertions MAY be attached to wsdl11:port
- or wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint
- or wsdl20:binding.
- </p>
-
- <p>
- In order to indicate that the subject supports a particular version of
- SOAP but does not require its use, an additional policy alternative
- SHOULD be provided which does not contain this assertion. The compact
- authoring style for an OPTIONAL policy assertion (the wsp:Optional
- attribute) provided by WS-Policy MAY be used to indicate two policy
- alternatives, one which contains the policy assertion, and another
- which does not.
+ alternatives.
</p>
<div2 id='SAS11'>
@@ -374,9 +362,9 @@
<label>/wssa:SOAP11</label>
<def>
<p>
- A policy assertion that specifies that the SOAP 1.1 protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When
+ present in a policy alternative, it indicates that the SOAP 1.1
+ protocol MUST be used when communicating with this endpoint.
</p>
</def>
</gitem>
@@ -404,9 +392,9 @@
<label>/wssa:SOAP12</label>
<def>
<p>
- A policy assertion that specifies that the SOAP 1.2 protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When
+ present in a policy alternative, it indicates that the SOAP 1.2
+ protocol MUST be used when communicating with this endpoint.
</p>
</def>
</gitem>
@@ -657,6 +645,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/04/20 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -d -r1.103 -r1.104
--- wsmex.xml 21 Apr 2010 01:49:56 -0000 1.103
+++ wsmex.xml 21 Apr 2010 03:10:03 -0000 1.104
@@ -629,6 +629,90 @@
Metadata Exchange namespace URI.
</p>
</div2>
+
+ <div2 id="terms">
+ <head>Terminology</head>
+
+ <glist>
+ <gitem>
+ <label> Service Endpoint </label>
+ <def>
+ <p>
+ A Web service that is addressable using a WS-Addressing endpoint
+ reference. Within the context of this specification, it is assumed
+ that the consumer's primary goal is to interact with this service.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Metadata Resource </label>
+ <def>
+ <p>
+ A specialized Web service that is addressable using either a
+ WS-Addressing endpoint reference or a URL and whose main purpose is
+ to expose the XML representation of a piece of metadata associated
+ with a Service Endpoint.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+
+ <p>
+ While technically a single Web service can be both a 'Service Endpoint'
+ as well as a 'Metadata Resource', for the purposes of clarifying the
+ various expectations of these two types Web services, this specification
+ will discuss these two concepts (or roles) as distinct entities.
+ </p>
+
+ </div2>
+
+ <div2 id="Compliance">
+ <head>Compliance</head>
+
+ <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 <specref ref="namespaces"/>) 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 be sent to a Web service
+ that is addressable by an EPR (see <bibref ref="AddrCore"/>).
+ </p>
+
+ <p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> 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>
+ Support for the GetMetadata operation by a Web service is
+ OPTIONAL. If metadata about a Web service endpoint is referenced by
+ a MetadataReference, which is a
+ <bibref ref='AddrCore'/> endpoint reference, then the MetadataReference
+ MUST refer to a <bibref ref='WS-Transfer'/> resource.
+ The referred resource MAY also support other resource management
+ and access specifications (e.g. HTTP, WS-ResourceFramework).
+ </p>
+
+ </div2>
<div2 id="namespaces">
<head>XML Namespaces</head>
@@ -729,89 +813,6 @@
</p>
</div2>
- <div2 id="terms">
- <head>Terminology</head>
-
- <glist>
- <gitem>
- <label> Service Endpoint </label>
- <def>
- <p>
- A Web service that is addressable using a WS-Addressing endpoint
- reference. Within the context of this specification, it is assumed
- that the consumer's primary goal is to interact with this service.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Metadata Resource </label>
- <def>
- <p>
- A specialized Web service that is addressable using either a
- WS-Addressing endpoint reference or a URL and whose main purpose is
- to expose the XML representation of a piece of metadata associated
- with a Service Endpoint.
- </p>
- </def>
- </gitem>
- </glist>
-
- <p>
- While technically a single Web service can be both a 'Service Endpoint'
- as well as a 'Metadata Resource', for the purposes of clarifying the
- various expectations of these two types Web services, this specification
- will discuss these two concepts (or roles) as distinct entities.
- </p>
-
- </div2>
-
- <div2 id="Compliance">
- <head>Compliance</head>
-
- <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 <specref ref="namespaces"/>) 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 be sent to a Web service
- that is addressable by an EPR (see <bibref ref="AddrCore"/>).
- </p>
-
- <p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <bibref ref="RFC3987"/> 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>
- Support for the GetMetadata operation by a Web service is
- OPTIONAL. If metadata about a Web service endpoint is referenced by
- a MetadataReference, which is a
- <bibref ref='AddrCore'/> endpoint reference, then the MetadataReference
- MUST refer to a <bibref ref='WS-Transfer'/> resource.
- The referred resource MAY also support other resource management
- and access specifications (e.g. HTTP, WS-ResourceFramework).
- </p>
-
- </div2>
</div1>
<div1 id = 'web-services-metadata'>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -d -r1.127 -r1.128
--- wsenum.html 21 Apr 2010 00:36:31 -0000 1.127
+++ wsenum.html 21 Apr 2010 03:10:03 -0000 1.128
@@ -45,9 +45,9 @@
2 <a href="#termsNotes">Notations and Terminology</a><br/>
2.1 <a href="#conv">Notational Conventions</a><br/>
2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 2.3 <a href="#namespaces">XML Namespaces</a><br/>
- 2.4 <a href="#terms">Terminology</a><br/>
- 2.5 <a href="#compliance">Compliance</a><br/>
+ 2.3 <a href="#terms">Terminology</a><br/>
+ 2.4 <a href="#compliance">Compliance</a><br/>
+ 2.5 <a href="#namespaces">XML Namespaces</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/>
@@ -242,7 +242,43 @@
Extension elements and attributes MUST NOT use the Web Services
Enumeration namespace URI.
</p></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"/>2.3 XML Namespaces</h3><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>
+ 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 Pull operation defined in this
+ specification
+ </p></dd></dl></div><div class="div2">
+<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 use the XML namespace identifier for this
+ specification (listed in <a href="#namespaces"><b>2.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 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></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>2.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/2002/ws/ra/edcopies/ws-enu">http://www.w3.org/2002/ws/ra/edcopies/ws-enu</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are used in
@@ -279,43 +315,7 @@
<a href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</a>.
- </p></div><div class="div2">
-<h3><a name="terms" id="terms"/>2.4 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 Pull operation defined in this
- specification
- </p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>2.5 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>2.3 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 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></div></div><div class="div1">
+ </p></div></div><div class="div1">
<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
Index: wssa.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- wssa.html 21 Apr 2010 01:49:56 -0000 1.1
+++ wssa.html 21 Apr 2010 03:10:03 -0000 1.2
@@ -44,15 +44,15 @@
2 <a href="#notterms">Notations</a><br/>
2.1 <a href="#Conventions">Notational Conventions</a><br/>
2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 2.3 <a href="#namespaces">XML Namespaces</a><br/>
- 2.4 <a href="#Compliance">Compliance</a><br/>
+ 2.3 <a href="#Compliance">Compliance</a><br/>
+ 2.4 <a href="#namespaces">XML Namespaces</a><br/>
3 <a href="#SOAPAssertions">SOAP Assertions</a><br/>
3.1 <a href="#SAS11">SOAP11 Assertion</a><br/>
3.2 <a href="#SAS12">SOAP12 Assertion</a><br/>
4 <a href="#Examples">Examples</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#References">References</a><br/>
- 6.1 <a href="#iddiv2_1_446">Normative References</a><br/>
+ 6.1 <a href="#iddiv2_1_444">Normative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#changelog">Change Log</a><br/>
@@ -129,7 +129,18 @@
Extension elements and attributes MUST NOT use the Web Services
Metadata Exchange namespace URI.
</p></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"/>2.3 XML Namespaces</h3><p>
+<h3><a name="Compliance" id="Compliance"/>2.3 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>2.4 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></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>2.4 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/2002/ws/ra/edcopies/ws-sas">http://www.w3.org/2002/ws/ra/edcopies/ws-sas</a></pre></div></div><p><a href="#XMLNS">Table 2-1</a> lists XML namespaces that are used in this
@@ -151,33 +162,11 @@
<a href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</a>.
- </p></div><div class="div2">
-<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 use the XML namespace identifier for this
- specification (listed in <a href="#namespaces"><b>2.3 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></div></div><div class="div1">
<h2><a name="SOAPAssertions" id="SOAPAssertions"/>3 SOAP Assertions</h2><p>
An endpoint MAY indicate that it requires the use of a certain version
of SOAP by using the following policy assertions with its policy
- alternatives. These policy assertions apply to the endpoint policy
- subject. For WSDL 1.1, these assertions MAY be attached to wsdl11:port
- or wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint
- or wsdl20:binding.
- </p><p>
- In order to indicate that the subject supports a particular version of
- SOAP but does not require its use, an additional policy alternative
- SHOULD be provided which does not contain this assertion. The compact
- authoring style for an OPTIONAL policy assertion (the wsp:Optional
- attribute) provided by WS-Policy MAY be used to indicate two policy
- alternatives, one which contains the policy assertion, and another
- which does not.
+ alternatives.
</p><div class="div2">
<h3><a name="SAS11" id="SAS11"/>3.1 SOAP11 Assertion</h3><p>
The normative outline of this assertion is:
@@ -185,9 +174,9 @@
The following describes additional, normative constraints on the
outline listed above:
</p><dl><dt class="label">/wssa:SOAP11</dt><dd><p>
- A policy assertion that specifies that the SOAP 1.1 protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When
+ present in a policy alternative, it indicates that the SOAP 1.1
+ protocol MUST be used when communicating with this endpoint.
</p></dd></dl></div><div class="div2">
<h3><a name="SAS12" id="SAS12"/>3.2 SOAP12 Assertion</h3><p>
The normative outline of this assertion is:
@@ -195,9 +184,9 @@
The following describes additional, normative constraints on the
outline listed above:
</p><dl><dt class="label">/wssa:SOAP12</dt><dd><p>
- A policy assertion that specifies that the SOAP 1.2 protocol MUST
- be used when communicating with this endpoint. This assertion has
- Endpoint Policy Subject.
+ This policy assertion has Endpoint Policy Subject. When
+ present in a policy alternative, it indicates that the SOAP 1.2
+ protocol MUST be used when communicating with this endpoint.
</p></dd></dl></div></div><div class="div1">
<h2><a name="Examples" id="Examples"/>4 Examples</h2><p>
The following example shows a sample policy expression that indicates
@@ -253,7 +242,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>6 References</h2><div class="div2">
-<h3><a name="iddiv2_1_446" id="iddiv2_1_446"/>6.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_444" id="iddiv2_1_444"/>6.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -331,4 +320,5 @@
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"/>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></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=9250">9250</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</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=9266">9266</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -d -r1.116 -r1.117
--- wsmex.html 21 Apr 2010 01:49:56 -0000 1.116
+++ wsmex.html 21 Apr 2010 03:10:03 -0000 1.117
@@ -50,9 +50,9 @@
3 <a href="#notterms">Notations and Terminology</a><br/>
3.1 <a href="#Conventions">Notational Conventions</a><br/>
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 3.3 <a href="#namespaces">XML Namespaces</a><br/>
- 3.4 <a href="#terms">Terminology</a><br/>
- 3.5 <a href="#Compliance">Compliance</a><br/>
+ 3.3 <a href="#terms">Terminology</a><br/>
+ 3.4 <a href="#Compliance">Compliance</a><br/>
+ 3.5 <a href="#namespaces">XML Namespaces</a><br/>
4 <a href="#web-services-metadata">Web Services Metadata Collection</a><br/>
5 <a href="#metadata-resources">Metadata Resources</a><br/>
6 <a href="#Retrieving-Metadata">Retrieving Metadata about Service Endpoints</a><br/>
@@ -61,19 +61,19 @@
7 <a href="#MetadataReferences">Metadata References</a><br/>
7.1 <a href="#mexLocation">mex:Location</a><br/>
7.2 <a href="#mexReference">mex:Reference</a><br/>
- 7.3 <a href="#iddiv2_1_1235">Examples</a><br/>
+ 7.3 <a href="#iddiv2_1_1234">Examples</a><br/>
8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
9 <a href="#ImplicitWSDL">Exposing Metadata for Implicitly Defined Features</a><br/>
10 <a href="#Security">Security Considerations</a><br/>
11 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 11.1 <a href="#iddiv2_1_1630">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1629">MetadataExchange Assertion</a><br/>
12 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
13 <a href="#acks">Acknowledgements</a><br/>
14 <a href="#References">References</a><br/>
- 14.1 <a href="#iddiv2_1_1783">Normative References</a><br/>
- 14.2 <a href="#iddiv2_1_1969">Informative References</a><br/>
+ 14.1 <a href="#iddiv2_1_1782">Normative References</a><br/>
+ 14.2 <a href="#iddiv2_1_1968">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#Appendix-B">WSDL</a><br/>
@@ -430,30 +430,7 @@
Extension elements and attributes MUST NOT use the Web Services
Metadata Exchange namespace URI.
</p></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"/>3.3 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/2002/ws/ra/edcopies/ws-mex">http://www.w3.org/2002/ws/ra/edcopies/ws-mex</a></pre></div></div><p><a href="#XMLNS">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="XMLNS" id="XMLNS"/><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 Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex </td><td> This specification </td></tr>tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wssa </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-sa </td><td><a href="#WS-SOAPAssertions">[WS-SOAPAssertions]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
- The working group intends to update the value of the Web Services
- Metadata Exchange 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 Metadata Exchange 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 class="div2">
-<h3><a name="terms" id="terms"/>3.4 Terminology</h3><dl><dt class="label"> Service Endpoint </dt><dd><p>
+<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Service Endpoint </dt><dd><p>
A Web service that is addressable using a WS-Addressing endpoint
reference. Within the context of this specification, it is assumed
that the consumer's primary goal is to interact with this service.
@@ -468,11 +445,11 @@
various expectations of these two types Web services, this specification
will discuss these two concepts (or roles) as distinct entities.
</p></div><div class="div2">
-<h3><a name="Compliance" id="Compliance"/>3.5 Compliance</h3><p>
+<h3><a name="Compliance" id="Compliance"/>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.3 XML Namespaces</b></a>) within SOAP
+ 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
@@ -498,6 +475,29 @@
MUST refer to a <a href="#WS-Transfer">[WS-Transfer]</a> resource.
The referred resource MAY also support other resource management
and access specifications (e.g. HTTP, WS-ResourceFramework).
+ </p></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>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/2002/ws/ra/edcopies/ws-mex">http://www.w3.org/2002/ws/ra/edcopies/ws-mex</a></pre></div></div><p><a href="#XMLNS">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="XMLNS" id="XMLNS"/><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 Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex </td><td> This specification </td></tr>tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wssa </td><td> http://www.w3.org//ws-sa </td><td><a href="#WS-SOAPAssertions">[WS-SOAPAssertions]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+ The working group intends to update the value of the Web Services
+ Metadata Exchange 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 Metadata Exchange 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="web-services-metadata" id="web-services-metadata"/>4 Web Services Metadata Collection</h2><p>
The WS-MetadataExchange Metadata element is a collection of metadata units
@@ -846,7 +846,7 @@
being referenced. Identifier is an absolute IRI. If omitted, there
is no implied value.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1235" id="iddiv2_1_1235"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1234" id="iddiv2_1_1234"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -877,7 +877,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_1267" id="idexample_1_1267"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexample_1_1266" id="idexample_1_1266"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
(02) ...
(03) <wsdl:service name="stockQuote">
(04) <wsdl:port binding="..." name="...">
@@ -1427,7 +1427,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1630" id="iddiv2_1_1630"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1629" id="iddiv2_1_1629"/>11.1 MetadataExchange Assertion</h3><p>
Services indicate support for the WS-MetadataExchange specification
through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1582,7 +1582,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>14 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1783" id="iddiv2_1_1783"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1782" id="iddiv2_1_1782"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1654,7 +1654,7 @@
, 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></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1969" id="iddiv2_1_1969"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1968" id="iddiv2_1_1968"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- wsevd.html 20 Apr 2010 21:46:45 -0000 1.12
+++ wsevd.html 21 Apr 2010 03:10:03 -0000 1.13
@@ -44,9 +44,9 @@
3 <a href="#notterms">Notations and Terminology</a><br/>
3.1 <a href="#conventions">Notational Conventions</a><br/>
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 3.3 <a href="#namespaces">XML Namespaces</a><br/>
- 3.4 <a href="#terms">Terminology</a><br/>
- 3.5 <a href="#compliance">Compliance</a><br/>
+ 3.3 <a href="#terms">Terminology</a><br/>
+ 3.4 <a href="#compliance">Compliance</a><br/>
+ 3.5 <a href="#namespaces">XML Namespaces</a><br/>
4 <a href="#Advertising">Advertising Event Information</a><br/>
4.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
4.1.1 <a href="#iddiv3_1_555">Retrieving Event Descriptions</a><br/>
@@ -129,7 +129,24 @@
Extension elements and attributes MUST NOT use the Web Services
Event Descriptions namespace URI.
</p></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"/>3.3 XML Namespaces</h3><p>
+<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Notification </dt><dd><p>
+ A message sent to indicate that an event, or events, have occurred.
+ </p></dd></dl></div><div class="div2">
+<h3><a name="compliance" id="compliance"/>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, which in turn take precedence over
+ outlines, which in turn take precedence over examples.
+ </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></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>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/2002/ws/ra/edcopies/ws-evd">http://www.w3.org/2002/ws/ra/edcopies/ws-evd</a></pre></div></div><p><a href="#Table3">Table 3-1</a> lists XML namespaces that are used in this
@@ -164,23 +181,6 @@
<a href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</a>.
- </p></div><div class="div2">
-<h3><a name="terms" id="terms"/>3.4 Terminology</h3><dl><dt class="label"> Notification </dt><dd><p>
- A message sent to indicate that an event, or events, have occurred.
- </p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>3.5 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.3 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, which in turn take precedence over
- outlines, which in turn take precedence over examples.
- </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></div></div><div class="div1">
<h2><a name="Advertising" id="Advertising"/>4 Advertising Event Information</h2><p>
There are many use cases in which it is necessary for an endpoint
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -d -r1.170 -r1.171
--- wseventing.xml 21 Apr 2010 00:38:51 -0000 1.170
+++ wseventing.xml 21 Apr 2010 03:10:03 -0000 1.171
@@ -580,6 +580,109 @@
</p>
</div2>
+ <div2 id="terms">
+ <head>Terminology</head>
+
+ <glist>
+ <gitem>
+ <label> Event Source </label>
+ <def>
+ <p>
+ A Web service that accepts requests to create subscriptions.
+ Notifications MAY be sent by any endpoint including the event source.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Event Sink </label>
+ <def>
+ <p>
+ A Web service that receives notifications.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Notification </label>
+ <def>
+ <p>
+ A message sent to indicate that an event, or events, have occurred.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Subscription </label>
+ <def>
+ <p>
+ A registration of interest in receiving notification messages from
+ an event source. Subscriptions MAY be created, renewed, expired
+ or cancelled. A subscription is "active" when it has been created
+ but has not been expired or cancelled.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Subscriber </label>
+ <def>
+ <p>
+ A Web service that sends requests to create, renew, and/or
+ delete subscriptions.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Subscription Manager </label>
+ <def>
+ <p>
+ A Web service that accepts requests to manage, get the status of,
+ renew, and/or delete subscriptions on behalf of an event source.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
+
+ <div2 id="compliance">
+ <head>Compliance</head>
+
+ <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 <specref ref="namespaces"/>) 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 be sent to a Web service
+ that is addressable by an EPR (see <bibref ref="AddrCore"/>).
+ </p>
+
+ <p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> 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>
+
+ </div2>
+
<div2 id="namespaces">
<head>XML Namespaces</head>
@@ -690,108 +793,6 @@
</p>
</div2>
- <div2 id="terms">
- <head>Terminology</head>
-
- <glist>
- <gitem>
- <label> Event Source </label>
- <def>
- <p>
- A Web service that accepts requests to create subscriptions.
- Notifications MAY be sent by any endpoint including the event source.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Event Sink </label>
- <def>
- <p>
- A Web service that receives notifications.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Notification </label>
- <def>
- <p>
- A message sent to indicate that an event, or events, have occurred.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Subscription </label>
- <def>
- <p>
- A registration of interest in receiving notification messages from
- an event source. Subscriptions MAY be created, renewed, expired
- or cancelled. A subscription is "active" when it has been created
- but has not been expired or cancelled.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Subscriber </label>
- <def>
- <p>
- A Web service that sends requests to create, renew, and/or
- delete subscriptions.
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Subscription Manager </label>
- <def>
- <p>
- A Web service that accepts requests to manage, get the status of,
- renew, and/or delete subscriptions on behalf of an event source.
- </p>
- </def>
- </gitem>
- </glist>
- </div2>
-
- <div2 id="compliance">
- <head>Compliance</head>
-
- <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 <specref ref="namespaces"/>) 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 be sent to a Web service
- that is addressable by an EPR (see <bibref ref="AddrCore"/>).
- </p>
-
- <p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <bibref ref="RFC3987"/> 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>
-
- </div2>
</div1>
<div1 id="SubMsgs">
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -d -r1.115 -r1.116
--- wst.html 30 Mar 2010 23:39:58 -0000 1.115
+++ wst.html 21 Apr 2010 03:10:04 -0000 1.116
@@ -41,11 +41,11 @@
<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="#Notations_and_Terminology">Terminology and Notation</a><br/>
- 2.1 <a href="#terminology">Terminology</a><br/>
- 2.2 <a href="#namespaces">XML Namespaces</a><br/>
- 2.3 <a href="#conven">Notational Conventions</a><br/>
- 2.4 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
- 2.5 <a href="#compliance">Compliance</a><br/>
+ 2.1 <a href="#conven">Notational Conventions</a><br/>
+ 2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
+ 2.3 <a href="#terminology">Terminology</a><br/>
+ 2.4 <a href="#compliance">Compliance</a><br/>
+ 2.5 <a href="#namespaces">XML Namespaces</a><br/>
3 <a href="#resourceOperations">Resource Operations</a><br/>
3.1 <a href="#Get">Get</a><br/>
3.2 <a href="#Put">Put</a><br/>
@@ -131,43 +131,7 @@
architecture.
</p></li></ul></div></div><div class="div1">
<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>2 Terminology and Notation</h2><div class="div2">
-<h3><a name="terminology" id="terminology"/>2.1 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>
- A Web service that is addressable using an endpoint reference
- and can be represented by an XML Information Set.
- The representation can be retrieved using the Get operation
- and can be manipulated using the Put and Delete operations.
- </p></dd><dt class="label">Resource Factory</dt><dd><p>A Web service that is capable of creating new resources using the
- Create operation defined in this specification.</p></dd></dl></div><div class="div2">
-<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/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</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"/><table border="1" cellpadding="5"><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> wst </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</a></td><td>
- This specification
- </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</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><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#WSDL11">[WSDL11]</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></tbody></table><p>
- The working group intends to update the value of the Web Services
- Transfer 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 Transfer 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 class="div2">
-<h3><a name="conven" id="conven"/>2.3 Notational Conventions</h3><p>
+<h3><a name="conven" id="conven"/>2.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",
@@ -225,7 +189,7 @@
security concerns - in these situations the fault MAY NOT
be transmitted.
</p></div><div class="div2">
-<h3><a name="extensions" id="extensions"/>2.4 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>2.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
@@ -247,11 +211,18 @@
Extension elements and attributes MUST NOT use the Web Services
Transfer namespace URI.
</p></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>2.5 Compliance</h3><p>
+<h3><a name="terminology" id="terminology"/>2.3 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>
+ A Web service that is addressable using an endpoint reference
+ and can be represented by an XML Information Set.
+ The representation can be retrieved using the Get operation
+ and can be manipulated using the Put and Delete operations.
+ </p></dd><dt class="label">Resource Factory</dt><dd><p>A Web service that is capable of creating new resources using the
+ Create operation defined in this specification.</p></dd></dl></div><div class="div2">
+<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 use the XML namespace identifier for this
- specification (listed in <a href="#namespaces"><b>2.2 XML Namespaces</b></a>) within SOAP
+ specification (listed in <a href="#namespaces"><b>2.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
@@ -269,7 +240,36 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
- </p></div></div><div class="div1">
+ </p></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>2.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/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</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"/><table border="1" cellpadding="5"><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> wst </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-tra">http://www.w3.org/2002/ws/ra/edcopies/ws-tra</a></td><td>
+ This specification
+ </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#SOAP121">[SOAP12]</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><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#WSDL11">[WSDL11]</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></tbody></table><p>
+ The working group intends to update the value of the Web Services
+ Transfer 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 Transfer 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="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><div class="div2">
<h3><a name="Get" id="Get"/>3.1 Get</h3><p>
This specification defines one Web service operation (Get) for
Received on Wednesday, 21 April 2010 03:10:14 UTC