- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 27 Feb 2006 00:01:03 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv31980/wsdl20
Modified Files:
wsdl20.html wsdl20-adjuncts.html wsdl20.xml
component-assertion-table.xml xmlspec.dtd wsdl20.tex
wsdl20-primer.html wsdl20-z-ie.html
document-assertion-table.xml wsdl20-z.html
Log Message:
Reviewed and added assertions to Part 1 sections 2. and 2.1.
Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.125
retrieving revision 1.126
diff -C2 -d -r1.125 -r1.126
*** wsdl20-adjuncts.html 25 Feb 2006 17:50:20 -0000 1.125
--- wsdl20-adjuncts.html 27 Feb 2006 00:00:59 -0000 1.126
***************
*** 87,96 ****
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#meps">Predefined Message Exchange Patterns</a><br>3. <a href="#ext">Predefined Extensions</a><br>4. <a href="#styles">Predefined Operation Styles</a><br>5. <a href="#soap-binding">WSDL SOAP Binding Extension</a><br>6. <a href="#http-binding">WSDL HTTP Binding Extension</a><br>7. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#component_summary">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br>D. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#meps">Predefined Message Exchange Patterns</a><br> 2.1 <a href="#mep-template">Template for Message Exchange Patterns</a><br> 2.1.1 <a href="#template-sample">Pattern Name</a><br> 2.2 <a href="#fault-rules">Fault Propagation Rules</a><br> 2.2.1 <a href="#fault-replacement">Fault Replaces Message</a><br> 2.2.2 <a href="#fault-trigger">Message Triggers Fault</a><br> 2.2.3 <a href="#no-fault">No Faults</a><br> 2.3 <a href="#patterns">Message Exchange Patterns</a><br> 2.3.1 <a href="#in-only">In-Only</a><br> &nsp; 2.3.2 <a href="#robust-in-only">Robust In-Only</a><br> 2.3.3 <a href="#in-out">In-Out</a><br> 2.3.4 <a href="#in-opt-out">In-Optional-Out</a><br> 2.3.5 <a href="#out-only">Out-Only</a><br> 2.3.6 <a href="#robust-out-only">Robust Out-Only</a><br> 2.3.7 <a href="#out-in">Out-In</a><br> 2.3.8 <a href="#out-opt-in">Out-Optional-In</a><br> 2.4 <a href="#mep-sec-sec">Security Considerations</a><br>3. <a href="#ext">Predefined Extensions</a><br> 3.1 <a href="#safety">Operation safety</a><br> 3.1.1 <a href="#safety-decl-relate">Relationship to WSDL Component Model</a><br> &nsp;3.1.2 <a href="#safety-decl-xml">XML Representation</a><br> 3.1.3 <a href="#safety-decl-mapping">Mapping from XML Representation to Component Properties</a><br>4. <a href="#styles">Predefined Operation Styles</a><br> 4.1 <a href="#RPCStyle">RPC Style</a><br> 4.1.1 <a href="#InterfaceOperation_RPC_Signature_Definition">wrpc:signature Extension</a><br> 4.1.2 <a href="#InterfaceOperation_RPC_Signature_XMLRep">XML Representation of the wrpc:signature Extension</a><br> 4.1.3 <a href="#InterfaceOperation_RPC_Signature_Mapping">wrpc:signature Extension Mapping To Properties of an
! Interface Operation component</a><br> 4.2 <a href="#_operation_iri_style">IRI Style</a><br> 4.3 <a href="#_operation_multipart_style">Multipart style</a><br>5. <a href="#soap-binding">WSDL SOAP Binding Extension</a><br> 5.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br> 5.2 <a href="#soap-binding-decl">Identifying the use of the SOAP Binding</a><br> 5.3 <a href="#soap-defaults">SOAP Binding Rules</a><br> 5.4 <a href="#soap-version">Specifying the SOAP Version</a><br> 5.4.1 <a href="#soap-version-description">Description</a><br> 5.4.2 <a href="#soap-version-relate">Relationship to WSDL Component Model</a><br> 5.4.3 <a href="#soap-version-decl-xml">XML Representation</a><br> &nsp; 5.4.4 <a href="#soap-version-decl-mapping">Mapping from XML Representation to Component properties</a><br> 5.5 <a href="#soap-protocol">Specifying the SOAP Underlying Protocol</a><br> 5.5.1 <a href="#soap-protocol-description">Description</a><br> 5.5.2 <a href="#soap-protocol-relate">Relationship to WSDL Component Model</a><br> 5.5.3 <a href="#soap-binding-decl-xml">XML Representation</a><br> 5.5.4 <a href="#soap-binding-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.6 <a href="#soap-fault-decl">Binding Faults</a><br> 5.6.1 <a href="#soap-fault-decl-description">Description</a><br> 5.6.2 <a href="#soap-fault-decl-relate">Relationship to WSDL Coponent Model</a><br> 5.6.3 <a href="#soap-fault-decl-xml">XML Representation</a><br> 5.6.4 <a href="#soap-fault-decl-mapping">Mapping XML Representation to Component Properties</a><br> 5.7 <a href="#soap-operation-decl">Binding Operations</a><br> 5.7.1 <a href="#soap-operation-decl-description">Description</a><br> 5.7.2 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br> 5.7.3 <a href="#soap-operation-decl-xml">XML Representation</a><br> 5.7.4 <a href="#soap-operation-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.8 <a href="#soap-module-decl">Declaring SOAP Modules</a><br> 5..1 <a href="#soap-module-decl-description">Description</a><br> 5.8.2 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br> 5.8.3 <a href="#soap-module-decl-property">SOAP Module component</a><br> 5.8.4 <a href="#soap-module-decl-xml">XML Representation</a><br> 5.8.5 <a href="#soap-module-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.8.6 <a href="#soap-module-decl-fragid">IRI Identification Of A SOAP Module component</a><br> 5.9 <a href="#soap-headers-decl">Declaring SOAP Header Blocks</a><br> 5.9.1 <a href="#soap-headers-decl-description">Description</a><br> 5.9.2 <a href="#soap-headers-decl-relate">Reltionship to WSDL Component Model</a><br> 5.9.3 <a href="#soap-header-decl-property">SOAP Header Block component</a><br> 5.9.4 <a href="#soap-headers-decl-xml">XML Representation</a><br> 5.9.5 <a href="#soap-headers-decl-mapping">Mapping XML Representation to Component Properties</a><br> 5.9.6 <a href="#soap-headers-decl-fragid">IRI Identification Of A SOAP Header Block component</a><br> 5.10 <a href="#soap12-binding">WSDL SOAP 1.2 Binding</a><br> 5.10.1 <a href="#soap12-binding-decl">Identifying a WSDL SOAP 1.2 Binding</a><br> 5.10.2 <a href="#soap12-binding-description">Description</a><br> 5.10.3 <a href="#soap12-defaults">SOAP 1.2 Binding Rules</a><br> &nsp; 5.10.4 <a href="#wsdl-mep-soap-mep">Binding WSDL 2.0 MEPs to SOAP 1.2 MEPs</a><br> 5.10.4.1 <a href="#soap-mep-r-r">Using SOAP Request-Response</a><br> 5.10.4.1.1 <a href="#N1177D">The Client</a><br> 5.10.4.1.2 <a href="#N117AB">The Service</a><br> 5.10.4.2 <a href="#N117CD">Using SOAP-Response</a><br> 5.10.4.2.1 <a href="#N117DB">The Client</a><br> 5.10.4.2.2 <a href="#N1180A">The Service</a><br> 5.11 <a href="#soap-conformance">Confrmance</a><br>6. <a href="#http-binding">WSDL HTTP Binding Extension</a><br> 6.1 <a href="#http-binding-id">Identifying the use of the HTTP Binding</a><br> 6.2 <a href="#http-syntax">HTTP Syntax Summary (Non-Normative)</a><br> 6.3 <a href="#_http_binding_default_rules">HTTP Binding Rules</a><br> 6.3.1 <a href="#_http_binding_default_rule_method">HTTP Method Selection</a><br> 6.3.2 <a href="#_http_binding_default_rule_psf">Payload Construction And Serialization Format</a><br> 6.3.2.1 <a href="#_http_ser_xml">Serialization rules for XML messages</a><br> 6.3.3 <a href="#_http_binding_default_rule_dsf">Default input and output serialization format</a><br> 6.3.4 <a href="#_http_default_rulehead">HTTP Header Construction</a><br> 6.4 <a href="#http-version-decl">Specifying the HTTP Version</a><br> 6.4.1 <a href="#http-version-description">Description</a><br> 6.4.2 <a href="#http-version-relate">Relationship to WSDL Component Model</a><br> 6.4.3 <a href="#http-version-decl-xml">XML Representation</a><br> 6.4.4 <a href="#http-version-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.5 <a href="#http-operation-decl">Binding Operations</a><br> 6.5.1 <a href="#http-operation-decl-dest">Description</a><br> 6.5.2 <a href="#http-operation-decl-relate">Relationship to WSDL Component Model</a><br> 6.5.3 <a ref="#_http_ser_val">Specification of serialization rules allowed</a><br> 6.5.4 <a href="#http-operation-decl-xml">XML Representation</a><br> 6.5.5 <a href="#http-operation-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.6 <a href="#http-headers-decl">Declaring HTTP Headers</a><br> 6.6.1 <a href="#http-headers-decl-description">Description</a><br> 6.6.2 <a href="#http-headers-decl-relate">Relationship to WSDL Component Model</a><br> 6.6.3 <a href="#http-header-decl-property">HTTP Header component</a><br> 6.6.4 <a href="#http-headers-decl-xml">XML Representation</a><br> 6.6.5 <a href="#http-headers-decl-mapping">Mapping from XML Reresentation to Component Properties</a><br> 6.6.6 <a href="#http-headers-decl-fragid">IRI Identification Of A HTTP Header component</a><br> 6.7 <a href="#http-fault-decl">Specifying HTTP Error Code for Faults</a><br> 6.7.1 <a href="#http-fault-decl-description">Description</a><br> 6.7.2 <a href="#http-fault-decl-relate">Relationship to WSDL Component Model</a><br> 6.7.3 <a href="#http-fault-decl-xml">XML Representation</a><br> 6.7.4 <a href="#http-fault-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.8 <a href="#_http_serialization">Serialization Format of Instance Data</a><br> 6.8.1 <a href="#_http_location_template">Serialization of the instance data i parts of the HTTP request IRI</a><br> 6.8.1.1 <a href="#_http_operation_location_cited_ser">Construction of the request IRI using the {http
location} property</a><br> 6.8.2 <a href="#_http_x-www-form-urlencoded">Serialization as application/x-www-form-urlencoded
</a><br> 6.8.2.1 <a href="#_http_operation_location_cited_get">Case of elements cited in the {http location} property</a><br> 6.8.2.2 <a href="#_http_operation_location_notcited_get">Serialization of content of the instance data not cited in the {http location} property</a><br> 6.8.2.2.1 <a href="#_http_operation_location_query_constr">Construction of the query string</a><br> 6.8.2.2.2 <a href="#_http_urlencoded_stop">Controlling the serialization of the query string in the request IRI</a><br> 6.8.2.2.3 <a href="#_http_operation_location_notcited_iri">Serialization in the requst IRI</a><br> 6.8.2.2.4 <a href="#_http_operation_location_notcited_body">Serialization in the message body</a><br> 6.8.3 <a href="#_http_operation_xml_encoding">Serialization as application/xml
</a><br> 6.8.4 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
</a><br> 6.9 <a href="#http-transfer-coding-decl">Specifying the Transfer Coding</a><br> 6.9.1 <a href="#http-transfer-description">Description</a><br> 6.9.2 <a href="#http-transfer-coding-relate">Relationship to WSDL Component Model</a><br> 6.9.3 <a href="#http-transfer-coding-decl-xml">XML Representation</a><br> 6.9.4 <a href="#http-transfer-coding-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.10 <a href="#http-cookies-decl">Specifying the Use of HTTP Cookies</a><br> 6.10.1 <a href="#http-cookies-description">Description</a><br> 6.10.2 <a href="#http-cookies-relate">Relationship to WSDL Component Model</a><br>   6.10.3 <a href="#http-cookies-decl-xml">XML Representation</a><br> 6.10.4 <a href="#http-cookies-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.11 <a href="#http-auth-decl">Specifying HTTP Access Authentication</a><br> 6.11.1 <a href="#http-auth-description">Description</a><br> 6.11.2 <a href="#http-auth-relate">Relationship to WSDL Component Model</a><br> 6.11.3 <a href="#http-auth-decl-xml">XML Representation</a><br> 6.11.4 <a href="#http-auth-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.12 <a href="#http-conformance">Conformance</a><br>7. <a href="#References">References</a><br> 7.1 <a href="#Normative-References">Normatie References</a><br> 7.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#component_summary">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br> C.1 <a href="#N13C7F">WSDL 2.0 Extensions Change Log</a><br> C.2 <a href="#N13F09">WSDL 2.0 Bindings Change Log</a><br>D. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
--- 87,96 ----
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#meps">Predefined Message Exchange Patterns</a><br>3. <a href="#ext">Predefined Extensions</a><br>4. <a href="#styles">Predefined Operation Styles</a><br>5. <a href="#soap-binding">WSDL SOAP Binding Extension</a><br>6. <a href="#http-binding">WSDL HTTP Binding Extension</a><br>7. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#component_summary">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br>D. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#meps">Predefined Message Exchange Patterns</a><br> 2.1 <a href="#mep-template">Template for Message Exchange Patterns</a><br> 2.1.1 <a href="#template-sample">Pattern Name</a><br> 2.2 <a href="#fault-rules">Fault Propagation Rules</a><br> 2.2.1 <a href="#fault-replacement">Fault Replaces Message</a><br> 2.2.2 <a href="#fault-trigger">Message Triggers Fault</a><br> 2.2.3 <a href="#no-fault">No Faults</a><br> 2.3 <a href="#patterns">Message Exchange Patterns</a><br> 2.3.1 <a href="#in-only">In-Only</a><br> &nsp; 2.3.2 <a href="#robust-in-only">Robust In-Only</a><br> 2.3.3 <a href="#in-out">In-Out</a><br> 2.3.4 <a href="#in-opt-out">In-Optional-Out</a><br> 2.3.5 <a href="#out-only">Out-Only</a><br> 2.3.6 <a href="#robust-out-only">Robust Out-Only</a><br> 2.3.7 <a href="#out-in">Out-In</a><br> 2.3.8 <a href="#out-opt-in">Out-Optional-In</a><br> 2.4 <a href="#mep-sec-sec">Security Considerations</a><br>3. <a href="#ext">Predefined Extensions</a><br> 3.1 <a href="#safety">Operation safety</a><br> 3.1.1 <a href="#safety-decl-relate">Relationship to WSDL Component Model</a><br> &nsp;3.1.2 <a href="#safety-decl-xml">XML Representation</a><br> 3.1.3 <a href="#safety-decl-mapping">Mapping from XML Representation to Component Properties</a><br>4. <a href="#styles">Predefined Operation Styles</a><br> 4.1 <a href="#RPCStyle">RPC Style</a><br> 4.1.1 <a href="#InterfaceOperation_RPC_Signature_Definition">wrpc:signature Extension</a><br> 4.1.2 <a href="#InterfaceOperation_RPC_Signature_XMLRep">XML Representation of the wrpc:signature Extension</a><br> 4.1.3 <a href="#InterfaceOperation_RPC_Signature_Mapping">wrpc:signature Extension Mapping To Properties of an
! Interface Operation component</a><br> 4.2 <a href="#_operation_iri_style">IRI Style</a><br> 4.3 <a href="#_operation_multipart_style">Multipart style</a><br>5. <a href="#soap-binding">WSDL SOAP Binding Extension</a><br> 5.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br> 5.2 <a href="#soap-binding-decl">Identifying the use of the SOAP Binding</a><br> 5.3 <a href="#soap-defaults">SOAP Binding Rules</a><br> 5.4 <a href="#soap-version">Specifying the SOAP Version</a><br> 5.4.1 <a href="#soap-version-description">Description</a><br> 5.4.2 <a href="#soap-version-relate">Relationship to WSDL Component Model</a><br> 5.4.3 <a href="#soap-version-decl-xml">XML Representation</a><br> &nsp; 5.4.4 <a href="#soap-version-decl-mapping">Mapping from XML Representation to Component properties</a><br> 5.5 <a href="#soap-protocol">Specifying the SOAP Underlying Protocol</a><br> 5.5.1 <a href="#soap-protocol-description">Description</a><br> 5.5.2 <a href="#soap-protocol-relate">Relationship to WSDL Component Model</a><br> 5.5.3 <a href="#soap-binding-decl-xml">XML Representation</a><br> 5.5.4 <a href="#soap-binding-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.6 <a href="#soap-fault-decl">Binding Faults</a><br> 5.6.1 <a href="#soap-fault-decl-description">Description</a><br> 5.6.2 <a href="#soap-fault-decl-relate">Relationship to WSDL Coponent Model</a><br> 5.6.3 <a href="#soap-fault-decl-xml">XML Representation</a><br> 5.6.4 <a href="#soap-fault-decl-mapping">Mapping XML Representation to Component Properties</a><br> 5.7 <a href="#soap-operation-decl">Binding Operations</a><br> 5.7.1 <a href="#soap-operation-decl-description">Description</a><br> 5.7.2 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br> 5.7.3 <a href="#soap-operation-decl-xml">XML Representation</a><br> 5.7.4 <a href="#soap-operation-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.8 <a href="#soap-module-decl">Declaring SOAP Modules</a><br> 5..1 <a href="#soap-module-decl-description">Description</a><br> 5.8.2 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br> 5.8.3 <a href="#soap-module-decl-property">SOAP Module component</a><br> 5.8.4 <a href="#soap-module-decl-xml">XML Representation</a><br> 5.8.5 <a href="#soap-module-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 5.8.6 <a href="#soap-module-decl-fragid">IRI Identification Of A SOAP Module component</a><br> 5.9 <a href="#soap-headers-decl">Declaring SOAP Header Blocks</a><br> 5.9.1 <a href="#soap-headers-decl-description">Description</a><br> 5.9.2 <a href="#soap-headers-decl-relate">Reltionship to WSDL Component Model</a><br> 5.9.3 <a href="#soap-header-decl-property">SOAP Header Block component</a><br> 5.9.4 <a href="#soap-headers-decl-xml">XML Representation</a><br> 5.9.5 <a href="#soap-headers-decl-mapping">Mapping XML Representation to Component Properties</a><br> 5.9.6 <a href="#soap-headers-decl-fragid">IRI Identification Of A SOAP Header Block component</a><br> 5.10 <a href="#soap12-binding">WSDL SOAP 1.2 Binding</a><br> 5.10.1 <a href="#soap12-binding-decl">Identifying a WSDL SOAP 1.2 Binding</a><br> 5.10.2 <a href="#soap12-binding-description">Description</a><br> 5.10.3 <a href="#soap12-defaults">SOAP 1.2 Binding Rules</a><br> &nsp; 5.10.4 <a href="#wsdl-mep-soap-mep">Binding WSDL 2.0 MEPs to SOAP 1.2 MEPs</a><br> 5.10.4.1 <a href="#soap-mep-r-r">Using SOAP Request-Response</a><br> 5.10.4.1.1 <a href="#N117B6">The Client</a><br> 5.10.4.1.2 <a href="#N117E4">The Service</a><br> 5.10.4.2 <a href="#N11806">Using SOAP-Response</a><br> 5.10.4.2.1 <a href="#N11814">The Client</a><br> 5.10.4.2.2 <a href="#N11843">The Service</a><br> 5.11 <a href="#soap-conformance">Confrmance</a><br>6. <a href="#http-binding">WSDL HTTP Binding Extension</a><br> 6.1 <a href="#http-binding-id">Identifying the use of the HTTP Binding</a><br> 6.2 <a href="#http-syntax">HTTP Syntax Summary (Non-Normative)</a><br> 6.3 <a href="#_http_binding_default_rules">HTTP Binding Rules</a><br> 6.3.1 <a href="#_http_binding_default_rule_method">HTTP Method Selection</a><br> 6.3.2 <a href="#_http_binding_default_rule_psf">Payload Construction And Serialization Format</a><br> 6.3.2.1 <a href="#_http_ser_xml">Serialization rules for XML messages</a><br> 6.3.3 <a href="#_http_binding_default_rule_dsf">Default input and output serialization format</a><br> 6.3.4 <a href="#_http_default_rulehead">HTTP Header Construction</a><br> 6.4 <a href="#http-version-decl">Specifying the HTTP Version</a><br> 6.4.1 <a href="#http-version-description">Description</a><br> 6.4.2 <a href="#http-version-relate">Relationship to WSDL Component Model</a><br> 6.4.3 <a href="#http-version-decl-xml">XML Representation</a><br> 6.4.4 <a href="#http-version-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.5 <a href="#http-operation-decl">Binding Operations</a><br> 6.5.1 <a href="#http-operation-decl-dest">Description</a><br> 6.5.2 <a href="#http-operation-decl-relate">Relationship to WSDL Component Model</a><br> 6.5.3 <a ref="#_http_ser_val">Specification of serialization rules allowed</a><br> 6.5.4 <a href="#http-operation-decl-xml">XML Representation</a><br> 6.5.5 <a href="#http-operation-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.6 <a href="#http-headers-decl">Declaring HTTP Headers</a><br> 6.6.1 <a href="#http-headers-decl-description">Description</a><br> 6.6.2 <a href="#http-headers-decl-relate">Relationship to WSDL Component Model</a><br> 6.6.3 <a href="#http-header-decl-property">HTTP Header component</a><br> 6.6.4 <a href="#http-headers-decl-xml">XML Representation</a><br> 6.6.5 <a href="#http-headers-decl-mapping">Mapping from XML Reresentation to Component Properties</a><br> 6.6.6 <a href="#http-headers-decl-fragid">IRI Identification Of A HTTP Header component</a><br> 6.7 <a href="#http-fault-decl">Specifying HTTP Error Code for Faults</a><br> 6.7.1 <a href="#http-fault-decl-description">Description</a><br> 6.7.2 <a href="#http-fault-decl-relate">Relationship to WSDL Component Model</a><br> 6.7.3 <a href="#http-fault-decl-xml">XML Representation</a><br> 6.7.4 <a href="#http-fault-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.8 <a href="#_http_serialization">Serialization Format of Instance Data</a><br> 6.8.1 <a href="#_http_location_template">Serialization of the instance data i parts of the HTTP request IRI</a><br> 6.8.1.1 <a href="#_http_operation_location_cited_ser">Construction of the request IRI using the {http
location} property</a><br> 6.8.2 <a href="#_http_x-www-form-urlencoded">Serialization as application/x-www-form-urlencoded
</a><br> 6.8.2.1 <a href="#_http_operation_location_cited_get">Case of elements cited in the {http location} property</a><br> 6.8.2.2 <a href="#_http_operation_location_notcited_get">Serialization of content of the instance data not cited in the {http location} property</a><br> 6.8.2.2.1 <a href="#_http_operation_location_query_constr">Construction of the query string</a><br> 6.8.2.2.2 <a href="#_http_urlencoded_stop">Controlling the serialization of the query string in the request IRI</a><br> 6.8.2.2.3 <a href="#_http_operation_location_notcited_iri">Serialization in the requst IRI</a><br> 6.8.2.2.4 <a href="#_http_operation_location_notcited_body">Serialization in the message body</a><br> 6.8.3 <a href="#_http_operation_xml_encoding">Serialization as application/xml
</a><br> 6.8.4 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
</a><br> 6.9 <a href="#http-transfer-coding-decl">Specifying the Transfer Coding</a><br> 6.9.1 <a href="#http-transfer-description">Description</a><br> 6.9.2 <a href="#http-transfer-coding-relate">Relationship to WSDL Component Model</a><br> 6.9.3 <a href="#http-transfer-coding-decl-xml">XML Representation</a><br> 6.9.4 <a href="#http-transfer-coding-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.10 <a href="#http-cookies-decl">Specifying the Use of HTTP Cookies</a><br> 6.10.1 <a href="#http-cookies-description">Description</a><br> 6.10.2 <a href="#http-cookies-relate">Relationship to WSDL Component Model</a><br>   6.10.3 <a href="#http-cookies-decl-xml">XML Representation</a><br> 6.10.4 <a href="#http-cookies-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.11 <a href="#http-auth-decl">Specifying HTTP Access Authentication</a><br> 6.11.1 <a href="#http-auth-description">Description</a><br> 6.11.2 <a href="#http-auth-relate">Relationship to WSDL Component Model</a><br> 6.11.3 <a href="#http-auth-decl-xml">XML Representation</a><br> 6.11.4 <a href="#http-auth-decl-mapping">Mapping from XML Representation to Component Properties</a><br> 6.12 <a href="#http-conformance">Conformance</a><br>7. <a href="#References">References</a><br> 7.1 <a href="#Normative-References">Normatie References</a><br> 7.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#component_summary">Component Summary</a> (Non-Normative)<br>C. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br> C.1 <a href="#N13CDE">WSDL 2.0 Extensions Change Log</a><br> C.2 <a href="#N13F68">WSDL 2.0 Bindings Change Log</a><br>D. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
***************
*** 2658,2662 ****
<div class="div5">
! <h6><a name="N1177D"></a>5.10.4.1.1 The Client</h6>
<p>As the client, the property
--- 2658,2662 ----
<div class="div5">
! <h6><a name="N117B6"></a>5.10.4.1.1 The Client</h6>
<p>As the client, the property
***************
*** 2678,2682 ****
<div class="div5">
! <h6><a name="N117AB"></a>5.10.4.1.2 The Service</h6>
<p>As the service, the property
--- 2678,2682 ----
<div class="div5">
! <h6><a name="N117E4"></a>5.10.4.1.2 The Service</h6>
<p>As the service, the property
***************
*** 2695,2699 ****
<div class="div4">
! <h5><a name="N117CD"></a>5.10.4.2 Using SOAP-Response</h5>
<p>When using the WSDL "http://www.w3.org/@@@@/@@/wsdl/in-out"
--- 2695,2699 ----
<div class="div4">
! <h5><a name="N11806"></a>5.10.4.2 Using SOAP-Response</h5>
<p>When using the WSDL "http://www.w3.org/@@@@/@@/wsdl/in-out"
***************
*** 2704,2708 ****
<div class="div5">
! <h6><a name="N117DB"></a>5.10.4.2.1 The Client</h6>
<p>As the client, the property
--- 2704,2708 ----
<div class="div5">
! <h6><a name="N11814"></a>5.10.4.2.1 The Client</h6>
<p>As the client, the property
***************
*** 2726,2730 ****
<div class="div5">
! <h6><a name="N1180A"></a>5.10.4.2.2 The Service</h6>
<p>As the service, the property
--- 2726,2730 ----
<div class="div5">
! <h6><a name="N11843"></a>5.10.4.2.2 The Service</h6>
<p>As the service, the property
***************
*** 6249,6253 ****
<div class="div2">
! <h3><a name="N13C7F"></a>C.1 WSDL 2.0 Extensions Change Log</h3>
<a name="wsdl-changelog-table"></a><br><table border="1">
--- 6249,6253 ----
<div class="div2">
! <h3><a name="N13CDE"></a>C.1 WSDL 2.0 Extensions Change Log</h3>
<a name="wsdl-changelog-table"></a><br><table border="1">
***************
*** 6497,6501 ****
<div class="div2">
! <h3><a name="N13F09"></a>C.2 WSDL 2.0 Bindings Change Log</h3>
<a name="wsdl-spec3-changelog-table"></a><br><table border="1">
<tbody>
--- 6497,6501 ----
<div class="div2">
! <h3><a name="N13F68"></a>C.2 WSDL 2.0 Bindings Change Log</h3>
<a name="wsdl-spec3-changelog-table"></a><br><table border="1">
<tbody>
Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -C2 -d -r1.71 -r1.72
*** wsdl20-z-ie.html 25 Feb 2006 17:50:19 -0000 1.71
--- wsdl20-z-ie.html 27 Feb 2006 00:00:59 -0000 1.72
***************
*** 80,84 ****
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
--- 80,84 ----
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
***************
*** 105,109 ****
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
--- 105,109 ----
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
***************
*** 1505,1512 ****
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes or imports. The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included or imported documents.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
--- 1505,1513 ----
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes and the namespaces that the initial document imports.
! The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included documents or imported namespaces.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
***************
*** 1545,1553 ****
</pre></div>
<p>
! WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s. A WSDL 2.0 Infoset contains
! representations for a collection of WSDL 2.0 components which
! share a common target namespace. A WSDL 2.0 Infoset which
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>
--- 1546,1555 ----
</pre></div>
<p>
! <a name="Description-1201000"></a><span class="test-assertion">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s.</span><sup><a title="Link to assertion Description-1201000 summary" href="#Description-1201000-summary">†</a></sup>
! 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>
***************
*** 1558,1572 ****
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.
! It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document which provides
! service description information for that namespace.</p>
! <p>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description. This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
--- 1560,1574 ----
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! <a name="Description-1201001"></a><span class="test-assertion">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</span><sup><a title="Link to assertion Description-1201001 summary" href="#Description-1201001-summary">†</a></sup>
! <a name="Description-1201002"></a><span class="test-assertion">It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.</span><sup><a title="Link to assertion Description-1201002 summary" href="#Description-1201002-summary">†</a></sup>
! <a name="Description-1201003"></a><span class="test-assertion">It MAY resolve to a WSDL 2.0 document that provides
! service description information for that namespace.</span><sup><a title="Link to assertion Description-1201003 summary" href="#Description-1201003-summary">†</a></sup></p>
! <p><a name="Description-1201004"></a><span class="test-assertion">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description.</span><sup><a title="Link to assertion Description-1201004 summary" href="#Description-1201004-summary">†</a></sup> This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
***************
*** 1583,1587 ****
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
--- 1585,1589 ----
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
***************
*** 1621,1626 ****
<li>
<p>
! Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:
</p>
<ol>
--- 1623,1628 ----
<li>
<p>
! <a name="Description-1201005"></a><span class="test-assertion">Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:</span><sup><a title="Link to assertion Description-1201005 summary" href="#Description-1201005-summary">†</a></sup>
</p>
<ol>
***************
*** 1784,1787 ****
--- 1786,1790 ----
[namespace name], [attributes] and [children]
properties of an <em>element information item</em>.
+ <a name="Types-1201006"></a><span class="test-assertion">Each XML Schema element declaration MUST have a unique QName.</span><sup><a title="Link to assertion Types-1201006 summary" href="#Types-1201006-summary">†</a></sup>
</td>
</tr>
***************
*** 1798,1802 ****
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">It is an error if there are multiple type definitions for each QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
--- 1801,1805 ----
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">Each XML Schema type definition MUST have a unique QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
***************
*** 12845,12849 ****
<div class="div1">
! <h2><a name="N1742F"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 12848,12852 ----
<div class="div1">
! <h2><a name="N174B4"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 13204,13207 ****
--- 13207,13216 ----
<tr>
+ <td rowspan="1" colspan="1">20060226</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Reviewed and added assertions to sections 2. and 2.1.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060224</td>
<td rowspan="1" colspan="1">RRC</td>
***************
*** 15460,15463 ****
--- 15469,15496 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201000" name="Description-1201000-summary">Description-1201000</a>
+ </td>
+ <td rowspan="1" colspan="1">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
+ Information Sets (Infosets), that is one or more
+ <code>description</code> <em>element information item</em>s.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201004" name="Description-1201004-summary">Description-1201004</a>
+ </td>
+ <td rowspan="1" colspan="1">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
+ (which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
+ SHOULD resolve to a master WSDL 2.0 document that includes all the
+ WSDL 2.0 documents needed for that service description.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201005" name="Description-1201005-summary">Description-1201005</a>
+ </td>
+ <td rowspan="1" colspan="1">Zero or more <em>element information item</em>s amongst its [children], in order as
+ follows:</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
</td>
***************
*** 16044,16048 ****
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</td>
--- 16077,16081 ----
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</td>
***************
*** 16050,16053 ****
--- 16083,16107 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201001" name="Description-1201001-summary">Description-1201001</a>
+ </td>
+ <td rowspan="1" colspan="1">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201002" name="Description-1201002-summary">Description-1201002</a>
+ </td>
+ <td rowspan="1" colspan="1">It SHOULD resolve to a human or machine
+ processable document that directly or indirectly defines the
+ intended semantics of those components.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201003" name="Description-1201003-summary">Description-1201003</a>
+ </td>
+ <td rowspan="1" colspan="1">It MAY resolve to a WSDL 2.0 document that provides
+ service description information for that namespace.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Endpoint-0064" name="Endpoint-0064-summary">Endpoint-0064</a>
</td>
***************
*** 16428,16432 ****
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">It is an error if there are multiple type definitions for each QName.</td>
</tr>
</tbody>
--- 16482,16492 ----
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">Each XML Schema type definition MUST have a unique QName.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Types-1201006" name="Types-1201006-summary">Types-1201006</a>
! </td>
! <td rowspan="1" colspan="1">Each XML Schema element declaration MUST have a unique QName.</td>
</tr>
</tbody>
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.105
retrieving revision 1.106
diff -C2 -d -r1.105 -r1.106
*** wsdl20.tex 25 Feb 2006 17:50:19 -0000 1.105
--- wsdl20.tex 27 Feb 2006 00:00:59 -0000 1.106
***************
*** 1922,1929 ****
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes or imports. The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included or imported documents.
However, any WSDL 2.0 document that contains component
--- 1922,1930 ----
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes and the namespaces that the initial document imports.
! The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included documents or imported namespaces.
However, any WSDL 2.0 document that contains component
***************
*** 1965,1971 ****
WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! \texttt{description} \textit{element information item}s. A WSDL 2.0 Infoset contains
! representations for a collection of WSDL 2.0 components which
! share a common target namespace. A WSDL 2.0 Infoset which
contains one or more \texttt{wsdl:import} \textit{element information item}s \hyperlink{imports}{\textbf{\ref*{imports} Importing Descriptions}} corresponds to a collection with components
drawn from multiple target namespaces.
--- 1966,1973 ----
WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! \texttt{description} \textit{element information item}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 \texttt{wsdl:import} \textit{element information item}s \hyperlink{imports}{\textbf{\ref*{imports} Importing Descriptions}} corresponds to a collection with components
drawn from multiple target namespaces.
***************
*** 1980,1984 ****
processable document that directly or indirectly defines the
intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document which provides
service description information for that namespace.
--- 1982,1986 ----
processable document that directly or indirectly defines the
intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document that provides
service description information for that namespace.
***************
*** 2001,2005 ****
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
--- 2003,2007 ----
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
***************
*** 2204,2207 ****
--- 2206,2210 ----
[namespace name], [attributes] and [children]
properties of an \textit{element information item}.
+ Each XML Schema element declaration MUST have a unique QName.
\\ \hline
***************
*** 2219,2223 ****
other type system which describes the [attributes]
and [children] properties of an \textit{element information item}.
! It is an error if there are multiple type definitions for each QName.
\\ \hline
--- 2222,2226 ----
other type system which describes the [attributes]
and [children] properties of an \textit{element information item}.
! Each XML Schema type definition MUST have a unique QName.
\\ \hline
***************
*** 15020,15023 ****
--- 15023,15032 ----
+ 20060226&
+ AGR&
+ Reviewed and added assertions to sections 2. and 2.1.
+ \\ \hline
+
+
20060224&
RRC&
***************
*** 17276,17279 ****
--- 17285,17312 ----
&
+ WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
+ Information Sets (Infosets), that is one or more
+ \texttt{description} \textit{element information item}s.
+ \\ \hline
+
+
+
+ &
+ If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
+ (which may be combined as needed via \hyperlink{includes}{\textbf{\ref*{includes} Including Descriptions}}), then the \texttt{targetNamespace} \textit{attribute information item}
+ SHOULD resolve to a master WSDL 2.0 document that includes all the
+ WSDL 2.0 documents needed for that service description.
+ \\ \hline
+
+
+
+ &
+ Zero or more \textit{element information item}s amongst its [children], in order as
+ follows:
+ \\ \hline
+
+
+
+ &
However, any WSDL 2.0 document that contains component
***************
*** 17860,17864 ****
&
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
--- 17893,17897 ----
&
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
***************
*** 17868,17871 ****
--- 17901,17925 ----
&
+ The value of the \texttt{targetNamespace} \textit{attribute information item} SHOULD be dereferenceable.
+ \\ \hline
+
+
+
+ &
+ It SHOULD resolve to a human or machine
+ processable document that directly or indirectly defines the
+ intended semantics of those components.
+ \\ \hline
+
+
+
+ &
+ It MAY resolve to a WSDL 2.0 document that provides
+ service description information for that namespace.
+ \\ \hline
+
+
+
+ &
This \textit{xs:anyURI} MUST
be an absolute IRI as defined by
***************
*** 18246,18250 ****
&
! It is an error if there are multiple type definitions for each QName.
\\ \hline
\end{longtable}
--- 18300,18310 ----
&
! Each XML Schema type definition MUST have a unique QName.
! \\ \hline
!
!
!
! &
! Each XML Schema element declaration MUST have a unique QName.
\\ \hline
\end{longtable}
Index: component-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/component-assertion-table.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** component-assertion-table.xml 25 Feb 2006 17:50:19 -0000 1.8
--- component-assertion-table.xml 27 Feb 2006 00:00:59 -0000 1.9
***************
*** 131,135 ****
</td>
<td>
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</td>
--- 131,135 ----
</td>
<td>
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</td>
***************
*** 137,140 ****
--- 137,161 ----
<tr>
<td>
+ <assert-summary ref="Description-1201001"/>
+ </td>
+ <td>The value of the <att>targetNamespace</att> <emph>attribute information item</emph> SHOULD be dereferenceable.</td>
+ </tr>
+ <tr>
+ <td>
+ <assert-summary ref="Description-1201002"/>
+ </td>
+ <td>It SHOULD resolve to a human or machine
+ processable document that directly or indirectly defines the
+ intended semantics of those components.</td>
+ </tr>
+ <tr>
+ <td>
+ <assert-summary ref="Description-1201003"/>
+ </td>
+ <td>It MAY resolve to a WSDL 2.0 document that provides
+ service description information for that namespace.</td>
+ </tr>
+ <tr>
+ <td>
<assert-summary ref="Endpoint-0064"/>
</td>
***************
*** 517,521 ****
<assert-summary ref="Types-0026"/>
</td>
! <td>It is an error if there are multiple type definitions for each QName.</td>
</tr>
</tbody>
--- 538,548 ----
<assert-summary ref="Types-0026"/>
</td>
! <td>Each XML Schema type definition MUST have a unique QName.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="Types-1201006"/>
! </td>
! <td>Each XML Schema element declaration MUST have a unique QName.</td>
</tr>
</tbody>
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.386
retrieving revision 1.387
diff -C2 -d -r1.386 -r1.387
*** wsdl20.xml 24 Feb 2006 23:32:43 -0000 1.386
--- wsdl20.xml 27 Feb 2006 00:00:59 -0000 1.387
***************
*** 1893,1900 ****
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes or imports. The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included or imported documents.
<assert class="document" id="Import-0001">
However, any WSDL 2.0 document that contains component
--- 1893,1901 ----
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes and the namespaces that the initial document imports.
! The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included documents or imported namespaces.
<assert class="document" id="Import-0001">
However, any WSDL 2.0 document that contains component
***************
*** 1932,1940 ****
</eg>
<p>
! WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <el>description</el> &EII;s. A WSDL 2.0 Infoset contains
! representations for a collection of WSDL 2.0 components which
! share a common target namespace. A WSDL 2.0 Infoset which
contains one or more <el>wsdl:import</el> &EII;s <specref
ref='imports' /> corresponds to a collection with components
--- 1933,1942 ----
</eg>
<p>
! <assert class="document" id="Description-1201000">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <el>description</el> &EII;s.</assert>
! 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 <el>wsdl:import</el> &EII;s <specref
ref='imports' /> corresponds to a collection with components
***************
*** 1946,1961 ****
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! The value of the <att>targetNamespace</att> &AII; SHOULD be dereferenceable.
! It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document which provides
! service description information for that namespace.</p>
! <p>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <specref
ref='includes'/>), then the <att>targetNamespace</att> &AII;
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description. This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
--- 1948,1963 ----
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! <assert class="component" id="Description-1201001" required="false">The value of the <att>targetNamespace</att> &AII; SHOULD be dereferenceable.</assert>
! <assert class="component" id="Description-1201002" required="false">It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.</assert>
! <assert class="component" id="Description-1201003" required="false">It MAY resolve to a WSDL 2.0 document that provides
! service description information for that namespace.</assert></p>
! <p><assert class="document" id="Description-1201004">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <specref
ref='includes'/>), then the <att>targetNamespace</att> &AII;
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description.</assert> This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
***************
*** 1972,1976 ****
<p>
<assert class="component" id="Description-0024">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</assert>
--- 1974,1978 ----
<p>
<assert class="component" id="Description-0024">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</assert>
***************
*** 2011,2016 ****
<item>
<p>
! Zero or more &EII;s amongst its [children], in order as
! follows:
</p>
<olist>
--- 2013,2018 ----
<item>
<p>
! <assert class="document" id="Description-1201005">Zero or more &EII;s amongst its [children], in order as
! follows:</assert>
</p>
<olist>
***************
*** 2181,2184 ****
--- 2183,2187 ----
[namespace name], [attributes] and [children]
properties of an &EII;.
+ <assert class="component" id="Types-1201006">Each XML Schema element declaration MUST have a unique QName.</assert>
</td>
</tr>
***************
*** 2196,2200 ****
other type system which describes the [attributes]
and [children] properties of an &EII;.
! <assert class="component" id="Types-0026">It is an error if there are multiple type definitions for each QName.</assert>
</td>
</tr>
--- 2199,2203 ----
other type system which describes the [attributes]
and [children] properties of an &EII;.
! <assert class="component" id="Types-0026">Each XML Schema type definition MUST have a unique QName.</assert>
</td>
</tr>
***************
*** 14300,14303 ****
--- 14303,14312 ----
<tr>
+ <td>20060226</td>
+ <td>AGR</td>
+ <td>Reviewed and added assertions to sections 2. and 2.1.</td>
+ </tr>
+
+ <tr>
<td>20060224</td>
<td>RRC</td>
Index: document-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/document-assertion-table.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** document-assertion-table.xml 25 Feb 2006 17:50:20 -0000 1.9
--- document-assertion-table.xml 27 Feb 2006 00:00:59 -0000 1.10
***************
*** 15,18 ****
--- 15,42 ----
<tr>
<td>
+ <assert-summary ref="Description-1201000"/>
+ </td>
+ <td>WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
+ Information Sets (Infosets), that is one or more
+ <el>description</el> <emph>element information item</emph>s.</td>
+ </tr>
+ <tr>
+ <td>
+ <assert-summary ref="Description-1201004"/>
+ </td>
+ <td>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
+ (which may be combined as needed via <specref ref="includes"/>), then the <att>targetNamespace</att> <emph>attribute information item</emph>
+ SHOULD resolve to a master WSDL 2.0 document that includes all the
+ WSDL 2.0 documents needed for that service description.</td>
+ </tr>
+ <tr>
+ <td>
+ <assert-summary ref="Description-1201005"/>
+ </td>
+ <td>Zero or more <emph>element information item</emph>s amongst its [children], in order as
+ follows:</td>
+ </tr>
+ <tr>
+ <td>
<assert-summary ref="Import-0001"/>
</td>
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.96
retrieving revision 1.97
diff -C2 -d -r1.96 -r1.97
*** wsdl20-z.html 25 Feb 2006 17:50:19 -0000 1.96
--- wsdl20-z.html 27 Feb 2006 00:00:59 -0000 1.97
***************
*** 80,84 ****
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
--- 80,84 ----
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
***************
*** 105,109 ****
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
--- 105,109 ----
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
***************
*** 1503,1510 ****
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes or imports. The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included or imported documents.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
--- 1503,1511 ----
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes and the namespaces that the initial document imports.
! The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included documents or imported namespaces.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
***************
*** 1543,1551 ****
</pre></div>
<p>
! WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s. A WSDL 2.0 Infoset contains
! representations for a collection of WSDL 2.0 components which
! share a common target namespace. A WSDL 2.0 Infoset which
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>
--- 1544,1553 ----
</pre></div>
<p>
! <a name="Description-1201000"></a><span class="test-assertion">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s.</span><sup><a title="Link to assertion Description-1201000 summary" href="#Description-1201000-summary">†</a></sup>
! 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>
***************
*** 1556,1570 ****
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.
! It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document which provides
! service description information for that namespace.</p>
! <p>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description. This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
--- 1558,1572 ----
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! <a name="Description-1201001"></a><span class="test-assertion">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</span><sup><a title="Link to assertion Description-1201001 summary" href="#Description-1201001-summary">†</a></sup>
! <a name="Description-1201002"></a><span class="test-assertion">It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.</span><sup><a title="Link to assertion Description-1201002 summary" href="#Description-1201002-summary">†</a></sup>
! <a name="Description-1201003"></a><span class="test-assertion">It MAY resolve to a WSDL 2.0 document that provides
! service description information for that namespace.</span><sup><a title="Link to assertion Description-1201003 summary" href="#Description-1201003-summary">†</a></sup></p>
! <p><a name="Description-1201004"></a><span class="test-assertion">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description.</span><sup><a title="Link to assertion Description-1201004 summary" href="#Description-1201004-summary">†</a></sup> This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
***************
*** 1581,1585 ****
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
--- 1583,1587 ----
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
***************
*** 1619,1624 ****
<li>
<p>
! Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:
</p>
<ol>
--- 1621,1626 ----
<li>
<p>
! <a name="Description-1201005"></a><span class="test-assertion">Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:</span><sup><a title="Link to assertion Description-1201005 summary" href="#Description-1201005-summary">†</a></sup>
</p>
<ol>
***************
*** 1782,1785 ****
--- 1784,1788 ----
[namespace name], [attributes] and [children]
properties of an <em>element information item</em>.
+ <a name="Types-1201006"></a><span class="test-assertion">Each XML Schema element declaration MUST have a unique QName.</span><sup><a title="Link to assertion Types-1201006 summary" href="#Types-1201006-summary">†</a></sup>
</td>
</tr>
***************
*** 1796,1800 ****
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">It is an error if there are multiple type definitions for each QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
--- 1799,1803 ----
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">Each XML Schema type definition MUST have a unique QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
***************
*** 12815,12819 ****
<div class="div1">
! <h2><a name="N1742F"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 12818,12822 ----
<div class="div1">
! <h2><a name="N174B4"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 13174,13177 ****
--- 13177,13186 ----
<tr>
+ <td rowspan="1" colspan="1">20060226</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Reviewed and added assertions to sections 2. and 2.1.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060224</td>
<td rowspan="1" colspan="1">RRC</td>
***************
*** 15430,15433 ****
--- 15439,15466 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201000" name="Description-1201000-summary">Description-1201000</a>
+ </td>
+ <td rowspan="1" colspan="1">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
+ Information Sets (Infosets), that is one or more
+ <code>description</code> <em>element information item</em>s.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201004" name="Description-1201004-summary">Description-1201004</a>
+ </td>
+ <td rowspan="1" colspan="1">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
+ (which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
+ SHOULD resolve to a master WSDL 2.0 document that includes all the
+ WSDL 2.0 documents needed for that service description.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201005" name="Description-1201005-summary">Description-1201005</a>
+ </td>
+ <td rowspan="1" colspan="1">Zero or more <em>element information item</em>s amongst its [children], in order as
+ follows:</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
</td>
***************
*** 16014,16018 ****
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</td>
--- 16047,16051 ----
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</td>
***************
*** 16020,16023 ****
--- 16053,16077 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201001" name="Description-1201001-summary">Description-1201001</a>
+ </td>
+ <td rowspan="1" colspan="1">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201002" name="Description-1201002-summary">Description-1201002</a>
+ </td>
+ <td rowspan="1" colspan="1">It SHOULD resolve to a human or machine
+ processable document that directly or indirectly defines the
+ intended semantics of those components.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201003" name="Description-1201003-summary">Description-1201003</a>
+ </td>
+ <td rowspan="1" colspan="1">It MAY resolve to a WSDL 2.0 document that provides
+ service description information for that namespace.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Endpoint-0064" name="Endpoint-0064-summary">Endpoint-0064</a>
</td>
***************
*** 16398,16402 ****
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">It is an error if there are multiple type definitions for each QName.</td>
</tr>
</tbody>
--- 16452,16462 ----
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">Each XML Schema type definition MUST have a unique QName.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Types-1201006" name="Types-1201006-summary">Types-1201006</a>
! </td>
! <td rowspan="1" colspan="1">Each XML Schema element declaration MUST have a unique QName.</td>
</tr>
</tbody>
Index: xmlspec.dtd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/xmlspec.dtd,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** xmlspec.dtd 18 Nov 2005 17:16:03 -0000 1.23
--- xmlspec.dtd 27 Feb 2006 00:00:59 -0000 1.24
***************
*** 2678,2681 ****
--- 2678,2685 ----
Change Log:
+ 2006-02-26 ryman
+ - added required attribute to assert element
+ - specified enumerated values for class attribute of assert element
+
2005-11-16 ryman
- added more Z elements
***************
*** 2705,2710 ****
<!ELEMENT assert (%p.pcd.mix.noassert;)*>
! <!ATTLIST assert class CDATA #REQUIRED>
<!ATTLIST assert id ID #REQUIRED>
<!ELEMENT assert-summary (%p.pcd.mix.noassert;)*>
--- 2709,2715 ----
<!ELEMENT assert (%p.pcd.mix.noassert;)*>
! <!ATTLIST assert class (component | document | exchange | message) #REQUIRED>
<!ATTLIST assert id ID #REQUIRED>
+ <!ATTLIST assert required (false | true) "true">
<!ELEMENT assert-summary (%p.pcd.mix.noassert;)*>
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.265
retrieving revision 1.266
diff -C2 -d -r1.265 -r1.266
*** wsdl20.html 25 Feb 2006 17:50:20 -0000 1.265
--- wsdl20.html 27 Feb 2006 00:00:58 -0000 1.266
***************
*** 80,84 ****
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
--- 80,84 ----
<hr><div class="toc">
! <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#component_model">Component Model</a><br>3. <a href="#eii-types">Types</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br>5. <a href="#eii-documentation">Documentation</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br>A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br>F. <a href="#assertionsummary">Assertion Summry</a> (Non-Normative)<br></p></div><hr><div class="toc">
<h2><a name="contents">Table of Contents</a></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="#markup">Document Conformance</a><br> 1.3 <a href="#meaning">The Meaning of a Service Description</a><br> 1.4 <a href="#notation">Notational Conventions</a><br> 1.4.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.4.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.4.3 <a href="#xmlSchemaAnyURI">XML Schema anyURI</a><br> 1.4.4 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.4.5 <a href="#terminology">Terms Used in This Specification</a><br> &nbp; 1.4.6 <a href="#xmlinfosetproperties">XML Information Set Properties</a><br> 1.4.7 <a href="#wsdlcomponentmodelproperties">WSDL 2.0 Component Model Properties</a><br> 1.4.8 <a href="#znotation">Z Notation</a><br> 1.4.9 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4.10 <a href="#assertions">Assertions</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attriute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner element]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nsp; 2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner element]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner element]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
***************
*** 105,109 ****
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N1742F">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
--- 105,109 ----
attribute information item
</a><br> 3.3.3 <a href="#wsdlx-consistency">wsdlx:interface and wsdlx:binding Consistency</a><br> 3.3.4 <a href="#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with xs:anyURI</a><br>4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a><br> 4.1 <a href="#includes">Including Descriptions</a><br> 4.1.1 <a href="#include_location_attribute">location attribute information item with include [owner element]</a><br> 4.2 <a href="#imports">Importing Descriptions</a><br> 4.2.1 <a href="#import_namespace_attribute">namespace attribute information item</a><br> 4.2.2 <a href="#import_location_attribute">location attribute information item with import [owner element]</a><br>5. <a href="#eii-documentation">Documentatin</a><br>6. <a href="#language-extensibility">Language Extensibility</a><br> 6.1 <a href="#eii-extensibility">Element based Extensibility</a><br> 6.1.1 <a href="#mandatoryext">Mandatory extensions</a><br> 6.1.2 <a href="#required-aii">required attribute information item</a><br> 6.2 <a href="#aii-extensibility">Attribute-based Extensibility</a><br> 6.3 <a href="#extensibility-semantics">Extensibility Semantics</a><br>7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a><br> 7.1 <a href="#wsdlLocation-aii">wsdli:wsdlLocation attribute information item</a><br>8. <a href="#conformance">Conformance</a><br> 8.1 <a href="#infoset">XML Information Set Conformance</a><br>9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a><br>10. <a href="#References">References</a><br> &nbs;10.1 <a href="#Normative-References">Normative References</a><br> 10.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml Media Type</a><br> A.1 <a href="#ietf-reg">Registration</a><br> A.2 <a href="#frag-ids">Fragment Identifiers</a><br> A.2.1 <a href="#wsdl.description">The Description Component</a><br> A.2.2 <a href="#wsdl.elementDeclaration">The Element Declaration Component</a><br> A.2.3 <a href="#wsdl.typeDefinition">The Type Definition Component</a><br> A.2.4 <a href="#wsdl.interface">The Interface Component</a><br> A.2.5 <a href="#wsdl.interfaceFault">The Interface Fault Component</a><br> A.2.6 <a href="#wsdl.interfaceOperation">The Interface Operation Component</a><br> &bsp; A.2.7 <a href="#wsdl.interfaceMessageReference">The Interface Message Reference Component</a><br> A.2.8 <a href="#wsdl.interfaceFaultReference">The Interface Fault Reference Component</a><br> A.2.9 <a href="#wsdl.binding">The Binding Component</a><br> A.2.10 <a href="#wsdl.bindingFault">The Binding Fault Component</a><br> A.2.11 <a href="#wsdl.bindingOperation">The Binding Operation Component</a><br> A.2.12 <a href="#wsdl.bindingMessageReference">The Binding Message Reference Component</a><br> A.2.13 <a href="#wsdl.bindingFaultReference">The Binding Fault Reference Component</a><br> A.2.14 <a href="#wsdl.service">The Service Component</a><br>&nbp; A.2.15 <a href="#wsdl.endpoint">The Endpoint Component</a><br> A.2.16 <a href="#wsdl.feature">The Feature Component</a><br> A.2.17 <a href="#wsdl.property">The Property Component</a><br> A.2.18 <a href="#wsdl.extension">Extension Components</a><br> A.3 <a href="#ietf-sec">Security considerations</a><br>B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0 Components</a> (Non-Normative)<br> C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a><br> C.2 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N174B4">Component Summary</a> (Non-Normative)<br>E. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> E.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changs</a><br>F. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br></p></div><hr><div class="body">
<div class="div1">
***************
*** 798,805 ****
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes or imports. The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included or imported documents.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
--- 798,806 ----
consists of the components defined in the initial document
and the components associated with the documents that the
! initial document includes and the namespaces that the initial document imports.
! The component model
makes no distinction between the components that are defined
in the initial document versus those that are defined in the
! included documents or imported namespaces.
<a name="Import-0001"></a><span class="test-assertion">
However, any WSDL 2.0 document that contains component
***************
*** 838,846 ****
</pre></div>
<p>
! WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s. A WSDL 2.0 Infoset contains
! representations for a collection of WSDL 2.0 components which
! share a common target namespace. A WSDL 2.0 Infoset which
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>
--- 839,848 ----
</pre></div>
<p>
! <a name="Description-1201000"></a><span class="test-assertion">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
Information Sets (Infosets), that is one or more
! <code>description</code> <em>element information item</em>s.</span><sup><a title="Link to assertion Description-1201000 summary" href="#Description-1201000-summary">†</a></sup>
! 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>
***************
*** 851,865 ****
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.
! It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.
! It MAY resolve to a WSDL 2.0 document which provides
! service description information for that namespace.</p>
! <p>If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description. This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
--- 853,867 ----
of related component definitions and represents an unambiguous
name for the intended semantics of the collection of components.
! <a name="Description-1201001"></a><span class="test-assertion">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</span><sup><a title="Link to assertion Description-1201001 summary" href="#Description-1201001-summary">†</a></sup>
! <a name="Description-1201002"></a><span class="test-assertion">It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
! intended semantics of those components.</span><sup><a title="Link to assertion Description-1201002 summary" href="#Description-1201002-summary">†</a></sup>
! <a name="Description-1201003"></a><span class="test-assertion">It MAY resolve to a WSDL 2.0 document that provides
! service description information for that namespace.</span><sup><a title="Link to assertion Description-1201003 summary" href="#Description-1201003-summary">†</a></sup></p>
! <p><a name="Description-1201004"></a><span class="test-assertion">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
(which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
SHOULD resolve to a master WSDL 2.0 document that includes all the
! WSDL 2.0 documents needed for that service description.</span><sup><a title="Link to assertion Description-1201004 summary" href="#Description-1201004-summary">†</a></sup> This
approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
***************
*** 876,880 ****
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
--- 878,882 ----
<p>
<a name="Description-0024"></a><span class="test-assertion">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</span><sup><a title="Link to assertion Description-0024 summary" href="#Description-0024-summary">†</a></sup>
***************
*** 914,919 ****
<li>
<p>
! Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:
</p>
<ol>
--- 916,921 ----
<li>
<p>
! <a name="Description-1201005"></a><span class="test-assertion">Zero or more <em>element information item</em>s amongst its [children], in order as
! follows:</span><sup><a title="Link to assertion Description-1201005 summary" href="#Description-1201005-summary">†</a></sup>
</p>
<ol>
***************
*** 1077,1080 ****
--- 1079,1083 ----
[namespace name], [attributes] and [children]
properties of an <em>element information item</em>.
+ <a name="Types-1201006"></a><span class="test-assertion">Each XML Schema element declaration MUST have a unique QName.</span><sup><a title="Link to assertion Types-1201006 summary" href="#Types-1201006-summary">†</a></sup>
</td>
</tr>
***************
*** 1091,1095 ****
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">It is an error if there are multiple type definitions for each QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
--- 1094,1098 ----
other type system which describes the [attributes]
and [children] properties of an <em>element information item</em>.
! <a name="Types-0026"></a><span class="test-assertion">Each XML Schema type definition MUST have a unique QName.</span><sup><a title="Link to assertion Types-0026 summary" href="#Types-0026-summary">†</a></sup>
</td>
</tr>
***************
*** 9637,9641 ****
<div class="div1">
! <h2><a name="N1742F"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 9640,9644 ----
<div class="div1">
! <h2><a name="N174B4"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 9996,9999 ****
--- 9999,10008 ----
<tr>
+ <td rowspan="1" colspan="1">20060226</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Reviewed and added assertions to sections 2. and 2.1.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060224</td>
<td rowspan="1" colspan="1">RRC</td>
***************
*** 12252,12255 ****
--- 12261,12288 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201000" name="Description-1201000-summary">Description-1201000</a>
+ </td>
+ <td rowspan="1" colspan="1">WSDL 2.0 definitions are represented in XML by one or more WSDL 2.0
+ Information Sets (Infosets), that is one or more
+ <code>description</code> <em>element information item</em>s.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201004" name="Description-1201004-summary">Description-1201004</a>
+ </td>
+ <td rowspan="1" colspan="1">If a WSDL 2.0 document is split into multiple WSDL 2.0 documents
+ (which may be combined as needed via <a href="#includes"><b>4.1 Including Descriptions</b></a>), then the <code>targetNamespace</code> <em>attribute information item</em>
+ SHOULD resolve to a master WSDL 2.0 document that includes all the
+ WSDL 2.0 documents needed for that service description.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201005" name="Description-1201005-summary">Description-1201005</a>
+ </td>
+ <td rowspan="1" colspan="1">Zero or more <em>element information item</em>s amongst its [children], in order as
+ follows:</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
</td>
***************
*** 12836,12840 ****
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component MUST be uniquely
identified by its qualified name.
</td>
--- 12869,12873 ----
</td>
<td rowspan="1" colspan="1">
! Each WSDL 2.0 or type system component of the same kind MUST be uniquely
identified by its qualified name.
</td>
***************
*** 12842,12845 ****
--- 12875,12899 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Description-1201001" name="Description-1201001-summary">Description-1201001</a>
+ </td>
+ <td rowspan="1" colspan="1">The value of the <code>targetNamespace</code> <em>attribute information item</em> SHOULD be dereferenceable.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201002" name="Description-1201002-summary">Description-1201002</a>
+ </td>
+ <td rowspan="1" colspan="1">It SHOULD resolve to a human or machine
+ processable document that directly or indirectly defines the
+ intended semantics of those components.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
+ <a href="#Description-1201003" name="Description-1201003-summary">Description-1201003</a>
+ </td>
+ <td rowspan="1" colspan="1">It MAY resolve to a WSDL 2.0 document that provides
+ service description information for that namespace.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Endpoint-0064" name="Endpoint-0064-summary">Endpoint-0064</a>
</td>
***************
*** 13220,13224 ****
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">It is an error if there are multiple type definitions for each QName.</td>
</tr>
</tbody>
--- 13274,13284 ----
<a href="#Types-0026" name="Types-0026-summary">Types-0026</a>
</td>
! <td rowspan="1" colspan="1">Each XML Schema type definition MUST have a unique QName.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Types-1201006" name="Types-1201006-summary">Types-1201006</a>
! </td>
! <td rowspan="1" colspan="1">Each XML Schema element declaration MUST have a unique QName.</td>
</tr>
</tbody>
Received on Monday, 27 February 2006 00:05:55 UTC