- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 03 May 2005 12:29:24 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv26982
Modified Files:
wsdl20-primer.xml
Log Message:
Added missing id on table
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -C2 -d -r1.79 -r1.80
*** wsdl20-primer.xml 3 May 2005 11:56:52 -0000 1.79
--- wsdl20-primer.xml 3 May 2005 12:29:22 -0000 1.80
***************
*** 6,9 ****
--- 6,10 ----
<!ENTITY document.status "Editors' copy $Date$">
<!ENTITY status SYSTEM "status-primer.xml">
+ <!ENTITY prevloc "http://www.w3.org/TR/2004/WD-wsdl20-primer-20041221">
]>
<spec w3c-doctype="wd" role="&document.role;">
***************
*** 20,28 ****
<loc href="&w3c-designation-part0;">&w3c-designation-part0;</loc>
</publoc>
- <!--
<prevlocs>
! <loc href=""></loc>
</prevlocs>
- -->
<latestloc>
<loc href="&part0.latest;">&part0.latest;</loc>
--- 21,27 ----
<loc href="&w3c-designation-part0;">&w3c-designation-part0;</loc>
</publoc>
<prevlocs>
! <loc href="&prevloc;">&prevloc;</loc>
</prevlocs>
<latestloc>
<loc href="&part0.latest;">&part0.latest;</loc>
***************
*** 77,81 ****
</langusage>
<revisiondesc>
! <p>Last Modified: $Date$</p>
</revisiondesc>
</header>
--- 76,80 ----
</langusage>
<revisiondesc>
! <p>Last Modif"Editors' copy $Date$</p>
</revisiondesc>
</header>
***************
*** 298,302 ****
</code></label><def><p>The <code>name</code> attribute defines a name for this fault. The name is required so that when an operation is defined, it can reference the desired fault by name. Fault names must be unique within an interface.</p></def></gitem><gitem><label><code>element = "ghns:invalidDataError"/></code></label><def><p>The <code>element</code> attribute specifies the schema type of the fault message, as previously defined in the <code>types</code> section. </p></def></gitem><gitem><label><code><operation name="opCheckAvailability"</code></label><def><p>The <code>name</code> attribute defines a name for this operation, so that it can be referenced later when bindings are defined. Operation names must also be unique within an interface. (WSDL 2.0 uses separate symbol spaces for operation and fault names, so operation name "foo" is distinct from fault name "foo".)</p></def></gitem>
! <gitem><label><code>pattern="http://www.w3.org/2005/05/wsdl/in-out" </code></label><def><p>This line specifies that this operation will use the <xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</xspecref> pattern as described above. WSDL 2.0 uses URIs to identify message exchange patterns in order to ensure that the identifiers are globally unambiguous, while also permitting future new patterns to be defined by anyone. (However, just because someone defines a new pattern and creates a URI to identify it, that does <emph>not</emph> mean that other WSDL processors will automatically recognize or understand that pattern. As with any other extension, it can be used among processors that <i>do</i> recognize and understand it.)</p></def></gitem>
<gitem><label><code>style="http://www.w3.org/2005/05/wsdl/style/uri" </code></label><def><p>
--- 297,301 ----
</code></label><def><p>The <code>name</code> attribute defines a name for this fault. The name is required so that when an operation is defined, it can reference the desired fault by name. Fault names must be unique within an interface.</p></def></gitem><gitem><label><code>element = "ghns:invalidDataError"/></code></label><def><p>The <code>element</code> attribute specifies the schema type of the fault message, as previously defined in the <code>types</code> section. </p></def></gitem><gitem><label><code><operation name="opCheckAvailability"</code></label><def><p>The <code>name</code> attribute defines a name for this operation, so that it can be referenced later when bindings are defined. Operation names must also be unique within an interface. (WSDL 2.0 uses separate symbol spaces for operation and fault names, so operation name "foo" is distinct from fault name "foo".)</p></def></gitem>
! <gitem><label><code>pattern="http://www.w3.org/2005/05/wsdl/in-out" </code></label><def><p>This line specifies that this operation will use the <xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</xspecref> pattern as described above. WSDL 2.0 uses URIs to identify message exchange patterns in order to ensure that the identifiers are globally unambiguous, while also permitting future new patterns to be defined by anyone. (However, just because someone defines a new pattern and creates a URI to identify it, that does <emph>not</emph> mean that other WSDL processors will automatically recognize or understand that pattern. As with any other extension, it can be used among processors that <emph>do</emph> recognize and understand it.)</p></def></gitem>
<gitem><label><code>style="http://www.w3.org/2005/05/wsdl/style/uri" </code></label><def><p>
***************
*** 665,669 ****
</example>
</div2>
! <div2 id="more-types-import-include-summary"><head>Summary of Import and Include Mechanisms</head><p>The following table summarizes the similarities and differences between the <code>wsdl:</code> and <code>xs:</code> <code>include</code> and <code>import</code> mechanisms.<table border="1"><caption>Summary of Import and Include Mechanisms</caption><thead><tr><th>Mechanism</th><th>Imported/Included Document Type</th><th>Meaning</th><th>Transitive?</th></tr></thead><tbody><tr><td>wsdl:import</td><td>WSDL 2.0 document</td><td>Merge Interface, Binding and Service components from another WSDL 2.0 document that has a DIFFERENT targetNamespace. (Schema type and element declarations are NOT merged.)</td><td>No</td></tr><tr><td>wsdl:include</td><td>WSDL 2.0 document</td><td>Merge Interface, Binding and Service components from another WSDL 2.0 document that has the SAME targetNamespace. (Schema type and element declarations are NOT merged.)</td><td>Yes</td></tr><tr><td>xs::import</td><td>XML Schema document</td<td>Merge type and element declarations from another XML Schema document that has a DIFFERENT targetNamespace.</td><td>No</td></tr><tr><td>xs:import</td><td>XML Schema document</td><td>Merge type and element declarations from another XML Schema document that has the SAME targetNamespace.</td><td>Yes</td></tr></tbody></table></p>
<p>More advanced topics on importing schemas are discussed in <specref ref="adv-multiple-inline-schemas"/></p>
--- 664,673 ----
</example>
</div2>
! <div2
! id="more-types-import-include-summary"><head>Summary of Import and Include Mechanisms</head>
! <p>The following table summarizes the similarities and differences
! between the <code>wsdl:</code> and <code>xs:</code>
! <code>include</code> and <code>import</code> mechanisms.</p>
! <table border="1" id='imin'><caption>Summary of Import and Include Mechanisms</caption><thead><tr><th>Mechanism</th><th>Imported/Included Document Type</th><th>Meaning</th><th>Transitive?</th></tr></thead><tbody><tr><td>wsdl:import</td><td>WSDL 2.0 document</td><td>Merge Interface, Binding and Service components from another WSDL 2.0 document that has a DIFFERENT targetNamespace. (Schema type and element declarations are NOT merged.)</td><td>No</td></tr><tr><td>wsdl:include</td><td>WSDL 2.0 document</td><td>Merge Interface, Binding and Service components from another WSDL 2.0 document that has the SAME targetNamespace. (Schema type and element declarations are NOT merged.)</td><td>Yes</td></tr><tr><td>xs::import</td><td>XML Schema document</td><td>Merge type and element declarations from another XML Schema document that has a DIFFERENT targetNamespace.</td><td>No</td></tr><tr><td>xs:import</td><td>XML Schema document</td><td>Merge type and element declarations from another XML Schema document that has te SAME targetNamespace.</td><td>Yes</td></tr></tbody></table>
<p>More advanced topics on importing schemas are discussed in <specref ref="adv-multiple-inline-schemas"/></p>
Received on Tuesday, 3 May 2005 12:29:39 UTC