- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 27 Feb 2006 03:00:26 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv10032/wsdl20
Modified Files:
component-assertion-table.xml wsdl20.tex wsdl20-z-ie.html
wsdl20-z.html wsdl20.html wsdl20-adjuncts.html wsdl20.xml
wsdl20-primer.html document-assertion-table.xml
Log Message:
Reviewed and added assertions for sections 4, 5, 6, 7, 8, A.
Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.72
retrieving revision 1.73
diff -C2 -d -r1.72 -r1.73
*** wsdl20-z-ie.html 27 Feb 2006 00:00:59 -0000 1.72
--- wsdl20-z-ie.html 27 Feb 2006 03:00:22 -0000 1.73
***************
*** 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
--- 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="#N174DE">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="#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">
--- 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="#N174DE">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">
***************
*** 9695,9700 ****
<code>description</code> <em>element information item</em>.</p>
! <p>It is an error if the IRI indicated by <code>location</code>
! does not resolve to a WSDL 2.0 document.</p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
--- 9695,9700 ----
<code>description</code> <em>element information item</em>.</p>
! <p><a name="Include-1400000"></a><span class="test-assertion">The IRI indicated by <code>location</code>
! MUST resolve to a WSDL 2.0 document.</span><sup><a title="Link to assertion Include-1400000 summary" href="#Include-1400000-summary">†</a></sup></p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
***************
*** 9717,9729 ****
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a target namespace.
! On its <code>wsdl:description</code> <em>element information item</em>, a WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em> that associates the document with a
! target namespace. This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! components not within the document's target namespace.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document containing definition
! components from that foreign target namespace.
</p>
--- 9717,9736 ----
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a namespace.
! Every WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em>
! on its <code>wsdl:description</code> <em>element information item</em>
! that associates the document with a
! target namespace which becomes the namespace of each
! top-level WSDL 2.0 component defined in the document.
! Any namespace other than the document's target namespace is referred
! to as a <em>foreign namespace</em> and any component associated with a foreign
! namespace is referred to as a <em>foreign component</em>.
! This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! foreign components.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document that contains definitions of
! foreign components.
</p>
***************
*** 9731,9750 ****
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used
! to import components from WSDL descriptions that
! do not share a target namespace with the importing
! document.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies namespaces used in
! foreign references. The existence of the WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for other namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
--- 9738,9754 ----
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used to import WSDL 2.0 components from a foreign namespace.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies a foreign namespace.
! The presence of a WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for foreign namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
***************
*** 9756,9770 ****
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! components from another namespace available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to components in a
! namespace other than its own target namespace if the
! WSDL 2.0 document contains an <code>wsdl:import</code> <em>element information item</em> for
! that foreign namespace.
</p>
! <p>This specification does not preclude repeating the <code>wsdl:import</code>
! <em>element information item</em> for the same value of the <code>namespace</code> <em>attribute information item</em> as long as
! they provide different values for the <code>location</code>
! <em>attribute information item</em>. Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
--- 9760,9772 ----
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! foreign components available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to foreign components if it contains an <code>wsdl:import</code> <em>element information item</em> for
! the associated foreign namespace.
</p>
! <p><a name="Import-1400001"></a><span class="test-assertion">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</span><sup><a title="Link to assertion Import-1400001 summary" href="#Import-1400001-summary">†</a></sup> Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
***************
*** 9842,9849 ****
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
--- 9844,9851 ----
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
***************
*** 9869,9873 ****
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! serialized XML 1.0 or a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
--- 9871,9875 ----
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! an XML 1.0 serialization of a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
***************
*** 9890,9894 ****
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable and/or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
--- 9892,9896 ----
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
***************
*** 9949,9955 ****
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name. The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.
</p>
--- 9951,9958 ----
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name.
! <a name="Extension-1600000"></a><span class="test-assertion">The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.</span><sup><a title="Link to assertion Extension-1600000 summary" href="#Extension-1600000-summary">†</a></sup>
</p>
***************
*** 9967,9971 ****
</p>
<p>
! It is expected that extensions will want to add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
--- 9970,9974 ----
</p>
<p>
! It is expected that extensions will add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
***************
*** 9975,9986 ****
</p>
-
-
<p>
! The WSDL 2.0 schema also defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional. The element
! declarations which serve as the heads of the defined substitution
! groups are all of type "xs:anyType".
</p>
--- 9978,9985 ----
</p>
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional.
</p>
***************
*** 10060,10064 ****
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a wsdl:required extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
--- 10059,10063 ----
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a <code>wsdl:required</code> extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
***************
*** 10171,10180 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements which may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions which have
an effective scope equal to the scope of a containing file. Extensions
! which modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
--- 10170,10179 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions that have
an effective scope equal to the scope of a containing file. Extensions
! that modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
***************
*** 10189,10198 ****
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL documents, WSDL fragments or
! references to WSDL components -via QNames- MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL for a
! namespace (or set of namespaces) can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
--- 10188,10197 ----
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document fragments or QName
! references to WSDL 2.0 components MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL 2.0 documents fo
! one or more namespaces can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
***************
*** 10232,10236 ****
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em> (of even length). <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
--- 10231,10235 ----
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em>. <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
***************
*** 10239,10242 ****
--- 10238,10243 ----
elements [<cite><a href="#WSDL11">WSDL 1.1</a></cite>])
for that namespace name.</span><sup><a title="Link to assertion Location-0077 summary" href="#Location-0077-summary">†</a></sup> The second IRI of a pair MAY be absolute or relative.
+ <a name="Location-1700000"></a><span class="test-assertion">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</span><sup><a title="Link to assertion Location-1700000 summary" href="#Location-1700000-summary">†</a></sup>
</p>
</div>
***************
*** 10814,10819 ****
</p>
<p>
! For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
--- 10815,10820 ----
</p>
<p>
! <a name="FragId-1900000"></a><span class="test-assertion">For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.</span><sup><a title="Link to assertion FragId-1900000 summary" href="#FragId-1900000-summary">†</a></sup>
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
***************
*** 10832,10835 ****
--- 10833,10839 ----
identifiers are then used to construct the pointer part in
the last column.
+ <a name="FragId-1900001"></a><span class="test-assertion">The fragment identifier in a WSDL 2.0 component IRI-reference
+ MUST resolve to some component as defined by the construction rules
+ in <a href="#frag-ids-table">Table A-1</a>.</span><sup><a title="Link to assertion FragId-1900001 summary" href="#FragId-1900001-summary">†</a></sup>
</p>
***************
*** 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>
--- 12852,12856 ----
<div class="div1">
! <h2><a name="N174DE"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 13209,13213 ****
<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>
--- 13213,13217 ----
<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. 2.1, 4, 5, 6, 7, 8 and Appendix A.</td>
</tr>
***************
*** 15518,15526 ****
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</td>
</tr>
<tr>
--- 15522,15530 ----
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</td>
</tr>
<tr>
***************
*** 15536,15543 ****
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</td>
</tr>
<tr>
--- 15540,15556 ----
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Import-1400001" name="Import-1400001-summary">Import-1400001</a>
! </td>
! <td rowspan="1" colspan="1">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</td>
</tr>
<tr>
***************
*** 15552,15555 ****
--- 15565,15575 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Include-1400000" name="Include-1400000-summary">Include-1400000</a>
+ </td>
+ <td rowspan="1" colspan="1">The IRI indicated by <code>location</code>
+ MUST resolve to a WSDL 2.0 document.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Interface-0031" name="Interface-0031-summary">Interface-0031</a>
</td>
***************
*** 15626,15629 ****
--- 15646,15656 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Location-1700000" name="Location-1700000-summary">Location-1700000</a>
+ </td>
+ <td rowspan="1" colspan="1">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#MessageLabel-0004" name="MessageLabel-0004-summary">MessageLabel-0004</a>
</td>
***************
*** 16180,16183 ****
--- 16207,16218 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Extension-1600000" name="Extension-1600000-summary">Extension-1600000</a>
+ </td>
+ <td rowspan="1" colspan="1">The meaning of an
+ extension SHOULD be defined (directly or indirectly) in a document
+ that is available at its namespace IRI.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#FeatureRef-0046" name="FeatureRef-0046-summary">FeatureRef-0046</a>
</td>
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.106
retrieving revision 1.107
diff -C2 -d -r1.106 -r1.107
*** wsdl20.tex 27 Feb 2006 00:00:59 -0000 1.106
--- wsdl20.tex 27 Feb 2006 03:00:22 -0000 1.107
***************
*** 10870,10875 ****
\texttt{description} \textit{element information item}.
! It is an error if the IRI indicated by \texttt{location}
! does not resolve to a WSDL 2.0 document.
The actual value of the \texttt{targetNamespace} \textit{attribute information item} of the
--- 10870,10875 ----
\texttt{description} \textit{element information item}.
! The IRI indicated by \texttt{location}
! MUST resolve to a WSDL 2.0 document.
The actual value of the \texttt{targetNamespace} \textit{attribute information item} of the
***************
*** 10893,10905 ****
\end{verbatim}
! Every top-level WSDL 2.0 component is associated with a target namespace.
! On its \texttt{wsdl:description} \textit{element information item}, a WSDL 2.0 document carries a
! \texttt{targetNamespace} \textit{attribute information item} that associates the document with a
! target namespace. This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! components not within the document's target namespace.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document containing definition
! components from that foreign target namespace.
--- 10893,10912 ----
\end{verbatim}
! Every top-level WSDL 2.0 component is associated with a namespace.
! Every WSDL 2.0 document carries a
! \texttt{targetNamespace} \textit{attribute information item}
! on its \texttt{wsdl:description} \textit{element information item}
! that associates the document with a
! target namespace which becomes the namespace of each
! top-level WSDL 2.0 component defined in the document.
! Any namespace other than the document's target namespace is referred
! to as a \textit{foreign namespace} and any component associated with a foreign
! namespace is referred to as a \textit{foreign component}.
! This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! foreign components.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document that contains definitions of
! foreign components.
***************
*** 10907,10926 ****
XML Schema \texttt{import} \textit{element information item} (see \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]},
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used
! to import components from WSDL descriptions that
! do not share a target namespace with the importing
! document.
! The WSDL 2.0 \texttt{import} \textit{element information item} identifies namespaces used in
! foreign references. The existence of the WSDL 2.0 \texttt{import} \textit{element information item}
signals that the WSDL 2.0 document may contain references to foreign components.
! The \texttt{wsdl:import} \textit{element information item} is therefore like a forward declaration for other namespaces.
! As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a \texttt{wsdl:import} \textit{element information item} for that namespace (but not necessarily
! providing a \texttt{location} \textit{attribute information item} identifying the WSDL 2.0 document
! in which the referenced component is declared). In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
--- 10914,10930 ----
XML Schema \texttt{import} \textit{element information item} (see \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]},
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used to import WSDL 2.0 components from a foreign namespace.
! The WSDL 2.0 \texttt{import} \textit{element information item} identifies a foreign namespace.
! The presence of a WSDL 2.0 \texttt{import} \textit{element information item}
signals that the WSDL 2.0 document may contain references to foreign components.
! The \texttt{wsdl:import} \textit{element information item} is therefore like a forward declaration for foreign namespaces.
! As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a \texttt{wsdl:import} \textit{element information item} for the associated foreign namespace (but which does not necessarily
! provide a \texttt{location} \textit{attribute information item} that identifies the WSDL 2.0 document
! in which the referenced component is defined). In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
***************
*** 10932,10945 ****
Using the \texttt{wsdl:import} \textit{element information item} is a necessary condition for making
! components from another namespace available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to components in a
! namespace other than its own target namespace if the
! WSDL 2.0 document contains an \texttt{wsdl:import} \textit{element information item} for
! that foreign namespace.
! This specification does not preclude repeating the \texttt{wsdl:import}
! \textit{element information item} for the same value of the \texttt{namespace} \textit{attribute information item} as long as
! they provide different values for the \texttt{location}
\textit{attribute information item}. Repeating the \texttt{wsdl:import} \textit{element information item} for the same
\texttt{namespace} value MAY be used as a way to provide alternate
--- 10936,10947 ----
Using the \texttt{wsdl:import} \textit{element information item} is a necessary condition for making
! foreign components available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to foreign components if it contains an \texttt{wsdl:import} \textit{element information item} for
! the associated foreign namespace.
! If a WSDL 2.0 document contains more than one \texttt{wsdl:import}
! \textit{element information item} for a given value of the \texttt{namespace} \textit{attribute information item} then
! they MUST provide different values for the \texttt{location}
\textit{attribute information item}. Repeating the \texttt{wsdl:import} \textit{element information item} for the same
\texttt{namespace} value MAY be used as a way to provide alternate
***************
*** 11019,11026 ****
value of \texttt{targetNamespace} \textit{attribute information item} in the enclosing WSDL 2.0 document.
If the location attribute in the \texttt{import} \textit{element information item}
! references a WSDL 2.0 document, then the actual value of the
\texttt{namespace} \textit{attribute information item} MUST be identical to the
actual value of the \texttt{targetNamespace} \textit{attribute information item}
! in the referenced WSDL 2.0 document.
--- 11021,11028 ----
value of \texttt{targetNamespace} \textit{attribute information item} in the enclosing WSDL 2.0 document.
If the location attribute in the \texttt{import} \textit{element information item}
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
\texttt{namespace} \textit{attribute information item} MUST be identical to the
actual value of the \texttt{targetNamespace} \textit{attribute information item}
! of the referenced WSDL 2.0 document.
***************
*** 11047,11051 ****
The \texttt{location} \textit{attribute information item} is optional. This allows WSDL 2.0
components to be constructed from information other than
! serialized XML 1.0 or a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have \textit{a prior} (i.e., built-in) knowledge of certain namespaces.
--- 11049,11053 ----
The \texttt{location} \textit{attribute information item} is optional. This allows WSDL 2.0
components to be constructed from information other than
! an XML 1.0 serialization of a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have \textit{a prior} (i.e., built-in) knowledge of certain namespaces.
***************
*** 11069,11073 ****
WSDL 2.0 uses the optional \texttt{documentation} \textit{element information item} as a container
! for human readable and/or machine processable documentation. The
content of the \textit{element information item} is arbitrary \textit{character information
items} and \textit{element information item}s ("mixed" content in XML Schema\hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}). The \texttt{documentation} \textit{element information item} is allowed
--- 11071,11075 ----
WSDL 2.0 uses the optional \texttt{documentation} \textit{element information item} as a container
! for human readable or machine processable documentation. The
content of the \textit{element information item} is arbitrary \textit{character information
items} and \textit{element information item}s ("mixed" content in XML Schema\hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}). The \texttt{documentation} \textit{element information item} is allowed
***************
*** 11129,11133 ****
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name. The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
that is available at its namespace IRI.
--- 11131,11136 ----
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name.
! The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
that is available at its namespace IRI.
***************
*** 11148,11152 ****
! It is expected that extensions will want to add to the
existing properties of components in the component model. The
specification for an extension \textit{element information item} should include definitions
--- 11151,11155 ----
! It is expected that extensions will add to the
existing properties of components in the component model. The
specification for an extension \textit{element information item} should include definitions
***************
*** 11156,11167 ****
-
-
! The WSDL 2.0 schema also defines a base type for use by extensibility
elements. \hyperlink{exttype}{Example \ref*{exttype} } shows the type definition. The
! use of this type as a base type is optional. The element
! declarations which serve as the heads of the defined substitution
! groups are all of type {\tt "xs:anyType"}.
--- 11159,11166 ----
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. \hyperlink{exttype}{Example \ref*{exttype} } shows the type definition. The
! use of this type as a base type is optional.
***************
*** 11242,11246 ****
If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a wsdl:required extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.
--- 11241,11245 ----
If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a \texttt{wsdl:required} extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.
***************
*** 11356,11365 ****
! Authors of extensibility elements which may manifest as properties of
the Description component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions which have
an effective scope equal to the scope of a containing file. Extensions
! which modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
--- 11355,11364 ----
! Authors of extensibility elements that may manifest as properties of
the Description component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions that have
an effective scope equal to the scope of a containing file. Extensions
! that modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
***************
*** 11375,11384 ****
! As an XML vocabulary, WSDL documents, WSDL fragments or
! references to WSDL components -via QNames- MAY appear within other
XML documents. This specification defines a global attribute,
\texttt{wsdlLocation}, to help with QName resolution (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL for a
! namespace (or set of namespaces) can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.
--- 11374,11383 ----
! As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document fragments or QName
! references to WSDL 2.0 components MAY appear within other
XML documents. This specification defines a global attribute,
\texttt{wsdlLocation}, to help with QName resolution (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL 2.0 documents fo
! one or more namespaces can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.
***************
*** 11419,11423 ****
The type of the \texttt{wsdlLocation} \textit{attribute information item} is a list
! \textit{xs:anyURI} (of even length). Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in \hyperlink{RFC3987}{[\textit{IETF RFC 3987}]}, indicates a
--- 11418,11422 ----
The type of the \texttt{wsdlLocation} \textit{attribute information item} is a list
! \textit{xs:anyURI}. Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in \hyperlink{RFC3987}{[\textit{IETF RFC 3987}]}, indicates a
***************
*** 11426,11429 ****
--- 11425,11430 ----
elements \hyperlink{WSDL11}{[\textit{WSDL 1.1}]})
for that namespace name. The second IRI of a pair MAY be absolute or relative.
+ For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.
***************
*** 12048,12051 ****
--- 12049,12055 ----
identifiers are then used to construct the pointer part in
the last column.
+ The fragment identifier in a WSDL 2.0 component IRI-reference
+ MUST resolve to some component as defined by the construction rules
+ in \hyperlink{frag-ids-table}{Table \ref*{frag-ids-table} }.
***************
*** 15025,15029 ****
20060226&
AGR&
! Reviewed and added assertions to sections 2. and 2.1.
\\ \hline
--- 15029,15033 ----
20060226&
AGR&
! Reviewed and added assertions to sections 2. 2.1, 4, 5, 6, 7, 8 and Appendix A.
\\ \hline
***************
*** 17332,17340 ****
&
! As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a \texttt{wsdl:import} \textit{element information item} for that namespace (but not necessarily
! providing a \texttt{location} \textit{attribute information item} identifying the WSDL 2.0 document
! in which the referenced component is declared).
\\ \hline
--- 17336,17344 ----
&
! As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a \texttt{wsdl:import} \textit{element information item} for the associated foreign namespace (but which does not necessarily
! provide a \texttt{location} \textit{attribute information item} that identifies the WSDL 2.0 document
! in which the referenced component is defined).
\\ \hline
***************
*** 17350,17357 ****
&
If the location attribute in the \texttt{import} \textit{element information item}
! references a WSDL 2.0 document, then the actual value of the
\texttt{namespace} \textit{attribute information item} MUST be identical to the
actual value of the \texttt{targetNamespace} \textit{attribute information item}
! in the referenced WSDL 2.0 document.
\\ \hline
--- 17354,17370 ----
&
If the location attribute in the \texttt{import} \textit{element information item}
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
\texttt{namespace} \textit{attribute information item} MUST be identical to the
actual value of the \texttt{targetNamespace} \textit{attribute information item}
! of the referenced WSDL 2.0 document.
! \\ \hline
!
!
!
! &
! If a WSDL 2.0 document contains more than one \texttt{wsdl:import}
! \textit{element information item} for a given value of the \texttt{namespace} \textit{attribute information item} then
! they MUST provide different values for the \texttt{location}
! \textit{attribute information item}.
\\ \hline
***************
*** 17368,17371 ****
--- 17381,17391 ----
&
+ The IRI indicated by \texttt{location}
+ MUST resolve to a WSDL 2.0 document.
+ \\ \hline
+
+
+
+ &
Its value, if present, MUST contain
absolute IRIs (see \hyperlink{RFC3987}{[\textit{IETF RFC 3987}]}).
***************
*** 17442,17445 ****
--- 17462,17472 ----
&
+ For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.
+ \\ \hline
+
+
+
+ &
The
***************
*** 17998,18001 ****
--- 18025,18036 ----
&
+ The meaning of an
+ extension SHOULD be defined (directly or indirectly) in a document
+ that is available at its namespace IRI.
+ \\ \hline
+
+
+
+ &
This \textit{xs:anyURI} MUST be an absolute IRI
as defined by \hyperlink{RFC3987}{[\textit{IETF RFC 3987}]}.
Index: component-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/component-assertion-table.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** component-assertion-table.xml 27 Feb 2006 00:00:59 -0000 1.9
--- component-assertion-table.xml 27 Feb 2006 03:00:22 -0000 1.10
***************
*** 234,237 ****
--- 234,245 ----
<tr>
<td>
+ <assert-summary ref="Extension-1600000"/>
+ </td>
+ <td>The meaning of an
+ extension SHOULD be defined (directly or indirectly) in a document
+ that is available at its namespace IRI.</td>
+ </tr>
+ <tr>
+ <td>
<assert-summary ref="FeatureRef-0046"/>
</td>
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.387
retrieving revision 1.388
diff -C2 -d -r1.387 -r1.388
*** wsdl20.xml 27 Feb 2006 00:00:59 -0000 1.387
--- wsdl20.xml 27 Feb 2006 03:00:24 -0000 1.388
***************
*** 10651,10656 ****
<el>description</el> &EII;.</p>
! <p>It is an error if the IRI indicated by <att>location</att>
! does not resolve to a WSDL 2.0 document.</p>
<p><assert class="document" id="Include-0069">The actual value of the <att>targetNamespace</att> &AII; of the
--- 10651,10656 ----
<el>description</el> &EII;.</p>
! <p><assert class="document" id="Include-1400000">The IRI indicated by <att>location</att>
! MUST resolve to a WSDL 2.0 document.</assert></p>
<p><assert class="document" id="Include-0069">The actual value of the <att>targetNamespace</att> &AII; of the
***************
*** 10672,10684 ****
</eg>
! <p>Every top-level WSDL 2.0 component is associated with a target namespace.
! On its <el>wsdl:description</el> &EII;, a WSDL 2.0 document carries a
! <att>targetNamespace</att> &AII; that associates the document with a
! target namespace. This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! components not within the document's target namespace.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document containing definition
! components from that foreign target namespace.
</p>
--- 10672,10691 ----
</eg>
! <p>Every top-level WSDL 2.0 component is associated with a namespace.
! Every WSDL 2.0 document carries a
! <att>targetNamespace</att> &AII;
! on its <el>wsdl:description</el> &EII;
! that associates the document with a
! target namespace which becomes the namespace of each
! top-level WSDL 2.0 component defined in the document.
! Any namespace other than the document's target namespace is referred
! to as a <emph>foreign namespace</emph> and any component associated with a foreign
! namespace is referred to as a <emph>foreign component</emph>.
! This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! foreign components.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document that contains definitions of
! foreign components.
</p>
***************
*** 10686,10705 ****
XML Schema <el>import</el> &EII; (see <bibref ref="XMLSchemaP1"/>,
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used
! to import components from WSDL descriptions that
! do not share a target namespace with the importing
! document.
! The WSDL 2.0 <el>import</el> &EII; identifies namespaces used in
! foreign references. The existence of the WSDL 2.0 <el>import</el> &EII;
signals that the WSDL 2.0 document may contain references to foreign components.
! The <el>wsdl:import</el> &EII; is therefore like a forward declaration for other namespaces.
</p>
<p>
! <assert class="document" id="Import-0070">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <el>wsdl:import</el> &EII; for that namespace (but not necessarily
! providing a <att>location</att> &AII; identifying the WSDL 2.0 document
! in which the referenced component is declared).</assert> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
--- 10693,10709 ----
XML Schema <el>import</el> &EII; (see <bibref ref="XMLSchemaP1"/>,
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used to import WSDL 2.0 components from a foreign namespace.
! The WSDL 2.0 <el>import</el> &EII; identifies a foreign namespace.
! The presence of a WSDL 2.0 <el>import</el> &EII;
signals that the WSDL 2.0 document may contain references to foreign components.
! The <el>wsdl:import</el> &EII; is therefore like a forward declaration for foreign namespaces.
</p>
<p>
! <assert class="document" id="Import-0070">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <el>wsdl:import</el> &EII; for the associated foreign namespace (but which does not necessarily
! provide a <att>location</att> &AII; that identifies the WSDL 2.0 document
! in which the referenced component is defined).</assert> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
***************
*** 10711,10725 ****
<p>Using the <el>wsdl:import</el> &EII; is a necessary condition for making
! components from another namespace available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to components in a
! namespace other than its own target namespace if the
! WSDL 2.0 document contains an <el>wsdl:import</el> &EII; for
! that foreign namespace.
</p>
! <p>This specification does not preclude repeating the <el>wsdl:import</el>
! &EII; for the same value of the <att>namespace</att> &AII; as long as
! they provide different values for the <att>location</att>
! &AII;. Repeating the <el>wsdl:import</el> &EII; for the same
<att>namespace</att> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
--- 10715,10727 ----
<p>Using the <el>wsdl:import</el> &EII; is a necessary condition for making
! foreign components available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to foreign components if it contains an <el>wsdl:import</el> &EII; for
! the associated foreign namespace.
</p>
! <p><assert class="document" id="Import-1400001">If a WSDL 2.0 document contains more than one <el>wsdl:import</el>
! &EII; for a given value of the <att>namespace</att> &AII; then
! they MUST provide different values for the <att>location</att>
! &AII;.</assert> Repeating the <el>wsdl:import</el> &EII; for the same
<att>namespace</att> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
***************
*** 10797,10804 ****
value of <att>targetNamespace</att> &AII; in the enclosing WSDL 2.0 document.</assert>
<assert class="document" id="Import-0072">If the location attribute in the <el>import</el> &EII;
! references a WSDL 2.0 document, then the actual value of the
<att>namespace</att> &AII; MUST be identical to the
actual value of the <att>targetNamespace</att> &AII;
! in the referenced WSDL 2.0 document.</assert>
</p>
</div3>
--- 10799,10806 ----
value of <att>targetNamespace</att> &AII; in the enclosing WSDL 2.0 document.</assert>
<assert class="document" id="Import-0072">If the location attribute in the <el>import</el> &EII;
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<att>namespace</att> &AII; MUST be identical to the
actual value of the <att>targetNamespace</att> &AII;
! of the referenced WSDL 2.0 document.</assert>
</p>
</div3>
***************
*** 10823,10827 ****
<p>The <att>location</att> &AII; is optional. This allows WSDL 2.0
components to be constructed from information other than
! serialized XML 1.0 or a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <emph>a prior</emph> (i.e., built-in) knowledge of certain namespaces.</p>
--- 10825,10829 ----
<p>The <att>location</att> &AII; is optional. This allows WSDL 2.0
components to be constructed from information other than
! an XML 1.0 serialization of a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <emph>a prior</emph> (i.e., built-in) knowledge of certain namespaces.</p>
***************
*** 10843,10847 ****
<p>
WSDL 2.0 uses the optional <el>documentation</el> &EII; as a container
! for human readable and/or machine processable documentation. The
content of the &EII; is arbitrary <emph>character information
items</emph> and &EII;s ("mixed" content in XML Schema<bibref
--- 10845,10849 ----
<p>
WSDL 2.0 uses the optional <el>documentation</el> &EII; as a container
! for human readable or machine processable documentation. The
content of the &EII; is arbitrary <emph>character information
items</emph> and &EII;s ("mixed" content in XML Schema<bibref
***************
*** 10902,10908 ****
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name. The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.
</p>
--- 10904,10911 ----
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name.
! <assert class="component" id="Extension-1600000" required="false">The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.</assert>
</p>
***************
*** 10919,10923 ****
</p>
<p>
! It is expected that extensions will want to add to the
existing properties of components in the component model. The
specification for an extension &EII; should include definitions
--- 10922,10926 ----
</p>
<p>
! It is expected that extensions will add to the
existing properties of components in the component model. The
specification for an extension &EII; should include definitions
***************
*** 10927,10938 ****
</p>
-
-
<p>
! The WSDL 2.0 schema also defines a base type for use by extensibility
elements. <specref ref='exttype' /> shows the type definition. The
! use of this type as a base type is optional. The element
! declarations which serve as the heads of the defined substitution
! groups are all of type <attval>xs:anyType</attval>.
</p>
--- 10930,10937 ----
</p>
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <specref ref='exttype' /> shows the type definition. The
! use of this type as a base type is optional.
</p>
***************
*** 11012,11016 ****
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a wsdl:required extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
--- 11011,11015 ----
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a <att>wsdl:required</att> extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
***************
*** 11120,11129 ****
<note><p>
! Authors of extensibility elements which may manifest as properties of
the <comp>Description</comp> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions which have
an effective scope equal to the scope of a containing file. Extensions
! which modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
--- 11119,11128 ----
<note><p>
! Authors of extensibility elements that may manifest as properties of
the <comp>Description</comp> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions that have
an effective scope equal to the scope of a containing file. Extensions
! that modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
***************
*** 11137,11147 ****
<head>Locating WSDL 2.0 Documents</head>
! <p>As an XML vocabulary, WSDL documents, WSDL fragments or
! references to WSDL components -via QNames- MAY appear within other
XML documents. This specification defines a global attribute,
<att>wsdlLocation</att>, to help with QName resolution (see <specref
ref="qnameres"/>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL for a
! namespace (or set of namespaces) can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
--- 11136,11146 ----
<head>Locating WSDL 2.0 Documents</head>
! <p>As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document fragments or QName
! references to WSDL 2.0 components MAY appear within other
XML documents. This specification defines a global attribute,
<att>wsdlLocation</att>, to help with QName resolution (see <specref
ref="qnameres"/>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL 2.0 documents fo
! one or more namespaces can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
***************
*** 11181,11185 ****
<p> The type of the <att>wsdlLocation</att> &AII; is a list
! <emph>xs:anyURI</emph> (of even length). <assert class="component" id="Location-0077">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in <bibref ref="RFC3987"/>, indicates a
--- 11180,11184 ----
<p> The type of the <att>wsdlLocation</att> &AII; is a list
! <emph>xs:anyURI</emph>. <assert class="component" id="Location-0077">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in <bibref ref="RFC3987"/>, indicates a
***************
*** 11188,11191 ****
--- 11187,11192 ----
elements <bibref ref="WSDL11"/>)
for that namespace name.</assert> The second IRI of a pair MAY be absolute or relative.
+ <assert class="document" id="Location-1700000">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</assert>
</p>
</div2>
***************
*** 11832,11837 ****
</p>
<p>
! For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
--- 11833,11838 ----
</p>
<p>
! <assert class="component" id="FragId-1900000">For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.</assert>
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
***************
*** 11850,11853 ****
--- 11851,11857 ----
identifiers are then used to construct the pointer part in
the last column.
+ <assert class="component" id="FragId-1900001">The fragment identifier in a WSDL 2.0 component IRI-reference
+ MUST resolve to some component as defined by the construction rules
+ in <specref ref="frag-ids-table" />.</assert>
</p>
***************
*** 14305,14309 ****
<td>20060226</td>
<td>AGR</td>
! <td>Reviewed and added assertions to sections 2. and 2.1.</td>
</tr>
--- 14309,14313 ----
<td>20060226</td>
<td>AGR</td>
! <td>Reviewed and added assertions to sections 2. 2.1, 4, 5, 6, 7, 8 and Appendix A.</td>
</tr>
Index: document-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/document-assertion-table.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** document-assertion-table.xml 27 Feb 2006 00:00:59 -0000 1.10
--- document-assertion-table.xml 27 Feb 2006 03:00:24 -0000 1.11
***************
*** 64,72 ****
<assert-summary ref="Import-0070"/>
</td>
! <td>As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <el>wsdl:import</el> <emph>element information item</emph> for that namespace (but not necessarily
! providing a <att>location</att> <emph>attribute information item</emph> identifying the WSDL 2.0 document
! in which the referenced component is declared).</td>
</tr>
<tr>
--- 64,72 ----
<assert-summary ref="Import-0070"/>
</td>
! <td>As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <el>wsdl:import</el> <emph>element information item</emph> for the associated foreign namespace (but which does not necessarily
! provide a <att>location</att> <emph>attribute information item</emph> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</td>
</tr>
<tr>
***************
*** 82,89 ****
</td>
<td>If the location attribute in the <el>import</el> <emph>element information item</emph>
! references a WSDL 2.0 document, then the actual value of the
<att>namespace</att> <emph>attribute information item</emph> MUST be identical to the
actual value of the <att>targetNamespace</att> <emph>attribute information item</emph>
! in the referenced WSDL 2.0 document.</td>
</tr>
<tr>
--- 82,98 ----
</td>
<td>If the location attribute in the <el>import</el> <emph>element information item</emph>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<att>namespace</att> <emph>attribute information item</emph> MUST be identical to the
actual value of the <att>targetNamespace</att> <emph>attribute information item</emph>
! of the referenced WSDL 2.0 document.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="Import-1400001"/>
! </td>
! <td>If a WSDL 2.0 document contains more than one <el>wsdl:import</el>
! <emph>element information item</emph> for a given value of the <att>namespace</att> <emph>attribute information item</emph> then
! they MUST provide different values for the <att>location</att>
! <emph>attribute information item</emph>.</td>
</tr>
<tr>
***************
*** 98,101 ****
--- 107,117 ----
<tr>
<td>
+ <assert-summary ref="Include-1400000"/>
+ </td>
+ <td>The IRI indicated by <att>location</att>
+ MUST resolve to a WSDL 2.0 document.</td>
+ </tr>
+ <tr>
+ <td>
<assert-summary ref="Interface-0031"/>
</td>
***************
*** 172,175 ****
--- 188,198 ----
<tr>
<td>
+ <assert-summary ref="Location-1700000"/>
+ </td>
+ <td>For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td>
+ </tr>
+ <tr>
+ <td>
<assert-summary ref="MessageLabel-0004"/>
</td>
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.97
retrieving revision 1.98
diff -C2 -d -r1.97 -r1.98
*** wsdl20-z.html 27 Feb 2006 00:00:59 -0000 1.97
--- wsdl20-z.html 27 Feb 2006 03:00:22 -0000 1.98
***************
*** 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
--- 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="#N174DE">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="#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">
--- 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="#N174DE">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">
***************
*** 9665,9670 ****
<code>description</code> <em>element information item</em>.</p>
! <p>It is an error if the IRI indicated by <code>location</code>
! does not resolve to a WSDL 2.0 document.</p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
--- 9665,9670 ----
<code>description</code> <em>element information item</em>.</p>
! <p><a name="Include-1400000"></a><span class="test-assertion">The IRI indicated by <code>location</code>
! MUST resolve to a WSDL 2.0 document.</span><sup><a title="Link to assertion Include-1400000 summary" href="#Include-1400000-summary">†</a></sup></p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
***************
*** 9687,9699 ****
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a target namespace.
! On its <code>wsdl:description</code> <em>element information item</em>, a WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em> that associates the document with a
! target namespace. This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! components not within the document's target namespace.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document containing definition
! components from that foreign target namespace.
</p>
--- 9687,9706 ----
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a namespace.
! Every WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em>
! on its <code>wsdl:description</code> <em>element information item</em>
! that associates the document with a
! target namespace which becomes the namespace of each
! top-level WSDL 2.0 component defined in the document.
! Any namespace other than the document's target namespace is referred
! to as a <em>foreign namespace</em> and any component associated with a foreign
! namespace is referred to as a <em>foreign component</em>.
! This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! foreign components.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document that contains definitions of
! foreign components.
</p>
***************
*** 9701,9720 ****
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used
! to import components from WSDL descriptions that
! do not share a target namespace with the importing
! document.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies namespaces used in
! foreign references. The existence of the WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for other namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
--- 9708,9724 ----
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used to import WSDL 2.0 components from a foreign namespace.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies a foreign namespace.
! The presence of a WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for foreign namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
***************
*** 9726,9740 ****
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! components from another namespace available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to components in a
! namespace other than its own target namespace if the
! WSDL 2.0 document contains an <code>wsdl:import</code> <em>element information item</em> for
! that foreign namespace.
</p>
! <p>This specification does not preclude repeating the <code>wsdl:import</code>
! <em>element information item</em> for the same value of the <code>namespace</code> <em>attribute information item</em> as long as
! they provide different values for the <code>location</code>
! <em>attribute information item</em>. Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
--- 9730,9742 ----
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! foreign components available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to foreign components if it contains an <code>wsdl:import</code> <em>element information item</em> for
! the associated foreign namespace.
</p>
! <p><a name="Import-1400001"></a><span class="test-assertion">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</span><sup><a title="Link to assertion Import-1400001 summary" href="#Import-1400001-summary">†</a></sup> Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
***************
*** 9812,9819 ****
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
--- 9814,9821 ----
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
***************
*** 9839,9843 ****
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! serialized XML 1.0 or a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
--- 9841,9845 ----
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! an XML 1.0 serialization of a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
***************
*** 9860,9864 ****
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable and/or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
--- 9862,9866 ----
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
***************
*** 9919,9925 ****
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name. The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.
</p>
--- 9921,9928 ----
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name.
! <a name="Extension-1600000"></a><span class="test-assertion">The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.</span><sup><a title="Link to assertion Extension-1600000 summary" href="#Extension-1600000-summary">†</a></sup>
</p>
***************
*** 9937,9941 ****
</p>
<p>
! It is expected that extensions will want to add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
--- 9940,9944 ----
</p>
<p>
! It is expected that extensions will add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
***************
*** 9945,9956 ****
</p>
-
-
<p>
! The WSDL 2.0 schema also defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional. The element
! declarations which serve as the heads of the defined substitution
! groups are all of type "xs:anyType".
</p>
--- 9948,9955 ----
</p>
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional.
</p>
***************
*** 10030,10034 ****
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a wsdl:required extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
--- 10029,10033 ----
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a <code>wsdl:required</code> extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
***************
*** 10141,10150 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements which may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions which have
an effective scope equal to the scope of a containing file. Extensions
! which modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
--- 10140,10149 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions that have
an effective scope equal to the scope of a containing file. Extensions
! that modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
***************
*** 10159,10168 ****
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL documents, WSDL fragments or
! references to WSDL components -via QNames- MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL for a
! namespace (or set of namespaces) can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
--- 10158,10167 ----
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document fragments or QName
! references to WSDL 2.0 components MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL 2.0 documents fo
! one or more namespaces can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
***************
*** 10202,10206 ****
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em> (of even length). <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
--- 10201,10205 ----
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em>. <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
***************
*** 10209,10212 ****
--- 10208,10213 ----
elements [<cite><a href="#WSDL11">WSDL 1.1</a></cite>])
for that namespace name.</span><sup><a title="Link to assertion Location-0077 summary" href="#Location-0077-summary">†</a></sup> The second IRI of a pair MAY be absolute or relative.
+ <a name="Location-1700000"></a><span class="test-assertion">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</span><sup><a title="Link to assertion Location-1700000 summary" href="#Location-1700000-summary">†</a></sup>
</p>
</div>
***************
*** 10784,10789 ****
</p>
<p>
! For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
--- 10785,10790 ----
</p>
<p>
! <a name="FragId-1900000"></a><span class="test-assertion">For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.</span><sup><a title="Link to assertion FragId-1900000 summary" href="#FragId-1900000-summary">†</a></sup>
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
***************
*** 10802,10805 ****
--- 10803,10809 ----
identifiers are then used to construct the pointer part in
the last column.
+ <a name="FragId-1900001"></a><span class="test-assertion">The fragment identifier in a WSDL 2.0 component IRI-reference
+ MUST resolve to some component as defined by the construction rules
+ in <a href="#frag-ids-table">Table A-1</a>.</span><sup><a title="Link to assertion FragId-1900001 summary" href="#FragId-1900001-summary">†</a></sup>
</p>
***************
*** 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>
--- 12822,12826 ----
<div class="div1">
! <h2><a name="N174DE"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 13179,13183 ****
<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>
--- 13183,13187 ----
<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. 2.1, 4, 5, 6, 7, 8 and Appendix A.</td>
</tr>
***************
*** 15488,15496 ****
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</td>
</tr>
<tr>
--- 15492,15500 ----
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</td>
</tr>
<tr>
***************
*** 15506,15513 ****
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</td>
</tr>
<tr>
--- 15510,15526 ----
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Import-1400001" name="Import-1400001-summary">Import-1400001</a>
! </td>
! <td rowspan="1" colspan="1">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</td>
</tr>
<tr>
***************
*** 15522,15525 ****
--- 15535,15545 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Include-1400000" name="Include-1400000-summary">Include-1400000</a>
+ </td>
+ <td rowspan="1" colspan="1">The IRI indicated by <code>location</code>
+ MUST resolve to a WSDL 2.0 document.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Interface-0031" name="Interface-0031-summary">Interface-0031</a>
</td>
***************
*** 15596,15599 ****
--- 15616,15626 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Location-1700000" name="Location-1700000-summary">Location-1700000</a>
+ </td>
+ <td rowspan="1" colspan="1">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#MessageLabel-0004" name="MessageLabel-0004-summary">MessageLabel-0004</a>
</td>
***************
*** 16150,16153 ****
--- 16177,16188 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Extension-1600000" name="Extension-1600000-summary">Extension-1600000</a>
+ </td>
+ <td rowspan="1" colspan="1">The meaning of an
+ extension SHOULD be defined (directly or indirectly) in a document
+ that is available at its namespace IRI.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#FeatureRef-0046" name="FeatureRef-0046-summary">FeatureRef-0046</a>
</td>
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.266
retrieving revision 1.267
diff -C2 -d -r1.266 -r1.267
*** wsdl20.html 27 Feb 2006 00:00:58 -0000 1.266
--- wsdl20.html 27 Feb 2006 03:00:23 -0000 1.267
***************
*** 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
--- 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="#N174DE">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="#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">
--- 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="#N174DE">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">
***************
*** 7297,7302 ****
<code>description</code> <em>element information item</em>.</p>
! <p>It is an error if the IRI indicated by <code>location</code>
! does not resolve to a WSDL 2.0 document.</p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
--- 7297,7302 ----
<code>description</code> <em>element information item</em>.</p>
! <p><a name="Include-1400000"></a><span class="test-assertion">The IRI indicated by <code>location</code>
! MUST resolve to a WSDL 2.0 document.</span><sup><a title="Link to assertion Include-1400000 summary" href="#Include-1400000-summary">†</a></sup></p>
<p><a name="Include-0069"></a><span class="test-assertion">The actual value of the <code>targetNamespace</code> <em>attribute information item</em> of the
***************
*** 7319,7331 ****
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a target namespace.
! On its <code>wsdl:description</code> <em>element information item</em>, a WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em> that associates the document with a
! target namespace. This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! components not within the document's target namespace.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document containing definition
! components from that foreign target namespace.
</p>
--- 7319,7338 ----
</pre></div>
! <p>Every top-level WSDL 2.0 component is associated with a namespace.
! Every WSDL 2.0 document carries a
! <code>targetNamespace</code> <em>attribute information item</em>
! on its <code>wsdl:description</code> <em>element information item</em>
! that associates the document with a
! target namespace which becomes the namespace of each
! top-level WSDL 2.0 component defined in the document.
! Any namespace other than the document's target namespace is referred
! to as a <em>foreign namespace</em> and any component associated with a foreign
! namespace is referred to as a <em>foreign component</em>.
! This section describes the syntax and mechanisms by
which references may be made from within a WSDL 2.0 document to
! foreign components.
In addition to this syntax, there is an optional facility for
! suggesting the IRI of a WSDL 2.0 document that contains definitions of
! foreign components.
</p>
***************
*** 7333,7352 ****
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used
! to import components from WSDL descriptions that
! do not share a target namespace with the importing
! document.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies namespaces used in
! foreign references. The existence of the WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for other namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
--- 7340,7356 ----
XML Schema <code>import</code> <em>element information item</em> (see [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
section 4.2.3 "References to schema components across namespaces").
! Specifically, it can be used to import WSDL 2.0 components from a foreign namespace.
! The WSDL 2.0 <code>import</code> <em>element information item</em> identifies a foreign namespace.
! The presence of a WSDL 2.0 <code>import</code> <em>element information item</em>
signals that the WSDL 2.0 document may contain references to foreign components.
! The <code>wsdl:import</code> <em>element information item</em> is therefore like a forward declaration for foreign namespaces.
</p>
<p>
! <a name="Import-0070"></a><span class="test-assertion">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</span><sup><a title="Link to assertion Import-0070 summary" href="#Import-0070-summary">†</a></sup> In
other respects, the visibility of components is
pervasive; if two WSDL 2.0 documents import the same
***************
*** 7358,7372 ****
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! components from another namespace available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to components in a
! namespace other than its own target namespace if the
! WSDL 2.0 document contains an <code>wsdl:import</code> <em>element information item</em> for
! that foreign namespace.
</p>
! <p>This specification does not preclude repeating the <code>wsdl:import</code>
! <em>element information item</em> for the same value of the <code>namespace</code> <em>attribute information item</em> as long as
! they provide different values for the <code>location</code>
! <em>attribute information item</em>. Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
--- 7362,7374 ----
<p>Using the <code>wsdl:import</code> <em>element information item</em> is a necessary condition for making
! foreign components available to a WSDL 2.0 document.
! That is, a WSDL 2.0 document can only refer to foreign components if it contains an <code>wsdl:import</code> <em>element information item</em> for
! the associated foreign namespace.
</p>
! <p><a name="Import-1400001"></a><span class="test-assertion">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</span><sup><a title="Link to assertion Import-1400001 summary" href="#Import-1400001-summary">†</a></sup> Repeating the <code>wsdl:import</code> <em>element information item</em> for the same
<code>namespace</code> value MAY be used as a way to provide alternate
locations to find information about a given namespace.</p>
***************
*** 7444,7451 ****
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
--- 7446,7453 ----
value of <code>targetNamespace</code> <em>attribute information item</em> in the enclosing WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0071 summary" href="#Import-0071-summary">†</a></sup>
<a name="Import-0072"></a><span class="test-assertion">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</span><sup><a title="Link to assertion Import-0072 summary" href="#Import-0072-summary">†</a></sup>
</p>
</div>
***************
*** 7471,7475 ****
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! serialized XML 1.0 or a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
--- 7473,7477 ----
<p>The <code>location</code> <em>attribute information item</em> is optional. This allows WSDL 2.0
components to be constructed from information other than
! an XML 1.0 serialization of a WSDL 2.0 document. It also allows the development
of WSDL 2.0 processors that
have <em>a prior</em> (i.e., built-in) knowledge of certain namespaces.</p>
***************
*** 7492,7496 ****
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable and/or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
--- 7494,7498 ----
<p>
WSDL 2.0 uses the optional <code>documentation</code> <em>element information item</em> as a container
! for human readable or machine processable documentation. The
content of the <em>element information item</em> is arbitrary <em>character information
items</em> and <em>element information item</em>s ("mixed" content in XML Schema[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]). The <code>documentation</code> <em>element information item</em> is allowed
***************
*** 7551,7557 ****
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name. The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.
</p>
--- 7553,7560 ----
extensibility model based on namespace-qualified elements and attributes.
An extension is identified by the QName consisting of its
! namespace IRI and its element name.
! <a name="Extension-1600000"></a><span class="test-assertion">The meaning of an
extension SHOULD be defined (directly or indirectly) in a document
! that is available at its namespace IRI.</span><sup><a title="Link to assertion Extension-1600000 summary" href="#Extension-1600000-summary">†</a></sup>
</p>
***************
*** 7569,7573 ****
</p>
<p>
! It is expected that extensions will want to add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
--- 7572,7576 ----
</p>
<p>
! It is expected that extensions will add to the
existing properties of components in the component model. The
specification for an extension <em>element information item</em> should include definitions
***************
*** 7577,7588 ****
</p>
-
-
<p>
! The WSDL 2.0 schema also defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional. The element
! declarations which serve as the heads of the defined substitution
! groups are all of type "xs:anyType".
</p>
--- 7580,7587 ----
</p>
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
! use of this type as a base type is optional.
</p>
***************
*** 7662,7666 ****
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a wsdl:required extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
--- 7661,7665 ----
<p>If a Web service requires the client to follow a particular convention
that is likely to be automatable in WSDL 2.0 toolkits, then that convention
! SHOULD be indicated in the WSDL 2.0 document as a <code>wsdl:required</code> extension,
rather than just being conveyed out of band, even if that convention is
not currently implemented in WSDL 2.0 toolkits.</p>
***************
*** 7773,7782 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements which may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions which have
an effective scope equal to the scope of a containing file. Extensions
! which modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
--- 7772,7781 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
! possible, within the component model, to define extensions that have
an effective scope equal to the scope of a containing file. Extensions
! that modify the behavior of the components contained in a description
may therefore unexpectedly modify the behavior of components in
imported descriptions as well, unless proper care is taken. Users of
***************
*** 7791,7800 ****
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL documents, WSDL fragments or
! references to WSDL components -via QNames- MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL for a
! namespace (or set of namespaces) can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
--- 7790,7799 ----
<h2><a name="wsdllocation"></a>7. Locating WSDL 2.0 Documents</h2>
! <p>As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document fragments or QName
! references to WSDL 2.0 components MAY appear within other
XML documents. This specification defines a global attribute,
<code>wsdlLocation</code> , to help with QName resolution (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). This attribute allows an element that contains
! such references to be annotated to indicate where the WSDL 2.0 documents fo
! one or more namespaces can be found. In particular, this
attribute is expected to be useful when using service references in
message exchanges.</p>
***************
*** 7834,7838 ****
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em> (of even length). <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
--- 7833,7837 ----
<p> The type of the <code>wsdlLocation</code> <em>attribute information item</em> is a list
! <em>xs:anyURI</em>. <a name="Location-0077"></a><span class="test-assertion">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC 3987</a></cite>], indicates a
***************
*** 7841,7844 ****
--- 7840,7845 ----
elements [<cite><a href="#WSDL11">WSDL 1.1</a></cite>])
for that namespace name.</span><sup><a title="Link to assertion Location-0077 summary" href="#Location-0077-summary">†</a></sup> The second IRI of a pair MAY be absolute or relative.
+ <a name="Location-1700000"></a><span class="test-assertion">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</span><sup><a title="Link to assertion Location-1700000 summary" href="#Location-1700000-summary">†</a></sup>
</p>
</div>
***************
*** 8416,8421 ****
</p>
<p>
! For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
--- 8417,8422 ----
</p>
<p>
! <a name="FragId-1900000"></a><span class="test-assertion">For QNames, any prefix
! MUST be defined by a preceding xmlns pointer part.</span><sup><a title="Link to assertion FragId-1900000 summary" href="#FragId-1900000-summary">†</a></sup>
If a QName does not have a prefix then its namespace
name is the target namespace of the WSDL 2.0 document.
***************
*** 8434,8437 ****
--- 8435,8441 ----
identifiers are then used to construct the pointer part in
the last column.
+ <a name="FragId-1900001"></a><span class="test-assertion">The fragment identifier in a WSDL 2.0 component IRI-reference
+ MUST resolve to some component as defined by the construction rules
+ in <a href="#frag-ids-table">Table A-1</a>.</span><sup><a title="Link to assertion FragId-1900001 summary" href="#FragId-1900001-summary">†</a></sup>
</p>
***************
*** 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>
--- 9644,9648 ----
<div class="div1">
! <h2><a name="N174DE"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 10001,10005 ****
<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>
--- 10005,10009 ----
<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. 2.1, 4, 5, 6, 7, 8 and Appendix A.</td>
</tr>
***************
*** 12310,12318 ****
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, each WSDL 2.0 document making references
! to components in a given (foreign) namespace MUST
! have a <code>wsdl:import</code> <em>element information item</em> for that namespace (but not necessarily
! providing a <code>location</code> <em>attribute information item</em> identifying the WSDL 2.0 document
! in which the referenced component is declared).</td>
</tr>
<tr>
--- 12314,12322 ----
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
! <td rowspan="1" colspan="1">As with XML schema, any WSDL 2.0 document that references
! a foreign component MUST
! have a <code>wsdl:import</code> <em>element information item</em> for the associated foreign namespace (but which does not necessarily
! provide a <code>location</code> <em>attribute information item</em> that identifies the WSDL 2.0 document
! in which the referenced component is defined).</td>
</tr>
<tr>
***************
*** 12328,12335 ****
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! references a WSDL 2.0 document, then the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! in the referenced WSDL 2.0 document.</td>
</tr>
<tr>
--- 12332,12348 ----
</td>
<td rowspan="1" colspan="1">If the location attribute in the <code>import</code> <em>element information item</em>
! is dereferencible then it MUST reference a WSDL 2.0 document and the actual value of the
<code>namespace</code> <em>attribute information item</em> MUST be identical to the
actual value of the <code>targetNamespace</code> <em>attribute information item</em>
! of the referenced WSDL 2.0 document.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">
! <a href="#Import-1400001" name="Import-1400001-summary">Import-1400001</a>
! </td>
! <td rowspan="1" colspan="1">If a WSDL 2.0 document contains more than one <code>wsdl:import</code>
! <em>element information item</em> for a given value of the <code>namespace</code> <em>attribute information item</em> then
! they MUST provide different values for the <code>location</code>
! <em>attribute information item</em>.</td>
</tr>
<tr>
***************
*** 12344,12347 ****
--- 12357,12367 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Include-1400000" name="Include-1400000-summary">Include-1400000</a>
+ </td>
+ <td rowspan="1" colspan="1">The IRI indicated by <code>location</code>
+ MUST resolve to a WSDL 2.0 document.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#Interface-0031" name="Interface-0031-summary">Interface-0031</a>
</td>
***************
*** 12418,12421 ****
--- 12438,12448 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Location-1700000" name="Location-1700000-summary">Location-1700000</a>
+ </td>
+ <td rowspan="1" colspan="1">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
+ a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#MessageLabel-0004" name="MessageLabel-0004-summary">MessageLabel-0004</a>
</td>
***************
*** 12972,12975 ****
--- 12999,13010 ----
<tr>
<td rowspan="1" colspan="1">
+ <a href="#Extension-1600000" name="Extension-1600000-summary">Extension-1600000</a>
+ </td>
+ <td rowspan="1" colspan="1">The meaning of an
+ extension SHOULD be defined (directly or indirectly) in a document
+ that is available at its namespace IRI.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">
<a href="#FeatureRef-0046" name="FeatureRef-0046-summary">FeatureRef-0046</a>
</td>
Received on Monday, 27 February 2006 03:01:15 UTC