- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Apr 2007 13:58:46 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv22692
Modified Files:
wsdl20.html wsdl20-primer.html wsdl20-adjuncts.html
Log Message:
New HTML versions
Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.178
retrieving revision 1.179
diff -C 2 -d -r1.178 -r1.179
*** wsdl20-adjuncts.html 19 Apr 2007 14:32:26 -0000 1.178
--- wsdl20-adjuncts.html 26 Apr 2007 13:58:42 -0000 1.179
***************
*** 79,83 ****
Language (WSDL) Version 2.0 Part 2: Adjuncts</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/03/19 11:23:46 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
--- 79,83 ----
Language (WSDL) Version 2.0 Part 2: Adjuncts</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/04/26 13:30:55 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
***************
*** 491,497 ****
(Non-Normative)<br />
D. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br />
! D.1 <a href="#id2331169">WSDL 2.0
Extensions Change Log</a><br />
! D.2 <a href="#id2332204">WSDL 2.0 Bindings
Change Log</a><br /></p>
</div>
--- 491,497 ----
(Non-Normative)<br />
D. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br />
! D.1 <a href="#id2331280">WSDL 2.0
Extensions Change Log</a><br />
! D.2 <a href="#id2332315">WSDL 2.0 Bindings
Change Log</a><br /></p>
</div>
***************
*** 1138,1142 ****
<p>An <a href="wsdl20.html#component-InterfaceOperation">Interface
Operation</a> component conforming to the RPC style MUST obey the
! constraints listed further below. Furthermore, if the
<code>wrpc:signature</code> extension is engaged simulatenously,
the corresponding <em>attribute information item</em> MUST be valid
--- 1138,1142 ----
<p>An <a href="wsdl20.html#component-InterfaceOperation">Interface
Operation</a> component conforming to the RPC style MUST obey the
! constraints listed further below. Also, if the
<code>wrpc:signature</code> extension is engaged simulatenously,
the corresponding <em>attribute information item</em> MUST be valid
***************
*** 1147,1150 ****
--- 1147,1156 ----
"#InterfaceOperation_RPC_Signature_XMLRep"><b>4.1.2 XML
Representation of the wrpc:signature Extension</b></a>.</p>
+ <p>Furthermore, the associated messages MUST conform to the rules
+ below, described using XML Schema [<cite><a href="#XMLSchemaP1">XML
+ Schema Structures</a></cite>]. Note that operations containing
+ messages described by other type systems may also indicate use of
+ the RPC style, as long as they are constructed in such a way as to
+ follow these rules.</p>
<p><span id="RPCStyle-2029" class="test-assertion">If the RPC style
is used by an <a href=
***************
*** 1157,1168 ****
"#RPCStyle-2029-summary" title=
"Link to assertion RPCStyle-2029 summary">†</a></sup></span></p>
- <p>The RPC style places restrictions for Remote Procedure
- Call-types of interactions. When this value is used, the associated
- messages MUST conform to the rules below, described using XML
- Schema [<cite><a href="#XMLSchemaP1">XML Schema
- Structures</a></cite>]. Note that operations containing messages
- described by other type systems may also indicate use of the RPC
- style, as long as they are constructed in such a way as to follow
- these rules.</p>
<p>If the <a href=
"wsdl20.html#component-InterfaceOperation">Interface Operation</a>
--- 1163,1166 ----
***************
*** 4057,4066 ****
"Link to assertion HTTPBindingOperation-2093 summary">†</a></sup></span>
If the {<a href="#property-BindingOperation.httplocation">http
! location</a>} property is set, the HTTP Request IRI is the value of
! the {<a href="wsdl20.html#property-Endpoint.address">address</a>}
! property of the <a href=
! "wsdl20.html#component-Endpoint">Endpoint</a> component. Input
! serializations may define additional processing rules to be applied
! to the value of {<a href=
"#property-BindingOperation.httplocation">http location</a>} before
applying the process of reference resolution, i.e. before combining
--- 4055,4064 ----
"Link to assertion HTTPBindingOperation-2093 summary">†</a></sup></span>
If the {<a href="#property-BindingOperation.httplocation">http
! location</a>} property is not set, the HTTP Request IRI is the
! value of the {<a href=
! "wsdl20.html#property-Endpoint.address">address</a>} property of
! the <a href="wsdl20.html#component-Endpoint">Endpoint</a>
! component. Input serializations may define additional processing
! rules to be applied to the value of {<a href=
"#property-BindingOperation.httplocation">http location</a>} before
applying the process of reference resolution, i.e. before combining
***************
*** 6217,6221 ****
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, June 1999.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC2234" id="RFC2234"></a>[IETF RFC
--- 6215,6219 ----
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, March 1997.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC2234" id="RFC2234"></a>[IETF RFC
***************
*** 6349,6357 ****
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/REC-xml-20040204/">Extensible Markup
! Language (XML) 1.0 (Third Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 4 February 2004. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
--- 6347,6355 ----
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup
! Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 16 August 2006. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2006/REC-xml-20060816/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
***************
*** 6459,6462 ****
--- 6457,6470 ----
Message Transmission Optimization Mechanism" document</a> is
available from http://www.w3.org/TR/soap12-mtom/.</dd>
+ <dt class="label"><a name="XPTR" id="XPTR"></a>[XPointer]</dt>
+ <dd><cite><a href=
+ "http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
+ Framework</a></cite>,Paul Grosso, Eve Maler, Jonathan Marsh, Norman
+ Walsh, Editors. World Wide Web Consortium, 25 March 2003. This
+ version of the XPointer Framework Proposed Recommendation is
+ http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
+ "http://www.w3.org/TR/xptr-framework/">latest version of XPointer
+ Framework</a> is available at
+ http://www.w3.org/TR/xptr-framework/.</dd>
</dl>
</div>
***************
*** 7369,7403 ****
</tr>
<tr>
- <td rowspan="1" colspan="1"><a name=
- "InOnlyComposition-2012-summary" href="#InOnlyComposition-2012" id=
- "InOnlyComposition-2012-summary">InOnlyComposition-2012</a></td>
- <td rowspan="1" colspan="1">The <code>in-only</code> message
- exchange pattern consists of exactly one message as follows:</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1"><a name="InOutComposition-2015-summary"
- href="#InOutComposition-2015" id=
- "InOutComposition-2015-summary">InOutComposition-2015</a></td>
- <td rowspan="1" colspan="1">The <code>in-out</code> message
- exchange pattern consists of exactly two messages, in order, as
- follows:</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1"><a name=
- "InterfaceOperation-2096-summary" href="#InterfaceOperation-2096"
- id=
- "InterfaceOperation-2096-summary">InterfaceOperation-2096</a></td>
- <td rowspan="1" colspan="1">202 when the MEP is
- "http://www.w3.org/ns/wsdl/in-only"</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1"><a name=
- "InterfaceOperation-2097-summary" href="#InterfaceOperation-2097"
- id=
- "InterfaceOperation-2097-summary">InterfaceOperation-2097</a></td>
- <td rowspan="1" colspan="1">204 when the MEP is
- "http://www.w3.org/ns/wsdl/robust-in-only"</td>
- </tr>
- <tr>
<td rowspan="1" colspan="1"><a name="IRIStyle-2051-summary" href=
"#IRIStyle-2051" id="IRIStyle-2051-summary">IRIStyle-2051</a></td>
--- 7377,7380 ----
***************
*** 7448,7451 ****
--- 7425,7459 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1"><a name=
+ "InOnlyComposition-2012-summary" href="#InOnlyComposition-2012" id=
+ "InOnlyComposition-2012-summary">InOnlyComposition-2012</a></td>
+ <td rowspan="1" colspan="1">The <code>in-only</code> message
+ exchange pattern consists of exactly one message as follows:</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><a name="InOutComposition-2015-summary"
+ href="#InOutComposition-2015" id=
+ "InOutComposition-2015-summary">InOutComposition-2015</a></td>
+ <td rowspan="1" colspan="1">The <code>in-out</code> message
+ exchange pattern consists of exactly two messages, in order, as
+ follows:</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><a name=
+ "InterfaceOperation-2096-summary" href="#InterfaceOperation-2096"
+ id=
+ "InterfaceOperation-2096-summary">InterfaceOperation-2096</a></td>
+ <td rowspan="1" colspan="1">202 when the MEP is
+ "http://www.w3.org/ns/wsdl/in-only"</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><a name=
+ "InterfaceOperation-2097-summary" href="#InterfaceOperation-2097"
+ id=
+ "InterfaceOperation-2097-summary">InterfaceOperation-2097</a></td>
+ <td rowspan="1" colspan="1">204 when the MEP is
+ "http://www.w3.org/ns/wsdl/robust-in-only"</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1"><a name="MultipartStyle-2057-summary"
href="#MultipartStyle-2057" id=
***************
*** 7516,7527 ****
</tr>
<tr>
- <td rowspan="1" colspan="1"><a name=
- "RobustInOnlyComposition-2013-summary" href=
- "#RobustInOnlyComposition-2013" id=
- "RobustInOnlyComposition-2013-summary">RobustInOnlyComposition-2013</a></td>
- <td rowspan="1" colspan="1">The <code>robust-in-only</code> message
- exchange pattern consists of exactly one message as follows:</td>
- </tr>
- <tr>
<td rowspan="1" colspan="1"><a name="RPCStyle-2029-summary" href=
"#RPCStyle-2029" id="RPCStyle-2029-summary">RPCStyle-2029</a></td>
--- 7524,7527 ----
***************
*** 7620,7623 ****
--- 7620,7631 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1"><a name=
+ "RobustInOnlyComposition-2013-summary" href=
+ "#RobustInOnlyComposition-2013" id=
+ "RobustInOnlyComposition-2013-summary">RobustInOnlyComposition-2013</a></td>
+ <td rowspan="1" colspan="1">The <code>robust-in-only</code> message
+ exchange pattern consists of exactly one message as follows:</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1"><a name="SOAPAction-2075-summary" href=
"#SOAPAction-2075" id=
***************
*** 7688,7691 ****
--- 7696,7723 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1"><a name=
+ "SOAPHTTPProperties-2064-summary" href="#SOAPHTTPProperties-2064"
+ id=
+ "SOAPHTTPProperties-2064-summary">SOAPHTTPProperties-2064</a></td>
+ <td rowspan="1" colspan="1">These properties MUST NOT be used
+ unless the underlying protocol is HTTP.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><a name=
+ "SOAPHTTPSelection-2082-summary" href="#SOAPHTTPSelection-2082" id=
+ "SOAPHTTPSelection-2082-summary">SOAPHTTPSelection-2082</a></td>
+ <td rowspan="1" colspan="1">This default binding rule is applicable
+ when the value of the {<a href=
+ "#property-Binding.soapunderlyingprotocol">soap underlying
+ protocol</a>} property of the <a href=
+ "wsdl20.html#component-Binding">Binding</a> component is
+ "http://www.w3.org/2003/05/soap/bindings/HTTP/". If the SOAP MEP
+ selected as specified above has the value
+ "http://www.w3.org/2003/05/soap/mep/request-response/" then the
+ HTTP method used is "POST". If the SOAP MEP selected has the value
+ "http://www.w3.org/2003/05/soap/mep/soap-response/" then the HTTP
+ method used is "GET".</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1"><a name="SOAPHeaderBlock-2077-summary"
href="#SOAPHeaderBlock-2077" id=
***************
*** 7720,7747 ****
</tr>
<tr>
- <td rowspan="1" colspan="1"><a name=
- "SOAPHTTPProperties-2064-summary" href="#SOAPHTTPProperties-2064"
- id=
- "SOAPHTTPProperties-2064-summary">SOAPHTTPProperties-2064</a></td>
- <td rowspan="1" colspan="1">These properties MUST NOT be used
- unless the underlying protocol is HTTP.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1"><a name=
- "SOAPHTTPSelection-2082-summary" href="#SOAPHTTPSelection-2082" id=
- "SOAPHTTPSelection-2082-summary">SOAPHTTPSelection-2082</a></td>
- <td rowspan="1" colspan="1">This default binding rule is applicable
- when the value of the {<a href=
- "#property-Binding.soapunderlyingprotocol">soap underlying
- protocol</a>} property of the <a href=
- "wsdl20.html#component-Binding">Binding</a> component is
- "http://www.w3.org/2003/05/soap/bindings/HTTP/". If the SOAP MEP
- selected as specified above has the value
- "http://www.w3.org/2003/05/soap/mep/request-response/" then the
- HTTP method used is "POST". If the SOAP MEP selected has the value
- "http://www.w3.org/2003/05/soap/mep/soap-response/" then the HTTP
- method used is "GET".</td>
- </tr>
- <tr>
<td rowspan="1" colspan="1"><a name="SOAPMEP-2074-summary" href=
"#SOAPMEP-2074" id="SOAPMEP-2074-summary">SOAPMEP-2074</a></td>
--- 7752,7755 ----
***************
*** 8019,8022 ****
--- 8027,8036 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1"><a name="NoFaults-2011-summary" href=
+ "#NoFaults-2011" id="NoFaults-2011-summary">NoFaults-2011</a></td>
+ <td rowspan="1" colspan="1">When the No Faults propagation rule is
+ in effect, faults MUST NOT be propagated.</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1"><a name="NodeIdentity-2001-summary"
href="#NodeIdentity-2001" id=
***************
*** 8026,8035 ****
</tr>
<tr>
- <td rowspan="1" colspan="1"><a name="NoFaults-2011-summary" href=
- "#NoFaults-2011" id="NoFaults-2011-summary">NoFaults-2011</a></td>
- <td rowspan="1" colspan="1">When the No Faults propagation rule is
- in effect, faults MUST NOT be propagated.</td>
- </tr>
- <tr>
<td rowspan="1" colspan="1"><a name=
"RobustInOnlyFaults-2014-summary" href="#RobustInOnlyFaults-2014"
--- 8040,8043 ----
***************
*** 8059,8062 ****
--- 8067,8081 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20070419</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">4468: Add missing NOT.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20070419</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">4435: Swap 2 paragraphs in the RPC
+ section.</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20070314</td>
<td rowspan="1" colspan="1">JJM</td>
***************
*** 9383,9387 ****
<br />
<div class="div2">
! <h3><a name="id2331169" id="id2331169"></a>D.1 WSDL 2.0 Extensions
Change Log</h3>
<a name="wsdl-changelog-table" id="wsdl-changelog-table"></a>
--- 9402,9406 ----
<br />
<div class="div2">
! <h3><a name="id2331280" id="id2331280"></a>D.1 WSDL 2.0 Extensions
Change Log</h3>
<a name="wsdl-changelog-table" id="wsdl-changelog-table"></a>
***************
*** 9610,9614 ****
<br /></div>
<div class="div2">
! <h3><a name="id2332204" id="id2332204"></a>D.2 WSDL 2.0 Bindings
Change Log</h3>
<a name="wsdl-spec3-changelog-table" id=
--- 9629,9633 ----
<br /></div>
<div class="div2">
! <h3><a name="id2332315" id="id2332315"></a>D.2 WSDL 2.0 Bindings
Change Log</h3>
<a name="wsdl-spec3-changelog-table" id=
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.319
retrieving revision 1.320
diff -C 2 -d -r1.319 -r1.320
*** wsdl20.html 19 Apr 2007 14:32:24 -0000 1.319
--- wsdl20.html 26 Apr 2007 13:58:41 -0000 1.320
***************
*** 79,83 ****
Language (WSDL) Version 2.0 Part 1: Core Language</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/04/12 16:30:46 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
--- 79,83 ----
Language (WSDL) Version 2.0 Part 1: Core Language</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/04/26 13:31:39 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
***************
*** 130,135 ****
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1. <a href="#intro">Introduction</a><br />
! 1.1 <a href="#intro_ws">Web
! Service</a><br />
1.2 <a href="#meaning">The Meaning of a
Service Description</a><br />
--- 130,135 ----
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1. <a href="#intro">Introduction</a><br />
! 1.1 <a href="#intro_ws">Service
! Description</a><br />
1.2 <a href="#meaning">The Meaning of a
Service Description</a><br />
***************
*** 577,581 ****
2616</a></cite>]).</p>
<div class="div2">
! <h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3>
<p>WSDL 2.0 describes a Web service in two fundamental stages: one
abstract and one concrete. Within each stage, the description uses
--- 577,582 ----
2616</a></cite>]).</p>
<div class="div2">
! <h3><a name="intro_ws" id="intro_ws"></a>1.1 Service
! Description</h3>
<p>WSDL 2.0 describes a Web service in two fundamental stages: one
abstract and one concrete. Within each stage, the description uses
***************
*** 773,777 ****
<dt class="label">Inlined Schema</dt>
<dd>
! <p>An XML schema that is defined in the <code>xs:types</code>
<em>element information item</em> of a WSDL 2.0 description. For
example, an XML Schema defined in an <code>xs:schema</code>
--- 774,778 ----
<dt class="label">Inlined Schema</dt>
<dd>
! <p>An XML schema that is defined in the <code>wsdl:types</code>
<em>element information item</em> of a WSDL 2.0 description. For
example, an XML Schema defined in an <code>xs:schema</code>
***************
*** 972,976 ****
<h4><a name="Description_details" id=
"Description_details"></a>2.1.1 The Description Component</h4>
! <p>At the abstract level, the <a href=
"#component-Description">Description</a> component is just a
container for two categories of components: WSDL 2.0 components and
--- 973,977 ----
<h4><a name="Description_details" id=
"Description_details"></a>2.1.1 The Description Component</h4>
! <p>At a high level, the <a href=
"#component-Description">Description</a> component is just a
container for two categories of components: WSDL 2.0 components and
***************
*** 1132,1140 ****
<code>description</code> <em>element information item</em>s. A WSDL
2.0 Infoset contains representations for a collection of WSDL 2.0
! components that share a common target namespace. A WSDL 2.0 Infoset
! that contains one or more <code>wsdl:import</code> <em>element
! information item</em>s <a href="#imports"><b>4.2 Importing
! Descriptions</b></a> corresponds to a collection with components
! drawn from multiple target namespaces.</p>
<p>The components directly defined or included within a <a href=
"#component-Description">Description</a> component are said to
--- 1133,1141 ----
<code>description</code> <em>element information item</em>s. A WSDL
2.0 Infoset contains representations for a collection of WSDL 2.0
! components that share a common target namespace and zero or more
! <code>wsdl:import</code> <em>element information item</em>s
! <a href="#imports"><b>4.2 Importing Descriptions</b></a> that
! correspond to a collection with components from multiple target
! namespaces.</p>
<p>The components directly defined or included within a <a href=
"#component-Description">Description</a> component are said to
***************
*** 3561,3565 ****
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
! define bindings for all the operations and faults of that <a href=
"#component-Interface">Interface</a> component.<sup><a href=
"#Binding-1045-summary" title=
--- 3562,3566 ----
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
! define bindings for all the operations of that <a href=
"#component-Interface">Interface</a> component.<sup><a href=
"#Binding-1045-summary" title=
***************
*** 5205,5211 ****
"#property-Endpoint.binding">binding</a>} property. <b>Note</b>
that the presence in this property of the characters "?" and "#"
! can conflict with those potentially added by the mapping to the
! SOAP-Response message exchange pattern, section 6.8.2,
! [<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</p>
</li>
<li>
--- 5206,5214 ----
"#property-Endpoint.binding">binding</a>} property. <b>Note</b>
that the presence in this property of the characters "?" and "#"
! can conflict with those potentially added by the query string
! serialization mechanism, as defined in <a href=
! "wsdl20-adjuncts.html/#_http_x-www-form-urlencoded">Serialization
! as "application/x-www-form-urlencoded"</a> ([<cite><a href=
! "#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>], section 6.8.2).</p>
</li>
<li>
***************
*** 5481,5487 ****
Components</h3>
<p>Two component instances of the same type are considered
! equivalent if, for each property of the first component, there is a
! corresponding property with an equivalent value on the second
! component, and vice versa.</p>
<p>Instances of properties of the same type are considered
equivalent if their values are equivalent.</p>
--- 5484,5490 ----
Components</h3>
<p>Two component instances of the same type are considered
! equivalent if, for each property value of the first component,
! there is a corresponding property with an equivalent value on the
! second component, and vice versa.</p>
<p>Instances of properties of the same type are considered
equivalent if their values are equivalent.</p>
***************
*** 6664,6673 ****
elements. <a href="#exttype">Example 6-1</a> shows the type
definition. The use of this type as a base type is optional.</p>
- <p>Extension elements are commonly used to specify some
- technology-specific binding. They allow innovation in the area of
- network and message protocols without having to revise the base
- WSDL 2.0 specification. WSDL 2.0 recommends that specifications
- defining such protocols also define any necessary WSDL 2.0
- extensions used to describe those protocols or formats.</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><a name="exttype"
--- 6667,6670 ----
***************
*** 6683,6686 ****
--- 6680,6689 ----
</pre></div>
</div>
+ <p>Extension elements are commonly used to specify some
+ technology-specific binding. They allow innovation in the area of
+ network and message protocols without having to revise the base
+ WSDL 2.0 specification. WSDL 2.0 recommends that specifications
+ defining such protocols also define any necessary WSDL 2.0
+ extensions used to describe those protocols or formats.</p>
<div class="div3">
<h4><a name="mandatoryext" id="mandatoryext"></a>6.1.1 Mandatory
***************
*** 7059,7068 ****
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, June 1999.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3023" id="RFC3023"></a>[IETF RFC
3023]</dt>
! <dd>IETF "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D.
! Kohn, July 1998.(See<cite><a href=
"http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a></cite>.)</dd>
<dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC
--- 7062,7072 ----
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, March 1997.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3023" id="RFC3023"></a>[IETF RFC
3023]</dt>
! <dd>IETF "XML Media Types", M. Murata, S. St. Laurent, D. Kohn,
! Authors. Internet Engineering Task Force, January 2001. Available
! at http://www.ietf.org/rfc/rfc3023.txt.(See<cite><a href=
"http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a></cite>.)</dd>
<dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC
***************
*** 7082,7090 ****
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/REC-xml-20040204/">Extensible Markup
! Language (XML) 1.0 (Third Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 4 February 2004. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
--- 7086,7094 ----
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup
! Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 16 August 2006. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2006/REC-xml-20060816/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
***************
*** 7093,7101 ****
Namespaces]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in
! XML</a></cite>, T. Bray, D. Hollander, and A. Layman, Editors.
! World Wide Web Consortium, 14 January 1999. This version of the
! Namespaces in XML Recommendation is
! http://www.w3.org/TR/1999/REC-xml-names-19990114. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
--- 7097,7105 ----
Namespaces]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2006/REC-xml-names-20060816">Namespaces in
! XML (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman,
! and R. Tobin, Editors. World Wide Web Consortium, 16 August 2006.
! This version of the XML Information Set Recommendation is
! http://www.w3.org/TR/2006/REC-xml-names-20060816. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
***************
*** 7115,7121 ****
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
! Part 1: Structures</a></cite>, H. Thompson, D. Beech, M. Maloney,
! and N. Mendelsohn, Editors. World Wide Web Consortium, 28 October
! 2004. This version of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
--- 7119,7126 ----
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
! Part 1: Structures Second Edition</a></cite>, H. Thompson, D.
! Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web
! Consortium, 28 October 2004. This version of the XML Schema Part 1
! Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
***************
*** 7125,7131 ****
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
! Part 2: Datatypes</a></cite>, P. Byron and A. Malhotra, Editors.
! World Wide Web Consortium, 28 October 2004. This version of the XML
! Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
--- 7130,7136 ----
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
! Part 2: Datatypes Second Edition</a></cite>, P. Byron and A.
! Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This
! version of the XML Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
***************
*** 7269,7273 ****
"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
Framework</a></cite>,Paul Grosso, Eve Maler, Jonathan Marsh, Norman
! Walsh, Editors. World Wide Web Consortium, 22 November 2002. This
version of the XPointer Framework Proposed Recommendation is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
--- 7274,7278 ----
"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
Framework</a></cite>,Paul Grosso, Eve Maler, Jonathan Marsh, Norman
! Walsh, Editors. World Wide Web Consortium, 25 March 2003. This
version of the XPointer Framework Proposed Recommendation is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
***************
*** 8318,8322 ****
http://example.org/TicketAgent.wsdl20#
xmlns(ns1=http://example.org/TicketAgent.xsd)
! wsdl.elementDeclaration(xsTicketAgent:reserveFlightResponse)
http://example.org/TicketAgent.wsdl20#
--- 8323,8327 ----
http://example.org/TicketAgent.wsdl20#
xmlns(ns1=http://example.org/TicketAgent.xsd)
! wsdl.elementDeclaration(ns1:reserveFlightResponse)
http://example.org/TicketAgent.wsdl20#
***************
*** 9193,9197 ****
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
! define bindings for all the operations and faults of that <a href=
"#component-Interface">Interface</a> component.</td>
</tr>
--- 9198,9202 ----
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
! define bindings for all the operations of that <a href=
"#component-Interface">Interface</a> component.</td>
</tr>
***************
*** 9841,9844 ****
--- 9846,9865 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20070425</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Fixed typo in Example C-2. Replaced
+ xsTicketAgent: with ns1:.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20070419</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">4431: Add value.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20070419</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">4430: Fix section reference.</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20070319</td>
<td rowspan="1" colspan="1">JJM</td>
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.185
retrieving revision 1.186
diff -C 2 -d -r1.185 -r1.186
*** wsdl20-primer.html 19 Apr 2007 14:32:28 -0000 1.185
--- wsdl20-primer.html 26 Apr 2007 13:58:42 -0000 1.186
***************
*** 79,83 ****
Language (WSDL) Version 2.0 Part 0: Primer</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/03/23 22:13:08 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
--- 79,83 ----
Language (WSDL) Version 2.0 Part 0: Primer</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editors' copy $Date:
! 2007/04/26 13:31:39 $ @@ @@@@ @@@@</h2>
<dl>
<dt>This version:</dt>
***************
*** 217,227 ****
<a href="#more-interfaces-op-attr">Operation Attributes</a><br />
2.4.4.2
! <a href="#id2292462">Operation Message References</a><br />
2.4.4.2.1
! <a href="#id2292503">The messageLabel Attribute</a><br />
2.4.4.2.2
! <a href="#id2292536">The element Attribute</a><br />
2.4.4.2.3
! <a href="#id2292647">Multiple infault or outfault
Elements</a><br />
2.4.4.3
--- 217,227 ----
<a href="#more-interfaces-op-attr">Operation Attributes</a><br />
2.4.4.2
! <a href="#id2294651">Operation Message References</a><br />
2.4.4.2.1
! <a href="#id2294692">The messageLabel Attribute</a><br />
2.4.4.2.2
! <a href="#id2294724">The element Attribute</a><br />
2.4.4.2.3
! <a href="#id2294836">Multiple infault or outfault
Elements</a><br />
2.4.4.3
***************
*** 246,250 ****
"#more-bindings-http">The HTTP Binding Extension</a><br />
2.5.6.1
! <a href="#id2293573">Explanation of Example</a><br />
2.5.7 <a href=
"#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br />
--- 246,250 ----
"#more-bindings-http">The HTTP Binding Extension</a><br />
2.5.6.1
! <a href="#id2295763">Explanation of Example</a><br />
2.5.7 <a href=
"#adv-get-vs-post">HTTP GET Versus POST: Which to Use?</a><br />
***************
*** 256,266 ****
"#adv-multiple-inline-schemas">Importing Schemas</a><br />
3.2.1 <a href=
! "#id2294274">Schemas in Imported Documents</a><br />
3.2.2 <a href=
! "#id2294552">Multiple Inline Schemas in One Document</a><br />
3.2.3 <a href=
"#adv-schema-location">The schemaLocation Attribute</a><br />
3.2.3.1
! <a href="#id2294823">Using the id Attribute to Identify Inline
Schemas</a><br />
4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility
--- 256,266 ----
"#adv-multiple-inline-schemas">Importing Schemas</a><br />
3.2.1 <a href=
! "#id2296464">Schemas in Imported Documents</a><br />
3.2.2 <a href=
! "#id2296742">Multiple Inline Schemas in One Document</a><br />
3.2.3 <a href=
"#adv-schema-location">The schemaLocation Attribute</a><br />
3.2.3.1
! <a href="#id2297013">Using the id Attribute to Identify Inline
Schemas</a><br />
4. <a href="#advanced-topic_iii">Advanced Topics II: Extensibility
***************
*** 296,321 ****
Service</a><br />
5.2.5.1
! <a href="#id2296293">Additional Optional Elements Added in
Content</a><br />
5.2.5.2
! <a href="#id2296346">Additional Optional Elements Added to a
Header</a><br />
5.2.5.3
! <a href="#id2296387">Additional Mandatory Elements in
Content</a><br />
5.2.5.4
! <a href="#id2296455">Additional Optional Operation Added to
Interface</a><br />
5.2.5.5
! <a href="#id2296477">Additional Mandatory Operation Added to
Interface</a><br />
5.2.5.6
! <a href="#id2296530">Indicating Incompatibility by Changing the
Endpoint URI</a><br />
5.2.5.7
! <a href="#id2296559">Indicating Incompatibility by Changing the
SOAP Action</a><br />
5.2.5.8
! <a href="#id2296608">Indicating Incompatibility by Changing the
Element Content</a><br />
5.3 <a href=
--- 296,321 ----
Service</a><br />
5.2.5.1
! <a href="#id2298484">Additional Optional Elements Added in
Content</a><br />
5.2.5.2
! <a href="#id2298536">Additional Optional Elements Added to a
Header</a><br />
5.2.5.3
! <a href="#id2298578">Additional Mandatory Elements in
Content</a><br />
5.2.5.4
! <a href="#id2298646">Additional Optional Operation Added to
Interface</a><br />
5.2.5.5
! <a href="#id2298667">Additional Mandatory Operation Added to
Interface</a><br />
5.2.5.6
! <a href="#id2298721">Indicating Incompatibility by Changing the
Endpoint URI</a><br />
5.2.5.7
! <a href="#id2298750">Indicating Incompatibility by Changing the
SOAP Action</a><br />
5.2.5.8
! <a href="#id2298798">Indicating Incompatibility by Changing the
Element Content</a><br />
5.3 <a href=
***************
*** 2192,2196 ****
</div>
<div class="div4">
! <h5><a name="id2292462" id="id2292462"></a>2.4.4.2 Operation
Message References</h5>
<p>An <code>operation</code> will also have <code>input</code>,
--- 2192,2196 ----
</div>
<div class="div4">
! <h5><a name="id2294651" id="id2294651"></a>2.4.4.2 Operation
Message References</h5>
<p>An <code>operation</code> will also have <code>input</code>,
***************
*** 2206,2210 ****
not previously explained.</p>
<div class="div5">
! <h6><a name="id2292503" id="id2292503"></a>2.4.4.2.1 The
messageLabel Attribute</h6>
<p>The <code>messageLabel</code> attribute of the
--- 2206,2210 ----
not previously explained.</p>
<div class="div5">
! <h6><a name="id2294692" id="id2294692"></a>2.4.4.2.1 The
messageLabel Attribute</h6>
<p>The <code>messageLabel</code> attribute of the
***************
*** 2216,2220 ****
</div>
<div class="div5">
! <h6><a name="id2292536" id="id2292536"></a>2.4.4.2.2 The element
Attribute</h6>
<p>The <code>element</code> attribute of the <code>input</code> and
--- 2216,2220 ----
</div>
<div class="div5">
! <h6><a name="id2294724" id="id2294724"></a>2.4.4.2.2 The element
Attribute</h6>
<p>The <code>element</code> attribute of the <code>input</code> and
***************
*** 2253,2257 ****
</div>
<div class="div5">
! <h6><a name="id2292647" id="id2292647"></a>2.4.4.2.3 Multiple
infault or outfault Elements</h6>
<p>When <code>infault</code> and/or <code>outfault</code> occur
--- 2253,2257 ----
</div>
<div class="div5">
! <h6><a name="id2294836" id="id2294836"></a>2.4.4.2.3 Multiple
infault or outfault Elements</h6>
<p>When <code>infault</code> and/or <code>outfault</code> occur
***************
*** 2717,2721 ****
</div>
<div class="div4">
! <h5><a name="id2293573" id="id2293573"></a>2.5.6.1 Explanation of
Example</h5>
<p>Most of this example is the same as previously explained in
--- 2717,2721 ----
</div>
<div class="div4">
! <h5><a name="id2295763" id="id2295763"></a>2.5.6.1 Explanation of
Example</h5>
<p>Most of this example is the same as previously explained in
***************
*** 3065,3069 ****
within the same document and from other documents.</p>
<div class="div3">
! <h4><a name="id2294274" id="id2294274"></a>3.2.1 Schemas in
Imported Documents</h4>
<p>In this example, we consider some GreatH Hotel Web services that
--- 3065,3069 ----
within the same document and from other documents.</p>
<div class="div3">
! <h4><a name="id2296464" id="id2296464"></a>3.2.1 Schemas in
Imported Documents</h4>
<p>In this example, we consider some GreatH Hotel Web services that
***************
*** 3224,3228 ****
</div>
<div class="div3">
! <h4><a name="id2294552" id="id2294552"></a>3.2.2 Multiple Inline
Schemas in One Document</h4>
<p>A WSDL 2.0 document may define multiple inline schemas in its
--- 3224,3228 ----
</div>
<div class="div3">
! <h4><a name="id2296742" id="id2296742"></a>3.2.2 Multiple Inline
Schemas in One Document</h4>
<p>A WSDL 2.0 document may define multiple inline schemas in its
***************
*** 3345,3349 ****
Framework</a></cite>]) can also be used.</p>
<div class="div4">
! <h5><a name="id2294823" id="id2294823"></a>3.2.3.1 Using the id
Attribute to Identify Inline Schemas</h5>
<p><a href="#schemaIds.wsdl">Example 3-6</a> shows the use of the
--- 3345,3349 ----
Framework</a></cite>]) can also be used.</p>
<div class="div4">
! <h5><a name="id2297013" id="id2297013"></a>3.2.3.1 Using the id
Attribute to Identify Inline Schemas</h5>
<p><a href="#schemaIds.wsdl">Example 3-6</a> shows the use of the
***************
*** 4101,4105 ****
Extending a Service</h4>
<div class="div4">
! <h5><a name="id2296293" id="id2296293"></a>5.2.5.1 Additional
Optional Elements Added in Content</h5>
<p>The following example demonstrates how content may be extended
--- 4101,4105 ----
Extending a Service</h4>
<div class="div4">
! <h5><a name="id2298484" id="id2298484"></a>5.2.5.1 Additional
Optional Elements Added in Content</h5>
<p>The following example demonstrates how content may be extended
***************
*** 4136,4140 ****
</div>
<div class="div4">
! <h5><a name="id2296346" id="id2296346"></a>5.2.5.2 Additional
Optional Elements Added to a Header</h5>
<p>Another option is to add the extension as a header block. This
--- 4136,4140 ----
</div>
<div class="div4">
! <h5><a name="id2298536" id="id2298536"></a>5.2.5.2 Additional
Optional Elements Added to a Header</h5>
<p>Another option is to add the extension as a header block. This
***************
*** 4177,4181 ****
</div>
<div class="div4">
! <h5><a name="id2296387" id="id2296387"></a>5.2.5.3 Additional
Mandatory Elements in Content</h5>
<p>This following example demonstrates an extension with additional
--- 4177,4181 ----
</div>
<div class="div4">
! <h5><a name="id2298578" id="id2298578"></a>5.2.5.3 Additional
Mandatory Elements in Content</h5>
<p>This following example demonstrates an extension with additional
***************
*** 4211,4215 ****
</div>
<div class="div4">
! <h5><a name="id2296455" id="id2296455"></a>5.2.5.4 Additional
Optional Operation Added to Interface</h5>
<p>Section <a href="#more-interfaces-inheritance"><b>2.4.2
--- 4211,4215 ----
</div>
<div class="div4">
! <h5><a name="id2298646" id="id2298646"></a>5.2.5.4 Additional
Optional Operation Added to Interface</h5>
<p>Section <a href="#more-interfaces-inheritance"><b>2.4.2
***************
*** 4222,4226 ****
</div>
<div class="div4">
! <h5><a name="id2296477" id="id2296477"></a>5.2.5.5 Additional
Mandatory Operation Added to Interface</h5>
<p>Often mandatory operations are added to an interface. The Hotel
--- 4222,4226 ----
</div>
<div class="div4">
! <h5><a name="id2298667" id="id2298667"></a>5.2.5.5 Additional
Mandatory Operation Added to Interface</h5>
<p>Often mandatory operations are added to an interface. The Hotel
***************
*** 4272,4276 ****
</div>
<div class="div4">
! <h5><a name="id2296530" id="id2296530"></a>5.2.5.6 Indicating
Incompatibility by Changing the Endpoint URI</h5>
<p>To indicate incompatibility, the URI of the Hotel Endpoint can
--- 4272,4276 ----
</div>
<div class="div4">
! <h5><a name="id2298721" id="id2298721"></a>5.2.5.6 Indicating
Incompatibility by Changing the Endpoint URI</h5>
<p>To indicate incompatibility, the URI of the Hotel Endpoint can
***************
*** 4279,4283 ****
</div>
<div class="div4">
! <h5><a name="id2296559" id="id2296559"></a>5.2.5.7 Indicating
Incompatibility by Changing the SOAP Action</h5>
<p>The SOAP Action can be set for the makeReservation request, and
--- 4279,4283 ----
</div>
<div class="div4">
! <h5><a name="id2298750" id="id2298750"></a>5.2.5.7 Indicating
Incompatibility by Changing the SOAP Action</h5>
<p>The SOAP Action can be set for the makeReservation request, and
***************
*** 4306,4310 ****
</div>
<div class="div4">
! <h5><a name="id2296608" id="id2296608"></a>5.2.5.8 Indicating
Incompatibility by Changing the Element Content</h5>
<p>The namespace or name of the makeReservation element can be
--- 4306,4310 ----
</div>
<div class="div4">
! <h5><a name="id2298798" id="id2298798"></a>5.2.5.8 Indicating
Incompatibility by Changing the Element Content</h5>
<p>The namespace or name of the makeReservation element can be
***************
*** 5218,5222 ****
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, June 1999.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC
--- 5218,5222 ----
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
! Bradner, Author. Internet Engineering Task Force, March 1997.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC
***************
*** 5236,5244 ****
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/REC-xml-20040204/">Extensible Markup
! Language (XML) 1.0 (Third Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 4 February 2004. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
--- 5236,5244 ----
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup
! Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
! Wide Web Consortium, 16 August 2006. This version of the XML 1.0
! Recommendation is http://www.w3.org/TR/2006/REC-xml-20060816/. The
<a href="http://www.w3.org/TR/REC-xml">latest version of
"Extensible Markup Language (XML) 1.0"</a> is available at
***************
*** 5258,5266 ****
Namespaces]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in
! XML</a></cite>, T. Bray, D. Hollander, and A. Layman, Editors.
! World Wide Web Consortium, 14 January 1999. This version of the XML
! Information Set Recommendation is
! http://www.w3.org/TR/1999/REC-xml-names-19990114. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
--- 5258,5266 ----
Namespaces]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2006/REC-xml-names-20060816">Namespaces in
! XML (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman,
! and R. Tobin, Editors. World Wide Web Consortium, 16 August 2006.
! This version of the XML Information Set Recommendation is
! http://www.w3.org/TR/2006/REC-xml-names-20060816. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
***************
*** 5269,5275 ****
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
! Part 1: Structures</a></cite>, H. Thompson, D. Beech, M. Maloney,
! and N. Mendelsohn, Editors. World Wide Web Consortium, 28 October
! 2004. This version of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
--- 5269,5276 ----
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
! Part 1: Structures Second Edition</a></cite>, H. Thompson, D.
! Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web
! Consortium, 28 October 2004. This version of the XML Schema Part 1
! Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
***************
*** 5279,5292 ****
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
! Part 2: Datatypes</a></cite>, P. Byron and A. Malhotra, Editors.
! World Wide Web Consortium, 28 October 2004. This version of the XML
! Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
Part 2</a> is available at http://www.w3.org/TR/xmlschema-2.</dd>
! <dt class="label"><a name="RFC3023" id="RFC3023"></a>[RFC
3023]</dt>
! <dd>IETF "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D.
! Kohn, July 1998.(See<cite><a href=
"http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a></cite>.)</dd>
<dt class="label"><a name="WSDL-PART1" id="WSDL-PART1"></a>[WSDL
--- 5280,5294 ----
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
! Part 2: Datatypes Second Edition</a></cite>, P. Byron and A.
! Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This
! version of the XML Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
Part 2</a> is available at http://www.w3.org/TR/xmlschema-2.</dd>
! <dt class="label"><a name="RFC3023" id="RFC3023"></a>[IETF RFC
3023]</dt>
! <dd>IETF "XML Media Types", M. Murata, S. St. Laurent, D. Kohn,
! Authors. Internet Engineering Task Force, January 2001. Available
! at http://www.ietf.org/rfc/rfc3023.txt.(See<cite><a href=
"http://www.ietf.org/rfc/rfc3023.txt">http://www.ietf.org/rfc/rfc3023.txt</a></cite>.)</dd>
<dt class="label"><a name="WSDL-PART1" id="WSDL-PART1"></a>[WSDL
***************
*** 5461,5465 ****
"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
Framework</a></cite>,Paul Grosso, Eve Maler, Jonathan Marsh, Norman
! Walsh, Editors. World Wide Web Consortium, 22 November 2002. This
version of the XPointer Framework Proposed Recommendation is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
--- 5463,5467 ----
"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
Framework</a></cite>,Paul Grosso, Eve Maler, Jonathan Marsh, Norman
! Walsh, Editors. World Wide Web Consortium, 25 March 2003. This
version of the XPointer Framework Proposed Recommendation is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
***************
*** 5493,5497 ****
"http://www.w3.org/XML/2005/xsd-versioning-use-cases/">XML Schema
Versioning Use Cases</a></cite> , Hoylen Sue. W3C XML Schema
! Working Group Draft, 15 April 2005. Available at
http://www.w3.org/XML/2005/xsd-versioning-use-cases/</dd>
<dt class="label"><a name="xsd-versioning-guide" id=
--- 5495,5499 ----
"http://www.w3.org/XML/2005/xsd-versioning-use-cases/">XML Schema
Versioning Use Cases</a></cite> , Hoylen Sue. W3C XML Schema
! Working Group Draft, 31 January 2006. Available at
http://www.w3.org/XML/2005/xsd-versioning-use-cases/</dd>
<dt class="label"><a name="xsd-versioning-guide" id=
Received on Thursday, 26 April 2007 13:59:03 UTC