- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 23 Apr 2010 15:31:54 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv19614
Modified Files:
wsenum.html wsenum.xml wsevd.html wsevd.xml wseventing.html
wseventing.xml wsfrag.html wsfrag.xml wsmex.html wsmex.xml
wsrt.xml wssa.html wssa.xml wst.html wst.xml
Log Message:
Minor edits:
- gave all specs the same "Composable Architecture" section
- s/XML Schema description/XML schema/ in some specs
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- wst.xml 21 Apr 2010 03:10:04 -0000 1.113
+++ wst.xml 23 Apr 2010 15:31:52 -0000 1.114
@@ -26,186 +26,210 @@
</publoc>
<latestloc>
- <loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="http://www.w3.org/TR/&wstra.shortname;">http://www.w3.org/TR/&wstra.shortname;
</loc>
</latestloc>
<prevlocs>
- <loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
+ <loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="&prev.wstra.dated;">&prev.wstra.dated;
- </loc>
+ </loc>
</prevlocs>
- <authlist>
- <author>
- <name>Doug Davis</name>
- <affiliation>IBM</affiliation>
- </author>
- <author>
- <name>Ashok Malhotra</name>
- <affiliation>Oracle</affiliation>
- </author>
- <author>
- <name>Katy Warr</name>
- <affiliation>IBM</affiliation>
- </author>
- <author>
- <name>Wu Chou</name>
- <affiliation>Avaya</affiliation>
- </author>
- </authlist>
- <status id='Status'>
- <p>This is the First Public Working Draft.</p>
- <p>
- Publication as a Working Draft does not imply endorsement by the
- W3C Membership. This is a draft document and can be updated, replaced
- or obsoleted by other documents at any time. It is inappropriate to
- cite this document as other than work in progress.
- </p>
- </status>
- <abstract>
- <p>
+ <authlist>
+ <author>
+ <name>Doug Davis</name>
+ <affiliation>IBM</affiliation>
+ </author>
+ <author>
+ <name>Ashok Malhotra</name>
+ <affiliation>Oracle</affiliation>
+ </author>
+ <author>
+ <name>Katy Warr</name>
+ <affiliation>IBM</affiliation>
+ </author>
+ <author>
+ <name>Wu Chou</name>
+ <affiliation>Avaya</affiliation>
+ </author>
+ </authlist>
+ <status id='Status'>
+ <p>This is the First Public Working Draft.</p>
+ <p>
+ Publication as a Working Draft does not imply endorsement by the
+ W3C Membership. This is a draft document and can be updated, replaced
+ or obsoleted by other documents at any time. It is inappropriate to
+ cite this document as other than work in progress.
+ </p>
+ </status>
+ <abstract>
+ <p>
This specification describes a general SOAP-based protocol for accessing
XML representations of Web service-based resources.
</p>
- </abstract>
- <langusage>
- <language id="en">English</language>
- </langusage>
- <revisiondesc>
- <p>Last Modified: $Date$</p>
- </revisiondesc>
- </header>
- <body>
- <div1 id="intro">
- <head>Introduction</head>
- <p>
- This specification defines a mechanism for acquiring XML-based
- representations of entities using the Web service infrastructure.
- It defines two types of entities:
- </p>
+ </abstract>
+ <langusage>
+ <language id="en">English</language>
+ </langusage>
+ <revisiondesc>
+ <p>Last Modified: $Date$</p>
+ </revisiondesc>
+ </header>
- <ulist>
- <item>
- <p>
- Resources, which are entities addressable by an endpoint
- reference that provide an XML representation
- </p>
- </item>
- <item>
- <p>Resource factories, which are Web services that can create new
- resources</p>
- </item>
- </ulist>
+ <body>
+ <div1 id="composable">
+ <head>Composable Architecture</head>
- <p>
- Specifically, it defines two operations for sending and receiving the
- representation of a given resource and two operations for creating and
- deleting a resource and its corresponding representation.
- </p>
+ <p>
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p>
+ </div1>
- <p>
- Note that the state maintenance of a resource is at most
- subject to the "best efforts" of the hosting server. When a client
- receives the server's acceptance of a request to create or update a
- resource, it can reasonably expect that the resource now exists at
- the confirmed location and with the confirmed representation, but this
- is not a guarantee, even in the absence of any third parties. The
- server MAY change the representation of a resource, MAY remove a
- resource entirely, or MAY bring back a resource that was deleted.
- </p>
+ <div1 id="intro">
+ <head>Introduction</head>
+ <p>
+ This specification defines a mechanism for acquiring XML-based
+ representations of entities using the Web service infrastructure.
+ It defines two types of entities:
+ </p>
+ <ulist>
+ <item>
<p>
- For instance, the server might store resource state information on a
- disk drive. If that drive crashes and the server recovers state
- information from a backup tape, changes that occurred after the
- backup was made will be lost.
+ Resources, which are entities addressable by an endpoint
+ reference that provide an XML representation
</p>
-
+ </item>
+ <item>
<p>
- A server might have other operational processes that change resource
- state information. For example, a server could purge resources that
- have not been accessed for some period of time.
+ Resource factories, which are Web services that can create new
+ resources
</p>
+ </item>
+ </ulist>
- <p>
- In addition to this, there might be application or process specific
- reasons for a server to augment or transform the representation
- provided by an update or create operation. For example, the server
- might populate the optional properties of a newly created resource
- with meaningful default values.
- </p>
+ <p>
+ Specifically, it defines two operations for sending and receiving the
+ representation of a given resource and two operations for creating and
+ deleting a resource and its corresponding representation.
+ </p>
- <p>
- Finally all clients need to be aware that there might be other clients
- simultaneously accessing, creating, and updating the same resources.
- </p>
+ <p>
+ Note that the state maintenance of a resource is at most
+ subject to the "best efforts" of the hosting server. When a client
+ receives the server's acceptance of a request to create or update a
+ resource, it can reasonably expect that the resource now exists at
+ the confirmed location and with the confirmed representation, but this
+ is not a guarantee, even in the absence of any third parties. The
+ server MAY change the representation of a resource, MAY remove a
+ resource entirely, or MAY bring back a resource that was deleted.
+ </p>
- <p>
- In essence, the confirmation by a service of having processed a
- request to create, modify, or delete a resource implies a commitment
- only at the instant that the confirmation was generated. While the
- usual case is that resources are long-lived and stable, there are no
- guarantees, and clients are advised to code defensively.
- </p>
+ <p>
+ For instance, the server might store resource state information on a
+ disk drive. If that drive crashes and the server recovers state
+ information from a backup tape, changes that occurred after the
+ backup was made will be lost.
+ </p>
- <p>
- There is no requirement for uniformity in resource representations
- between the messages defined in this specification. For example, the
- representations used by Create or Put can differ from the representation
- returned by Get, depending on the semantic requirements of the service.
- Additionally, there is no requirement that the resource content is
- fixed for any given endpoint reference. The resource content can vary
- based on environmental factors, such as the security context, time
- of day, configuration, or the dynamic state of the service.
- </p>
+ <p>
+ A server might have other operational processes that change resource
+ state information. For example, a server could purge resources that
+ have not been accessed for some period of time.
+ </p>
- <div2 id="reqs">
- <head>Requirements</head>
- <p>This specification intends to meet the following requirements:</p>
- <ulist>
- <item>
- <p>Provide a SOAP-based protocol for managing resources and their
- representations.
- </p>
- </item>
- <item>
- <p>Minimize additional mechanism beyond the current Web Services
- architecture.
- </p>
- </item>
- </ulist>
- </div2>
- </div1>
- <div1 id="Notations_and_Terminology">
- <head>Terminology and Notation</head>
+ <p>
+ In addition to this, there might be application or process specific
+ reasons for a server to augment or transform the representation
+ provided by an update or create operation. For example, the server
+ might populate the optional properties of a newly created resource
+ with meaningful default values.
+ </p>
- <div2 id="conven">
- <head>Notational Conventions</head>
- <p>
- The keywords "MUST", "MUST NOT",
- "REQUIRED", "SHALL", "SHALL NOT",
- "SHOULD", "SHOULD NOT", "RECOMMENDED",
- "MAY", and "OPTIONAL" in this document are to be
- interpreted as described in RFC 2119
- <bibref ref="RFC2119"/>.
+ <p>
+ Finally all clients need to be aware that there might be other clients
+ simultaneously accessing, creating, and updating the same resources.
</p>
- <p>
- This specification uses the following syntax to define outlines for
- messages:
+
+ <p>
+ In essence, the confirmation by a service of having processed a
+ request to create, modify, or delete a resource implies a commitment
+ only at the instant that the confirmation was generated. While the
+ usual case is that resources are long-lived and stable, there are no
+ guarantees, and clients are advised to code defensively.
</p>
- <ulist>
- <item>
- <p>
- The syntax appears as an XML instance, but values in italics
- indicate data types instead of literal values.
+
+ <p>
+ There is no requirement for uniformity in resource representations
+ between the messages defined in this specification. For example, the
+ representations used by Create or Put can differ from the representation
+ returned by Get, depending on the semantic requirements of the service.
+ Additionally, there is no requirement that the resource content is
+ fixed for any given endpoint reference. The resource content can vary
+ based on environmental factors, such as the security context, time
+ of day, configuration, or the dynamic state of the service.
+ </p>
+
+ <div2 id="reqs">
+ <head>Requirements</head>
+ <p>
+ This specification intends to meet the following requirements:
+ </p>
+ <ulist>
+ <item>
+ <p>
+ Provide a SOAP-based protocol for managing resources and their
+ representations.
+ </p>
+ </item>
+ <item>
+ <p>
+ Minimize additional mechanism beyond the current Web Services
+ architecture.
+ </p>
+ </item>
+ </ulist>
+ </div2>
+ </div1>
+
+ <div1 id="Notations_and_Terminology">
+ <head>Terminology and Notation</head>
+
+ <div2 id="conven">
+ <head>Notational Conventions</head>
+ <p>
+ The keywords "MUST", "MUST NOT",
+ "REQUIRED", "SHALL", "SHALL NOT",
+ "SHOULD", "SHOULD NOT", "RECOMMENDED",
+ "MAY", and "OPTIONAL" in this document are to be
+ interpreted as described in RFC 2119
+ <bibref ref="RFC2119"/>.
</p>
- </item>
- <item>
- <p>
+ <p>
+ This specification uses the following syntax to define outlines for
+ messages:
+ </p>
+ <ulist>
+ <item>
+ <p>
+ The syntax appears as an XML instance, but values in italics
+ indicate data types instead of literal values.
+ </p>
+ </item>
+ <item>
+ <p>
Characters are appended to elements and attributes to indicate
cardinality:
</p>
@@ -462,7 +486,7 @@
<loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
</td>
<td>
- <bibref ref="SOAP121"/>
+ <bibref ref="SOAP12"/>
</td>
</tr>
<tr>
@@ -1985,7 +2009,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -d -r1.45 -r1.46
--- wsrt.xml 24 Feb 2010 15:04:01 -0000 1.45
+++ wsrt.xml 23 Apr 2010 15:31:51 -0000 1.46
@@ -87,16 +87,19 @@
</header>
<body>
-
- <div1 id="comp">
+ <div1 id="composable">
<head>Composable Architecture</head>
-
+
<p>
- The Web service specifications (WS-*) are designed to be
- composed with each other to provide a rich set of tools for the Web
- services environment. This specification relies on other Web service
- specifications to provide secure, reliable, and/or transacted message
- delivery and to express Web service metadata.
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
</p>
</div1>
@@ -158,7 +161,7 @@
<p>
Support a variety of encoding formats including (but not limited
to) both SOAP 1.1 <bibref ref="SOAP11"/> and
- SOAP 1.2 <bibref ref="SOAP121"/> Envelopes.
+ SOAP 1.2 <bibref ref="SOAP12"/> Envelopes.
</p>
</item>
</ulist>
@@ -455,7 +458,7 @@
<tr>
<td> s12 </td>
<td> http://www.w3.org/2003/05/soap-envelope </td>
- <td> <bibref ref="SOAP121"/> </td>
+ <td> <bibref ref="SOAP12"/> </td>
</tr>
<tr>
<td> wsa </td>
@@ -2758,7 +2761,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
@@ -3430,8 +3433,7 @@
</example>
<p>
- A non-normative copy of the XML Schema description is listed
- below for convenience.
+ A non-normative copy of the XML schema is listed below for convenience.
</p>
<example>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.179
retrieving revision 1.180
diff -u -d -r1.179 -r1.180
--- wseventing.html 21 Apr 2010 17:13:07 -0000 1.179
+++ wseventing.html 23 Apr 2010 15:31:51 -0000 1.180
@@ -99,7 +99,7 @@
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
- <a href="#SOAP121">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
@@ -158,7 +158,7 @@
</p></li><li><p>
Support a variety of encoding formats, including (but not
limited to) both SOAP 1.1 <a href="#SOAP11">[SOAP11]</a>
- and SOAP 1.2 <a href="#SOAP121">[SOAP12]</a> Envelopes.
+ and SOAP 1.2 <a href="#SOAP12">[SOAP12]</a> Envelopes.
</p></li></ul></div><div class="div2">
<h3><a name="Delivery" id="Delivery"/>2.2 Delivery</h3><p>
This specification defines a method for transmitting notifications
@@ -437,7 +437,7 @@
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/">
+ </a></td><td>SOAP 1.2 <a href="#SOAP12">[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
@@ -1715,7 +1715,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- wsenum.xml 21 Apr 2010 03:10:03 -0000 1.119
+++ wsenum.xml 23 Apr 2010 15:31:51 -0000 1.120
@@ -88,6 +88,21 @@
</header>
<body>
+ <div1 id="composable">
+ <head>Composable Architecture</head>
+
+ <p>
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p>
+ </div1>
<div1 id="intro">
<head>Introduction</head>
@@ -484,7 +499,7 @@
http://www.w3.org/2003/05/soap-envelope
</loc>
</td>
- <td> SOAP 1.2 <bibref ref="SOAP121"/> </td>
+ <td> SOAP 1.2 <bibref ref="SOAP12"/> </td>
</tr>
<tr>
<td> s11 </td>
@@ -2673,7 +2688,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- wsevd.xml 21 Apr 2010 03:10:03 -0000 1.10
+++ wsevd.xml 23 Apr 2010 15:31:51 -0000 1.11
@@ -86,13 +86,12 @@
</header>
<body>
-
<div1 id="composable">
<head>Composable Architecture</head>
<p>
By using the XML and SOAP <bibref ref="SOAP11"/>,
- <bibref ref="SOAP121"/>
+ <bibref ref="SOAP12"/>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
@@ -333,7 +332,7 @@
http://www.w3.org/2003/05/soap-envelope
</loc>
</td>
- <td>SOAP 1.2 <bibref ref="SOAP121"/></td>
+ <td>SOAP 1.2 <bibref ref="SOAP12"/></td>
</tr>
<tr>
<td>wsa</td>
@@ -782,7 +781,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -d -r1.61 -r1.62
--- wsfrag.xml 21 Apr 2010 03:10:03 -0000 1.61
+++ wsfrag.xml 23 Apr 2010 15:31:51 -0000 1.62
@@ -84,6 +84,22 @@
</header>
<body>
+ <div1 id="composable">
+ <head>Composable Architecture</head>
+
+ <p>
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p>
+ </div1>
+
<div1 id="intro">
<head>Introduction</head>
<p>
@@ -436,7 +452,7 @@
<loc href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</loc>
</td>
<td>
- <bibref ref="SOAP121"/>
+ <bibref ref="SOAP12"/>
</td>
</tr>
<tr>
@@ -2107,7 +2123,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- wsfrag.html 21 Apr 2010 03:10:03 -0000 1.63
+++ wsfrag.html 23 Apr 2010 15:31:51 -0000 1.64
@@ -40,40 +40,52 @@
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>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="#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/>
- 3.3 <a href="#Get">Get</a><br/>
- 3.4 <a href="#Put">Put</a><br/>
- 3.5 <a href="#Delete">Delete</a><br/>
- 3.6 <a href="#Create">Create</a><br/>
-4 <a href="#iddiv1_1_1404">Examples</a><br/>
- 4.1 <a href="#iddiv2_1_1407">Examples</a><br/>
-5 <a href="#QName">QName Expression Language</a><br/>
-6 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
-7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
-8 <a href="#Faults">Faults</a><br/>
- 8.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
- 8.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
- 8.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
-9 <a href="#metadata">WS-Fragment Metadata</a><br/>
- 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_2002">Normative References</a><br/>
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
+ 2.1 <a href="#reqs">Requirements</a><br/>
+3 <a href="#Notations_and_Terminology">Terminology and Notation</a><br/>
+ 3.1 <a href="#conven">Notational Conventions</a><br/>
+ 3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
+ 3.3 <a href="#terminology">Terminology</a><br/>
+ 3.4 <a href="#compliance">Compliance</a><br/>
+ 3.5 <a href="#namespaces">XML Namespaces</a><br/>
+4 <a href="#fragments">Fragment WS-Transfer Dialect</a><br/>
+ 4.1 <a href="#IdResSubset">Identification of a Resource Subset</a><br/>
+ 4.2 <a href="#FragSer">Fragment Serialization</a><br/>
+ 4.3 <a href="#Get">Get</a><br/>
+ 4.4 <a href="#Put">Put</a><br/>
+ 4.5 <a href="#Delete">Delete</a><br/>
+ 4.6 <a href="#Create">Create</a><br/>
+5 <a href="#iddiv1_1_1419">Examples</a><br/>
+ 5.1 <a href="#iddiv2_1_1422">Examples</a><br/>
+6 <a href="#QName">QName Expression Language</a><br/>
+7 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
+8 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
+9 <a href="#Faults">Faults</a><br/>
+ 9.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
+ 9.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
+ 9.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
+10 <a href="#metadata">WS-Fragment Metadata</a><br/>
+ 10.1 <a href="#iddiv2_1_1954">Fragment Assertion</a><br/>
+11 <a href="#acks">Acknowledgements</a><br/>
+12 <a href="#refs">References</a><br/>
+ 12.1 <a href="#iddiv2_1_2017">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/>
</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"/>1 Introduction</h2><p>
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
+ By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p></div><div class="div1">
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
This specification extends the WS-Transfer specification and defines
a mechanism that allows clients to retrieve and manipulate subsets
(parts or fragments)
@@ -98,7 +110,7 @@
it is RECOMMENDED that those languages
reuse the fragment transfer framework that this specification defines.
</p><div class="div2">
-<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>
+<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>
Provide an extension mechanism to WS-Transfer that allows for
subsets (parts or fragments) of a resource to be retrieved or modified.
</p></li><li><p>
@@ -107,8 +119,8 @@
Provide a set of expression languages that implementations
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="conven" id="conven"/>2.1 Notational Conventions</h3><p>
+<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>3 Terminology and Notation</h2><div class="div2">
+<h3><a name="conven" id="conven"/>3.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",
@@ -137,7 +149,7 @@
</p></li><li><p>
Ellipsis (i.e. "...") indicate points of extensibility.
</p></li><li><p>
- XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used
+ XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
to indicate the namespace of the element being defined.
</p></li></ul><p>
In addition to Message Information Header properties
@@ -170,7 +182,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.2 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
@@ -192,17 +204,17 @@
Extension elements and attributes MUST NOT use the Web Services
Fragment namespace URI.
</p></div><div class="div2">
-<h3><a name="terminology" id="terminology"/>2.3 Terminology</h3><dl><dt class="label">Expression</dt><dd><p>
+<h3><a name="terminology" id="terminology"/>3.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>
+<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>2.5 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
@@ -221,18 +233,18 @@
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>
+<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-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
+ </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 3-1</a> lists XML namespaces that are
used in this specification. The
choice of any namespace prefix is arbitrary and not semantically
significant.
- </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><caption>Table 2-1:
+ </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><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> 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>
+ </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="#SOAP12">[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
@@ -250,7 +262,7 @@
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>
+<h2><a name="fragments" id="fragments"/>4 Fragment WS-Transfer Dialect</h2><p>
This section defines the fragment transfer mechanism that the expression
languages defined in subsequent sections will use.
The following sections define the expected behavior when the WS-Fragment
@@ -262,7 +274,7 @@
perform such operations. This specification only extends but does
not modify the base WS-Transfer behavior.
</p><div class="div2">
-<h3><a name="IdResSubset" id="IdResSubset"/>3.1 Identification of a Resource Subset</h3><p>
+<h3><a name="IdResSubset" id="IdResSubset"/>4.1 Identification of a Resource Subset</h3><p>
The WS-Fragment Dialect is used to identify a portion of a resource
representation to update. The WS-Transfer Get and Put operations have
an Expression that allows a requester to specify which subset of the
@@ -299,7 +311,7 @@
For the purposes of this specification, attributes are treated as
single strings - multi-value attributes are not supported.
</p></div><div class="div2">
-<h3><a name="FragSer" id="FragSer"/>3.2 Fragment Serialization</h3><p>
+<h3><a name="FragSer" id="FragSer"/>4.2 Fragment Serialization</h3><p>
When using the WS-Fragment Dialect, subsets of resource representations
are serialized into the Get response and Put request messages. To
ensure that the receiver of those messages can unambiguously parse the
@@ -369,7 +381,7 @@
prefixes. For example, use an expression such as
"/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
</p></div><div class="div2">
-<h3><a name="Get" id="Get"/>3.3 Get</h3><p>
+<h3><a name="Get" id="Get"/>4.3 Get</h3><p>
To retrieve a subset of a resource
a client MUST specify the WS-Fragment Dialect IRI in the wst:Get request.
</p><p>
@@ -423,7 +435,7 @@
Other components of the outline above are not further constrained
by this specification.
</p></div><div class="div2">
-<h3><a name="Put" id="Put"/>3.4 Put</h3><p>
+<h3><a name="Put" id="Put"/>4.4 Put</h3><p>
To update a subset of a resource a client MUST specify the WS-Fragment
IRI in the wst:Put request.
</p><p>
@@ -549,7 +561,7 @@
default value.
</p><p>
The children of this element MUST be serialized according to the
- rules defined in <a href="#FragSer"><b>3.2 Fragment Serialization</b></a>.
+ rules defined in <a href="#FragSer"><b>4.2 Fragment Serialization</b></a>.
</p></dd></dl><p>
If the resource accepts a Put request, it MUST reply with a response of
the following form:
@@ -575,16 +587,16 @@
Note: for the sake of clarity, some element names have a ' or " to
indicate that it is a different instance of that type of element.
</p><table border="1"><tbody><tr><td>Initial Representation</td><td>@Mode</td><td>Expression</td><td>Value</td><td>Final Represenation</td></tr><tr><td/><td>Add</td><td>/</td><td><a/></td><td><a/></td></tr><tr><td/><td>Replace</td><td>/</td><td><a/></td><td><a/></td></tr><tr><td><a/></td><td>Add</td><td>/</td><td><a'/></td><td>fault</td></tr><tr><td><a/></td><td>Replace</td><td>/a</td><td><a'/></td><td><a'/></td></tr><tr><td><a/></td><td>Add</td><td>/a</td><td><wsf:AttributeNode name="foo">1</wsf:AttributeNode></td><td><a foo="1"/></td></tr><tr><td><a foo="1"/></td><td>Add</td><td>/a</td><td><wsf:AttributeNode name="foo">2</wsf:AttributeNode></td><td>fault</td></tr><tr><td><a foo="1"/></td><td>Replace</td><td>/a@foo</td><td><wsf:AttributeNode name="foo">2</wsf:AttributeNode></td><td><a foo="2"/></td></tr><tr><td><a foo="1"/></td><td>Replace</td><td>/a@foo</td><td><wsf:AttribueNode name="bar">2</wsf:AttributeNode></td><td><a bar="2"/></td></tr><tr><td><a/></td><td>Replace</td><td>/a@foo</td><td><wsf:AttributeNode name="bar">2</wsf:AttributeNode></td><td><a bar="2"/></td></tr><tr><td><a foo="1"/></td><td>Remove</td><td>/a@foo</td><td/><td><a/></td></tr><tr><td><a/></td><td>Add</td><td>/a</td><td><b/></td><td><a> <b/> </a></td></tr><tr><td><a> <b/> </a></td><td>Add</td><td>/a</td><td><b'/></td><td><a> <b/> <b'/> </a></td></tr><tr><td><a> <b/> </a></td><td>Replace</td><td>/a/b</td><td><b'/></td><td><a> <b'/> </a></td></tr><tr><td><a/></td><td>Replace</td><td>/a/b</td><td><b/></td><td><a> <b/> </a></td></tr><tr><td><a> <b/> <b'> </a></td><td>InsertAfter</td><td>/a/b or /a/b[last()]</td><td><b"/></td><td><a> <b/> <b'> <b"/> </a></td></tr><tr><td><a> <b/> <b'> </a></td><td>InsertBefore</td><td>/a/b or /a/b[1]</td><td><b"/></td><td><a> <b"/> <b> <b'/> </a></td></tr><tr><td><a> <b/> <b'> </a></td><td>Replace</td><td>/a/b</td><td><b"/></td><td><a> <b"/> </a></td></tr><tr><td><a> <b/> <b'> </a></td><td>Replace</td><td>/a/b[1]</td><td><b"/></td><td><a> <b"/> <b'> </a></td></tr><tr><td><a> <b/> </a></td><td>Remove</td><td>/a/b</td><td/><td><a/></td></tr><tr><td><a> <b/> <b'> </a></td><td>Remove</td><td>/a/b</td><td/><td><a/></td></tr><tr><td><a> <b/> <b'> </a></td><td>Remove</td><td>/a/b[1]</td><td/><td><a> <b'> </a></td></tr><tr><td><a> <b/> <b'> </a></td><td>Replace</td><td>/a/b</td><td><c/></td><td><a> <c> </a></td></tr></tbody></tabl></div><div class="div2">
-<h3><a name="Delete" id="Delete"/>3.5 Delete</h3><p>
+<h3><a name="Delete" id="Delete"/>4.5 Delete</h3><p>
This specification does not extend the Delete operation defined in
WS-Transfer.
</p></div><div class="div2">
-<h3><a name="Create" id="Create"/>3.6 Create</h3><p>
+<h3><a name="Create" id="Create"/>4.6 Create</h3><p>
This specification does not extend the Create operation defined in
WS-Transfer.
</p></div></div><div class="div1">
-<h2><a name="iddiv1_1_1404" id="iddiv1_1_1404"/>4 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_1407" id="iddiv2_1_1407"/>4.1 Examples</h3><p>
+<h2><a name="iddiv1_1_1419" id="iddiv1_1_1419"/>5 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_1422" id="iddiv2_1_1422"/>5.1 Examples</h3><p>
In the following examples, and Expression Language definitions,
the following representation of a resource is used for
informational purposes:
@@ -670,7 +682,7 @@
</wst:GetResponse>
</s:Body>
</s:Envelope></pre></div></div></div></div><div class="div1">
-<h2><a name="QName" id="QName"/>5 QName Expression Language</h2><p>
+<h2><a name="QName" id="QName"/>6 QName Expression Language</h2><p>
The QName expression language is a syntax for expressions that
uses a single QName to reference the immediate children of the root
element of
@@ -682,7 +694,7 @@
</p><p>
The QName language MUST be indicated by using the IRI:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/QName">http://www.w3.org/2002/ws/ra/edcopies/ws-fra/QName</a></pre></div></div></div><div class="div1">
-<h2><a name="XPathL1" id="XPathL1"/>6 XPath Level 1 Expression Language</h2><p>
+<h2><a name="XPathL1" id="XPathL1"/>7 XPath Level 1 Expression Language</h2><p>
The XPath Level 1 expression language uses an XPath to
reference specific fragments of the resource representation. The XPath is
logically applied to the XML representation of the resource and the
@@ -818,7 +830,7 @@
</p><p>
The XPath Level 1 language does not support computed values.
</p></div><div class="div1">
-<h2><a name="XPath10" id="XPath10"/>7 XPath 1.0 Expression Language</h2><p>
+<h2><a name="XPath10" id="XPath10"/>8 XPath 1.0 Expression Language</h2><p>
The XPath 1.0 expression language uses an XPath to reference specific
fragments of the resource representation. The XPath is logically
applied to the XML representation of the resource and the result of
@@ -848,7 +860,7 @@
The serialization and context rules defined by the XPath Level 1
language apply to the XPath 1.0 language as well.
</p></div><div class="div1">
-<h2><a name="Faults" id="Faults"/>8 Faults</h2><p>
+<h2><a name="Faults" id="Faults"/>9 Faults</h2><p>
All fault messages defined in this specification MUST be sent
according to the rules and usage described in
<a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
@@ -896,14 +908,14 @@
</s11:Fault>
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
-<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
+<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>9.1 UnsupportedLanguage</h3><p>
This fault MUST be generated when a service detects an unknown or
unsupported Language
IRI in a request message.
</p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnsupportedLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
The specified Language IRI is not supported.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Language IRI.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidExpression" id="InvalidExpression"/>8.2 InvalidExpression</h3><p>
+<h3><a name="InvalidExpression" id="InvalidExpression"/>9.2 InvalidExpression</h3><p>
This fault MUST be generated when a service determines that the Language
expression specified in a request does not conform to the syntax
of the language specified in the Language attribute or is semantically
@@ -911,20 +923,20 @@
</p><a name="Table5" id="Table5"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidExpression</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
The specified Language expression is invalid.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnsupportedMode" id="UnsupportedMode"/>8.3 UnsupportedMode</h3><p>
+<h3><a name="UnsupportedMode" id="UnsupportedMode"/>9.3 UnsupportedMode</h3><p>
This fault MUST be generated when a service detects a Mode in a Put
request that is not supported.
</p><a name="Table6" id="Table6"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnsupportedMode</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
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>
+<h2><a name="metadata" id="metadata"/>10 WS-Fragment Metadata</h2><p>
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>
+<h3><a name="iddiv2_1_1954" id="iddiv2_1_1954"/>10.1 Fragment Assertion</h3><p>
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 -
@@ -957,7 +969,7 @@
Any metadata that appears is scoped to the operations and features
of the WS-Fragment specification.
</p></dd></dl></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>11 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
@@ -987,8 +999,8 @@
Wu Chou (Avaya Communications),
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_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>
+<h2><a name="refs" id="refs"/>12 References</h2><div class="div2">
+<h3><a name="iddiv2_1_2017" id="iddiv2_1_2017"/>12.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.
@@ -1008,7 +1020,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Index: wssa.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- wssa.xml 21 Apr 2010 18:05:31 -0000 1.4
+++ wssa.xml 23 Apr 2010 15:31:52 -0000 1.5
@@ -87,7 +87,20 @@
</header>
<body>
- <div1 id="Introduction">
+ <div1 id="composable">
+ <head>Composable Architecture</head>
+
+ <p>
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment.
+ </p>
+ </div1>
+
+ <div1 id="intro">
<head>Introduction</head>
<p>
@@ -103,7 +116,7 @@
<p>
However, one key aspect of the message exchanges is whether either
endpoint requires the use of SOAP 1.1 <bibref ref="SOAP11"/>
- or SOAP 1.2 <bibref ref="SOAP121"/>. While this information might be
+ or SOAP 1.2 <bibref ref="SOAP12"/>. While this information might be
obtainable through examination of a WSDL <bibref ref="WSDL11"/>
document, or implied through some out of band knowledge, there is no
way to make this determination during the application of the policy
@@ -286,7 +299,7 @@
<tr>
<td> s12 </td>
<td> http://www.w3.org/2003/05/soap-envelope </td>
- <td> <bibref ref="SOAP121"/> </td>
+ <td> <bibref ref="SOAP12"/> </td>
</tr>
<tr>
<td> wsa </td>
@@ -508,7 +521,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
@@ -602,8 +615,7 @@
</example>
<p>
- A non-normative copy of the XML Schema description is listed below for
- convenience.
+ A non-normative copy of the XML schema is listed below for convenience.
</p>
<example>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- wsmex.xml 21 Apr 2010 03:10:03 -0000 1.104
+++ wsmex.xml 23 Apr 2010 15:31:51 -0000 1.105
@@ -91,19 +91,23 @@
</header>
<body>
- <div1 id="Composable">
+ <div1 id="composable">
<head>Composable Architecture</head>
<p>
- The Web services specifications (WS-*) are designed to be composed with
- each other to provide a rich set of tools for the Web services
- environment. This specification specifically relies on other Web
- services specifications to provide secure, reliable, and/or transacted
- message delivery and to express Web service metadata.
+ By using the XML, SOAP <bibref ref="SOAP11"/>,
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
</p>
</div1>
- <div1 id="Introduction">
+ <div1 id="intro">
<head>Introduction</head>
<p>
@@ -754,7 +758,7 @@
<tr>
<td> s12 </td>
<td> http://www.w3.org/2003/05/soap-envelope </td>
- <td> <bibref ref="SOAP121"/> </td>
+ <td> <bibref ref="SOAP12"/> </td>
</tr>
<tr>
<td> wsa </td>
@@ -783,7 +787,7 @@
</tr>
<tr>
<td> wssa </td>
- <td> http://www.w3.org/&wssa.nsprefix;/ws-sa </td>
+ <td> http://www.w3.org/&wssas.nsprefix;/ws-sa </td>
<td> <bibref ref="WS-SOAPAssertions"/> </td>
</tr>
<tr>
@@ -2635,7 +2639,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
@@ -2796,8 +2800,7 @@
</example>
<p>
- A non-normative copy of the XML Schema description is listed below for
- convenience.
+ A non-normative copy of the XML schema is listed below for convenience.
</p>
<example>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.128
retrieving revision 1.129
diff -u -d -r1.128 -r1.129
--- wsenum.html 21 Apr 2010 03:10:03 -0000 1.128
+++ wsenum.html 23 Apr 2010 15:31:51 -0000 1.129
@@ -40,47 +40,59 @@
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
- 1.1 <a href="#reqs">Requirements</a><br/>
-2 <a href="#termsNotes">Notations and Terminology</a><br/>
- 2.1 <a href="#conv">Notational Conventions</a><br/>
- 2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</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/>
- 3.3 <a href="#Renew">Renew</a><br/>
- 3.4 <a href="#GetStatus">GetStatus</a><br/>
- 3.5 <a href="#Release">Release</a><br/>
- 3.6 <a href="#EnumerationEnd">EnumerationEnd</a><br/>
-4 <a href="#Faults">Faults</a><br/>
- 4.1 <a href="#InvalidExpirationTime">InvalidExpirationTime</a><br/>
- 4.2 <a href="#ExpirationTimeExceeded">ExpirationTimeExceeded</a><br/>
- 4.3 <a href="#UnsupportedExpirationTime">UnsupportedExpirationTime</a><br/>
- 4.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br/>
- 4.5 <a href="#FilterDialectRequestedUnavailable">FilterDialectRequestedUnavailable</a><br/>
- 4.6 <a href="#CannotProcessFilter">CannotProcessFilter</a><br/>
- 4.7 <a href="#InvalidEnumerationContext">InvalidEnumerationContext</a><br/>
- 4.8 <a href="#TimedOut">TimedOut</a><br/>
- 4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
- 4.10 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
- 4.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
-5 <a href="#Security">Security Considerations</a><br/>
-6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_2023">Enumeration Assertion</a><br/>
-7 <a href="#acks">Acknowledgements</a><br/>
-8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2130">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2316">Informative References</a><br/>
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
+ 2.1 <a href="#reqs">Requirements</a><br/>
+3 <a href="#termsNotes">Notations and Terminology</a><br/>
+ 3.1 <a href="#conv">Notational Conventions</a><br/>
+ 3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</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="#EnumMsgs">Enumeration Messages</a><br/>
+ 4.1 <a href="#Enumerate">Enumerate</a><br/>
+ 4.2 <a href="#Pull">Pull</a><br/>
+ 4.3 <a href="#Renew">Renew</a><br/>
+ 4.4 <a href="#GetStatus">GetStatus</a><br/>
+ 4.5 <a href="#Release">Release</a><br/>
+ 4.6 <a href="#EnumerationEnd">EnumerationEnd</a><br/>
+5 <a href="#Faults">Faults</a><br/>
+ 5.1 <a href="#InvalidExpirationTime">InvalidExpirationTime</a><br/>
+ 5.2 <a href="#ExpirationTimeExceeded">ExpirationTimeExceeded</a><br/>
+ 5.3 <a href="#UnsupportedExpirationTime">UnsupportedExpirationTime</a><br/>
+ 5.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br/>
+ 5.5 <a href="#FilterDialectRequestedUnavailable">FilterDialectRequestedUnavailable</a><br/>
+ 5.6 <a href="#CannotProcessFilter">CannotProcessFilter</a><br/>
+ 5.7 <a href="#InvalidEnumerationContext">InvalidEnumerationContext</a><br/>
+ 5.8 <a href="#TimedOut">TimedOut</a><br/>
+ 5.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
+ 5.10 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
+ 5.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
+6 <a href="#Security">Security Considerations</a><br/>
+7 <a href="#metadata">WS-Enumeration Metadata</a><br/>
+ 7.1 <a href="#iddiv2_1_2038">Enumeration Assertion</a><br/>
+8 <a href="#acks">Acknowledgements</a><br/>
+9 <a href="#refs">References</a><br/>
+ 9.1 <a href="#iddiv2_1_2145">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_2331">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
C <a href="#actiontables">Action Tables</a><br/>
D <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"/>1 Introduction</h2><p>
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
+ By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p></div><div class="div1">
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
There are numerous applications for which a
simple single-request/single-reply metaphor is insufficient for
transferring large data sets over SOAP. Applications that do not
@@ -139,7 +151,7 @@
items that are returned in a Pull response are removed from the
queue.
</p><div class="div2">
-<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>
+<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>
This specification intends to meet the following requirements:
</p><ul><li><p>
Support enumeration of data sources
@@ -152,12 +164,12 @@
Minimize additional mechanism
beyond the current web service architecture.
</p></li></ul></div></div><div class="div1">
-<h2><a name="termsNotes" id="termsNotes"/>2 Notations and Terminology</h2><p>
+<h2><a name="termsNotes" id="termsNotes"/>3 Notations and Terminology</h2><p>
This section specifies the notations,
namespaces, and terminology used in this
specification.
</p><div class="div2">
-<h3><a name="conv" id="conv"/>2.1 Notational Conventions</h3><p>
+<h3><a name="conv" id="conv"/>3.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as described
@@ -190,7 +202,7 @@
</p></li><li><p>
Ellipsis (i.e. "...") indicate points of extensibility.
</p></li><li><p>
- XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used
+ XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
to indicate the namespace of the element being
defined.
</p></li></ul><p>
@@ -220,7 +232,7 @@
security concerns - in these situations the fault MAY NOT
be transmitted.
</p></div><div class="div2">
-<h3><a name="extensions" id="extensions"/>2.2 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
@@ -242,7 +254,7 @@
Extension elements and attributes MUST NOT use the Web Services
Enumeration namespace URI.
</p></div><div class="div2">
-<h3><a name="terms" id="terms"/>2.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
+<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
The Web service that is requesting the data
enumeration from the data source
</p></dd><dt class="label"> Data Source </dt><dd><p>
@@ -255,11 +267,11 @@
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>
+<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>2.5 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
@@ -278,19 +290,19 @@
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>
+<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-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
+ </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 3-1</a> lists XML namespaces that are used in
this specification. The choice of any namespace prefix is arbitrary
and not semantically significant.
- </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1"><caption>Table 2-1:
+ </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1"><caption>Table 3-1:
Prefixes and XML namespaces used in this specification
</caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-enu">
http://www.w3.org/2002/ws/ra/edcopies/ws-enu
</a></td><td> This specification </td></tr><tr><td> s </td><td><a href="http://www.w3.org/2003/05/soap-envelope">
http://www.w3.org/2003/05/soap-envelope
- </a></td><td> SOAP 1.2 <a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
+ </a></td><td> SOAP 1.2 <a href="#SOAP12">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
http://schemas.xmlsoap.org/soap/envelope/
</a></td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">
http://www.w3.org/2005/08/addressing
@@ -316,7 +328,7 @@
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div></div><div class="div1">
-<h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
+<h2><a name="EnumMsgs" id="EnumMsgs"/>4 Enumeration Messages</h2><p>
Enumeration contexts represent a specific
traversal through a sequence of XML information items. An Enumerate
operation can be used to establish an enumeration context from a
@@ -372,7 +384,7 @@
MUST NOT issue any more WS-Enumeration request messages referencing
that enumeration context.
</p><div class="div2">
-<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
+<h3><a name="Enumerate" id="Enumerate"/>4.1 Enumerate</h3><p>
This specification defines the Enumerate operation to start an enumeration.
This operation MUST be supported by compliant data sources.
</p><p>
@@ -399,7 +411,7 @@
This OPTIONAL element denotes where to send
an EnumerationEnd message if the enumeration is terminated
unexpectedly
- (see <a href="#EnumerationEnd"><b>3.6 EnumerationEnd</b></a>).
+ (see <a href="#EnumerationEnd"><b>4.6 EnumerationEnd</b></a>).
If present, this element MUST
be of type wsa:EndpointReferenceType. Default is to not send this
message. The endpoint to which the EndTo EPR
@@ -594,9 +606,9 @@
consumer is REQUIRED to pass this XML data in Pull requests for
this enumeration context, until and unless a PullResponse or
RenewResponse message updates the enumeration context.
- </p></dd></dl><p><a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
+ </p></dd></dl><p><a href="#enumReq">Example 4-1</a> lists a sample Enumerate request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 4-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:wsen="http://www.w3.org/2002/ws/ra/edcopies/ws-enu">
(04) <s:Header>
@@ -619,7 +631,7 @@
(21) </wsen:Enumerate>
(22) </s:Body>
(23) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#enumReq">Example 3-1</a> indicate this message
+ Lines (05-07) in <a href="#enumReq">Example 4-1</a> indicate this message
is an Enumerate request and that the data source is expected to
respond with an Enumerate response message. The wsen:Expires
element on line (20) indicates that the consumer would like an
@@ -628,10 +640,10 @@
period. No wsen:Filter element is present, so the resultant
enumeration context is expected to return all available
elements.
- </p><p><a href="#enumRes">Example 3-2</a> lists a response to the request in
- <a href="#enumReq">Example 3-1</a>.
+ </p><p><a href="#enumRes">Example 4-2</a> lists a response to the request in
+ <a href="#enumReq">Example 4-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumRes" id="enumRes"/>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
+<div class="exampleHeader"><a name="enumRes" id="enumRes"/>Example 4-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
(02) xmlns:wsen='http://www.w3.org/2002/ws/ra/edcopies/ws-enu'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'>
(04) <s:Header>
@@ -654,14 +666,14 @@
(21) </wsen:EnumerateResponse>
(22) </s:Body>
(23) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#enumRes">Example 3-2</a> indicate this message
+ Lines (05-07) in <a href="#enumRes">Example 4-2</a> indicate this message
is an Enumerate response message. Line (17) indicates that the data
source has actually created an enumeration context with a lifetime
of 15 minutes. Lines (18-20) are the XML representation of the
enumeration context that supports the Pull operation defined
below.
</p></div><div class="div2">
-<h3><a name="Pull" id="Pull"/>3.2 Pull</h3><p>
+<h3><a name="Pull" id="Pull"/>4.2 Pull</h3><p>
The Pull operation is initiated by sending a Pull request message to
the data source.
This operation MUST be supported by compliant data sources.
@@ -780,9 +792,9 @@
wsen:EnumerationContext and wsen:EndOfSequence MUST NOT both
appear; neither can appear, or one without the other, but not both
in the same PullResponse.
- </p><p><a href="#pullReq">Example 3-3</a> lists a Pull request.
+ </p><p><a href="#pullReq">Example 4-3</a> lists a Pull request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullReq" id="pullReq"/>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullReq" id="pullReq"/>Example 4-3: Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:wsen="http://www.w3.org/2002/ws/ra/edcopies/ws-enu">
(04) <s:Header>
@@ -807,17 +819,17 @@
(23) </wsen:Pull>
(24) </s:Body>
(25) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#pullReq">Example 3-3</a> indicate this message
+ Lines (05-07) in <a href="#pullReq">Example 4-3</a> indicate this message
is a Pull request and that the data source is expected to respond
with a Pull response message. Line (21) indicates that the response
message SHOULD be generated no more than 30 seconds after receipt
of the Pull request message. Line (22) indicates that no more than
10 elements can be returned in the body of the Pull response
message.
- </p><p><a href="#pullRes">Example 3-4</a> lists a response to the request in
- <a href="#pullReq">Example 3-3</a>.
+ </p><p><a href="#pullRes">Example 4-4</a> lists a response to the request in
+ <a href="#pullReq">Example 4-3</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullRes" id="pullRes"/>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullRes" id="pullRes"/>Example 4-4: Response to Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsen="http://www.w3.org/2002/ws/ra/edcopies/ws-enu"
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing">
(04) <s:Header>
@@ -844,13 +856,13 @@
(25) </wsen:PullResponse>
(26) </s:Body>
(27) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#pullRes">Example 3-4</a> indicate this message
+ Lines (05-07) in <a href="#pullRes">Example 4-4</a> indicate this message
is a Pull response message. Lines (18-22) are the five elements
returned by this Pull request. The presence of a wsen:EndOfSequence
element (line (24)) indicates that no more elements are available
and that the enumeration context is now invalid.
</p></div><div class="div2">
-<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
+<h3><a name="Renew" id="Renew"/>4.3 Renew</h3><p>
To update, or renew, the expiration for an enumeration, a Renew
request message is sent to the data source.
This operation MUST be supported by compliant data sources.
@@ -870,7 +882,7 @@
</wsen:Renew></pre></div></div><p>
Components of the outline listed above are
additionally constrained as for a request to create an enumeration
- (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>) with the following
+ (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>) with the following
addition(s):
</p><dl><dt class="label"><b>[Body]</b>/wsen:Renew/wsen:EnumerationContext </dt><dd><p>
This REQUIRED element contains the XML data
@@ -895,7 +907,7 @@
</wsen:RenewResponse></pre></div></div><p>
Components of the outline listed above are
constrained as for a response to an Enumerate request
- (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>) with the following addition:
+ (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>) with the following addition:
</p><dl><dt class="label"><b>[Body]</b>/wsen:RenewResponse/wsen:EnumerationContext
</dt><dd><p>
This element is OPTIONAL in this response.
@@ -908,7 +920,7 @@
Other components of the outline above are not
further constrained by this specification.
</p></div><div class="div2">
-<h3><a name="GetStatus" id="GetStatus"/>3.4 GetStatus</h3><p>
+<h3><a name="GetStatus" id="GetStatus"/>4.4 GetStatus</h3><p>
To get the status of an enumeration, the
consumer sends a GetStatus request message to the data source.
This operation MUST be supported by compliant data sources.
@@ -923,7 +935,7 @@
</wsen:GetStatus></pre></div></div><p>
Components of the outline listed above are
additionally constrained as for a request to renew an enumeration
- (see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are
+ (see <a href="#Renew"><b>4.3 Renew</b></a>). Other components of the outline above are
not further constrained by this specification.
</p><p>
If the enumeration is valid the data source MUST reply with a
@@ -940,7 +952,7 @@
</wsen:GetStatusResponse></pre></div></div><p>
Components of the outline listed above are
constrained as for a response to a renew request
- (see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are
+ (see <a href="#Renew"><b>4.3 Renew</b></a>). Other components of the outline above are
not further constrained by this specification.
</p><p>
This operation is safe; it will not result in any side effect
@@ -948,7 +960,7 @@
protocol error that might get unnoticed, resending the same request
can be done automatically.
</p></div><div class="div2">
-<h3><a name="Release" id="Release"/>3.5 Release</h3><p>
+<h3><a name="Release" id="Release"/>4.5 Release</h3><p>
The Release operation is initiated by sending a
Release request message to the data source.
This operation MUST be supported by compliant data sources.
@@ -981,9 +993,9 @@
<b>[Body]</b>
<wsen:ReleaseResponse ...>
<em>xs:any</em>*
- </wsen:ReleaseResponse></pre></div></div><p><a href="#releaseReq">Example 3-5</a> lists a Release request.
+ </wsen:ReleaseResponse></pre></div></div><p><a href="#releaseReq">Example 4-5</a> lists a Release request.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseReq" id="releaseReq"/>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseReq" id="releaseReq"/>Example 4-5: Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:wsen="http://www.w3.org/2002/ws/ra/edcopies/ws-enu">
(04) <s:Header>
@@ -1006,13 +1018,13 @@
(21) </wsen:Release>
(22) </s:Body>
(23) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#releaseReq">Example 3-5</a> indicate this message
+ Lines (05-07) in <a href="#releaseReq">Example 4-5</a> indicate this message
is a Release request.
Line (20) identifies the enumeration context to be released.
- </p><p><a href="#releaseRes">Example 3-6</a> lists a response to the request in
- <a href="#releaseReq">Example 3-5</a>.
+ </p><p><a href="#releaseRes">Example 4-6</a> lists a response to the request in
+ <a href="#releaseReq">Example 4-5</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseRes" id="releaseRes"/>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseRes" id="releaseRes"/>Example 4-6: Response to Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsen="http://www.w3.org/2002/ws/ra/edcopies/ws-enu"
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing">
(04) <s:Header>
@@ -1030,13 +1042,13 @@
(16) <wsen:ReleaseResponse/>
(17) </s:Body>
(18) </s:Envelope></pre></div></div><p>
- Lines (05-07) in <a href="#releaseRes">Example 3-6</a> indicate this message
+ Lines (05-07) in <a href="#releaseRes">Example 4-6</a> indicate this message
is a Release response message.
</p></div><div class="div2">
-<h3><a name="EnumerationEnd" id="EnumerationEnd"/>3.6 EnumerationEnd</h3><p>
+<h3><a name="EnumerationEnd" id="EnumerationEnd"/>4.6 EnumerationEnd</h3><p>
If the data source terminates an enumeration unexpectedly, and it
supports the use of the EndTo EPR, and the EndTo EPR was present in the
- Enumerate message for that enumeration (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>),
+ Enumerate message for that enumeration (see <a href="#Enumerate"><b>4.1 Enumerate</b></a>),
the EnumerationEnd message MUST be sent to the endpoint reference
indicated by that EPR.
</p><p>
@@ -1084,7 +1096,7 @@
Other components of the outline above are not
further constrained by this specification.
</p></div></div><div class="div1">
-<h2><a name="Faults" id="Faults"/>4 Faults</h2><p>
+<h2><a name="Faults" id="Faults"/>5 Faults</h2><p>
All fault messages defined in this specification MUST be sent
according to the rules and usage described in
<a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
@@ -1132,30 +1144,30 @@
</s11:Fault>
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
-<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>4.1 InvalidExpirationTime</h3><p>
+<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>5.1 InvalidExpirationTime</h3><p>
This fault MUST be generated when a request specified an expiration that
is malformed.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:InvalidExpirationTime </td></tr><tr><td><b>[Reason]</b></td><td>
Invalid expiration time.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="ExpirationTimeExceeded" id="ExpirationTimeExceeded"/>4.2 ExpirationTimeExceeded</h3><p>
+<h3><a name="ExpirationTimeExceeded" id="ExpirationTimeExceeded"/>5.2 ExpirationTimeExceeded</h3><p>
This fault MUST be generated when a request specifies an
expiration that is not within the min/max range.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:ExpirationTimeExceeded </td></tr><tr><td><b>[Reason]</b></td><td>
The expiration time requested is not within the min/max range.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="UnsupportedExpirationTime" id="UnsupportedExpirationTime"/>4.3 UnsupportedExpirationTime</h3><p>
+<h3><a name="UnsupportedExpirationTime" id="UnsupportedExpirationTime"/>5.3 UnsupportedExpirationTime</h3><p>
This fault MUST be generated when the Enumerate expiration time that is
specified is not a duration.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:UnsupportedExpirationTime </td></tr><tr><td><b>[Reason]</b></td><td>
Unsupported expiration time.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>4.4 FilteringNotSupported</h3><p>
+<h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>5.4 FilteringNotSupported</h3><p>
This fault MUST generated when the data source does not support filters.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:FilteringNotSupported </td></tr><tr><td><b>[Reason]</b></td><td>
Filtering not supported.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="FilterDialectRequestedUnavailable" id="FilterDialectRequestedUnavailable"/>4.5 FilterDialectRequestedUnavailable</h3><p>
+<h3><a name="FilterDialectRequestedUnavailable" id="FilterDialectRequestedUnavailable"/>5.5 FilterDialectRequestedUnavailable</h3><p>
This fault MUST be generated when the data source does not support
the requested filter dialect.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:FilterDialectRequestedUnavailable </td></tr><tr><td><b>[Reason]</b></td><td>
@@ -1164,13 +1176,13 @@
<wsen:SupportedDialect> +
<br/><em>OPTIONAL; repeating; one per filter dialect supported by the
receiver</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="CannotProcessFilter" id="CannotProcessFilter"/>4.6 CannotProcessFilter</h3><p>
+<h3><a name="CannotProcessFilter" id="CannotProcessFilter"/>5.6 CannotProcessFilter</h3><p>
This fault MUST be generated when the data source can not process the
filter content.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:CannotProcessFilter </td></tr><tr><td><b>[Reason]</b></td><td>
Cannot filter as requested.
</td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidEnumerationContext" id="InvalidEnumerationContext"/>4.7 InvalidEnumerationContext</h3><p>
+<h3><a name="InvalidEnumerationContext" id="InvalidEnumerationContext"/>5.7 InvalidEnumerationContext</h3><p>
This fault MUST be generated when the enumeration context is invalid.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Receiver </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:InvalidEnumerationContext </td></tr><tr><td><b>[Reason]</b></td><td><em>
Text explaining why the enumeration context is no longer valid, or
@@ -1179,25 +1191,25 @@
<em>
if no additional information is available.
</em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="TimedOut" id="TimedOut"/>4.8 TimedOut</h3><p>
+<h3><a name="TimedOut" id="TimedOut"/>5.8 TimedOut</h3><p>
This fault MUST be generated when the data source times out during the
processing of a Pull operation, if the wsen:MaxTime is reached.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td> s12:Receiver </td></tr><tr><td><b>[Subcode]</b></td><td> wsen:TimedOut </td></tr><tr><td><b>[Reason]</b></td><td> Timeout. </td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="UnusableEPR" id="UnusableEPR"/>4.9 UnusableEPR</h3><p>
+<h3><a name="UnusableEPR" id="UnusableEPR"/>5.9 UnusableEPR</h3><p>
This fault MUST be generated when a data source detects
that the wsen:EndTo EPR is unusable.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:EndTo EPR is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> Details as to why the EPR is unusable. </em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="EndToNotSupported" id="EndToNotSupported"/>4.10 EndToNotSupported</h3><p>
+<h3><a name="EndToNotSupported" id="EndToNotSupported"/>5.10 EndToNotSupported</h3><p>
This fault MUST be generated by an data source that does not support
/wsen:Enumerate/wsen:EndTo semantics, in response to a enumerate
request that contains a wsen:EndTo element.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wsen:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="EmptyFilter" id="EmptyFilter"/>4.11 EmptyFilter</h3><p>
+<h3><a name="EmptyFilter" id="EmptyFilter"/>5.11 EmptyFilter</h3><p>
This fault MUST be generated when a data source detects a
wsen:Enumerate request containing a filter that, for whatever
reason, will never evaluate to true.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:Filter would result in zero data items.</td></tr><tr><td><b>[Detail]</b></td><td><em> The wsen:Filter value. </em></td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="Security" id="Security"/>5 Security Considerations</h2><p>
+<h2><a name="Security" id="Security"/>6 Security Considerations</h2><p>
It is strongly RECOMMENDED that the
communication between services be secured using the mechanisms
described in <a href="#WSSecurity">[WS-Security]</a>.
@@ -1289,7 +1301,7 @@
taken to ensure that minimal state is saved prior to any
authenticating sequences.
</p></li></ul></div><div class="div1">
-<h2><a name="metadata" id="metadata"/>6 WS-Enumeration Metadata</h2><p>
+<h2><a name="metadata" id="metadata"/>7 WS-Enumeration Metadata</h2><p>
An endpoint MAY indicate its support of WS-Enumeration, or its features,
by including the WS-Enumeration DataSource Policy assertion within its
WSDL. By
@@ -1312,7 +1324,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2023" id="iddiv2_1_2023"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_2038" id="iddiv2_1_2038"/>7.1 Enumeration Assertion</h3><p>
Services indicate support for the WS-Enumeration's definition of a
data source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1383,7 +1395,7 @@
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
</p></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
This specification has been developed as a
result of joint work with many individuals and teams,
including:
@@ -1414,8 +1426,8 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
-<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2130" id="iddiv2_1_2130"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
+<h3><a name="iddiv2_1_2145" id="iddiv2_1_2145"/>9.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.
@@ -1435,7 +1447,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
@@ -1487,7 +1499,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2316" id="iddiv2_1_2316"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2331" id="iddiv2_1_2331"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -1980,7 +1992,7 @@
[msg] </code></td><td valign="top" nowrap="true"><code>
Create new context <br/>
Send EnumerateResponse <br/>
- {<a href="#Enumerate"><b>3.1</b></a>}</code></td><td/><td/></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#Enumerate"><b>4.1</b></a>}</code></td><td/><td/></tr><tr><td valign="top" nowrap="true"><code>
Pull Request <br/>
[msg]</code></td><td/><td valign="top" nowrap="true"><code>
If (end of sequence) {<br/>
@@ -1988,55 +2000,55 @@
  invalidate context<br/>
} <br/>
Send PullResponse <br/>
- {<a href="#Pull"><b>3.2</b></a>}</code></td><td valign="top" nowrap="true"><code>
+ {<a href="#Pull"><b>4.2</b></a>}</code></td><td valign="top" nowrap="true"><code>
Generate <br/>
  InvalidEnumerationContext <br/>
  Fault<br/>
- {<a href="#EnumMsgs"><b>3</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#EnumMsgs"><b>4</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
Renew Request <br/>
[msg] </code></td><td/><td valign="top" nowrap="true"><code>
Update expiration timer<br/>
Send RenewReponse<br/>
- {<a href="#Renew"><b>3.3</b></a>}</code></td><td valign="top" nowrap="true"><code>
+ {<a href="#Renew"><b>4.3</b></a>}</code></td><td valign="top" nowrap="true"><code>
Generate <br/>
  InvalidEnumerationContext <br/>
  Fault<br/>
- {<a href="#EnumMsgs"><b>3</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#EnumMsgs"><b>4</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
GetStatus Request <br/>
[msg] </code></td><td/><td valign="top" nowrap="true"><code>
Send GetStatusResponse <br/>
- {<a href="#GetStatus"><b>3.4</b></a>}</code></td><td valign="top" nowrap="true"><code>
+ {<a href="#GetStatus"><b>4.4</b></a>}</code></td><td valign="top" nowrap="true"><code>
Generate <br/>
  InvalidEnumerationContext <br/>
  Fault<br/>
- {<a href="#EnumMsgs"><b>3</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#EnumMsgs"><b>4</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
Release Request <br/>
[msg] </code></td><td/><td valign="top" nowrap="true"><code>
Send wse:ReleaseResponse<br/>
Invalidate context<br/>
- {<a href="#Release"><b>3.5</b></a>}</code></td><td valign="top" nowrap="true"><code>
+ {<a href="#Release"><b>4.5</b></a>}</code></td><td valign="top" nowrap="true"><code>
Generate <br/>
  InvalidEnumerationContext <br/>
  Fault<br/>
- {<a href="#EnumMsgs"><b>3</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#EnumMsgs"><b>4</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
Expiration <br/>
[timer] </code></td><td/><td valign="top" nowrap="true"><code>
Invalidate context<br/>
- {<a href="#Enumerate"><b>3.1</b></a>}</code></td><td/></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#Enumerate"><b>4.1</b></a>}</code></td><td/></tr><tr><td valign="top" nowrap="true"><code>
Shutdown/Error <br/>
[app] </code></td><td/><td valign="top" nowrap="true"><code>
if (EndTo engaged) <br/>
  send EnumerationEnd <br/>
Invalidate context <br/>
- {<a href="#EnumerationEnd"><b>3.6</b></a>}</code></td><td/></tr></tbody></table><p/><table border="1"><caption>Table C-2: Consumer Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#EnumerationEnd"><b>4.6</b></a>}</code></td><td/></tr></tbody></table><p/><table border="1"><caption>Table C-2: Consumer Action Table</caption><tbody><tr><td valign="bottom"><b>Trigger</b></td><td align="center"><b>Action</b></td></tr><tr><td valign="top" nowrap="true"><code>
Expiration<br/>
[timer] </code></td><td valign="top" nowrap="true"><code>
Invalidate context<br/>
- {<a href="#Enumerate"><b>3.1</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
+ {<a href="#Enumerate"><b>4.1</b></a>}</code></td></tr><tr><td valign="top" nowrap="true"><code>
EnumerationEnd<br/>
[msg]</code></td><td valign="top" nowrap="true"><code>
Invalidate context<br/>
- {<a href="#EnumerationEnd"><b>3.6</b></a>}</code></td></tr></tbody></table></div><div class="div1">
+ {<a href="#EnumerationEnd"><b>4.6</b></a>}</code></td></tr></tbody></table></div><div class="div1">
<h2><a name="changelog" id="changelog"/>D Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
Index: wssa.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- wssa.html 21 Apr 2010 18:05:31 -0000 1.4
+++ wssa.html 23 Apr 2010 15:31:51 -0000 1.5
@@ -39,25 +39,34 @@
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#Introduction">Introduction</a><br/>
- 1.1 <a href="#Requirements">Requirements</a><br/>
-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="#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_444">Normative References</a><br/>
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
+ 2.1 <a href="#Requirements">Requirements</a><br/>
+3 <a href="#notterms">Notations</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="#Compliance">Compliance</a><br/>
+ 3.4 <a href="#namespaces">XML Namespaces</a><br/>
+4 <a href="#SOAPAssertions">SOAP Assertions</a><br/>
+ 4.1 <a href="#SAS11">SOAP11 Assertion</a><br/>
+ 4.2 <a href="#SAS12">SOAP12 Assertion</a><br/>
+5 <a href="#Examples">Examples</a><br/>
+6 <a href="#acks">Acknowledgements</a><br/>
+7 <a href="#References">References</a><br/>
+ 7.1 <a href="#iddiv2_1_459">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/>
</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="Introduction" id="Introduction"/>1 Introduction</h2><p>
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
+ By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment.
+ </p></div><div class="div1">
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
Using the Web Service Policy - Framework <a href="#wspolicy">[WS-Policy]</a>
and Web Services Policy - Attachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a>
specifications, an endpoint can indicate support for a variety of
@@ -68,7 +77,7 @@
</p><p>
However, one key aspect of the message exchanges is whether either
endpoint requires the use of SOAP 1.1 <a href="#SOAP11">[SOAP11]</a>
- or SOAP 1.2 <a href="#SOAP121">[SOAP12]</a>. While this information might be
+ or SOAP 1.2 <a href="#SOAP12">[SOAP12]</a>. While this information might be
obtainable through examination of a WSDL <a href="#WSDL11">[WSDL11]</a>
document, or implied through some out of band knowledge, there is no
way to make this determination during the application of the policy
@@ -76,17 +85,17 @@
assertions that allows for this critical piece of information to be
available during normal policy processing.
</p><div class="div2">
-<h3><a name="Requirements" id="Requirements"/>1.1 Requirements</h3><p>
+<h3><a name="Requirements" id="Requirements"/>2.1 Requirements</h3><p>
This specification intends to meet the following requirement:
</p><ul><li><p>
Provide a set of policy assertions to indicate the requirement to
use a certain version of SOAP.
</p></li></ul></div></div><div class="div1">
-<h2><a name="notterms" id="notterms"/>2 Notations</h2><p>
+<h2><a name="notterms" id="notterms"/>3 Notations</h2><p>
This section specifies the notations and namespaces
used in this specification.
</p><div class="div2">
-<h3><a name="Conventions" id="Conventions"/>2.1 Notational Conventions</h3><p>
+<h3><a name="Conventions" id="Conventions"/>3.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119
@@ -111,7 +120,7 @@
</p></li><li><p>
Ellipses (i.e., "...") indicate points of extensibility.
</p></li><li><p>
- XML namespace prefixes (see <a href="#XMLNS">Table 2-1</a>) are used to
+ XML namespace prefixes (see <a href="#XMLNS">Table 3-1</a>) are used to
indicate the namespace of the element being defined.
</p></li></ul><p>
This specification can be used in terms of XML Information Set (Infoset)
@@ -119,7 +128,7 @@
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
</p></div><div class="div2">
-<h3><a name="extensions" id="extensions"/>2.2 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
@@ -129,24 +138,24 @@
Extension elements and attributes MUST NOT use the Web Services
Metadata Exchange namespace URI.
</p></div><div class="div2">
-<h3><a name="Compliance" id="Compliance"/>2.3 Compliance</h3><p>
+<h3><a name="Compliance" id="Compliance"/>3.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
+ specification (listed in <a href="#namespaces"><b>3.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>
+<h3><a name="namespaces" id="namespaces"/>3.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
+ </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 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 2-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> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> wssa </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-sas </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></tbody></table><p>
+ </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="#SOAP12">[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> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td><a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> wssa </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-sas </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></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
@@ -163,12 +172,12 @@
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div></div><div class="div1">
-<h2><a name="SOAPAssertions" id="SOAPAssertions"/>3 SOAP Assertions</h2><p>
+<h2><a name="SOAPAssertions" id="SOAPAssertions"/>4 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.
</p><div class="div2">
-<h3><a name="SAS11" id="SAS11"/>3.1 SOAP11 Assertion</h3><p>
+<h3><a name="SAS11" id="SAS11"/>4.1 SOAP11 Assertion</h3><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wssa:SOAP11 ...> ... <wssa:SOAP11></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -178,7 +187,7 @@
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>
+<h3><a name="SAS12" id="SAS12"/>4.2 SOAP12 Assertion</h3><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wssa:SOAP12 ...> ... <wssa:SOAP12></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -188,7 +197,7 @@
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>
+<h2><a name="Examples" id="Examples"/>5 Examples</h2><p>
The following example shows a sample policy expression that indicates
SOAP 1.1 is required:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsp:Policy>
@@ -211,7 +220,7 @@
<wssa:SOAP12/>
</wsp:Policy>
<wsa:EndpointReference></pre></div></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>5 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>6 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
@@ -241,8 +250,8 @@
Wu Chou (Avaya Communications),
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_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>
+<h2><a name="References" id="References"/>7 References</h2><div class="div2">
+<h3><a name="iddiv2_1_459" id="iddiv2_1_459"/>7.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.
@@ -252,7 +261,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
@@ -299,8 +308,7 @@
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd">http://www.w3.org/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd</a></pre></div></div><p>
- A non-normative copy of the XML Schema description is listed below for
- convenience.
+ A non-normative copy of the XML schema is listed below for convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-sas'
xmlns:tns='http://www.w3.org/2002/ws/ra/edcopies/ws-sas'
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- wsmex.html 21 Apr 2010 03:10:03 -0000 1.117
+++ wsmex.html 23 Apr 2010 15:31:51 -0000 1.118
@@ -43,8 +43,8 @@
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#Composable">Composable Architecture</a><br/>
-2 <a href="#Introduction">Introduction</a><br/>
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
2.1 <a href="#Requirements">Requirements</a><br/>
2.2 <a href="#Examples">Examples</a><br/>
3 <a href="#notterms">Notations and Terminology</a><br/>
@@ -61,32 +61,36 @@
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_1234">Examples</a><br/>
+ 7.3 <a href="#iddiv2_1_1244">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_1629">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1639">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_1782">Normative References</a><br/>
- 14.2 <a href="#iddiv2_1_1968">Informative References</a><br/>
+ 14.1 <a href="#iddiv2_1_1792">Normative References</a><br/>
+ 14.2 <a href="#iddiv2_1_1978">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/>
C <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="Composable" id="Composable"/>1 Composable Architecture</h2><p>
- The Web services specifications (WS-*) are designed to be composed with
- each other to provide a rich set of tools for the Web services
- environment. This specification specifically relies on other Web
- services specifications to provide secure, reliable, and/or transacted
- message delivery and to express Web service metadata.
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
+ By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
</p></div><div class="div1">
-<h2><a name="Introduction" id="Introduction"/>2 Introduction</h2><p>
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
Web services use metadata to describe what other endpoints need to know
to interact with them. Specifically, <a href="#wspolicy">[WS-Policy]</a>
describes the capabilities, requirements, and general characteristics
@@ -482,7 +486,7 @@
</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>
+ </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="#SOAP12">[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><r><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
@@ -846,7 +850,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_1234" id="iddiv2_1_1234"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1244" id="iddiv2_1_1244"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -877,7 +881,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_1266" id="idexample_1_1266"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexample_1_1276" id="idexample_1_1276"/>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 +1431,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_1629" id="iddiv2_1_1629"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1639" id="iddiv2_1_1639"/>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 +1586,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_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>
+<h3><a name="iddiv2_1_1792" id="iddiv2_1_1792"/>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.
@@ -1602,7 +1606,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
@@ -1654,7 +1658,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_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>
+<h3><a name="iddiv2_1_1978" id="iddiv2_1_1978"/>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>
@@ -1686,8 +1690,7 @@
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-mex/MetadataExchange.xsd">http://www.w3.org/2002/ws/ra/edcopies/ws-mex/MetadataExchange.xsd</a></pre></div></div><p>
- A non-normative copy of the XML Schema description is listed below for
- convenience.
+ A non-normative copy of the XML schema is listed below for convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-mex'
xmlns:tns='http://www.w3.org/2002/ws/ra/edcopies/ws-mex'
Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- wsevd.html 21 Apr 2010 03:10:03 -0000 1.13
+++ wsevd.html 23 Apr 2010 15:31:51 -0000 1.14
@@ -61,7 +61,7 @@
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML and SOAP <a href="#SOAP11">[SOAP11]</a>,
- <a href="#SOAP121">[SOAP12]</a>
+ <a href="#SOAP12">[SOAP12]</a>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
@@ -156,7 +156,7 @@
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>wsa</td><td><a href="http://www.w3.org/2005/08/addressing">
+ </a></td><td>SOAP 1.2 <a href="#SOAP12">[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>WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td>wsevd</td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evd">
http://www.w3.org/2002/ws/ra/edcopies/ws-evd
@@ -420,7 +420,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.172
retrieving revision 1.173
diff -u -d -r1.172 -r1.173
--- wseventing.xml 21 Apr 2010 17:13:07 -0000 1.172
+++ wseventing.xml 23 Apr 2010 15:31:51 -0000 1.173
@@ -87,13 +87,12 @@
</header>
<body>
-
<div1 id="composable">
<head>Composable Architecture</head>
<p>
By using the XML, SOAP <bibref ref="SOAP11"/>,
- <bibref ref="SOAP121"/>, and WSDL <bibref ref="WSDL11"/>
+ <bibref ref="SOAP12"/>, and WSDL <bibref ref="WSDL11"/>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
@@ -201,7 +200,7 @@
<p>
Support a variety of encoding formats, including (but not
limited to) both SOAP 1.1 <bibref ref="SOAP11"/>
- and SOAP 1.2 <bibref ref="SOAP121"/> Envelopes.
+ and SOAP 1.2 <bibref ref="SOAP12"/> Envelopes.
</p>
</item>
</ulist>
@@ -731,7 +730,7 @@
http://www.w3.org/2003/05/soap-envelope
</loc>
</td>
- <td>SOAP 1.2 <bibref ref="SOAP121"/></td>
+ <td>SOAP 1.2 <bibref ref="SOAP12"/></td>
</tr>
<tr>
<td>wsdl</td>
@@ -3075,7 +3074,7 @@
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
- <bibl key="SOAP12" id="SOAP121"
+ <bibl key="SOAP12" id="SOAP12"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -d -r1.116 -r1.117
--- wst.html 21 Apr 2010 03:10:04 -0000 1.116
+++ wst.html 23 Apr 2010 15:31:52 -0000 1.117
@@ -38,113 +38,131 @@
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"/>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="#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/>
- 3.3 <a href="#Delete">Delete</a><br/>
-4 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br/>
- 4.1 <a href="#Factory_Create">Create</a><br/>
-5 <a href="#Faults">Faults</a><br/>
- 5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
- 5.2 <a href="#UnknownDialect">UnknownDialect</a><br/>
- 5.3 <a href="#PutDenied">PutDenied</a><br/>
- 5.4 <a href="#UnknownResource">UnknownResource</a><br/>
-6 <a href="#Security_Considerations">Security Considerations</a><br/>
-7 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 7.1 <a href="#iddiv2_1_1370">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1452">TransferResourceFactory Assertion</a><br/>
-8 <a href="#acks">Acknowledgements</a><br/>
-9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1517">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1690">Informative References</a><br/>
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
+ 2.1 <a href="#reqs">Requirements</a><br/>
+3 <a href="#Notations_and_Terminology">Terminology and Notation</a><br/>
+ 3.1 <a href="#conven">Notational Conventions</a><br/>
+ 3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
+ 3.3 <a href="#terminology">Terminology</a><br/>
+ 3.4 <a href="#compliance">Compliance</a><br/>
+ 3.5 <a href="#namespaces">XML Namespaces</a><br/>
+4 <a href="#resourceOperations">Resource Operations</a><br/>
+ 4.1 <a href="#Get">Get</a><br/>
+ 4.2 <a href="#Put">Put</a><br/>
+ 4.3 <a href="#Delete">Delete</a><br/>
+5 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br/>
+ 5.1 <a href="#Factory_Create">Create</a><br/>
+6 <a href="#Faults">Faults</a><br/>
+ 6.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
+ 6.2 <a href="#UnknownDialect">UnknownDialect</a><br/>
+ 6.3 <a href="#PutDenied">PutDenied</a><br/>
+ 6.4 <a href="#UnknownResource">UnknownResource</a><br/>
+7 <a href="#Security_Considerations">Security Considerations</a><br/>
+8 <a href="#metadata">WS-Transfer Metadata</a><br/>
+ 8.1 <a href="#iddiv2_1_1385">TransferResource Assertion</a><br/>
+ 8.2 <a href="#iddiv2_1_1467">TransferResourceFactory Assertion</a><br/>
+9 <a href="#acks">Acknowledgements</a><br/>
+10 <a href="#refs">References</a><br/>
+ 10.1 <a href="#iddiv2_1_1532">Normative References</a><br/>
+ 10.2 <a href="#iddiv2_1_1705">Informative 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="#WSDL">WSDL</a><br/>
C <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"/>1 Introduction</h2><p>
- This specification defines a mechanism for acquiring XML-based
- representations of entities using the Web service infrastructure.
- It defines two types of entities:
- </p><ul><li><p>
- Resources, which are entities addressable by an endpoint
- reference that provide an XML representation
- </p></li><li><p>Resource factories, which are Web services that can create new
- resources</p></li></ul><p>
- Specifically, it defines two operations for sending and receiving the
- representation of a given resource and two operations for creating and
- deleting a resource and its corresponding representation.
- </p><p>
- Note that the state maintenance of a resource is at most
- subject to the "best efforts" of the hosting server. When a client
- receives the server's acceptance of a request to create or update a
- resource, it can reasonably expect that the resource now exists at
- the confirmed location and with the confirmed representation, but this
- is not a guarantee, even in the absence of any third parties. The
- server MAY change the representation of a resource, MAY remove a
- resource entirely, or MAY bring back a resource that was deleted.
- </p><p>
- For instance, the server might store resource state information on a
- disk drive. If that drive crashes and the server recovers state
- information from a backup tape, changes that occurred after the
- backup was made will be lost.
- </p><p>
- A server might have other operational processes that change resource
- state information. For example, a server could purge resources that
- have not been accessed for some period of time.
- </p><p>
- In addition to this, there might be application or process specific
- reasons for a server to augment or transform the representation
- provided by an update or create operation. For example, the server
- might populate the optional properties of a newly created resource
- with meaningful default values.
- </p><p>
- Finally all clients need to be aware that there might be other clients
- simultaneously accessing, creating, and updating the same resources.
- </p><p>
- In essence, the confirmation by a service of having processed a
- request to create, modify, or delete a resource implies a commitment
- only at the instant that the confirmation was generated. While the
- usual case is that resources are long-lived and stable, there are no
- guarantees, and clients are advised to code defensively.
- </p><p>
- There is no requirement for uniformity in resource representations
- between the messages defined in this specification. For example, the
- representations used by Create or Put can differ from the representation
- returned by Get, depending on the semantic requirements of the service.
- Additionally, there is no requirement that the resource content is
- fixed for any given endpoint reference. The resource content can vary
- based on environmental factors, such as the security context, time
- of day, configuration, or the dynamic state of the service.
- </p><div class="div2">
-<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
- representations.
- </p></li><li><p>Minimize additional mechanism beyond the current Web Services
- 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="conven" id="conven"/>2.1 Notational Conventions</h3><p>
- The keywords "MUST", "MUST NOT",
- "REQUIRED", "SHALL", "SHALL NOT",
- "SHOULD", "SHOULD NOT", "RECOMMENDED",
- "MAY", and "OPTIONAL" in this document are to be
- interpreted as described in RFC 2119
- <a href="#RFC2119">[RFC 2119]</a>.
- </p><p>
- This specification uses the following syntax to define outlines for
- messages:
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
+ By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
+ <a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
+ extensibility models, the Web service
+ specifications (WS-*) are designed to be composed with each other
+ to provide a rich set of tools to provide security in the Web
+ services environment. This specification specifically relies on
+ other Web service specifications to provide secure, reliable,
+ and/or transacted message delivery and to express Web service and
+ client policy.
+ </p></div><div class="div1">
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
+ This specification defines a mechanism for acquiring XML-based
+ representations of entities using the Web service infrastructure.
+ It defines two types of entities:
</p><ul><li><p>
- The syntax appears as an XML instance, but values in italics
- indicate data types instead of literal values.
+ Resources, which are entities addressable by an endpoint
+ reference that provide an XML representation
</p></li><li><p>
+ Resource factories, which are Web services that can create new
+ resources
+ </p></li></ul><p>
+ Specifically, it defines two operations for sending and receiving the
+ representation of a given resource and two operations for creating and
+ deleting a resource and its corresponding representation.
+ </p><p>
+ Note that the state maintenance of a resource is at most
+ subject to the "best efforts" of the hosting server. When a client
+ receives the server's acceptance of a request to create or update a
+ resource, it can reasonably expect that the resource now exists at
+ the confirmed location and with the confirmed representation, but this
+ is not a guarantee, even in the absence of any third parties. The
+ server MAY change the representation of a resource, MAY remove a
+ resource entirely, or MAY bring back a resource that was deleted.
+ </p><p>
+ For instance, the server might store resource state information on a
+ disk drive. If that drive crashes and the server recovers state
+ information from a backup tape, changes that occurred after the
+ backup was made will be lost.
+ </p><p>
+ A server might have other operational processes that change resource
+ state information. For example, a server could purge resources that
+ have not been accessed for some period of time.
+ </p><p>
+ In addition to this, there might be application or process specific
+ reasons for a server to augment or transform the representation
+ provided by an update or create operation. For example, the server
+ might populate the optional properties of a newly created resource
+ with meaningful default values.
+ </p><p>
+ Finally all clients need to be aware that there might be other clients
+ simultaneously accessing, creating, and updating the same resources.
+ </p><p>
+ In essence, the confirmation by a service of having processed a
+ request to create, modify, or delete a resource implies a commitment
+ only at the instant that the confirmation was generated. While the
+ usual case is that resources are long-lived and stable, there are no
+ guarantees, and clients are advised to code defensively.
+ </p><p>
+ There is no requirement for uniformity in resource representations
+ between the messages defined in this specification. For example, the
+ representations used by Create or Put can differ from the representation
+ returned by Get, depending on the semantic requirements of the service.
+ Additionally, there is no requirement that the resource content is
+ fixed for any given endpoint reference. The resource content can vary
+ based on environmental factors, such as the security context, time
+ of day, configuration, or the dynamic state of the service.
+ </p><div class="div2">
+<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>
+ This specification intends to meet the following requirements:
+ </p><ul><li><p>
+ Provide a SOAP-based protocol for managing resources and their
+ representations.
+ </p></li><li><p>
+ Minimize additional mechanism beyond the current Web Services
+ architecture.
+ </p></li></ul></div></div><div class="div1">
+<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>3 Terminology and Notation</h2><div class="div2">
+<h3><a name="conven" id="conven"/>3.1 Notational Conventions</h3><p>
+ The keywords "MUST", "MUST NOT",
+ "REQUIRED", "SHALL", "SHALL NOT",
+ "SHOULD", "SHOULD NOT", "RECOMMENDED",
+ "MAY", and "OPTIONAL" in this document are to be
+ interpreted as described in RFC 2119
+ <a href="#RFC2119">[RFC 2119]</a>.
+ </p><p>
+ This specification uses the following syntax to define outlines for
+ messages:
+ </p><ul><li><p>
+ The syntax appears as an XML instance, but values in italics
+ indicate data types instead of literal values.
+ </p></li><li><p>
Characters are appended to elements and attributes to indicate
cardinality:
</p><ul><li><p> "?" (0 or 1) </p></li><li><p> "*" (0 or more) </p></li><li><p> "+" (1 or more) </p></li></ul></li><li><p>
@@ -160,7 +178,7 @@
</p></li><li><p>
Ellipsis (i.e. "...") indicate points of extensibility.
</p></li><li><p>
- XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used
+ XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
to indicate the namespace of the element being defined.
</p></li></ul><p>
In addition to Message Information Header properties
@@ -189,7 +207,7 @@
security concerns - in these situations the fault MAY NOT
be transmitted.
</p></div><div class="div2">
-<h3><a name="extensions" id="extensions"/>2.2 Considerations on the Use of Extensibility Points</h3><p>
+<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
@@ -211,18 +229,18 @@
Extension elements and attributes MUST NOT use the Web Services
Transfer namespace URI.
</p></div><div class="div2">
-<h3><a name="terminology" id="terminology"/>2.3 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>
+<h3><a name="terminology" id="terminology"/>3.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>
+<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>2.5 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
@@ -241,18 +259,18 @@
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>
+<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-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
+ </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 3-1</a> lists XML namespaces that are
used in this specification. The
choice of any namespace prefix is arbitrary and not semantically
significant.
- </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><caption>Table 2-1:
+ </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><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> 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>
+ </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="#SOAP12">[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
@@ -270,8 +288,8 @@
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>
+<h2><a name="resourceOperations" id="resourceOperations"/>4 Resource Operations</h2><div class="div2">
+<h3><a name="Get" id="Get"/>4.1 Get</h3><p>
This specification defines one Web service operation (Get) for
fetching a one-time snapshot of the representation of a resource.
This operation MUST be supported by compliant WS-Transfer resources.
@@ -306,7 +324,7 @@
implementation MUST generate a wst:UnknownResource fault.
</p><p>
A Get request MUST be targeted at the resource whose representation is
- desired as described in <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of
+ desired as described in <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of
this specification.
</p><p>
If the resource accepts a Get request, it MUST reply with a response
@@ -405,7 +423,7 @@
<xxx:state>CA</xxx:state>
<xxx:zip>90266</xxx:zip>
</xxx:Customer></pre></div></div></div><div class="div2">
-<h3><a name="Put" id="Put"/>3.2 Put</h3><p>
+<h3><a name="Put" id="Put"/>4.2 Put</h3><p>
This specification defines one Web service operation (Put) for
updating a resource.
This operation MAY be supported by compliant WS-Transfer resources.
@@ -464,7 +482,7 @@
</p><p>
A Put request MUST be targeted at the resource whose representation is
desired to be updated, as described in
- <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this specification.
+ <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of this specification.
</p><p>
The replacement representation could be considered to be invalid if
it does not conform to the schema(s) for the target resource or
@@ -480,7 +498,7 @@
to allow the client to change. An implementation MAY choose to ignore
such elements or attributes. If an implementation does not ignore
those elements or attributes, it MUST generate a wst:PutDenied fault.
- See <a href="#Faults"><b>5 Faults</b></a>.
+ See <a href="#Faults"><b>6 Faults</b></a>.
</p><p>
Other components of the outline above are not
further constrained by this specification.
@@ -567,7 +585,7 @@
<wst:PutResponse/>
</s:Body>
</s:Envelope> </pre></div></div></div><div class="div2">
-<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>
+<h3><a name="Delete" id="Delete"/>4.3 Delete</h3><p>
This specification defines one Web service operation (Delete) for
deleting a resource in its entirety.
This operation MAY be supported by compliant WS-Transfer resources.
@@ -597,7 +615,7 @@
implementation MUST generate a wst:UnknownResource fault.
</p><p>
A Delete request MUST be targeted at the resource to be deleted as
- described in <a href="#Notations_and_Terminology"><b>2 Terminology and Notation</b></a> of this
+ described in <a href="#Notations_and_Terminology"><b>3 Terminology and Notation</b></a> of this
specification.
</p><p>
Other components of the outline above are not further constrained by
@@ -669,8 +687,8 @@
<wst:DeleteResponse/>
</s:Body>
</s:Envelope> </pre></div></div></div></div><div class="div1">
-<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"/>4 Resource Factory Operations</h2><div class="div2">
-<h3><a name="Factory_Create" id="Factory_Create"/>4.1 Create</h3><p>
+<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"/>5 Resource Factory Operations</h2><div class="div2">
+<h3><a name="Factory_Create" id="Factory_Create"/>5.1 Create</h3><p>
This specification defines one Web service operation (Create) for
creating a resource and providing its initial representation.
This operation MAY be supported by compliant WS-Transfer resource
@@ -820,7 +838,7 @@
</wst:CreateResponse>
</s:Body>
</s:Envelope></pre></div></div></div></div><div class="div1">
-<h2><a name="Faults" id="Faults"/>5 Faults</h2><p>
+<h2><a name="Faults" id="Faults"/>6 Faults</h2><p>
All fault messages defined in this specification MUST be sent
according to the rules and usage described in
<a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
@@ -868,30 +886,30 @@
</s11:Fault>
</s11:Body>
</s11:Envelope></pre></div></div><div class="div2">
-<h3><a name="InvalidRepresentation" id="InvalidRepresentation"/>5.1 InvalidRepresentation</h3><p>
+<h3><a name="InvalidRepresentation" id="InvalidRepresentation"/>6.1 InvalidRepresentation</h3><p>
This fault MUST be generated when an incorrect representation is
sent in a wst:Put or wst:Create message.
</p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnknownDialect" id="UnknownDialect"/>5.2 UnknownDialect</h3><p>
+<h3><a name="UnknownDialect" id="UnknownDialect"/>6.2 UnknownDialect</h3><p>
This fault MUST be generated when a service detects an unknown
Dialect IRI in a request message.
</p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownDialect</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
The specified Dialect IRI is not known.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown IRI if specified</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="PutDenied" id="PutDenied"/>5.3 PutDenied</h3><p>
+<h3><a name="PutDenied" id="PutDenied"/>6.3 PutDenied</h3><p>
This fault MUST be generated when a Put request message attempts
to modify a portion of a resource but is not allowed to do so.
</p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UpdateDenied</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
One or more elements or attributes cannot be updated.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>An OPTIONAL list of the QNames of the elements or
attributes that are not allowed to be updated.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnknownResource" id="UnknownResource"/>5.4 UnknownResource</h3><p>
+<h3><a name="UnknownResource" id="UnknownResource"/>6.4 UnknownResource</h3><p>
This fault MUST be generated when a request specifies a resource
that is not known.
</p><table border="1"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownResource</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
The resource is not known.
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>It is strongly RECOMMENDED that the communication between services be
+<h2><a name="Security_Considerations" id="Security_Considerations"/>7 Security Considerations</h2><p>It is strongly RECOMMENDED that the communication between services be
secured using the mechanisms described in <a href="#WSSecurity">[WS-Security]</a>.</p><p>In order to properly secure messages, the body (even if empty) and all
relevant headers need to be included in the signature. Specifically, the
WS-Addressing header blocks, WS-Security timestamp, and any header blocks
@@ -941,7 +959,7 @@
denial of service attacks are harder to avoid and are outside the scope
of this specification. That said, care SHOULD be taken to ensure that
minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
-<h2><a name="metadata" id="metadata"/>7 WS-Transfer Metadata</h2><p>
+<h2><a name="metadata" id="metadata"/>8 WS-Transfer Metadata</h2><p>
An endpoint MAY indicate its support of WS-Transfer, or its features,
by including the WS-Transfer TransferResource or TransferResourceFactory
Policy assertions within its WSDL. By
@@ -965,7 +983,7 @@
that indicate a particular security mechanism used to protect
the WS-Transfer operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1370" id="iddiv2_1_1370"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1385" id="iddiv2_1_1385"/>8.1 TransferResource Assertion</h3><p>
Services indicate support for the
WS-Transfer's definition of a Transfer Resource
through the use of the Web Services
@@ -1030,7 +1048,7 @@
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_1452" id="iddiv2_1_1452"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1467" id="iddiv2_1_1467"/>8.2 TransferResourceFactory Assertion</h3><p>
Services indicate support for
WS-Transfer's definition of a Transfer Resource Factory
through the use of the Web Services
@@ -1071,7 +1089,7 @@
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
</p></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>9 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
@@ -1101,8 +1119,8 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
-<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1517" id="iddiv2_1_1517"/>9.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>
+<h2><a name="refs" id="refs"/>10 References</h2><div class="div2">
+<h3><a name="iddiv2_1_1532" id="iddiv2_1_1532"/>10.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.
@@ -1122,7 +1140,7 @@
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
- Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
+ Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
@@ -1170,7 +1188,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_1690" id="iddiv2_1_1690"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1705" id="iddiv2_1_1705"/>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
Received on Friday, 23 April 2010 15:32:00 UTC