- From: David Booth <dbooth@dev.w3.org>
- Date: Mon, 20 Dec 2004 16:58:30 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv27154
Modified Files:
wsdl20-primer.html
Log Message:
pubrules fixes
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** wsdl20-primer.html 20 Dec 2004 08:39:35 -0000 1.13
--- wsdl20-primer.html 20 Dec 2004 16:58:28 -0000 1.14
***************
*** 70,78 ****
<h1>Web Services Description Language (WSDL) Version 2.0 Part 0:
Primer</h1>
! <h2>W3C Working Draft 23 December 2004</h2>
<dl>
<dt>This version:</dt>
<dd><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-primer-20041223">http://www.w3.org/TR/2004/WD-wsdl20-primer-20041223</a></dd>
<dt>Latest version:</dt>
<dd><a href=
--- 70,78 ----
<h1>Web Services Description Language (WSDL) Version 2.0 Part 0:
Primer</h1>
! <h2>W3C Working Draft 21 December 2004</h2>
<dl>
<dt>This version:</dt>
<dd><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-primer-20041221">http://www.w3.org/TR/2004/WD-wsdl20-primer-20041221</a></dd>
<dt>Latest version:</dt>
<dd><a href=
***************
*** 349,353 ****
service, client, and the purpose and function of a Web service
description. (For an explanation of basic Web services concepts,
! see <em>Web Services Architecture</em> [<cite><a href="#wsarch">Web
Architecture</a></cite>] <a href=
"http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#whatis">Section
--- 349,353 ----
service, client, and the purpose and function of a Web service
description. (For an explanation of basic Web services concepts,
! see <em>Web Services Architecture</em> [<cite><a href="#wsarch">WS
Architecture</a></cite>] <a href=
"http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#whatis">Section
***************
*** 489,493 ****
at http://greath.example.com/2004/reservation-documentation.html
</documentation>
!
<types>
<xs:schema
--- 489,493 ----
at http://greath.example.com/2004/reservation-documentation.html
</documentation>
!
<types>
<xs:schema
***************
*** 546,550 ****
<endpoint name="reservationEndpoint"
binding="tns:reservationSOAPBinding"
! address ="http://greath.example.com/reservation"/>
</service>
--- 546,550 ----
<endpoint name="reservationEndpoint"
binding="tns:reservationSOAPBinding"
! address ="http://greath.example.com/2004/reservation"/>
</service>
***************
*** 594,602 ****
<description
xmlns="http://www.w3.org/2004/08/wsdl"
! target namespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
. . . >
- . . .
</description>
</pre></div>
--- 594,602 ----
<description
xmlns="http://www.w3.org/2004/08/wsdl"
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
. . . >
+ . . .
</description>
</pre></div>
***************
*** 638,643 ****
specified above as the value of the <code>targetNamespace</code>
attribute. This will allow us later to use the <code>tns:</code>
! prefix in <a href="@@xml-schema#qname@@">qnames</a>, to refer to
! the WSDL target namespace of the GreatH service.</p>
</dd>
</dl>
--- 638,646 ----
specified above as the value of the <code>targetNamespace</code>
attribute. This will allow us later to use the <code>tns:</code>
! prefix in qnames, to refer to the WSDL target namespace of the
! GreatH service. (For more on QNames see [<cite><a href="#XMLNS">XML
! Namespaces</a></cite>] section 3 <a href=
! "http://www.w3.org/TR/1999/REC-xml-names-19990114/#ns-qualnames">Qualified
! Names</a>.)</p>
</dd>
</dl>
***************
*** 695,699 ****
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
. . . >
!
<types>
<xs:schema
--- 698,704 ----
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
. . . >
!
! , , ,
!
<types>
<xs:schema
***************
*** 775,784 ****
operation also specifies a message exchange <em>pattern</em> that
indicates the sequence in which the associated messages are to be
! transmitted between the parties. For example, the <a href=
! "@@part2#in-out@@">in-out</a> pattern indicates that if the client
! sends a message <em>in</em> to the service, the service will either
! send a reply message back <em>out</em> to the client (in the normal
! case) or it will send a fault message back to the client (in the
! case of an error).</p>
<p>For the GreatH service, we will (initially) define an interface
containing a single operation, <code>opCheckAvailability</code>,
--- 780,792 ----
operation also specifies a message exchange <em>pattern</em> that
indicates the sequence in which the associated messages are to be
! transmitted between the parties. For example, the <em>in-out</em>
! pattern (see <em>WSDL 2.0 Predefined Extensions</em>
! [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined
! Extensions</a></cite>] section 2.2.3 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">In-Out</a>)
! indicates that if the client sends a message <em>in</em> to the
! service, the service will either send a reply message back
! <em>out</em> to the client (in the normal case) or it will send a
! fault message back to the client (in the case of an error).</p>
<p>For the GreatH service, we will (initially) define an interface
containing a single operation, <code>opCheckAvailability</code>,
***************
*** 786,797 ****
<code>checkAvailabilityResponse</code> message types that we
defined in the <code>types</code> section. We'll use the <a href=
! "@@part2#in-out@@">in-out</a> pattern for this operation, because
! this is the most natural way to represent a simple request-response
! interaction. We could have instead defined two separate operations
! using the <a href="@@part2#in-only@@">in-only</a> and <a href=
! "@@part2#out-only@@">out-only</a> patterns (for example), but that
! would just complicate matters for the client, because we would then
! have to separately indicate to the client developer that the two
! operations should be used together as a request-response pair.</p>
<p>In addition to the normal input and output messages, we also
need to specify the fault message that we wish to use in the event
--- 794,815 ----
<code>checkAvailabilityResponse</code> message types that we
defined in the <code>types</code> section. We'll use the <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</a>
! pattern for this operation, because this is the most natural way to
! represent a simple request-response interaction. We could have
! instead (for example) defined two separate operations using the
! <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-only</a>
! and <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#out-only">
! out-only</a> patterns (see <em>WSDL 2.0 Predefined Extensions</em>
! [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined
! Extensions</a></cite>] section 2.2.1 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-only">In-Only</a>
! and section 2.2.5 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#out-only">
! Out-Only</a>), but that would just complicate matters for the
! client, because we would then have to separately indicate to the
! client developer that the two operations should be used together as
! a request-response pair.</p>
<p>In addition to the normal input and output messages, we also
need to specify the fault message that we wish to use in the event
***************
*** 816,820 ****
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
. . . >
!
<types>
<xs:schema
--- 834,839 ----
xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
. . . >
!
! . . .
<types>
<xs:schema
***************
*** 825,829 ****
<xs:element name="checkAvailability" type="tCheckAvailability"/>
. . .
!
<xs:element name="checkAvailabilityResponse" type="xs:double"/>
--- 844,848 ----
<xs:element name="checkAvailability" type="tCheckAvailability"/>
. . .
!
<xs:element name="checkAvailabilityResponse" type="xs:double"/>
***************
*** 848,851 ****
--- 867,871 ----
</interface>
+
. . .
</description>
***************
*** 898,911 ****
<dd>
<p>This line specifies that this operation will use the <a href=
! "@@part2#in-out@@">in-out</a> pattern defined in <a href=
! "@@part2@@">WSDL 2.0 Part 2</a>. WSDL 2.0 uses URIs to identify
! message exchange patterns in order to ensure that they are
! uambiguously identified, 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
! <em>not</em> mean that other WSDL processors will automatically
! recognize or understand that pattern. As with any other extension,
! it can be used among processors that do recognize and understand
! it.)</p>
</dd>
<dt class="label"><code><input messageLabel="In"</code></dt>
--- 918,930 ----
<dd>
<p>This line specifies that this operation will use the <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</a>
! pattern as described above. WSDL 2.0 uses URIs to identify message
! exchange patterns in order to ensure that they are uambiguously
! identified, 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 <em>not</em> mean that
! other WSDL processors will automatically recognize or understand
! that pattern. As with any other extension, it can be used among
! processors that do recognize and understand it.)</p>
</dd>
<dt class="label"><code><input messageLabel="In"</code></dt>
***************
*** 918,930 ****
which potential input message in the pattern this particular input
message represents. This is the purpose of the
! <code>messageLabel</code> attribute. Since the WSDL 2.0 <a href=
! "@@part2#in-out@@">in-out</a> pattern that we've chosen to use only
! has one input message, it is a no-brainer in this case: we simply
! fill in the message label "In" that was defined in <a href=
! "@@Part2@@">WSDL 2.0 Part 2</a> for the <a href=
! "@@part2#in-out@@">in-out</a> pattern. However, in theory, new
! patterns could be defined that involve multiple input messages, and
! the different input messages in the pattern would be distinguished
! by having different labels.</p>
</dd>
<dt class="label"><code>element="ghns:checkAvailability"
--- 937,954 ----
which potential input message in the pattern this particular input
message represents. This is the purpose of the
! <code>messageLabel</code> attribute. Since the <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</a>
! pattern that we've chosen to use only has one input message, it is
! trivial in this case: we simply fill in the message label "In" that
! was defined in <em>WSDL 2.0 Predefined Extensions</em>
! [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined
! Extensions</a></cite>] section 2.2.3 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">In-Out</a>
! for the <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</a>
! pattern. However, in theory, new patterns could be defined that
! involve multiple input messages, and the different input messages
! in the pattern would be distinguished by having different
! labels.</p>
</dd>
<dt class="label"><code>element="ghns:checkAvailability"
***************
*** 954,961 ****
message that will either trigger this fault or that this fault will
replace, depending on the pattern. (Some patterns use a <a href=
! "@@part2#message-triggers-fault@@">message-triggers-fault rule</a>;
! others use a <a href=
! "@@part2#fault-replaces-message@@">fault-replaces-message</a>
! rule.)</p>
</dd>
</dl>
--- 978,991 ----
message that will either trigger this fault or that this fault will
replace, depending on the pattern. (Some patterns use a <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#fault-trigger">
! message-triggers-fault rule</a>; others use a <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#fault-replacement">
! fault-replaces-message</a> rule. See <em>WSDL 2.0 Predefined
! Extensions</em> [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined
! Extensions</a></cite>] section 2.1.2 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#fault-trigger">
! Message Triggers Fault</a> and section 2.1.1 <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#fault-replacement">
! Fault Replaces Message</a>.)</p>
</dd>
</dl>
***************
*** 1031,1037 ****
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12"
xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
!
<types>
! . . .
</types>
--- 1061,1068 ----
xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12"
xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
! . . .
!
<types>
! . . .
</types>
***************
*** 1060,1063 ****
--- 1091,1095 ----
</binding>
+
. . .
</description>
***************
*** 1147,1152 ****
specifies the SOAP message exchange pattern that will be used to
implement the abstract WSDL 2.0 message exchange pattern (<a href=
! "@@part2#in-out@@">in-out</a>) that was specified when the
! <code>opCheckAvailability</code> operation was defined.</p>
</dd>
<dt class="label"><code><fault
--- 1179,1185 ----
specifies the SOAP message exchange pattern that will be used to
implement the abstract WSDL 2.0 message exchange pattern (<a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</a>)
! that was specified when the <code>opCheckAvailability</code>
! operation was defined.</p>
</dd>
<dt class="label"><code><fault
***************
*** 1209,1214 ****
xmlns="http://www.w3.org/2004/08/wsdl"
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl" . . . >
!
<types>
. . .
--- 1242,1251 ----
xmlns="http://www.w3.org/2004/08/wsdl"
targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12"
! xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
! . . .
!
<types>
. . .
***************
*** 1216,1224 ****
<interface name = "reservationInterface" >
! . . .
</interface>
<binding name="reservationSOAPBinding"
! interface="tns:reservationInterface" . . . >
. . .
</binding>
--- 1253,1262 ----
<interface name = "reservationInterface" >
! . . .
</interface>
<binding name="reservationSOAPBinding"
! interface="tns:reservationInterface"
! . . . >
. . .
</binding>
***************
*** 1232,1237 ****
</service>
-
- </description>
</pre></div>
</div>
--- 1270,1273 ----
***************
*** 1318,1328 ****
at http://greath.example.com/2004/reservation-documentation.html
</documentation>
!
<types>
! . . .
</types>
! . . .
!
</description>
</pre></div>
--- 1354,1363 ----
at http://greath.example.com/2004/reservation-documentation.html
</documentation>
!
<types>
! . . .
</types>
! . . .
</description>
</pre></div>
***************
*** 1612,1620 ****
"#adv-import-and-authoring"><b>7.3 Import mechanism and authoring
style</b></a>. The schema components defined in the imported schema
! are available for reference by QName (see section @@@@ ). Note that
! only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL.
! Specifically, components that the schema imports via
! <code>xs:import</code> are NOT available to WSDL.</p>
<table border="1" summary="Editorial note: dbooth">
<tr>
--- 1647,1655 ----
"#adv-import-and-authoring"><b>7.3 Import mechanism and authoring
style</b></a>. The schema components defined in the imported schema
! are available for reference by QName. Note that only components
! defined in the schema itself and components included by it via
! <code>xs:include</code> are available to WSDL. Specifically,
! components that the schema imports via <code>xs:import</code> are
! NOT available to WSDL.</p>
<table border="1" summary="Editorial note: dbooth">
<tr>
***************
*** 1668,1672 ****
element.</p>
<p>The schema components defined in the embedded schema are
! available to WSDL for reference by QName (see @@@). Note that only
components defined in the schema itself and components included by
it via <code>xs:include</code> are available to WSDL. Specifically,
--- 1703,1707 ----
element.</p>
<p>The schema components defined in the embedded schema are
! available to WSDL for reference by QName (see @@@@). Note that only
components defined in the schema itself and components included by
it via <code>xs:include</code> are available to WSDL. Specifically,
***************
*** 1729,1768 ****
"example-schema-import"></a><i><span>Example 3-1.</span> Importing
Message Definitions into WSDL 2.0</i></p>
! <table border="1" summary="Editorial note">
! <tr>
! <td align="left" valign="top" width="50%"><b>Editorial
! note</b></td>
! <td align="right" valign="top" width="50%"> </td>
! </tr>
! <tr>
! <td colspan="2" align="left" valign="top">Need to update this
! example.</td>
! </tr>
! </table>
<div class="exampleInner">
<pre>
!
<description
! targetNamespace= "http://www.greath.com/2004/05/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
!
! <documentation>
! Description: The definition of the reservation Web service of GreatH hotel.
! Author: Joe Somebody
! Date: 05/17/2004
! </documentation>
! <<b>types</b>>
<documentation>
! Messages definitions of the reservation Web service of GreatH hotel.
</documentation>
! <xs:import namespace="http://www.greath.com/2004/05/schemas/resSvc.xsd"
! schemaLocation= "http://www.greath.com/2004/05/schemas/resSvc.xsd"/>
!
! </<b>types</b>>
</description>
</pre></div>
--- 1764,1791 ----
"example-schema-import"></a><i><span>Example 3-1.</span> Importing
Message Definitions into WSDL 2.0</i></p>
! <div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example
! 3-2.</span> Importing Message Definitions</i></p>
<div class="exampleInner">
<pre>
! <?xml version="1.0" encoding="utf-8" ?>
<description
! xmlns="http://www.w3.org/2004/08/wsdl"
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! . . . >
! . . .
! <types>
<documentation>
! Messages definitions of the reservation Web service of GreatH hotel.
</documentation>
! <xs:import namespace="http://greath.example.com/2004/schemas/resSvc.xsd"
! schemaLocation= "http://greath.example.com/2004/schemas/resSvc.xsd"/>
! </types>
+ . . .
</description>
</pre></div>
***************
*** 1771,1774 ****
--- 1794,1798 ----
</div>
</div>
+ </div>
<div class="div1">
<h2><a name="more-interfaces" id="more-interfaces"></a>4. More on
***************
*** 1950,1954 ****
uniquely. The optional <code>element</code> attribute can be used
to indicate the content or playload of the fault message. Its value
! should be the qname of the XML schema global element declaration
which defines the fault message. Please note when other type
systems are used to define a fault message, additional attributes
--- 1974,1978 ----
uniquely. The optional <code>element</code> attribute can be used
to indicate the content or playload of the fault message. Its value
! should be the QName of the XML schema global element declaration
which defines the fault message. Please note when other type
systems are used to define a fault message, additional attributes
***************
*** 1975,1981 ****
<description
! targetNamespace= "http://www.greath.com/2004/05/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
--- 1999,2005 ----
<description
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/2004/08/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
***************
*** 1988,1993 ****
<types>
! <xs:import namespace="http://www.greath.com/2004/05/schemas/resSvc.xsd"
! schemaLocation= "http://www.greath.com/2004/05/schemas/resSvc.xsd"/>
</types>
--- 2012,2017 ----
<types>
! <xs:import namespace="http://greath.example.com/2004/schemas/resSvc.xsd"
! schemaLocation= "http://greath.example.com/2004/schemas/resSvc.xsd"/>
</types>
***************
*** 2025,2029 ****
<tr>
<td colspan="2" align="left" valign="top">Need clarification -
! fault must be name uniquely across interfaces?</td>
</tr>
</table>
--- 2049,2053 ----
<tr>
<td colspan="2" align="left" valign="top">Need clarification -
! fault must be named uniquely across interfaces?</td>
</tr>
</table>
***************
*** 2166,2172 ****
<pre>
<description
! targetNamespace= "http://www.greath.com/2004/05/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
--- 2190,2196 ----
<pre>
<description
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/2004/08/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
***************
*** 2179,2184 ****
<types>
! <xs:import namespace="http://www.greath.com/2004/05/schemas/resSvc.xsd"
! schemaLocation= "http://www.greath.com/2004/05/schemas/resSvc.xsd"/>
</types>
--- 2203,2208 ----
<types>
! <xs:import namespace="http://greath.example.com/2004/schemas/resSvc.xsd"
! schemaLocation= "http://greath.example.com/2004/schemas/resSvc.xsd"/>
</types>
***************
*** 2429,2433 ****
corresponding interface.</p>
<p>The binding constructs can be grouped into two categories: those
! in the WSDL namespace of "http://www.w3.org/@@@@/@@/wsdl" and those
not in WSDL namespace. WSDL 2.0 part 1 defines a set of binding
constructs within the WSDL namespace that can be used to host
--- 2453,2457 ----
corresponding interface.</p>
<p>The binding constructs can be grouped into two categories: those
! in the WSDL namespace of "http://www.w3.org/2004/08/wsdl" and those
not in WSDL namespace. WSDL 2.0 part 1 defines a set of binding
constructs within the WSDL namespace that can be used to host
***************
*** 2566,2570 ****
<tr>
<td colspan="2" align="left" valign="top">Need clarification -
! wording about qname uniqueness in part 1 section 2.10.1 and 2.11.1
need to change. it's not correct to say "A particular operation of
an interface is uniquely identified by the WSDL target namespace of
--- 2590,2594 ----
<tr>
<td colspan="2" align="left" valign="top">Need clarification -
! wording about QName uniqueness in part 1 section 2.10.1 and 2.11.1
need to change. it's not correct to say "A particular operation of
an interface is uniquely identified by the WSDL target namespace of
***************
*** 2594,2600 ****
<description
! targetNamespace= "http://www.greath.com/2004/05/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
--- 2618,2624 ----
<description
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/2004/08/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
***************
*** 2614,2620 ****
<pre>
<description
! targetNamespace= "http://www.greath.com/2004/05/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
--- 2638,2644 ----
<pre>
<description
! targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"
! xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"
! xmlns = "http://www.w3.org/2004/08/wsdl"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
***************
*** 2710,2716 ****
(non-wsdl) XML namespaces to be interspersed into a WSDL document;
and <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20041223#Features">Features</a>
and <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20041223#Properties">Properties</a>.
Both mechanisms use URIs to identify the semantics of the
extensions. For extension XML elements and attributes, the
--- 2734,2740 ----
(non-wsdl) XML namespaces to be interspersed into a WSDL document;
and <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20040803#Features">Features</a>
and <a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20040803#Properties">Properties</a>.
Both mechanisms use URIs to identify the semantics of the
extensions. For extension XML elements and attributes, the
***************
*** 2968,2984 ****
<div class="div1">
<h2><a name="References" id="References"></a>8. References</h2>
! <p>@@ Update reference to RDF mapping @@</p>
! <p>@@ Delete self-reference to primer @@</p>
! <table border="1" summary="Editorial note: KevinL">
! <tr>
! <td align="left" valign="top" width="50%"><b>Editorial note:
! KevinL</b></td>
! <td align="right" valign="top" width="50%">20040626</td>
! </tr>
! <tr>
! <td colspan="2" align="left" valign="top">copied from part 1 spec
! as place holder, needs cleanup</td>
! </tr>
! </table>
<div class="div2">
<h3><a name="Normative-References" id=
--- 2992,2997 ----
<div class="div1">
<h2><a name="References" id="References"></a>8. References</h2>
! <p>@@ To do: Enable the reference to the RDF mapping when it's
! done. @@</p>
<div class="div2">
<h3><a name="Normative-References" id=
***************
*** 3062,3066 ****
2.0 Core Language]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20041223">Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
Language</a></cite>, R. Chinnici, M. Gudgin, J-J. Moreau, A. Ryman,
--- 3075,3079 ----
2.0 Core Language]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-20040803">Web Services
Description Language (WSDL) Version 2.0 Part 1: Core
Language</a></cite>, R. Chinnici, M. Gudgin, J-J. Moreau, A. Ryman,
***************
*** 3068,3072 ****
August 2004. This version of the "Web Services Description Language
(WSDL) Version 2.0 Part 1: Core Language" Specification is
! available at http://www.w3.org/TR/2004/WD-wsdl20-20041223. The
<a href="http://www.w3.org/TR/wsdl20">latest version of "Web
Services Description Language (WSDL) Version 2.0 Part 1: Core
--- 3081,3085 ----
August 2004. This version of the "Web Services Description Language
(WSDL) Version 2.0 Part 1: Core Language" Specification is
! available at http://www.w3.org/TR/2004/WD-wsdl20-20040803. The
<a href="http://www.w3.org/TR/wsdl20">latest version of "Web
Services Description Language (WSDL) Version 2.0 Part 1: Core
***************
*** 3075,3079 ****
2.0 Predefined Extensions]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20041223">Web
Services Description Language (WSDL) Version 2.0 Part 2: Predefined
Extensions</a></cite>, M. Gudgin, A. Lewis, and J. Schlimmer,
--- 3088,3092 ----
2.0 Predefined Extensions]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803">Web
Services Description Language (WSDL) Version 2.0 Part 2: Predefined
Extensions</a></cite>, M. Gudgin, A. Lewis, and J. Schlimmer,
***************
*** 3081,3085 ****
the "Web Services Description Language (WSDL) Version 2.0 Part 2:
Predefined Extensions" Specification is available at
! http://www.w3.org/TR/2004/WD-wsdl20-extensions-20041223. The
<a href="http://www.w3.org/TR/wsdl20-extensions">latest version of
"Web Services Description Language (WSDL) Version 2.0 Part 2:
--- 3094,3098 ----
the "Web Services Description Language (WSDL) Version 2.0 Part 2:
Predefined Extensions" Specification is available at
! http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803. The
<a href="http://www.w3.org/TR/wsdl20-extensions">latest version of
"Web Services Description Language (WSDL) Version 2.0 Part 2:
***************
*** 3089,3093 ****
2.0 Bindings]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-bindings-20041223">Web
Services Description Language (WSDL) Version 2.0 Part 3:
Bindings</a></cite>, H. Haas, P. Le Hégaret, J-J. Moreau, D.
--- 3102,3106 ----
2.0 Bindings]</dt>
<dd><cite><a href=
! "http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803">Web
Services Description Language (WSDL) Version 2.0 Part 3:
Bindings</a></cite>, H. Haas, P. Le Hégaret, J-J. Moreau, D.
***************
*** 3095,3099 ****
Consortium, 3 August 2004. This version of the "Web Services
Description Version 2.0: Bindings" Specification is available at
! http://www.w3.org/TR/2004/WD-wsdl20-bindings-20041223. The <a href=
"http://www.w3.org/TR/wsdl20-bindings">latest version of "Web
Services Description Language (WSDL) Version 2.0 Part 3:
--- 3108,3112 ----
Consortium, 3 August 2004. This version of the "Web Services
Description Version 2.0: Bindings" Specification is available at
! http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803. The <a href=
"http://www.w3.org/TR/wsdl20-bindings">latest version of "Web
Services Description Language (WSDL) Version 2.0 Part 3:
***************
*** 3108,3112 ****
2004. Available at http://www.w3.org/TR/2004/REC-webarch-20041215/
.</dd>
! <dt class="label"><a name="wsarch" id="wsarch"></a>[Web
Architecture]</dt>
<dd><cite><a href=
--- 3121,3125 ----
2004. Available at http://www.w3.org/TR/2004/REC-webarch-20041215/
.</dd>
! <dt class="label"><a name="wsarch" id="wsarch"></a>[WS
Architecture]</dt>
<dd><cite><a href=
Received on Monday, 20 December 2004 16:58:31 UTC