- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 11 Jan 2007 01:39:56 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv31224/wsdl20
Modified Files:
component-assertion-table.xml wsdl20.tex wsdl20.toc
wsdl20-z-ie.html wsdl20-z.html wsdl20.html wsdl20.xml
wsdl20-primer.html document-assertion-table.xml
Log Message:
[CR100], [CR101], [CR102], [CR103] Fixed.
Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.102
retrieving revision 1.103
diff -C 2 -d -r1.102 -r1.103
*** wsdl20-z-ie.html 11 Jan 2007 00:58:22 -0000 1.102
--- wsdl20-z-ie.html 11 Jan 2007 01:39:49 -0000 1.103
***************
*** 81,85 ****
<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="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
--- 81,85 ----
<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="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
***************
*** 106,110 ****
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
--- 106,110 ----
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
***************
*** 1481,1485 ****
in the initial document versus those that are defined in the
included documents or imported namespaces.
- <span class="test-assertion" id="Import-0001">
However, any WSDL 2.0 document that contains component
definitions that refer by QName to WSDL 2.0 components
--- 1481,1484 ----
***************
*** 1489,1498 ****
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).<sup><a title="Link to assertion Import-0001 summary" href="#Import-0001-summary">†</a></sup></span>
! <span class="test-assertion" id="QName-0002">
Furthermore, all QName references, whether to the same or
! to different namespaces MUST resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).<sup><a title="Link to assertion QName-0002 summary" href="#QName-0002-summary">†</a></sup></span>
</p>
--- 1488,1496 ----
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).
Furthermore, all QName references, whether to the same or
! to different namespaces must resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).
</p>
***************
*** 1546,1555 ****
<p>
! <span class="test-assertion" id="Import-0003">
! Imported components have different target namespace
! values from the
! WSDL 2.0 document that is importing them.<sup><a title="Link to assertion Import-0003 summary" href="#Import-0003-summary">†</a></sup></span>
! Thus importing is the mechanism to use components from one
! namespace in definition of components from another namespace.
</p>
--- 1544,1552 ----
<p>
! Components that belong to imported namespaces have
! different target namespace values than that of the
! importing WSDL 2.0 document. Thus importing is the
! mechanism to use components from one namespace in the
! definition of components from another namespace.
</p>
***************
*** 7570,7582 ****
<p>
! <span class="test-assertion" id="Types-1300000">Every QName reference MUST
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).<sup><a title="Link to assertion Types-1300000 summary" href="#Types-1300000-summary">†</a></sup></span>
! <span class="test-assertion" id="Types-1300001">When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document.<sup><a title="Link to assertion Types-1300001 summary" href="#Types-1300001-summary">†</a></sup></span> If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a <code>schemaLocation</code> attribute, so long as the
! inline schema has been resolved in the current component
! model.
</p>
</div>
--- 7567,7575 ----
<p>
! Every QName reference must
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).
! Note that when resolving
! QNames references for schema definitions, the namespace must
! be imported by the referring WSDL 2.0 document (see <b><a href="#Schema-0016">???</a></b>).
</p>
</div>
***************
*** 7588,7596 ****
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>Inlining an XML schema uses the existing top-level
! <code>xs:schema</code> <em>element information item</em> defined by XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]. Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types <em>element information item</em>.</p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
--- 7581,7597 ----
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>
! Inlining an XML schema uses the existing
! top-level
! <code>xs:schema</code>
! <em>element information item</em>
! defined by XML Schema
! [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
! Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types
! <em>element information item</em>.
! </p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
***************
*** 7599,7602 ****
--- 7600,7608 ----
<code>xs:import</code> are not automatically referenceable from the WSDL 2.0 document
that contains the inline schema.
+ If the namespace referenced in a QName is contained in an inline schema,
+ it MAY be imported without a
+ <code>schemaLocation</code>
+ attribute, so long as the inline schema has been resolved in the
+ current component model.
</p>
***************
*** 11109,11113 ****
<div class="div1">
! <h2><a name="N163CD"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 11115,11119 ----
<div class="div1">
! <h2><a name="N163B2"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 11473,11499 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
- </td>
- <td rowspan="1" colspan="1">
- However, any WSDL 2.0 document that contains component
- definitions that refer by QName to WSDL 2.0 components
- that belong to a different namespace MUST contain a
- <code>wsdl:import</code>
- <em>element information item</em>
- for that namespace (see
- <a href="#imports"><b>4.2 Importing Descriptions</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Import-0003" name="Import-0003-summary">Import-0003</a>
- </td>
- <td rowspan="1" colspan="1">
- Imported components have different target namespace
- values from the
- WSDL 2.0 document that is importing them.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
--- 11479,11482 ----
***************
*** 11877,11895 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Types-1300000" name="Types-1300000-summary">Types-1300000</a>
- </td>
- <td rowspan="1" colspan="1">Every QName reference MUST
- resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Types-1300001" name="Types-1300001-summary">Types-1300001</a>
- </td>
- <td rowspan="1" colspan="1">When resolving
- QNames references for schema definitions, the namespace MUST
- be imported by the referring WSDL 2.0 document.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Types-1300005" name="Types-1300005-summary">Types-1300005</a>
</td>
--- 11860,11863 ----
***************
*** 12498,12511 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#QName-0002" name="QName-0002-summary">QName-0002</a>
- </td>
- <td rowspan="1" colspan="1">
- Furthermore, all QName references, whether to the same or
- to different namespaces MUST resolve to components (see
- <a href="#qnameres"><b>2.17 QName resolution</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Service-0063" name="Service-0063-summary">Service-0063</a>
</td>
--- 12466,12469 ----
***************
*** 12562,12566 ****
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR098">
CR099
</a>
--- 12520,12579 ----
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103">
! CR103
! </a>
! : Removed assertion markup for Types-1300001 since is a
! duplicate of Schema-0016.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102">
! CR102
! </a>
! : Removed assertion markup for Import-0003 since is a
! duplicate of Import-0071.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101">
! CR101
! </a>
! : Removed assertion markup for QName-0002 and Types-1300000
! since they are duplicates of QName-resolution-121900.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100">
! CR100
! </a>
! : Removed assertion markup for Import-0001 "However, any
! WSDL 2.0 document that contains component definitions that
! refer by QName to WSDL 2.0 components that belong to a
! different namespace MUST contain a
! <code>wsdl:import</code>
! <em>element information item</em>
! for that namespace." (see
! <a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! ). Import-0001 is a duplicate of Import-0070.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR099">
CR099
</a>
***************
*** 12570,12574 ****
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details). " Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
--- 12583,12587 ----
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details)." Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.134
retrieving revision 1.135
diff -C 2 -d -r1.134 -r1.135
*** wsdl20.tex 11 Jan 2007 00:58:22 -0000 1.134
--- wsdl20.tex 11 Jan 2007 01:39:49 -0000 1.135
***************
*** 1867,1871 ****
in the initial document versus those that are defined in the
included documents or imported namespaces.
-
However, any WSDL 2.0 document that contains component
definitions that refer by QName to WSDL 2.0 components
--- 1867,1870 ----
***************
*** 1876,1882 ****
\hyperlink{imports}{\textbf{\ref*{imports} Importing Descriptions}}
).
-
Furthermore, all QName references, whether to the same or
! to different namespaces MUST resolve to components (see
\hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}
).
--- 1875,1880 ----
\hyperlink{imports}{\textbf{\ref*{imports} Importing Descriptions}}
).
Furthermore, all QName references, whether to the same or
! to different namespaces must resolve to components (see
\hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}
).
***************
*** 1933,1942 ****
!
! Imported components have different target namespace
! values from the
! WSDL 2.0 document that is importing them.
! Thus importing is the mechanism to use components from one
! namespace in definition of components from another namespace.
--- 1931,1939 ----
! Components that belong to imported namespaces have
! different target namespace values than that of the
! importing WSDL 2.0 document. Thus importing is the
! mechanism to use components from one namespace in the
! definition of components from another namespace.
***************
*** 8597,8609 ****
! Every QName reference MUST
resolve (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document. If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a \texttt{schemaLocation} attribute, so long as the
! inline schema has been resolved in the current component
! model.
--- 8594,8602 ----
! Every QName reference must
resolve (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! Note that when resolving
! QNames references for schema definitions, the namespace must
! be imported by the referring WSDL 2.0 document (see \hyperlink{Schema-0016}{\textbf{\ref*{Schema-0016} ???}}).
***************
*** 8616,8624 ****
! Inlining an XML schema uses the existing top-level
! \texttt{xs:schema} \textit{element information item} defined by XML Schema \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}. Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types \textit{element information item}.
! The schema components defined and declared in the inlined schema
document are referenceable by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Only components defined and declared in
the schema itself and components included by it via xs:include are
--- 8609,8625 ----
!
! Inlining an XML schema uses the existing
! top-level
! \texttt{xs:schema}
! \textit{element information item}
! defined by XML Schema
! \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}.
! Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types
! \textit{element information item}.
!
! The schema components defined and declared in the inlined schema
document are referenceable by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Only components defined and declared in
the schema itself and components included by it via xs:include are
***************
*** 8627,8630 ****
--- 8628,8636 ----
\texttt{xs:import} are not automatically referenceable from the WSDL 2.0 document
that contains the inline schema.
+ If the namespace referenced in a QName is contained in an inline schema,
+ it MAY be imported without a
+ \texttt{schemaLocation}
+ attribute, so long as the inline schema has been resolved in the
+ current component model.
***************
*** 13070,13096 ****
&
-
- However, any WSDL 2.0 document that contains component
- definitions that refer by QName to WSDL 2.0 components
- that belong to a different namespace MUST contain a
- \texttt{wsdl:import}
- \textit{element information item}
- for that namespace (see
- \hyperlink{imports}{\textbf{\ref*{imports} Importing Descriptions}}
- ).
- \\ \hline
-
-
-
- &
-
- Imported components have different target namespace
- values from the
- WSDL 2.0 document that is importing them.
- \\ \hline
-
-
-
- &
As with XML schema, any WSDL 2.0 document that references
a foreign component MUST
--- 13076,13079 ----
***************
*** 13474,13492 ****
&
- Every QName reference MUST
- resolve (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
- \\ \hline
-
-
-
- &
- When resolving
- QNames references for schema definitions, the namespace MUST
- be imported by the referring WSDL 2.0 document.
- \\ \hline
-
-
-
- &
The type of the
\texttt{wsdlx:interface}
--- 13457,13460 ----
***************
*** 14100,14113 ****
&
- Furthermore, all QName references, whether to the same or
- to different namespaces MUST resolve to components (see
- \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}
- ).
- \\ \hline
-
-
-
- &
-
For each
Service
--- 14068,14071 ----
***************
*** 14159,14163 ****
AGR&
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR098}{
CR099
}
--- 14117,14176 ----
AGR&
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103}{
! CR103
! }
! : Removed assertion markup for Types-1300001 since is a
! duplicate of Schema-0016.
!
! \\ \hline
!
!
! 20070110&
! AGR&
!
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102}{
! CR102
! }
! : Removed assertion markup for Import-0003 since is a
! duplicate of Import-0071.
!
! \\ \hline
!
!
! 20070110&
! AGR&
!
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101}{
! CR101
! }
! : Removed assertion markup for QName-0002 and Types-1300000
! since they are duplicates of QName-resolution-121900.
!
! \\ \hline
!
!
! 20070110&
! AGR&
!
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100}{
! CR100
! }
! : Removed assertion markup for Import-0001 "However, any
! WSDL 2.0 document that contains component definitions that
! refer by QName to WSDL 2.0 components that belong to a
! different namespace MUST contain a
! \texttt{wsdl:import}
! \textit{element information item}
! for that namespace." (see
! \hyperlink{Description_details}{\textbf{\ref*{Description_details} The Description Component}}
! ). Import-0001 is a duplicate of Import-0070.
!
! \\ \hline
!
!
! 20070110&
! AGR&
!
! \href{http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR099}{
CR099
}
***************
*** 14167,14171 ****
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details). " Replaced this by a better statement (see
\hyperlink{inlining-xsd}{\textbf{\ref*{inlining-xsd} Inlining XML Schema}}
).
--- 14180,14184 ----
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details)." Replaced this by a better statement (see
\hyperlink{inlining-xsd}{\textbf{\ref*{inlining-xsd} Inlining XML Schema}}
).
Index: wsdl20.toc
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.toc,v
retrieving revision 1.34
retrieving revision 1.35
diff -C 2 -d -r1.34 -r1.35
*** wsdl20.toc 21 Dec 2006 15:22:20 -0000 1.34
--- wsdl20.toc 11 Jan 2007 01:39:49 -0000 1.35
***************
*** 116,120 ****
\contentsline {section}{\numberline {3.3}Describing Messages that Refer to Services and Endpoints}{111}{section.3.3}
\contentsline {subsection}{\numberline {3.3.1} \texttt {wsdlx:interface} \textit {attribute information item} }{111}{subsection.3.3.1}
! \contentsline {subsection}{\numberline {3.3.2} \texttt {wsdlx:binding} \textit {attribute information item} }{111}{subsection.3.3.2}
\contentsline {subsection}{\numberline {3.3.3}\texttt {wsdlx:interface} and \texttt {wsdlx:binding} Consistency}{112}{subsection.3.3.3}
\contentsline {subsection}{\numberline {3.3.4}Use of \texttt {wsdlx:interface} and \texttt {wsdlx:binding} with \texttt {xs:anyURI}}{112}{subsection.3.3.4}
--- 116,120 ----
\contentsline {section}{\numberline {3.3}Describing Messages that Refer to Services and Endpoints}{111}{section.3.3}
\contentsline {subsection}{\numberline {3.3.1} \texttt {wsdlx:interface} \textit {attribute information item} }{111}{subsection.3.3.1}
! \contentsline {subsection}{\numberline {3.3.2} \texttt {wsdlx:binding} \textit {attribute information item} }{112}{subsection.3.3.2}
\contentsline {subsection}{\numberline {3.3.3}\texttt {wsdlx:interface} and \texttt {wsdlx:binding} Consistency}{112}{subsection.3.3.3}
\contentsline {subsection}{\numberline {3.3.4}Use of \texttt {wsdlx:interface} and \texttt {wsdlx:binding} with \texttt {xs:anyURI}}{112}{subsection.3.3.4}
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.419
retrieving revision 1.420
diff -C 2 -d -r1.419 -r1.420
*** wsdl20.xml 11 Jan 2007 01:05:59 -0000 1.419
--- wsdl20.xml 11 Jan 2007 01:39:53 -0000 1.420
***************
*** 1846,1854 ****
<specref ref="imports" />
).
- <assert class="component" id="QName-0002">
Furthermore, all QName references, whether to the same or
! to different namespaces MUST resolve to components (see
<specref ref="qnameres" />
! ).</assert>
</p>
--- 1846,1853 ----
<specref ref="imports" />
).
Furthermore, all QName references, whether to the same or
! to different namespaces must resolve to components (see
<specref ref="qnameres" />
! ).
</p>
***************
*** 1903,1912 ****
<p>
! <assert class="document" id="Import-0003">
! Imported components have different target namespace
! values from the
! WSDL 2.0 document that is importing them.</assert>
! Thus importing is the mechanism to use components from one
! namespace in definition of components from another namespace.
</p>
--- 1902,1910 ----
<p>
! Components that belong to imported namespaces have
! different target namespace values than that of the
! importing WSDL 2.0 document. Thus importing is the
! mechanism to use components from one namespace in the
! definition of components from another namespace.
</p>
***************
*** 8418,8430 ****
<p>
! <assert class="document" id="Types-1300000">Every QName reference MUST
! resolve (see <specref ref="qnameres"/>).</assert>
! <assert class="document" id="Types-1300001">When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document.</assert> If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a <att>schemaLocation</att> attribute, so long as the
! inline schema has been resolved in the current component
! model.
</p>
</div4>
--- 8416,8424 ----
<p>
! Every QName reference must
! resolve (see <specref ref="qnameres"/>).
! Note that when resolving
! QNames references for schema definitions, the namespace must
! be imported by the referring WSDL 2.0 document (see <specref ref="Schema-0016"/>).
</p>
</div4>
***************
*** 8435,8444 ****
<head>Inlining XML Schema</head>
! <p>Inlining an XML schema uses the existing top-level
! <el>xs:schema</el> &EII; defined by XML Schema <bibref
! ref='XMLSchemaP1'/>. Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types &EII;.</p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <specref
ref='qnameres'/>). Only components defined and declared in
--- 8429,8445 ----
<head>Inlining XML Schema</head>
! <p>
! Inlining an XML schema uses the existing
! top-level
! <el>xs:schema</el>
! &EII;
! defined by XML Schema
! <bibref ref='XMLSchemaP1' />.
! Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types
! &EII;.
! </p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <specref
ref='qnameres'/>). Only components defined and declared in
***************
*** 8448,8451 ****
--- 8449,8457 ----
<el>xs:import</el> are not automatically referenceable from the WSDL 2.0 document
that contains the inline schema.
+ If the namespace referenced in a QName is contained in an inline schema,
+ it MAY be imported without a
+ <att>schemaLocation</att>
+ attribute, so long as the inline schema has been resolved in the
+ current component model.
</p>
***************
*** 12400,12403 ****
--- 12406,12448 ----
<td>
<loc
+ href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103">
+ CR103
+ </loc>
+ : Removed assertion markup for Types-1300001 since is a
+ duplicate of Schema-0016.
+ </td>
+ </tr>
+
+ <tr>
+ <td>20070110</td>
+ <td>AGR</td>
+ <td>
+ <loc
+ href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102">
+ CR102
+ </loc>
+ : Removed assertion markup for Import-0003 since is a
+ duplicate of Import-0071.
+ </td>
+ </tr>
+
+ <tr>
+ <td>20070110</td>
+ <td>AGR</td>
+ <td>
+ <loc
+ href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101">
+ CR101
+ </loc>
+ : Removed assertion markup for QName-0002 and Types-1300000
+ since they are duplicates of QName-resolution-121900.
+ </td>
+ </tr>
+
+ <tr>
+ <td>20070110</td>
+ <td>AGR</td>
+ <td>
+ <loc
href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100">
CR100
Index: document-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/document-assertion-table.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -C 2 -d -r1.19 -r1.20
*** document-assertion-table.xml 11 Jan 2007 00:58:26 -0000 1.19
--- document-assertion-table.xml 11 Jan 2007 01:39:53 -0000 1.20
***************
*** 31,57 ****
<tr>
<td>
- <assert-summary ref="Import-0001"/>
- </td>
- <td>
- However, any WSDL 2.0 document that contains component
- definitions that refer by QName to WSDL 2.0 components
- that belong to a different namespace MUST contain a
- <el>wsdl:import</el>
- <emph>element information item</emph>
- for that namespace (see
- <specref ref="imports"/>
- ).</td>
- </tr>
- <tr>
- <td>
- <assert-summary ref="Import-0003"/>
- </td>
- <td>
- Imported components have different target namespace
- values from the
- WSDL 2.0 document that is importing them.</td>
- </tr>
- <tr>
- <td>
<assert-summary ref="Import-0070"/>
</td>
--- 31,34 ----
***************
*** 435,453 ****
<tr>
<td>
- <assert-summary ref="Types-1300000"/>
- </td>
- <td>Every QName reference MUST
- resolve (see <specref ref="qnameres"/>).</td>
- </tr>
- <tr>
- <td>
- <assert-summary ref="Types-1300001"/>
- </td>
- <td>When resolving
- QNames references for schema definitions, the namespace MUST
- be imported by the referring WSDL 2.0 document.</td>
- </tr>
- <tr>
- <td>
<assert-summary ref="Types-1300005"/>
</td>
--- 412,415 ----
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.128
retrieving revision 1.129
diff -C 2 -d -r1.128 -r1.129
*** wsdl20-z.html 11 Jan 2007 00:58:22 -0000 1.128
--- wsdl20-z.html 11 Jan 2007 01:39:49 -0000 1.129
***************
*** 81,85 ****
<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="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
--- 81,85 ----
<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="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
***************
*** 106,110 ****
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
--- 106,110 ----
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
***************
*** 1479,1483 ****
in the initial document versus those that are defined in the
included documents or imported namespaces.
- <span class="test-assertion" id="Import-0001">
However, any WSDL 2.0 document that contains component
definitions that refer by QName to WSDL 2.0 components
--- 1479,1482 ----
***************
*** 1487,1496 ****
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).<sup><a title="Link to assertion Import-0001 summary" href="#Import-0001-summary">†</a></sup></span>
! <span class="test-assertion" id="QName-0002">
Furthermore, all QName references, whether to the same or
! to different namespaces MUST resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).<sup><a title="Link to assertion QName-0002 summary" href="#QName-0002-summary">†</a></sup></span>
</p>
--- 1486,1494 ----
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).
Furthermore, all QName references, whether to the same or
! to different namespaces must resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).
</p>
***************
*** 1544,1553 ****
<p>
! <span class="test-assertion" id="Import-0003">
! Imported components have different target namespace
! values from the
! WSDL 2.0 document that is importing them.<sup><a title="Link to assertion Import-0003 summary" href="#Import-0003-summary">†</a></sup></span>
! Thus importing is the mechanism to use components from one
! namespace in definition of components from another namespace.
</p>
--- 1542,1550 ----
<p>
! Components that belong to imported namespaces have
! different target namespace values than that of the
! importing WSDL 2.0 document. Thus importing is the
! mechanism to use components from one namespace in the
! definition of components from another namespace.
</p>
***************
*** 7544,7556 ****
<p>
! <span class="test-assertion" id="Types-1300000">Every QName reference MUST
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).<sup><a title="Link to assertion Types-1300000 summary" href="#Types-1300000-summary">†</a></sup></span>
! <span class="test-assertion" id="Types-1300001">When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document.<sup><a title="Link to assertion Types-1300001 summary" href="#Types-1300001-summary">†</a></sup></span> If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a <code>schemaLocation</code> attribute, so long as the
! inline schema has been resolved in the current component
! model.
</p>
</div>
--- 7541,7549 ----
<p>
! Every QName reference must
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).
! Note that when resolving
! QNames references for schema definitions, the namespace must
! be imported by the referring WSDL 2.0 document (see <b><a href="#Schema-0016">???</a></b>).
</p>
</div>
***************
*** 7562,7570 ****
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>Inlining an XML schema uses the existing top-level
! <code>xs:schema</code> <em>element information item</em> defined by XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]. Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types <em>element information item</em>.</p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
--- 7555,7571 ----
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>
! Inlining an XML schema uses the existing
! top-level
! <code>xs:schema</code>
! <em>element information item</em>
! defined by XML Schema
! [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
! Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types
! <em>element information item</em>.
! </p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
***************
*** 7573,7576 ****
--- 7574,7582 ----
<code>xs:import</code> are not automatically referenceable from the WSDL 2.0 document
that contains the inline schema.
+ If the namespace referenced in a QName is contained in an inline schema,
+ it MAY be imported without a
+ <code>schemaLocation</code>
+ attribute, so long as the inline schema has been resolved in the
+ current component model.
</p>
***************
*** 11083,11087 ****
<div class="div1">
! <h2><a name="N163CD"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 11089,11093 ----
<div class="div1">
! <h2><a name="N163B2"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 11447,11473 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
- </td>
- <td rowspan="1" colspan="1">
- However, any WSDL 2.0 document that contains component
- definitions that refer by QName to WSDL 2.0 components
- that belong to a different namespace MUST contain a
- <code>wsdl:import</code>
- <em>element information item</em>
- for that namespace (see
- <a href="#imports"><b>4.2 Importing Descriptions</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Import-0003" name="Import-0003-summary">Import-0003</a>
- </td>
- <td rowspan="1" colspan="1">
- Imported components have different target namespace
- values from the
- WSDL 2.0 document that is importing them.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
--- 11453,11456 ----
***************
*** 11851,11869 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Types-1300000" name="Types-1300000-summary">Types-1300000</a>
- </td>
- <td rowspan="1" colspan="1">Every QName reference MUST
- resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Types-1300001" name="Types-1300001-summary">Types-1300001</a>
- </td>
- <td rowspan="1" colspan="1">When resolving
- QNames references for schema definitions, the namespace MUST
- be imported by the referring WSDL 2.0 document.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Types-1300005" name="Types-1300005-summary">Types-1300005</a>
</td>
--- 11834,11837 ----
***************
*** 12472,12485 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#QName-0002" name="QName-0002-summary">QName-0002</a>
- </td>
- <td rowspan="1" colspan="1">
- Furthermore, all QName references, whether to the same or
- to different namespaces MUST resolve to components (see
- <a href="#qnameres"><b>2.17 QName resolution</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Service-0063" name="Service-0063-summary">Service-0063</a>
</td>
--- 12440,12443 ----
***************
*** 12536,12540 ****
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR098">
CR099
</a>
--- 12494,12553 ----
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103">
! CR103
! </a>
! : Removed assertion markup for Types-1300001 since is a
! duplicate of Schema-0016.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102">
! CR102
! </a>
! : Removed assertion markup for Import-0003 since is a
! duplicate of Import-0071.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101">
! CR101
! </a>
! : Removed assertion markup for QName-0002 and Types-1300000
! since they are duplicates of QName-resolution-121900.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100">
! CR100
! </a>
! : Removed assertion markup for Import-0001 "However, any
! WSDL 2.0 document that contains component definitions that
! refer by QName to WSDL 2.0 components that belong to a
! different namespace MUST contain a
! <code>wsdl:import</code>
! <em>element information item</em>
! for that namespace." (see
! <a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! ). Import-0001 is a duplicate of Import-0070.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR099">
CR099
</a>
***************
*** 12544,12548 ****
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details). " Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
--- 12557,12561 ----
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details)." Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
Index: component-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/component-assertion-table.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -C 2 -d -r1.17 -r1.18
*** component-assertion-table.xml 21 Dec 2006 14:47:28 -0000 1.17
--- component-assertion-table.xml 11 Jan 2007 01:39:49 -0000 1.18
***************
*** 583,596 ****
<tr>
<td>
- <assert-summary ref="QName-0002"/>
- </td>
- <td>
- Furthermore, all QName references, whether to the same or
- to different namespaces MUST resolve to components (see
- <specref ref="qnameres"/>
- ).</td>
- </tr>
- <tr>
- <td>
<assert-summary ref="Service-0063"/>
</td>
--- 583,586 ----
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.301
retrieving revision 1.302
diff -C 2 -d -r1.301 -r1.302
*** wsdl20.html 11 Jan 2007 00:58:23 -0000 1.301
--- wsdl20.html 11 Jan 2007 01:39:51 -0000 1.302
***************
*** 81,85 ****
<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="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
--- 81,85 ----
<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="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change og</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
***************
*** 106,110 ****
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163CD">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
--- 106,110 ----
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> 4.3 <a href="#extenions-and-modules">Extensions</a><br>5. <a href="#eii-documentation">Documentation</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-Normtive)</a><br>10. <a href="#References">References</a><br> 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.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="#component-designator-canonical-form">Canonical Form for WSDL 2.0 Component Designators</a><br> C.3 <a href="#Iri-ref-ex">Example</a><br>D. <a href="#N163B2">Component Summary</a> (Non-Normative)<br>E. <a href="#assertionsummary">Assertion Summary</a> (Non-Normative)<br>F. <a href="#changelog">Part 1 Change Log</a> (Non-Normative)<br> F.1 <a href="#wsdl-changelog">WSDL 2.0 Specification Changes</a><br></p>/div><hr><div class="body">
<div class="div1">
***************
*** 780,784 ****
in the initial document versus those that are defined in the
included documents or imported namespaces.
- <span class="test-assertion" id="Import-0001">
However, any WSDL 2.0 document that contains component
definitions that refer by QName to WSDL 2.0 components
--- 780,783 ----
***************
*** 788,797 ****
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).<sup><a title="Link to assertion Import-0001 summary" href="#Import-0001-summary">†</a></sup></span>
! <span class="test-assertion" id="QName-0002">
Furthermore, all QName references, whether to the same or
! to different namespaces MUST resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).<sup><a title="Link to assertion QName-0002 summary" href="#QName-0002-summary">†</a></sup></span>
</p>
--- 787,795 ----
for that namespace (see
<a href="#imports"><b>4.2 Importing Descriptions</b></a>
! ).
Furthermore, all QName references, whether to the same or
! to different namespaces must resolve to components (see
<a href="#qnameres"><b>2.17 QName resolution</b></a>
! ).
</p>
***************
*** 845,854 ****
<p>
! <span class="test-assertion" id="Import-0003">
! Imported components have different target namespace
! values from the
! WSDL 2.0 document that is importing them.<sup><a title="Link to assertion Import-0003 summary" href="#Import-0003-summary">†</a></sup></span>
! Thus importing is the mechanism to use components from one
! namespace in definition of components from another namespace.
</p>
--- 843,851 ----
<p>
! Components that belong to imported namespaces have
! different target namespace values than that of the
! importing WSDL 2.0 document. Thus importing is the
! mechanism to use components from one namespace in the
! definition of components from another namespace.
</p>
***************
*** 5414,5426 ****
<p>
! <span class="test-assertion" id="Types-1300000">Every QName reference MUST
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).<sup><a title="Link to assertion Types-1300000 summary" href="#Types-1300000-summary">†</a></sup></span>
! <span class="test-assertion" id="Types-1300001">When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document.<sup><a title="Link to assertion Types-1300001 summary" href="#Types-1300001-summary">†</a></sup></span> If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a <code>schemaLocation</code> attribute, so long as the
! inline schema has been resolved in the current component
! model.
</p>
</div>
--- 5411,5419 ----
<p>
! Every QName reference must
! resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).
! Note that when resolving
! QNames references for schema definitions, the namespace must
! be imported by the referring WSDL 2.0 document (see <b><a href="#Schema-0016">???</a></b>).
</p>
</div>
***************
*** 5432,5440 ****
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>Inlining an XML schema uses the existing top-level
! <code>xs:schema</code> <em>element information item</em> defined by XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>]. Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types <em>element information item</em>.</p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
--- 5425,5441 ----
<h4><a name="inlining-xsd"></a>3.1.2 Inlining XML Schema</h4>
! <p>
! Inlining an XML schema uses the existing
! top-level
! <code>xs:schema</code>
! <em>element information item</em>
! defined by XML Schema
! [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
! Conceptually, it may be viewed as simply cutting and pasting
! an existing schema document to a location inside the types
! <em>element information item</em>.
! </p>
! <p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href="#qnameres"><b>2.17 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
***************
*** 5443,5446 ****
--- 5444,5452 ----
<code>xs:import</code> are not automatically referenceable from the WSDL 2.0 document
that contains the inline schema.
+ If the namespace referenced in a QName is contained in an inline schema,
+ it MAY be imported without a
+ <code>schemaLocation</code>
+ attribute, so long as the inline schema has been resolved in the
+ current component model.
</p>
***************
*** 8215,8219 ****
<div class="div1">
! <h2><a name="N163CD"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
--- 8221,8225 ----
<div class="div1">
! <h2><a name="N163B2"></a>D. Component Summary (Non-Normative)</h2>
<p>
<a href="#component-summary">Table D-1</a>
***************
*** 8579,8605 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Import-0001" name="Import-0001-summary">Import-0001</a>
- </td>
- <td rowspan="1" colspan="1">
- However, any WSDL 2.0 document that contains component
- definitions that refer by QName to WSDL 2.0 components
- that belong to a different namespace MUST contain a
- <code>wsdl:import</code>
- <em>element information item</em>
- for that namespace (see
- <a href="#imports"><b>4.2 Importing Descriptions</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Import-0003" name="Import-0003-summary">Import-0003</a>
- </td>
- <td rowspan="1" colspan="1">
- Imported components have different target namespace
- values from the
- WSDL 2.0 document that is importing them.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Import-0070" name="Import-0070-summary">Import-0070</a>
</td>
--- 8585,8588 ----
***************
*** 8983,9001 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#Types-1300000" name="Types-1300000-summary">Types-1300000</a>
- </td>
- <td rowspan="1" colspan="1">Every QName reference MUST
- resolve (see <a href="#qnameres"><b>2.17 QName resolution</b></a>).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <a href="#Types-1300001" name="Types-1300001-summary">Types-1300001</a>
- </td>
- <td rowspan="1" colspan="1">When resolving
- QNames references for schema definitions, the namespace MUST
- be imported by the referring WSDL 2.0 document.</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Types-1300005" name="Types-1300005-summary">Types-1300005</a>
</td>
--- 8966,8969 ----
***************
*** 9604,9617 ****
<tr>
<td rowspan="1" colspan="1">
- <a href="#QName-0002" name="QName-0002-summary">QName-0002</a>
- </td>
- <td rowspan="1" colspan="1">
- Furthermore, all QName references, whether to the same or
- to different namespaces MUST resolve to components (see
- <a href="#qnameres"><b>2.17 QName resolution</b></a>
- ).</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
<a href="#Service-0063" name="Service-0063-summary">Service-0063</a>
</td>
--- 9572,9575 ----
***************
*** 9668,9672 ****
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR098">
CR099
</a>
--- 9626,9685 ----
<td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR103">
! CR103
! </a>
! : Removed assertion markup for Types-1300001 since is a
! duplicate of Schema-0016.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR102">
! CR102
! </a>
! : Removed assertion markup for Import-0003 since is a
! duplicate of Import-0071.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR101">
! CR101
! </a>
! : Removed assertion markup for QName-0002 and Types-1300000
! since they are duplicates of QName-resolution-121900.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR100">
! CR100
! </a>
! : Removed assertion markup for Import-0001 "However, any
! WSDL 2.0 document that contains component definitions that
! refer by QName to WSDL 2.0 components that belong to a
! different namespace MUST contain a
! <code>wsdl:import</code>
! <em>element information item</em>
! for that namespace." (see
! <a href="#Description_details"><b>2.1.1 The Description Component</b></a>
! ). Import-0001 is a duplicate of Import-0070.
! </td>
! </tr>
!
! <tr>
! <td rowspan="1" colspan="1">20070110</td>
! <td rowspan="1" colspan="1">AGR</td>
! <td rowspan="1" colspan="1">
! <a href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR099">
CR099
</a>
***************
*** 9676,9680 ****
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details). " Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
--- 9689,9693 ----
imported (using wsdl:import ) the WSDL 2.0 document that
inlines the schema (see 4.2 Importing Descriptions for more
! details)." Replaced this by a better statement (see
<a href="#inlining-xsd"><b>3.1.2 Inlining XML Schema</b></a>
).
Received on Thursday, 11 January 2007 01:40:17 UTC