- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 28 Nov 2010 15:54:21 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv4942
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
wsfrag.html wsfrag.xml wsmex.html wsmex.xml wssa.html wssa.xml
wst.html wst.xml xmlspec.xsl
Log Message:
More ws-i bp reference stuff - 8284
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -d -r1.131 -r1.132
--- wst.xml 19 Nov 2010 22:43:20 -0000 1.131
+++ wst.xml 28 Nov 2010 15:54:19 -0000 1.132
@@ -450,6 +450,13 @@
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
</p>
+
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
</div2>
@@ -2026,6 +2033,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -2107,20 +2132,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.215
retrieving revision 1.216
diff -u -d -r1.215 -r1.216
--- wseventing.html 19 Nov 2010 22:43:19 -0000 1.215
+++ wseventing.html 28 Nov 2010 15:54:18 -0000 1.216
@@ -73,26 +73,26 @@
6.10 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
6.11 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
- 7.1 <a href="#iddiv2x1x2080">Notifications</a><br/>
- 7.2 <a href="#iddiv2x1x2089">Subscriptions</a><br/>
- 7.3 <a href="#iddiv2x1x2094">Endpoint Verification</a><br/>
+ 7.1 <a href="#iddiv2x1x2088">Notifications</a><br/>
+ 7.2 <a href="#iddiv2x1x2097">Subscriptions</a><br/>
+ 7.3 <a href="#iddiv2x1x2102">Endpoint Verification</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2x1x2120">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2x1x2244">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2x1x2128">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2x1x2252">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2x1x2307">Normative References</a><br/>
- 11.2 <a href="#iddiv2x1x2459">Informative References</a><br/>
+ 11.1 <a href="#iddiv2x1x2315">Normative References</a><br/>
+ 11.2 <a href="#iddiv2x1x2475">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3x1x2609">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3x1x2657">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4x1x2662">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4x1x2683">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3x1x2625">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3x1x2673">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4x1x2678">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4x1x2699">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3x1x2710">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3x1x2726">Retrieving Notification WSDLs</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -431,6 +431,11 @@
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of
@@ -1428,7 +1433,7 @@
urged to perform a security analysis to determine their particular
threat profile and the appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x2080" id="iddiv2x1x2080"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2x1x2088" id="iddiv2x1x2088"/>7.1 Notifications</h3><p>
The information contained in Notifications might be sensitive. In
such cases it is advisable to authenticate and authorize subscribers
as part of the processing of the Subscribe request. Note that an
@@ -1449,7 +1454,7 @@
and trace the origin of such attempts. Additionally, the
authorization of Subscribers reduces the pool of potential attackers.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2089" id="iddiv2x1x2089"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2x1x2097" id="iddiv2x1x2097"/>7.2 Subscriptions</h3><p>
Once created, subscriptions ought to be treated as protected
resources. Renew, GetStatus, and Unsubscribe requests ought to be
authenticated and authorized (for example, the identity of the
@@ -1464,7 +1469,7 @@
the identities of these entities are discovered and verified)
are particular to individual deployments.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2094" id="iddiv2x1x2094"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x2102" id="iddiv2x1x2102"/>7.3 Endpoint Verification</h3><p>
Implementations that perform validity checks on the EPRs used in
WS-Eventing (wse:NotifyTo, wse:EndTo) are advised that such checks
can be misused to obtain information about a target network. For
@@ -1515,7 +1520,7 @@
that indicate a particular security mechanism used to protect
the WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2x1x2120" id="iddiv2x1x2120"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2x1x2128" id="iddiv2x1x2128"/>9.1 EventSource Assertion</h3><p>
Services indicate support for the WS-Eventing's definition
of an event source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1627,7 +1632,7 @@
(10) - (12) contains the EventDescription data that describes the
syntax of the events that this event source might send.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2244" id="iddiv2x1x2244"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2x1x2252" id="iddiv2x1x2252"/>9.2 SubscriptionManager Assertion</h3><p>
Services indicate support for the
WS-Eventing's definition of a subscription manager
through the use of the Web Services
@@ -1698,7 +1703,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2307" id="iddiv2x1x2307"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2x1x2315" id="iddiv2x1x2315"/>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -1749,18 +1764,8 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x2459" id="iddiv2x1x2459"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd></dl></div><div class="div2">
+<h3><a name="iddiv2x1x2475" id="iddiv2x1x2475"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1838,7 +1843,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x2599" id="idexamplex1x2599"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexamplex1x2615" id="idexamplex1x2615"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1859,7 +1864,7 @@
(GED) for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3x1x2609" id="iddiv3x1x2609"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2625" id="iddiv3x1x2625"/>A.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an event source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1906,7 +1911,7 @@
(10) </mex:GetMetadataResponse> </pre></div></div><p><a href="#mexEVD">Example A-4</a> shows how the Event Descriptions metadata
might appear within a GetMetadataResponse message.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x2657" id="iddiv3x1x2657"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2673" id="iddiv3x1x2673"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST be possible to determine how a
given wsevd:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1918,7 +1923,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4x1x2662" id="iddiv4x1x2662"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2678" id="iddiv4x1x2678"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wsevd:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1933,7 +1938,7 @@
event being transmitted. If the @element attribute is absent then
the <b>[Body]</b> property has no children.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4x1x2683" id="iddiv4x1x2683"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2699" id="iddiv4x1x2699"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
The information about an Event Type contained in the eventType element
binds to a Wrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1959,7 +1964,7 @@
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x2704" id="idexamplex1x2704"/>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexamplex1x2720" id="idexamplex1x2720"/>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1994,7 +1999,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3x1x2710" id="iddiv3x1x2710"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3x1x2726" id="iddiv3x1x2726"/>A.2.1 Retrieving Notification WSDLs</h4><p>
Although there are many ways in which an event source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -d -r1.144 -r1.145
--- wsenum.xml 19 Nov 2010 22:43:19 -0000 1.144
+++ wsenum.xml 28 Nov 2010 15:54:18 -0000 1.145
@@ -105,218 +105,218 @@
<div1 id="intro">
<head>Introduction</head>
+ <p>
+ There are numerous applications for which a
+ simple single-request/single-reply metaphor is insufficient for
+ transferring large data sets over SOAP. Applications that do not
+ fit into this simple paradigm include streaming, traversal, query,
+ and enumeration.
+ </p>
+ <p>
+ This specification defines a simple SOAP-based
+ protocol for enumeration that allows the data source to provide a
+ session abstraction, called an enumeration context, to a consumer
+ that represents a logical cursor through a sequence of data items.
+ The consumer can then request XML element information items using
+ this enumeration context over the span of one or more SOAP
+ messages.
+ </p>
+ <p>
+ Somewhere, state MUST be maintained regarding
+ the progress of the iteration. This state MAY be maintained between
+ requests by the data source being enumerated or by the data
+ consumer. WS-Enumeration allows the data source to decide, on a
+ request-by-request basis, which party will be responsible for
+ maintaining this state for the next request.
+ </p>
+ <p>
+ In its simplest form, WS-Enumeration defines an operation, Enumerate,
+ used to establish the creation of an enumeration session or
+ which allows a data source, in the context
+ of a specific enumeration, to produce a sequence of XML elements in
+ the body of a SOAP message. Each subsequent Enumerate operation returns
+ the next N elements in the aggregate sequence.
+ </p>
+ <p>
+ A data source MAY provide a custom mechanism for
+ starting a new enumeration. For instance, a data source that
+ provides access to a SQL database can support a SELECT operation
+ that performs a database query and uses an explicit database cursor
+ to iterate through the returned rows. In general, however, it is
+ simpler if all data sources support a single, standard operation to
+ start an enumeration. This specification mandates
+ that data sources MUST implement the Enumerate operation for starting a new
+ enumeration of a data source.
+ Each new enumeration results in a distinct enumeration context,
+ each with its own logical cursor/position.
+ </p>
+ <p>
+ Note that different
+ enumerations of the same data source can produce different results;
+ this can happen even for two enumeration contexts created
+ concurrently by a single consumer using identical Enumerate
+ requests. The ordering or completeness of the enumeration
+ is undefined; the returned data items represent a selection by the
+ data source of items it wishes to present to that consumer at that
+ time in that order, with no guarantee that every available item is
+ returned or that the order in which items is returned has any
+ semantic meaning whatsoever (of course, any specific data source
+ can provide strong guarantees, if so desired). In particular,
+ note that the very act of enumerating the contents of a
+ data source can modify the contents of the data source; for
+ instance, a queue might be represented as a data source such that
+ items that are returned in a Enumerate response are removed from the
+ queue.
+ </p>
+
+ <div2 id="reqs">
+ <head>Requirements</head>
<p>
- There are numerous applications for which a
- simple single-request/single-reply metaphor is insufficient for
- transferring large data sets over SOAP. Applications that do not
- fit into this simple paradigm include streaming, traversal, query,
- and enumeration.
- </p>
- <p>
- This specification defines a simple SOAP-based
- protocol for enumeration that allows the data source to provide a
- session abstraction, called an enumeration context, to a consumer
- that represents a logical cursor through a sequence of data items.
- The consumer can then request XML element information items using
- this enumeration context over the span of one or more SOAP
- messages.
- </p>
- <p>
- Somewhere, state MUST be maintained regarding
- the progress of the iteration. This state MAY be maintained between
- requests by the data source being enumerated or by the data
- consumer. WS-Enumeration allows the data source to decide, on a
- request-by-request basis, which party will be responsible for
- maintaining this state for the next request.
- </p>
- <p>
- In its simplest form, WS-Enumeration defines an operation, Enumerate,
- used to establish the creation of an enumeration session or
- which allows a data source, in the context
- of a specific enumeration, to produce a sequence of XML elements in
- the body of a SOAP message. Each subsequent Enumerate operation returns
- the next N elements in the aggregate sequence.
+ This specification intends to meet the following requirements:
</p>
+ <ulist>
+ <item>
+ <p>
+ Support enumeration of data sources
+ that cannot practically fit into a single SOAP
+ message.
+ </p>
+ </item>
+ <item>
+ <p>
+ Support both server-side and
+ client-side enumeration state maintenance.
+ </p>
+ </item>
+ <item>
+ <p>
+ Minimize additional mechanism
+ beyond the current web service architecture.
+ </p>
+ </item>
+ </ulist>
+ </div2>
+ </div1>
+
+ <div1 id="termsNotes">
+ <head>Notations and Terminology</head>
+ <p>
+ This section specifies the notations,
+ namespaces, and terminology used in this
+ specification.
+ </p>
+
+ <div2 id="conv">
+ <head>Notational Conventions</head>
+
<p>
- A data source MAY provide a custom mechanism for
- starting a new enumeration. For instance, a data source that
- provides access to a SQL database can support a SELECT operation
- that performs a database query and uses an explicit database cursor
- to iterate through the returned rows. In general, however, it is
- simpler if all data sources support a single, standard operation to
- start an enumeration. This specification mandates
- that data sources MUST implement the Enumerate operation for starting a new
- enumeration of a data source.
- Each new enumeration results in a distinct enumeration context,
- each with its own logical cursor/position.
+ 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>
+
<p>
- Note that different
- enumerations of the same data source can produce different results;
- this can happen even for two enumeration contexts created
- concurrently by a single consumer using identical Enumerate
- requests. The ordering or completeness of the enumeration
- is undefined; the returned data items represent a selection by the
- data source of items it wishes to present to that consumer at that
- time in that order, with no guarantee that every available item is
- returned or that the order in which items is returned has any
- semantic meaning whatsoever (of course, any specific data source
- can provide strong guarantees, if so desired). In particular,
- note that the very act of enumerating the contents of a
- data source can modify the contents of the data source; for
- instance, a queue might be represented as a data source such that
- items that are returned in a Enumerate response are removed from the
- queue.
+ This specification uses the following syntax to
+ define normative outlines for messages:
</p>
-
- <div2 id="reqs">
- <head>Requirements</head>
+
+ <ulist>
+ <item>
<p>
- This specification intends to meet the following requirements:
+ The syntax appears as an XML
+ instance, but values in italics indicate data types instead of
+ values.
</p>
- <ulist>
- <item>
- <p>
- Support enumeration of data sources
- that cannot practically fit into a single SOAP
- message.
- </p>
- </item>
- <item>
- <p>
- Support both server-side and
- client-side enumeration state maintenance.
- </p>
- </item>
- <item>
- <p>
- Minimize additional mechanism
- beyond the current web service architecture.
- </p>
- </item>
- </ulist>
- </div2>
- </div1>
+ </item>
+ <item>
+ <p>
+ Characters are appended to elements
+ and attributes to indicate cardinality:
+ </p>
+ </item>
+ <item>
+ <p>
+ "?" (0 or 1)
+ </p>
+ </item>
+ <item>
+ <p>
+ "*" (0 or more)
+ </p>
+ </item>
+ <item>
+ <p>
+ "+" (1 or more)
+ </p>
+ </item>
+ <item>
+ <p>
+ The character "|" is used to
+ indicate a choice between alternatives.
+ </p>
+ </item>
+ <item>
+ <p>
+ The characters "(" and ")" are used to indicate that contained items
+ are to be treated as a group with respect to cardinality or choice.
+ </p>
+ </item>
+ <item>
+ <p>
+ The characters "[" and "]" are used to call out references and
+ property names.
+ </p>
+ </item>
+ <item>
+ <p>
+ Ellipsis (i.e. "...") indicate points of extensibility.
+ </p>
+ </item>
+ <item>
+ <p>
+ XML namespace prefixes (see <specref ref="xmlnamespaces"/>) are used
+ to indicate the namespace of the element being
+ defined.
+ </p>
+ </item>
+ </ulist>
- <div1 id="termsNotes">
- <head>Notations and Terminology</head>
<p>
- This section specifies the notations,
- namespaces, and terminology used in this
- specification.
+ In addition to Message Information Header properties
+ <bibref ref="AddrCore"/>,
+ this specification uses the following properties to define messages:
</p>
- <div2 id="conv">
- <head>Notational Conventions</head>
+ <glist>
+ <gitem>
+ <label> <kw>[Headers]</kw> </label>
+ <def>
+ <p> Unordered message headers. </p>
+ </def>
+ </gitem>
- <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>
-
- <p>
- This specification uses the following syntax to
- define normative outlines for messages:
- </p>
-
- <ulist>
- <item>
- <p>
- The syntax appears as an XML
- instance, but values in italics indicate data types instead of
- values.
- </p>
- </item>
- <item>
- <p>
- Characters are appended to elements
- and attributes to indicate cardinality:
- </p>
- </item>
- <item>
- <p>
- "?" (0 or 1)
- </p>
- </item>
- <item>
- <p>
- "*" (0 or more)
- </p>
- </item>
- <item>
- <p>
- "+" (1 or more)
- </p>
- </item>
- <item>
- <p>
- The character "|" is used to
- indicate a choice between alternatives.
- </p>
- </item>
- <item>
- <p>
- The characters "(" and ")" are used to indicate that contained items
- are to be treated as a group with respect to cardinality or choice.
- </p>
- </item>
- <item>
- <p>
- The characters "[" and "]" are used to call out references and
- property names.
- </p>
- </item>
- <item>
- <p>
- Ellipsis (i.e. "...") indicate points of extensibility.
- </p>
- </item>
- <item>
- <p>
- XML namespace prefixes (see <specref ref="xmlnamespaces"/>) are used
- to indicate the namespace of the element being
- defined.
- </p>
- </item>
- </ulist>
+ <gitem>
+ <label> <kw>[Action]</kw> </label>
+ <def>
+ <p> The value to be used for the wsa:Action IRI. </p>
+ </def>
+ </gitem>
- <p>
- In addition to Message Information Header properties
- <bibref ref="AddrCore"/>,
- this specification uses the following properties to define messages:
- </p>
-
- <glist>
- <gitem>
- <label> <kw>[Headers]</kw> </label>
- <def>
- <p> Unordered message headers. </p>
- </def>
- </gitem>
-
- <gitem>
- <label> <kw>[Action]</kw> </label>
- <def>
- <p> The value to be used for the wsa:Action IRI. </p>
- </def>
- </gitem>
-
- <gitem>
- <label> <kw>[Body]</kw> </label>
- <def>
- <p> A message body. </p>
- </def>
- </gitem>
- </glist>
-
- <p>
- These properties bind to a SOAP Envelope as follows:
- </p>
-
- <example>
- <eg><s:Envelope>
+ <gitem>
+ <label> <kw>[Body]</kw> </label>
+ <def>
+ <p> A message body. </p>
+ </def>
+ </gitem>
+ </glist>
+
+ <p>
+ These properties bind to a SOAP Envelope as follows:
+ </p>
+
+ <example>
+ <eg><s:Envelope>
<s:Header>
<kw>[Headers]</kw>
<wsa:Action><kw>[Action]</kw></wsa:Action>
@@ -324,247 +324,254 @@
</s:Header>
<s:Body><kw>[Body]</kw></s:Body>
</s:Envelope></eg>
- </example>
+ </example>
- <p>
- This specification can be used in terms of XML Information Set (Infoset)
- <bibref ref="XMLInfoset"/>, even though the specification uses XML 1.0
- terminology. Valid Infoset for this specification is the one
- serializable in XML 1.0, hence the use of XML 1.0.
- </p>
+ <p>
+ This specification can be used in terms of XML Information Set (Infoset)
+ <bibref ref="XMLInfoset"/>, even though the specification uses XML 1.0
+ terminology. Valid Infoset for this specification is the one
+ serializable in XML 1.0, hence the use of XML 1.0.
+ </p>
- <p>
- The term "generate" is used in relation to the various faults defined
- by this specification to imply that a fault is produced and no
- further processing SHOULD be performed. In these cases the fault
- SHOULD be transmitted. However, there might be reasons when a compliant
- implementation can choose not to transmit the fault - for example,
- security concerns - in these situations the service MAY choose
- not to transmit the fault.
- </p>
+ <p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ further processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the service MAY choose
+ not to transmit the fault.
+ </p>
- </div2>
+ </div2>
- <div2 id="extensions">
- <head>Considerations on the Use of Extensibility Points</head>
+ <div2 id="extensions">
+ <head>Considerations on the Use of Extensibility Points</head>
- <p>
- The elements defined in this specification MAY be extended at the
- points indicated by their outlines and schema. Implementations MAY
- add child elements and/or attributes at the indicated extension
- points but MUST NOT contradict the semantics of the parent and/or
- owner, respectively. If a receiver does not recognize an extension,
- the receiver SHOULD ignore that extension. Senders MAY indicate
- the presence of an extension that has to be understood through the use
- of a corresponding SOAP Header with a soap:mustUnderstand attribute
- with the value "1".
- </p>
+ <p>
+ The elements defined in this specification MAY be extended at the
+ points indicated by their outlines and schema. Implementations MAY
+ add child elements and/or attributes at the indicated extension
+ points but MUST NOT contradict the semantics of the parent and/or
+ owner, respectively. If a receiver does not recognize an extension,
+ the receiver SHOULD ignore that extension. Senders MAY indicate
+ the presence of an extension that has to be understood through the use
+ of a corresponding SOAP Header with a soap:mustUnderstand attribute
+ with the value "1".
+ </p>
- <p>
- In cases where it is either desirable or necessary for the receiver
- of a request that has been extended to indicate that it has
- recognized and accepted the semantics associated with that extension,
- it is RECOMMENDED that the receiver add a corresponding extension
- to the response message. The definition of an extension SHOULD clearly
- specify how the extension that appears in the response correlates
- with that in the corresponding request.
- </p>
+ <p>
+ In cases where it is either desirable or necessary for the receiver
+ of a request that has been extended to indicate that it has
+ recognized and accepted the semantics associated with that extension,
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD clearly
+ specify how the extension that appears in the response correlates
+ with that in the corresponding request.
+ </p>
- <p>
- Extension elements and attributes MUST NOT use the Web Services
- Enumeration namespace URI.
- </p>
- </div2>
+ <p>
+ Extension elements and attributes MUST NOT use the Web Services
+ Enumeration namespace URI.
+ </p>
+ </div2>
- <div2 id="terms">
- <head>Terminology</head>
+ <div2 id="terms">
+ <head>Terminology</head>
- <glist>
- <gitem>
- <label> Consumer </label>
- <def>
- <p>
- The Web service that is requesting the data
- enumeration from the data source
- </p>
- </def>
- </gitem>
-
- <gitem>
- <label> Data Source </label>
- <def>
- <p>
- A Web service that supports traversal using
- enumeration contexts via the Enumerate operation defined in this
- specification
- </p>
- </def>
- </gitem>
+ <glist>
+ <gitem>
+ <label> Consumer </label>
+ <def>
+ <p>
+ The Web service that is requesting the data
+ enumeration from the data source
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> Data Source </label>
+ <def>
+ <p>
+ A Web service that supports traversal using
+ enumeration contexts via the Enumerate operation defined in this
+ specification
+ </p>
+ </def>
+ </gitem>
- <gitem>
- <label> Enumeration context </label>
- <def>
- <p>
- A session context that represents a specific
- traversal through a logical sequence of XML element information
- items using the Enumerate operation defined in this
- specification
- </p>
- </def>
- </gitem>
- </glist>
- </div2>
+ <gitem>
+ <label> Enumeration context </label>
+ <def>
+ <p>
+ A session context that represents a specific
+ traversal through a logical sequence of XML element information
+ items using the Enumerate operation defined in this
+ specification
+ </p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
- <div2 id="compliance">
- <head>Compliance</head>
-
- <p>
- An implementation is not compliant with this specification if it fails to
- satisfy one or more of the MUST or REQUIRED level requirements defined
- herein. A SOAP Node MUST NOT use the XML namespace identifier for this
- specification (listed in <specref ref="namespaces"/>) within SOAP
- Envelopes unless it is compliant with this specification.
- </p>
-
- <p>
- Normative text within this specification takes precedence over the XML
- Schema and WSDL descriptions, which in turn take precedence over
- outlines, which in turn take precedence over examples.
- </p>
-
- <p>
- All messages defined by this specification MUST conform to the
- WS-Addressing specifications and be sent to a Web service that
- is addressable by an EPR (see <bibref ref="AddrCore"/>).
- </p>
+ <div2 id="compliance">
+ <head>Compliance</head>
+
+ <p>
+ An implementation is not compliant with this specification if it fails to
+ satisfy one or more of the MUST or REQUIRED level requirements defined
+ herein. A SOAP Node MUST NOT use the XML namespace identifier for this
+ specification (listed in <specref ref="namespaces"/>) within SOAP
+ Envelopes unless it is compliant with this specification.
+ </p>
+
+ <p>
+ Normative text within this specification takes precedence over the XML
+ Schema and WSDL descriptions, which in turn take precedence over
+ outlines, which in turn take precedence over examples.
+ </p>
+
+ <p>
+ All messages defined by this specification MUST conform to the
+ WS-Addressing specifications and be sent to a Web service that
+ is addressable by an EPR (see <bibref ref="AddrCore"/>).
+ </p>
- <p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
- </p>
+ <p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
+ </p>
- <p>
- For any message defined by this specification, any OPTIONAL elements
- or attributes in the message MAY be used by senders of the message;
- however receivers of those messages MUST support those OPTIONAL
- elements and attributes, unless other behavior is explicitly defined
- by this specification.
- </p>
+ <p>
+ For any message defined by this specification, any OPTIONAL elements
+ or attributes in the message MAY be used by senders of the message;
+ however receivers of those messages MUST support those OPTIONAL
+ elements and attributes, unless other behavior is explicitly defined
+ by this specification.
+ </p>
- <p>
- Implementations are expected to support both UTF-8 and UTF-16 as
- described in XML 1.0.
- </p>
-
- </div2>
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
- <div2 id="namespaces">
- <head>XML Namespaces</head>
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
+
+ </div2>
- <p>
- The XML namespace URI that MUST be used by
- implementations of this specification is:
- </p>
- <example>
- <eg><loc href="http://www.w3.org/&wsenu.nsprefix;/ws-enu">http://www.w3.org/&wsenu.nsprefix;/ws-enu</loc></eg>
- </example>
+ <div2 id="namespaces">
+ <head>XML Namespaces</head>
- <p>
- <specref ref="xmlnamespaces"/> lists XML namespaces that are used in
- this specification. The choice of any namespace prefix is arbitrary
- and not semantically significant.
- </p>
+ <p>
+ The XML namespace URI that MUST be used by
+ implementations of this specification is:
+ </p>
+ <example>
+ <eg><loc href="http://www.w3.org/&wsenu.nsprefix;/ws-enu">http://www.w3.org/&wsenu.nsprefix;/ws-enu</loc></eg>
+ </example>
- <table id='xmlnamespaces' border="1">
- <caption>
- Prefixes and XML namespaces used in this specification
- </caption>
+ <p>
+ <specref ref="xmlnamespaces"/> lists XML namespaces that are used in
+ this specification. The choice of any namespace prefix is arbitrary
+ and not semantically significant.
+ </p>
- <tbody>
- <tr>
- <th align="left"> Prefix </th>
- <th align="left"> XML Namespace </th>
- <th align="left"> Specification(s) </th>
- </tr>
+ <table id='xmlnamespaces' border="1">
+ <caption>
+ Prefixes and XML namespaces used in this specification
+ </caption>
- <tr>
- <td> wsen </td>
- <td>
- <loc href="http://www.w3.org/&wsenu.nsprefix;/ws-enu">
- http://www.w3.org/&wsenu.nsprefix;/ws-enu
- </loc>
- </td>
- <td> This specification </td>
- </tr>
- <tr>
- <td> s </td>
- <td>
- <loc href="http://www.w3.org/2003/05/soap-envelope">
- http://www.w3.org/2003/05/soap-envelope
- </loc>
- </td>
- <td> SOAP 1.2 <bibref ref="SOAP12"/> </td>
- </tr>
- <tr>
- <td> s11 </td>
- <td>
- <loc href="http://schemas.xmlsoap.org/soap/envelope/">
- http://schemas.xmlsoap.org/soap/envelope/
- </loc>
- </td>
- <td> SOAP 1.1 <bibref ref="SOAP11"/> </td>
- </tr>
- <tr>
- <td> wsa </td>
- <td>
- <loc href="http://www.w3.org/2005/08/addressing">
- http://www.w3.org/2005/08/addressing
- </loc>
- </td>
- <td> WS-Addressing <bibref ref="AddrCore"/> </td>
- </tr>
- <tr>
- <td> xs </td>
- <td>
- <loc href="http://www.w3.org/2001/XMLSchema">
- http://www.w3.org/2001/XMLSchema
- </loc>
- </td>
- <td>
- XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
- </td>
- </tr>
- <tr>
- <td> wsdl </td>
- <td>
- <loc href="http://schemas.xmlsoap.org/wsdl">
- http://schemas.xmlsoap.org/wsdl
- </loc>
- </td>
- <td> WSDL/1.1 <bibref ref="WSDL11"/> </td>
- </tr>
- </tbody>
- </table>
+ <tbody>
+ <tr>
+ <th align="left"> Prefix </th>
+ <th align="left"> XML Namespace </th>
+ <th align="left"> Specification(s) </th>
+ </tr>
- <p>
- The working group intends to update the value of the Web Services
- Enumeration namespace URI each time a new version of this document is
- published until such time that the document reaches Candidate
- Recommendation status. Once it has reached Candidate Recommendation
- status, the working group intends to maintain the value of the
- Web Services Enumeration namespace URI that was assigned in the
- Candidate Recommendation unless significant changes are made that
- impact the implementation or break post-CR implementations of the
- specification. Also see
- <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
- http://www.w3.org/2001/tag/doc/namespaceState.html
- </loc> and
- <loc href="http://www.w3.org/2005/07/13-nsuri">
- http://www.w3.org/2005/07/13-nsuri
- </loc>.
- </p>
+ <tr>
+ <td> wsen </td>
+ <td>
+ <loc href="http://www.w3.org/&wsenu.nsprefix;/ws-enu">
+ http://www.w3.org/&wsenu.nsprefix;/ws-enu
+ </loc>
+ </td>
+ <td> This specification </td>
+ </tr>
+ <tr>
+ <td> s </td>
+ <td>
+ <loc href="http://www.w3.org/2003/05/soap-envelope">
+ http://www.w3.org/2003/05/soap-envelope
+ </loc>
+ </td>
+ <td> SOAP 1.2 <bibref ref="SOAP12"/> </td>
+ </tr>
+ <tr>
+ <td> s11 </td>
+ <td>
+ <loc href="http://schemas.xmlsoap.org/soap/envelope/">
+ http://schemas.xmlsoap.org/soap/envelope/
+ </loc>
+ </td>
+ <td> SOAP 1.1 <bibref ref="SOAP11"/> </td>
+ </tr>
+ <tr>
+ <td> wsa </td>
+ <td>
+ <loc href="http://www.w3.org/2005/08/addressing">
+ http://www.w3.org/2005/08/addressing
+ </loc>
+ </td>
+ <td> WS-Addressing <bibref ref="AddrCore"/> </td>
+ </tr>
+ <tr>
+ <td> xs </td>
+ <td>
+ <loc href="http://www.w3.org/2001/XMLSchema">
+ http://www.w3.org/2001/XMLSchema
+ </loc>
+ </td>
+ <td>
+ XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
+ </td>
+ </tr>
+ <tr>
+ <td> wsdl </td>
+ <td>
+ <loc href="http://schemas.xmlsoap.org/wsdl">
+ http://schemas.xmlsoap.org/wsdl
+ </loc>
+ </td>
+ <td> WSDL/1.1 <bibref ref="WSDL11"/> </td>
+ </tr>
+ </tbody>
+ </table>
- </div2>
+ <p>
+ The working group intends to update the value of the Web Services
+ Enumeration namespace URI each time a new version of this document is
+ published until such time that the document reaches Candidate
+ Recommendation status. Once it has reached Candidate Recommendation
+ status, the working group intends to maintain the value of the
+ Web Services Enumeration namespace URI that was assigned in the
+ Candidate Recommendation unless significant changes are made that
+ impact the implementation or break post-CR implementations of the
+ specification. Also see
+ <loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
+ http://www.w3.org/2001/tag/doc/namespaceState.html
+ </loc> and
+ <loc href="http://www.w3.org/2005/07/13-nsuri">
+ http://www.w3.org/2005/07/13-nsuri
+ </loc>.
+ </p>
+
+ </div2>
</div1>
@@ -2589,6 +2596,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -2669,20 +2694,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- wsfrag.xml 19 Nov 2010 22:43:20 -0000 1.72
+++ wsfrag.xml 28 Nov 2010 15:54:18 -0000 1.73
@@ -397,6 +397,13 @@
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
</p>
+
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
</div2>
@@ -1948,6 +1955,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -2037,20 +2062,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- wsfrag.html 19 Nov 2010 22:43:19 -0000 1.75
+++ wsfrag.html 28 Nov 2010 15:54:18 -0000 1.76
@@ -57,8 +57,8 @@
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="#iddiv1x1x1421">Examples</a><br/>
- 5.1 <a href="#iddiv2x1x1424">Examples</a><br/>
+5 <a href="#iddiv1x1x1429">Examples</a><br/>
+ 5.1 <a href="#iddiv2x1x1432">Examples</a><br/>
6 <a href="#QName">QName Expression Language</a><br/>
7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
8 <a href="#XPath20">XPath 2.0 Expression Language</a><br/>
@@ -67,10 +67,10 @@
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="#iddiv2x1x1889">Fragment Assertion</a><br/>
+ 10.1 <a href="#iddiv2x1x1897">Fragment Assertion</a><br/>
11 <a href="#acks">Acknowledgements</a><br/>
12 <a href="#refs">References</a><br/>
- 12.1 <a href="#iddiv2x1x1952">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x1960">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/>
@@ -237,6 +237,11 @@
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML Namespace URI that MUST be used by implementations of this
@@ -600,8 +605,8 @@
This specification does not extend the Create operation defined in
WS-Transfer.
</p></div></div><div class="div1">
-<h2><a name="iddiv1x1x1421" id="iddiv1x1x1421"/>5 Examples</h2><div class="div2">
-<h3><a name="iddiv2x1x1424" id="iddiv2x1x1424"/>5.1 Examples</h3><p>
+<h2><a name="iddiv1x1x1429" id="iddiv1x1x1429"/>5 Examples</h2><div class="div2">
+<h3><a name="iddiv2x1x1432" id="iddiv2x1x1432"/>5.1 Examples</h3><p>
In the following examples, and Expression Language definitions,
the following representation of a resource is used for
informational purposes:
@@ -851,7 +856,7 @@
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
-<h3><a name="iddiv2x1x1889" id="iddiv2x1x1889"/>10.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2x1x1897" id="iddiv2x1x1897"/>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 -
@@ -915,7 +920,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2x1x1952" id="iddiv2x1x1952"/>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>
+<h3><a name="iddiv2x1x1960" id="iddiv2x1x1960"/>12.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -966,17 +981,7 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
Index: wssa.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- wssa.xml 19 Nov 2010 22:43:20 -0000 1.10
+++ wssa.xml 28 Nov 2010 15:54:18 -0000 1.11
@@ -261,6 +261,13 @@
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
</p>
+
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
</div2>
@@ -508,6 +515,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -570,20 +595,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -d -r1.131 -r1.132
--- wsmex.xml 19 Nov 2010 22:43:20 -0000 1.131
+++ wsmex.xml 28 Nov 2010 15:54:18 -0000 1.132
@@ -732,6 +732,13 @@
described in XML 1.0.
</p>
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
+
</div2>
<div2 id="namespaces">
@@ -3194,6 +3201,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -3292,20 +3317,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- wsenum.html 19 Nov 2010 22:43:19 -0000 1.153
+++ wsenum.html 28 Nov 2010 15:54:18 -0000 1.154
@@ -68,15 +68,15 @@
5.10 <a href="#EmptyFilter">EmptyFilter</a><br/>
5.11 <a href="#MaxElementsMustBeZero">MaxElementsMustBeZero</a><br/>
6 <a href="#Security">Security Considerations</a><br/>
- 6.1 <a href="#iddiv2x1x1900">Creating Enumeration Contexts</a><br/>
- 6.2 <a href="#iddiv2x1x1905">Protecting Enumeration Contexts</a><br/>
- 6.3 <a href="#iddiv2x1x1912">Endpoint Verification</a><br/>
+ 6.1 <a href="#iddiv2x1x1908">Creating Enumeration Contexts</a><br/>
+ 6.2 <a href="#iddiv2x1x1913">Protecting Enumeration Contexts</a><br/>
+ 6.3 <a href="#iddiv2x1x1920">Endpoint Verification</a><br/>
7 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 7.1 <a href="#iddiv2x1x1932">Enumeration Assertion</a><br/>
+ 7.1 <a href="#iddiv2x1x1940">Enumeration Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2x1x2052">Normative References</a><br/>
- 9.2 <a href="#iddiv2x1x2256">Informative References</a><br/>
+ 9.1 <a href="#iddiv2x1x2060">Normative References</a><br/>
+ 9.2 <a href="#iddiv2x1x2272">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/>
@@ -95,124 +95,124 @@
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
- fit into this simple paradigm include streaming, traversal, query,
- and enumeration.
- </p><p>
- This specification defines a simple SOAP-based
- protocol for enumeration that allows the data source to provide a
- session abstraction, called an enumeration context, to a consumer
- that represents a logical cursor through a sequence of data items.
- The consumer can then request XML element information items using
- this enumeration context over the span of one or more SOAP
- messages.
- </p><p>
- Somewhere, state MUST be maintained regarding
- the progress of the iteration. This state MAY be maintained between
- requests by the data source being enumerated or by the data
- consumer. WS-Enumeration allows the data source to decide, on a
- request-by-request basis, which party will be responsible for
- maintaining this state for the next request.
- </p><p>
- In its simplest form, WS-Enumeration defines an operation, Enumerate,
- used to establish the creation of an enumeration session or
- which allows a data source, in the context
- of a specific enumeration, to produce a sequence of XML elements in
- the body of a SOAP message. Each subsequent Enumerate operation returns
- the next N elements in the aggregate sequence.
- </p><p>
- A data source MAY provide a custom mechanism for
- starting a new enumeration. For instance, a data source that
- provides access to a SQL database can support a SELECT operation
- that performs a database query and uses an explicit database cursor
- to iterate through the returned rows. In general, however, it is
- simpler if all data sources support a single, standard operation to
- start an enumeration. This specification mandates
- that data sources MUST implement the Enumerate operation for starting a new
- enumeration of a data source.
- Each new enumeration results in a distinct enumeration context,
- each with its own logical cursor/position.
- </p><p>
- Note that different
- enumerations of the same data source can produce different results;
- this can happen even for two enumeration contexts created
- concurrently by a single consumer using identical Enumerate
- requests. The ordering or completeness of the enumeration
- is undefined; the returned data items represent a selection by the
- data source of items it wishes to present to that consumer at that
- time in that order, with no guarantee that every available item is
- returned or that the order in which items is returned has any
- semantic meaning whatsoever (of course, any specific data source
- can provide strong guarantees, if so desired). In particular,
- note that the very act of enumerating the contents of a
- data source can modify the contents of the data source; for
- instance, a queue might be represented as a data source such that
- items that are returned in a Enumerate response are removed from the
- queue.
- </p><div class="div2">
+ There are numerous applications for which a
+ simple single-request/single-reply metaphor is insufficient for
+ transferring large data sets over SOAP. Applications that do not
+ fit into this simple paradigm include streaming, traversal, query,
+ and enumeration.
+ </p><p>
+ This specification defines a simple SOAP-based
+ protocol for enumeration that allows the data source to provide a
+ session abstraction, called an enumeration context, to a consumer
+ that represents a logical cursor through a sequence of data items.
+ The consumer can then request XML element information items using
+ this enumeration context over the span of one or more SOAP
+ messages.
+ </p><p>
+ Somewhere, state MUST be maintained regarding
+ the progress of the iteration. This state MAY be maintained between
+ requests by the data source being enumerated or by the data
+ consumer. WS-Enumeration allows the data source to decide, on a
+ request-by-request basis, which party will be responsible for
+ maintaining this state for the next request.
+ </p><p>
+ In its simplest form, WS-Enumeration defines an operation, Enumerate,
+ used to establish the creation of an enumeration session or
+ which allows a data source, in the context
+ of a specific enumeration, to produce a sequence of XML elements in
+ the body of a SOAP message. Each subsequent Enumerate operation returns
+ the next N elements in the aggregate sequence.
+ </p><p>
+ A data source MAY provide a custom mechanism for
+ starting a new enumeration. For instance, a data source that
+ provides access to a SQL database can support a SELECT operation
+ that performs a database query and uses an explicit database cursor
+ to iterate through the returned rows. In general, however, it is
+ simpler if all data sources support a single, standard operation to
+ start an enumeration. This specification mandates
+ that data sources MUST implement the Enumerate operation for starting a new
+ enumeration of a data source.
+ Each new enumeration results in a distinct enumeration context,
+ each with its own logical cursor/position.
+ </p><p>
+ Note that different
+ enumerations of the same data source can produce different results;
+ this can happen even for two enumeration contexts created
+ concurrently by a single consumer using identical Enumerate
+ requests. The ordering or completeness of the enumeration
+ is undefined; the returned data items represent a selection by the
+ data source of items it wishes to present to that consumer at that
+ time in that order, with no guarantee that every available item is
+ returned or that the order in which items is returned has any
+ semantic meaning whatsoever (of course, any specific data source
+ can provide strong guarantees, if so desired). In particular,
+ note that the very act of enumerating the contents of a
+ data source can modify the contents of the data source; for
+ instance, a queue might be represented as a data source such that
+ items that are returned in a Enumerate response are removed from the
+ queue.
+ </p><div class="div2">
<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>
- This specification intends to meet the following requirements:
- </p><ul><li><p>
- Support enumeration of data sources
- that cannot practically fit into a single SOAP
- message.
- </p></li><li><p>
- Support both server-side and
- client-side enumeration state maintenance.
- </p></li><li><p>
- Minimize additional mechanism
- beyond the current web service architecture.
- </p></li></ul></div></div><div class="div1">
+ This specification intends to meet the following requirements:
+ </p><ul><li><p>
+ Support enumeration of data sources
+ that cannot practically fit into a single SOAP
+ message.
+ </p></li><li><p>
+ Support both server-side and
+ client-side enumeration state maintenance.
+ </p></li><li><p>
+ Minimize additional mechanism
+ beyond the current web service architecture.
+ </p></li></ul></div></div><div class="div1">
<h2><a name="termsNotes" id="termsNotes"/>3 Notations and Terminology</h2><p>
- This section specifies the notations,
- namespaces, and terminology used in this
- specification.
- </p><div class="div2">
+ This section specifies the notations,
+ namespaces, and terminology used in this
+ specification.
+ </p><div class="div2">
<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
- in RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.
- </p><p>
- This specification uses the following syntax to
- define normative outlines for messages:
- </p><ul><li><p>
- The syntax appears as an XML
- instance, but values in italics indicate data types instead of
- values.
- </p></li><li><p>
- Characters are appended to elements
- and attributes to indicate cardinality:
- </p></li><li><p>
- "?" (0 or 1)
- </p></li><li><p>
- "*" (0 or more)
- </p></li><li><p>
- "+" (1 or more)
- </p></li><li><p>
- The character "|" is used to
- indicate a choice between alternatives.
- </p></li><li><p>
- The characters "(" and ")" are used to indicate that contained items
- are to be treated as a group with respect to cardinality or choice.
- </p></li><li><p>
- The characters "[" and "]" are used to call out references and
- property names.
- </p></li><li><p>
- Ellipsis (i.e. "...") indicate points of extensibility.
- </p></li><li><p>
- XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
- to indicate the namespace of the element being
- defined.
- </p></li></ul><p>
- In addition to Message Information Header properties
- <a href="#AddrCore">[WS-Addressing]</a>,
- this specification uses the following properties to define messages:
- </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
- These properties bind to a SOAP Envelope as follows:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
+ The keywords "MUST", "MUST NOT", "REQUIRED",
+ "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
+ and "OPTIONAL" in this document are to be interpreted as described
+ in RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.
+ </p><p>
+ This specification uses the following syntax to
+ define normative outlines for messages:
+ </p><ul><li><p>
+ The syntax appears as an XML
+ instance, but values in italics indicate data types instead of
+ values.
+ </p></li><li><p>
+ Characters are appended to elements
+ and attributes to indicate cardinality:
+ </p></li><li><p>
+ "?" (0 or 1)
+ </p></li><li><p>
+ "*" (0 or more)
+ </p></li><li><p>
+ "+" (1 or more)
+ </p></li><li><p>
+ The character "|" is used to
+ indicate a choice between alternatives.
+ </p></li><li><p>
+ The characters "(" and ")" are used to indicate that contained items
+ are to be treated as a group with respect to cardinality or choice.
+ </p></li><li><p>
+ The characters "[" and "]" are used to call out references and
+ property names.
+ </p></li><li><p>
+ Ellipsis (i.e. "...") indicate points of extensibility.
+ </p></li><li><p>
+ XML namespace prefixes (see <a href="#xmlnamespaces">Table 3-1</a>) are used
+ to indicate the namespace of the element being
+ defined.
+ </p></li></ul><p>
+ In addition to Message Information Header properties
+ <a href="#AddrCore">[WS-Addressing]</a>,
+ this specification uses the following properties to define messages:
+ </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+ These properties bind to a SOAP Envelope as follows:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
<s:Header>
<b>[Headers]</b>
<wsa:Action><b>[Action]</b></wsa:Action>
@@ -220,119 +220,124 @@
</s:Header>
<s:Body><b>[Body]</b></s:Body>
</s:Envelope></pre></div></div><p>
- This specification can be used in terms of XML Information Set (Infoset)
- <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
- terminology. Valid Infoset for this specification is the one
- serializable in XML 1.0, hence the use of XML 1.0.
- </p><p>
- The term "generate" is used in relation to the various faults defined
- by this specification to imply that a fault is produced and no
- further processing SHOULD be performed. In these cases the fault
- SHOULD be transmitted. However, there might be reasons when a compliant
- implementation can choose not to transmit the fault - for example,
- security concerns - in these situations the service MAY choose
- not to transmit the fault.
- </p></div><div class="div2">
+ This specification can be used in terms of XML Information Set (Infoset)
+ <a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
+ terminology. Valid Infoset for this specification is the one
+ serializable in XML 1.0, hence the use of XML 1.0.
+ </p><p>
+ The term "generate" is used in relation to the various faults defined
+ by this specification to imply that a fault is produced and no
+ further processing SHOULD be performed. In these cases the fault
+ SHOULD be transmitted. However, there might be reasons when a compliant
+ implementation can choose not to transmit the fault - for example,
+ security concerns - in these situations the service MAY choose
+ not to transmit the fault.
+ </p></div><div class="div2">
<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
- The elements defined in this specification MAY be extended at the
- points indicated by their outlines and schema. Implementations MAY
- add child elements and/or attributes at the indicated extension
- points but MUST NOT contradict the semantics of the parent and/or
- owner, respectively. If a receiver does not recognize an extension,
- the receiver SHOULD ignore that extension. Senders MAY indicate
- the presence of an extension that has to be understood through the use
- of a corresponding SOAP Header with a soap:mustUnderstand attribute
- with the value "1".
- </p><p>
- In cases where it is either desirable or necessary for the receiver
- of a request that has been extended to indicate that it has
- recognized and accepted the semantics associated with that extension,
- it is RECOMMENDED that the receiver add a corresponding extension
- to the response message. The definition of an extension SHOULD clearly
- specify how the extension that appears in the response correlates
- with that in the corresponding request.
- </p><p>
- Extension elements and attributes MUST NOT use the Web Services
- Enumeration namespace URI.
- </p></div><div class="div2">
+ The elements defined in this specification MAY be extended at the
+ points indicated by their outlines and schema. Implementations MAY
+ add child elements and/or attributes at the indicated extension
+ points but MUST NOT contradict the semantics of the parent and/or
+ owner, respectively. If a receiver does not recognize an extension,
+ the receiver SHOULD ignore that extension. Senders MAY indicate
+ the presence of an extension that has to be understood through the use
+ of a corresponding SOAP Header with a soap:mustUnderstand attribute
+ with the value "1".
+ </p><p>
+ In cases where it is either desirable or necessary for the receiver
+ of a request that has been extended to indicate that it has
+ recognized and accepted the semantics associated with that extension,
+ it is RECOMMENDED that the receiver add a corresponding extension
+ to the response message. The definition of an extension SHOULD clearly
+ specify how the extension that appears in the response correlates
+ with that in the corresponding request.
+ </p><p>
+ Extension elements and attributes MUST NOT use the Web Services
+ Enumeration namespace URI.
+ </p></div><div class="div2">
<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
- The Web service that is requesting the data
- enumeration from the data source
- </p></dd><dt class="label"> Data Source </dt><dd><p>
- A Web service that supports traversal using
- enumeration contexts via the Enumerate operation defined in this
- specification
- </p></dd><dt class="label"> Enumeration context </dt><dd><p>
- A session context that represents a specific
- traversal through a logical sequence of XML element information
- items using the Enumerate operation defined in this
- specification
- </p></dd></dl></div><div class="div2">
+ The Web service that is requesting the data
+ enumeration from the data source
+ </p></dd><dt class="label"> Data Source </dt><dd><p>
+ A Web service that supports traversal using
+ enumeration contexts via the Enumerate operation defined in this
+ specification
+ </p></dd><dt class="label"> Enumeration context </dt><dd><p>
+ A session context that represents a specific
+ traversal through a logical sequence of XML element information
+ items using the Enumerate operation defined in this
+ specification
+ </p></dd></dl></div><div class="div2">
<h3><a name="compliance" id="compliance"/>3.4 Compliance</h3><p>
- An implementation is not compliant with this specification if it fails to
- satisfy one or more of the MUST or REQUIRED level requirements defined
- herein. A SOAP Node MUST NOT use the XML namespace identifier for this
- specification (listed in <a href="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP
- Envelopes unless it is compliant with this specification.
- </p><p>
- Normative text within this specification takes precedence over the XML
- Schema and WSDL descriptions, which in turn take precedence over
- outlines, which in turn take precedence over examples.
- </p><p>
- All messages defined by this specification MUST conform to the
- WS-Addressing specifications and be sent to a Web service that
- is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
- </p><p>
- Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
- MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
- </p><p>
- For any message defined by this specification, any OPTIONAL elements
- or attributes in the message MAY be used by senders of the message;
- however receivers of those messages MUST support those OPTIONAL
- elements and attributes, unless other behavior is explicitly defined
- by this specification.
- </p><p>
- Implementations are expected to support both UTF-8 and UTF-16 as
- described in XML 1.0.
- </p></div><div class="div2">
+ An implementation is not compliant with this specification if it fails to
+ satisfy one or more of the MUST or REQUIRED level requirements defined
+ herein. A SOAP Node MUST NOT use the XML namespace identifier for this
+ specification (listed in <a href="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP
+ Envelopes unless it is compliant with this specification.
+ </p><p>
+ Normative text within this specification takes precedence over the XML
+ Schema and WSDL descriptions, which in turn take precedence over
+ outlines, which in turn take precedence over examples.
+ </p><p>
+ All messages defined by this specification MUST conform to the
+ WS-Addressing specifications and be sent to a Web service that
+ is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
+ </p><p>
+ Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
+ MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
+ </p><p>
+ For any message defined by this specification, any OPTIONAL elements
+ or attributes in the message MAY be used by senders of the message;
+ however receivers of those messages MUST support those OPTIONAL
+ elements and attributes, unless other behavior is explicitly defined
+ by this specification.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
+ </p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>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 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 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="#SOAP12">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
- http://schemas.xmlsoap.org/soap/envelope/
- </a></td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">
- http://www.w3.org/2005/08/addressing
- </a></td><td> WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">
- http://www.w3.org/2001/XMLSchema
- </a></td><td>
- XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl">
- http://schemas.xmlsoap.org/wsdl
- </a></td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a></td></tr></tbody></table><p>
- The working group intends to update the value of the Web Services
- Enumeration namespace URI each time a new version of this document is
- published until such time that the document reaches Candidate
- Recommendation status. Once it has reached Candidate Recommendation
- status, the working group intends to maintain the value of the
- Web Services Enumeration namespace URI that was assigned in the
- Candidate Recommendation unless significant changes are made that
- impact the implementation or break post-CR implementations of the
- specification. Also see
- <a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
- http://www.w3.org/2001/tag/doc/namespaceState.html
- </a> and
- <a href="http://www.w3.org/2005/07/13-nsuri">
- http://www.w3.org/2005/07/13-nsuri
- </a>.
- </p></div></div><div class="div1">
+ 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 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 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="#SOAP12">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
+ http://schemas.xmlsoap.org/soap/envelope/
+ </a></td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">
+ http://www.w3.org/2005/08/addressing
+ </a></td><td> WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">
+ http://www.w3.org/2001/XMLSchema
+ </a></td><td>
+ XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl">
+ http://schemas.xmlsoap.org/wsdl
+ </a></td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a></td></tr></tbody></table><p>
+ The working group intends to update the value of the Web Services
+ Enumeration namespace URI each time a new version of this document is
+ published until such time that the document reaches Candidate
+ Recommendation status. Once it has reached Candidate Recommendation
+ status, the working group intends to maintain the value of the
+ Web Services Enumeration namespace URI that was assigned in the
+ Candidate Recommendation unless significant changes are made that
+ impact the implementation or break post-CR implementations of the
+ specification. Also see
+ <a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
+ http://www.w3.org/2001/tag/doc/namespaceState.html
+ </a> and
+ <a href="http://www.w3.org/2005/07/13-nsuri">
+ http://www.w3.org/2005/07/13-nsuri
+ </a>.
+ </p></div></div><div class="div1">
<h2><a name="EnumMsgs" id="EnumMsgs"/>4 Enumeration Messages</h2><p>
Enumeration contexts represent a specific
traversal through a sequence of XML information items. A Enumerate
@@ -1210,7 +1215,7 @@
a security analysis to determine their particular threat profile and
the appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x1900" id="iddiv2x1x1900"/>6.1 Creating Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1908" id="iddiv2x1x1908"/>6.1 Creating Enumeration Contexts</h3><p>
An enumeration represents a logical cursor through a sequence of
data items. If the information in these items is sensitive, it is
advisable to for Data Sources to authenticate and authorize Consumers
@@ -1221,7 +1226,7 @@
the time the Enumerate request is processed or varies during the
lifetime of the enumeration.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1905" id="iddiv2x1x1905"/>6.2 Protecting Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1913" id="iddiv2x1x1913"/>6.2 Protecting Enumeration Contexts</h3><p>
Once created, it is advisable to treat Enumeration Contexts as
protected resources. Renew, GetStatus, and Release requests ought to
be authenticated and authorized (for example, the identity of the
@@ -1243,7 +1248,7 @@
Data Sources are advised to authenticate and authorize clients
sending Enumerate requests.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1912" id="iddiv2x1x1912"/>6.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x1920" id="iddiv2x1x1920"/>6.3 Endpoint Verification</h3><p>
Data Source implementations that perform validity checks on the
EndTo EPR used in the Enumerate request are advised that such checks
can be misused to obtain information about a target network. For
@@ -1285,7 +1290,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="iddiv2x1x1932" id="iddiv2x1x1932"/>7.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2x1x1940" id="iddiv2x1x1940"/>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 -
@@ -1400,7 +1405,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2052" id="iddiv2x1x2052"/>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>
+<h3><a name="iddiv2x1x2060" id="iddiv2x1x2060"/>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -1446,17 +1461,7 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
@@ -1482,7 +1487,7 @@
, A. Berglund, et al., Editors.
World Wide Web Consortium (W3C), 23 January 2007.
Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x2256" id="iddiv2x1x2256"/>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>
+<h3><a name="iddiv2x1x2272" id="iddiv2x1x2272"/>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>
Index: wssa.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- wssa.html 19 Nov 2010 22:43:20 -0000 1.11
+++ wssa.html 28 Nov 2010 15:54:18 -0000 1.12
@@ -54,7 +54,7 @@
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="#iddiv2x1x461">Normative References</a><br/>
+ 7.1 <a href="#iddiv2x1x469">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/>
@@ -152,6 +152,11 @@
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.4 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
@@ -255,7 +260,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>7 References</h2><div class="div2">
-<h3><a name="iddiv2x1x461" id="iddiv2x1x461"/>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>
+<h3><a name="iddiv2x1x469" id="iddiv2x1x469"/>7.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -291,17 +306,7 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -d -r1.141 -r1.142
--- wsmex.html 19 Nov 2010 22:43:20 -0000 1.141
+++ wsmex.html 28 Nov 2010 15:54:18 -0000 1.142
@@ -64,7 +64,7 @@
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="#iddiv2x1x1471">Examples</a><br/>
+ 7.3 <a href="#iddiv2x1x1479">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/>
@@ -73,13 +73,13 @@
10.1 <a href="#UnsupportedMetadata">UnsupportedMetadata</a><br/>
10.2 <a href="#InvalidMetadata">UnknownDialect</a><br/>
11 <a href="#Security">Security Considerations</a><br/>
- 11.1 <a href="#iddiv2x1x2021">Metadata and Security Bootstrapping</a><br/>
+ 11.1 <a href="#iddiv2x1x2029">Metadata and Security Bootstrapping</a><br/>
12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 12.1 <a href="#iddiv2x1x2042">MetadataExchange Assertion</a><br/>
+ 12.1 <a href="#iddiv2x1x2050">MetadataExchange Assertion</a><br/>
13 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
14 <a href="#acks">Acknowledgements</a><br/>
15 <a href="#References">References</a><br/>
- 15.1 <a href="#iddiv2x1x2298">Normative References</a><br/>
+ 15.1 <a href="#iddiv2x1x2306">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="#Appendix-B">WSDL</a><br/>
@@ -497,6 +497,11 @@
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
@@ -1046,7 +1051,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="iddiv2x1x1471" id="iddiv2x1x1471"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1479" id="iddiv2x1x1479"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -1077,7 +1082,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1503" id="idexamplex1x1503"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexamplex1x1511" id="idexamplex1x1511"/>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="...">
@@ -1489,7 +1494,7 @@
WS-Eventing WSDL. As discussed above, this WSDL might be annotated to
specify additional constrains on the WS-Eventing message exchanges.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1764" id="idexamplex1x1764"/>Example 9-2: Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) <wsp:Policy>
+<div class="exampleHeader"><a name="idexamplex1x1772" id="idexamplex1x1772"/>Example 9-2: Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) <wsp:Policy>
(02) <wse:EventSource>
(03) <wse:FormatName
(04) URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Unwrap">
@@ -1519,7 +1524,7 @@
specific endpoint to which those protocol messages are to be sent - if
it is different from the address specified on line 02.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1774" id="idexamplex1x1774"/>Example 9-3: Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) <wse:NotifyTo>
+<div class="exampleHeader"><a name="idexamplex1x1782" id="idexamplex1x1782"/>Example 9-3: Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) <wse:NotifyTo>
(02) <wsa:Address> http://example.com </wsa:Address>
(03) <wsa:Metadata>
(04) <wsp:Policy>
@@ -1620,7 +1625,7 @@
security analysis to determine their particular threat profile and the
appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x2021" id="iddiv2x1x2021"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2029" id="iddiv2x1x2029"/>11.1 Metadata and Security Bootstrapping</h3><p>
There are cases in which the metadata used to describe a service might
be considered sensitive information. In these cases it is advisable
for services to authenticate and authorize consumers as part of the
@@ -1658,7 +1663,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2x1x2042" id="iddiv2x1x2042"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2050" id="iddiv2x1x2050"/>12.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 -
@@ -1878,7 +1883,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>15 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2298" id="iddiv2x1x2298"/>15.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="iddiv2x1x2306" id="iddiv2x1x2306"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -1934,17 +1949,7 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.207
retrieving revision 1.208
diff -u -d -r1.207 -r1.208
--- wseventing.xml 19 Nov 2010 22:43:19 -0000 1.207
+++ wseventing.xml 28 Nov 2010 15:54:18 -0000 1.208
@@ -685,6 +685,13 @@
described in XML 1.0.
</p>
+ <p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <bibref ref="BP12"/> and WS-I Basic Profile 2.0
+ <bibref ref="BP20"/>.
+ </p>
+
</div2>
<div2 id="namespaces">
@@ -3009,6 +3016,24 @@
<head>Normative References</head>
<blist>
+ <bibl key="BP12" id="BP12"
+ href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 1.2
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
+ <bibl key="BP20" id="BP20"
+ href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">
+ <titleref>
+ WS-I Profile, Basic Profile Version 2.0
+ </titleref>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ </bibl>
+
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
@@ -3098,20 +3123,6 @@
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- <bibl_note>
- <phrase>
- <phrase/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<loc href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </loc>) and WS-I Basic Profile 2.0
- (<loc href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </loc>).
- </phrase>
- </bibl_note>
</bibl>
</blist>
Index: xmlspec.xsl
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/xmlspec.xsl,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- xmlspec.xsl 19 Nov 2010 21:38:39 -0000 1.17
+++ xmlspec.xsl 28 Nov 2010 15:54:19 -0000 1.18
@@ -142,6 +142,7 @@
<xsl:key name="ids" match="*[@id]" use="@id"/>
<xsl:key name="specrefs" match="specref" use="@ref"/>
<xsl:key name="bibrefs" match="bibref" use="@ref"/>
+ <xsl:key name="bibls" match="bibl" use="@id"/>
<xsl:output method="xml" omit-xml-declaration="no" encoding="UTF-8" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" indent="no" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>
@@ -346,6 +347,13 @@
<!-- if the bibl has a key, put it in square brackets; otherwise use
the bibl's ID -->
<xsl:template match="bibref">
+ <xsl:if test="not(key('bibls', @ref))">
+ <xsl:message>
+ <xsl:text> Missing bibref </xsl:text>
+ <xsl:value-of select='@ref'/>
+ </xsl:message>
+ </xsl:if>
+
<a xmlns="http://www.w3.org/1999/xhtml">
<xsl:attribute name="href">
<xsl:call-template name="href.target">
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -d -r1.133 -r1.134
--- wst.html 19 Nov 2010 22:43:20 -0000 1.133
+++ wst.html 28 Nov 2010 15:54:19 -0000 1.134
@@ -60,15 +60,15 @@
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/>
- 7.1 <a href="#iddiv2x1x1311">Protecting Resources</a><br/>
- 7.2 <a href="#iddiv2x1x1316">Protecting Resource Factories</a><br/>
+ 7.1 <a href="#iddiv2x1x1319">Protecting Resources</a><br/>
+ 7.2 <a href="#iddiv2x1x1324">Protecting Resource Factories</a><br/>
8 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 8.1 <a href="#iddiv2x1x1334">TransferResource Assertion</a><br/>
- 8.2 <a href="#iddiv2x1x1416">TransferResourceFactory Assertion</a><br/>
+ 8.1 <a href="#iddiv2x1x1342">TransferResource Assertion</a><br/>
+ 8.2 <a href="#iddiv2x1x1424">TransferResourceFactory Assertion</a><br/>
9 <a href="#acks">Acknowledgements</a><br/>
10 <a href="#refs">References</a><br/>
- 10.1 <a href="#iddiv2x1x1490">Normative References</a><br/>
- 10.2 <a href="#iddiv2x1x1668">Informative References</a><br/>
+ 10.1 <a href="#iddiv2x1x1498">Normative References</a><br/>
+ 10.2 <a href="#iddiv2x1x1684">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/>
@@ -276,6 +276,11 @@
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
+ </p><p>
+ Implementations of this specification MUST conform to the corrected
+ version of WSDL as defined by the 'WSDL Correction' sections of WS-I
+ Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
+ <a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML Namespace URI that MUST be used by implementations of this
@@ -970,7 +975,7 @@
to perform a security analysis to determine their particular threat
profile and the appropriate responses to those threats.
</p><div class="div2">
-<h3><a name="iddiv2x1x1311" id="iddiv2x1x1311"/>7.1 Protecting Resources</h3><p>
+<h3><a name="iddiv2x1x1319" id="iddiv2x1x1319"/>7.1 Protecting Resources</h3><p>
Both resources and the information that makes up their representation
might be sensitive. In these cases, it is advisable for resource
managers to authenticate and authorize clients attempting Get, Put,
@@ -979,7 +984,7 @@
ought to have the appropriate authenticity, integrity, and
confidentiality measures applied.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1316" id="iddiv2x1x1316"/>7.2 Protecting Resource Factories</h3><p>
+<h3><a name="iddiv2x1x1324" id="iddiv2x1x1324"/>7.2 Protecting Resource Factories</h3><p>
In cases where resources and/or the information that makes up their
representation are sensitive so, too, are the services that create
these resources. In such cases it is advisable for resource factories
@@ -1012,7 +1017,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="iddiv2x1x1334" id="iddiv2x1x1334"/>8.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2x1x1342" id="iddiv2x1x1342"/>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
@@ -1078,7 +1083,7 @@
WS-Transfer message exchanges. Any metadata that appears is scoped
to the operations and features of the WS-Transfer specification.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x1416" id="iddiv2x1x1416"/>8.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2x1x1424" id="iddiv2x1x1424"/>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
@@ -1156,7 +1161,17 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>10 References</h2><div class="div2">
-<h3><a name="iddiv2x1x1490" id="iddiv2x1x1490"/>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>
+<h3><a name="iddiv2x1x1498" id="iddiv2x1x1498"/>10.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 1.2
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"/>BP20</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
+ WS-I Profile, Basic Profile Version 2.0
+ </cite></a>
+ , R. Chumbley, et al, Editors.
+ Web Services Interoperability Organization (WS-I), 9 November 2010.
+ Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -1203,17 +1218,7 @@
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
- Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.<span/><br/>
- Note: implementations of this specification
- MUST conform to the corrected version of WSDL as defined
- by the 'WSDL Correction' sections of WS-I Basic Profile 1.2
- (<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html#wsdlcorrections
- </a>) and WS-I Basic Profile 2.0
- (<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections">
- http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html#wsdlcorrections
- </a>).
- </dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
+ Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
@@ -1229,7 +1234,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="iddiv2x1x1668" id="iddiv2x1x1668"/>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>
+<h3><a name="iddiv2x1x1684" id="iddiv2x1x1684"/>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 Sunday, 28 November 2010 15:54:27 UTC