- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 27 Mar 2005 16:35:36 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv11294
Modified Files:
wsdl20-primer.xml
Log Message:
Replace obsolete references to Part 3 with corrected references to Part 2.
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -C2 -d -r1.39 -r1.40
*** wsdl20-primer.xml 27 Mar 2005 16:13:01 -0000 1.39
--- wsdl20-primer.xml 27 Mar 2005 16:35:34 -0000 1.40
***************
*** 39,46 ****
</authlist>
<abstract id="Abstract">
! <p>This document is a companion to the WSDL 2.0 specification (<emph>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</emph> <bibref ref="WSDL-PART1"/>, <emph>Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions</emph> <bibref ref="WSDL-PART2"/>, <emph>Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings</emph> <bibref ref="WSDL-PART3"/>). It is intended for readers who wish to have an easier, less technical introduction to the main features of the language. </p><p>This primer is only intended to be a starting point toward use of WSDL 2.0, and hence does not describe every feature of the language. Users are expected to consult the WSDL 2.0 specification if they wish to make use of more sophisticated features or techniques.</p>
! <p>Finally, this primer is <emph>non-normative</emph>. Any specific questions of what WSDL 2.0 requires or forbids should be referred to the WSDL 2.0 specification. </p>
</abstract>
! &status;
<langusage>
<language id="en">English</language>
--- 39,76 ----
</authlist>
<abstract id="Abstract">
! <p>
! This document is a companion to the WSDL 2.0
! specification (
! <emph>
! Web Services Description Language (WSDL) Version 2.0
! Part 1: Core Language
! </emph>
! <bibref ref="WSDL-PART1" />
! ,
! <emph>
! Web Services Description Language (WSDL) Version 2.0
! Part 2: Adjuncts
! </emph>
! <bibref ref="WSDL-PART2" />
! ). It is intended for readers who wish to have an
! easier, less technical introduction to the main features
! of the language.
! </p>
! <p>
! This primer is only intended to be a starting point
! toward use of WSDL 2.0, and hence does not describe
! every feature of the language. Users are expected to
! consult the WSDL 2.0 specification if they wish to make
! use of more sophisticated features or techniques.
! </p>
! <p>
! Finally, this primer is
! <emph>non-normative</emph>
! . Any specific questions of what WSDL 2.0 requires or
! forbids should be referred to the WSDL 2.0
! specification.
! </p>
</abstract>
! &status;
<langusage>
<language id="en">English</language>
***************
*** 269,273 ****
! <div2 id="basics-binding"><head>Defining a Binding</head><p>Although we have specified <emph>what</emph> abstract messages can be exchanged with the GreatH Web service, we have not yet specified <emph>how</emph> those messages can be exchanged. This is the purpose of a <emph>binding</emph>. A binding specifies concrete message format and transmission protocol details for an interface, and must supply such details for every operation and fault in the interface. </p><p>In the general case, binding details for each operation and fault are specified using <code>operation</code> and <code>fault</code> elements inside a <code>binding</code> element, as shown in the example below. However, in some cases it is possible to use defaulting rules to supply the information. The WSDL 2.0 SOAP binding, for example, defines some defaulting rules for operations. (See <emph>Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings</emph> <bibref ref="WSDL-PART3"/>, section 2.3 <xspecref href="http://ww.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-defaults">Default Binding Rules</xspecref>.) </p><p>In order to accommodate new kinds of message formats and transmission protocols, bindings are defined using extensions to the WSDL 2.0 language, via WSDL 2.0's open content model. WSDL 2.0 Part 3 defines binding constructs for SOAP 1.2 <bibref ref="SOAP12-PART1"/> and HTTP 1.1 <bibref ref="RFC2616"/> as predefined extensions, so that SOAP 1.2 or HTTP 1.1 bindings can be easily defined in WSDL documents. However, other specifications could define new binding constructs that could also be used to define bindings. (As with any extension, other WSDL processors would have to know about the new constructs in order to make use of them.) </p><p>For the GreatH service, we will use SOAP 1.2 as our concrete message format and HTTP as our underlying transmission protocol, as shown below. </p><example id="example-initial-binding">
<head>GreatH Binding Definition</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
--- 299,341 ----
! <div2 id="basics-binding"><head>Defining a Binding</head>
! <p>
! Although we have specified
! <emph>what</emph>
! abstract messages can be exchanged with the GreatH Web
! service, we have not yet specified
! <emph>how</emph>
! those messages can be exchanged. This is the purpose of
! a
! <emph>binding</emph>. A binding specifies concrete message format and
! transmission protocol details for an interface, and must
! supply such details for every operation and fault in the
! interface.
! </p>
! <p>
! In the general case, binding details for each operation
! and fault are specified using
! <code>operation</code>
! and
! <code>fault</code>
! elements inside a
! <code>binding</code>
! element, as shown in the example below. However, in some
! cases it is possible to use defaulting rules to supply
! the information. The WSDL 2.0 SOAP binding, for example,
! defines some defaulting rules for operations. (See
! <emph>
! Web Services Description Language (WSDL) Version 2.0
! Part 2: Adjuncts
! </emph>
! <bibref ref="WSDL-PART2" />
! , section 4.3
! <xspecref
! href="http://www.w3.org/TR/2004/WD-wsdl20-adjuncts/#soap-defaults">
! Default Binding Rules
! </xspecref>
! .)
! </p>
! <p>In order to accommodate new kinds of message formats and transmission protocols, bindings are defined using extensions to the WSDL 2.0 language, via WSDL 2.0's open content model. WSDL 2.0 Part 3 defines binding constructs for SOAP 1.2 <bibref ref="SOAP12-PART1"/> and HTTP 1.1 <bibref ref="RFC2616"/> as predefined extensions, so that SOAP 1.2 or HTTP 1.1 bindings can be easily defined in WSDL documents. However, other specifications could define new binding constructs that could also be used to define bindings. (As with any extension, other WSDL processors would have to know about the new constructs in order to make use of them.) </p><p>For the GreatH service, we will use SOAP 1.2 as our concrete message format and HTTP as our underlying transmission protocol, as shown below. </p><example id="example-initial-binding">
<head>GreatH Binding Definition</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
***************
*** 312,316 ****
. . .
</description>]]></eg>
! </example><div3 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12"</code></label><def><p>We've added two more namespace declarations. This one is the namespace for the SOAP 1.2 binding construct that is defined in WSDL 2.0 Part 3 <bibref ref="SOAP12-PART1"/>. Elements and attributes prefixed with <code>wsoap:</code> are constructs defined there. </p></def></gitem><gitem><label><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></label><def><p>This namespace is defined by the SOAP 1.2 specification itself. The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts. Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></def></gitem><gitem><label><code><binding name="reservationSOAPBinding"</code></label><def><p>Bindings are declared directly inside the <code>description</code>element. The <att>name</att> attribute defines a name for this binding. Each name must be unique among all bindings in this WSDL target namespace, and will be used later when we define a service endpoint that references this binding. WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></def></gitem><gitem><label><code>interface="tns:reservationInterface"</code></label><def><p>This is the name of the interface whose message format and transmission protocols we are specifying. As discussed in <specref ref="more-bindings"/>, a reusable binding can be defined by omitting the <att>interface</att> attribute. Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL target namespace for this WSDL document. In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <specref ref="adv-import-and-authoring"/>we will see how WSDL 2.0's import mechanismcan be used to combine components that are defined in different WSDL target namespaces.</p></def></gitem><gitem><label><code>type="http://www.w3.org/2004/08/wsdl/soap12"</code></label><def><p>This specifies the type of concrete message format to use, in this case SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></label><def><p>This attribute is specific to WSDL 2.0's SOAP binding (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP. </p></def></gitem><gitem><label><code><operation ref="tns:opCheckAvailability"</code></label><def><p>This not defining a new operation. Rather, it is referencing the previously defined <code>opCheckAvailability</code> operation in order to specify binding details for it. This element can be omitted if defaulting rules are instead used to supply the necessary information. (See the SOAP binding in <emph>WSDL 2.0 Bindings</emh> <bibref ref="WSDL-PART3"/> section 2.3 <xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-defaults">Default Binding Rules</xspecref>.)</p></def></gitem><gitem><label><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"></code></label><def><p>This attribute is also specific to WSDL 2.0's SOAP binding. It specifies the SOAP message exchange pattern that will be used to implement the abstract WSDL 2.0 message exchange pattern (<xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</xspecref>) that was specified when the <code>opCheckAvailability</code> operation was defined. </p></def></gitem><gitem><label><code><fault ref="tns:invalidDataFault"</code></label><def><p>As with a binding operation, this is not declaring a new fault. Rather, it is referencing a fault (<code>invalidDataFault</code>) that was previously defined in the <code>opCheckAvailability</code> interface, in order to specify binding details for it.</p></de></gitem><gitem><label><code>wsoap:code="soap:Sender"/></code></label><def><p>This attribute is also specific to WSDL 2.0's SOAP binding. This specifies the SOAP 1.2 fault code that will cause this fault message to be sent. If desired, an list of subcodes can also be specified using the optional <att>wsoap:subcodes</att> attribute.</p></def></gitem></glist></div3></div2><div2 id="basics-service"><head>Defining a Service</head><p>Now that our binding has specified <emph>how</emph> messages will be transmitted, we are ready to specify <emph>where</emph> the service can be accessed, by use of the <code>service</code> element. </p><p>A WSDL 2.0 <emph>service</emph> specifies a single interface that the service will support, and a list of <emph>endpoint</emph> locations where that service can be accessed. Each endpoint must also reference a previously defined binding in order to indicate the binding details that are to be used at that endpoint. A service is only permitted to have one interface. (However, WSDL 2.0 does not prohibit one from declaring multiple services that use different interfaces but happen to use the same endpoint address. See <specref ref="adv-multiple-docs-describing-same-service"/>.) </p><p>Here is a definition for our GreatH service.</p><example id="example-initial-service">
<head>GreatH Service Definition</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
--- 380,400 ----
. . .
</description>]]></eg>
! </example><div3 id="example-initial-binding-explanation"><head>Explanation of Example</head><glist><gitem><label><code>xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12"</code></label><def><p>We've added two more namespace declarations. This one is the namespace for the SOAP 1.2 binding construct that is defined in WSDL 2.0 Part 3 <bibref ref="SOAP12-PART1"/>. Elements and attributes prefixed with <code>wsoap:</code> are constructs defined there. </p></def></gitem><gitem><label><code>xmlns:soap="http://www.w3.org/2003/05/soap-envelope"</code></label><def><p>This namespace is defined by the SOAP 1.2 specification itself. The SOAP 1.2 specification defines certain terms within this namespace to unambiguously identify particular concepts. Thus, we will use the <code>soap:</code> prefix when we need to refer to one of those terms.</p></def></gitem><gitem><label><code><binding name="reservationSOAPBinding"</code></label><def><p>Bindings are declared directly inside the <code>description</code>element. The <att>name</att> attribute defines a name for this binding. Each name must be unique among all bindings in this WSDL target namespace, and will be used later when we define a service endpoint that references this binding. WSDL 2.0 uses separate symbol spaces for interfaces, bindings and services, so interface "foo", binding "foo" and service "foo" are all distinct. </p></def></gitem><gitem><label><code>interface="tns:reservationInterface"</code></label><def><p>This is the name of the interface whose message format and transmission protocols we are specifying. As discussed in <specref ref="more-bindings"/>, a reusable binding can be defined by omitting the <att>interface</att> attribute. Note also the use of the <code>tns:</code> prefix, which refers to the previously defined WSDL target namespace for this WSDL document. In this case it may seem silly to have to specify the <code>tns:</code> prefix, but in <specref ref="adv-import-and-authoring"/>we will see how WSDL 2.0's import mechanismcan be used to combine components that are defined in different WSDL target namespaces.</p></def></gitem><gitem><label><code>type="http://www.w3.org/2004/08/wsdl/soap12"</code></label><def><p>This specifies the type of concrete message format to use, in this case SOAP 1.2.</p></def></gitem><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></label><def><p>This attribute is specific to WSDL 2.0's SOAP binding (thus it uses the <code>wsoap:</code> prefix). It specifies the underlying transmission protocol that should be used, in this case HTTP. </p></def></gitem><gitem><label><code><operation ref="tns:opCheckAvailability"</code></label><def>
! <p>
! This not defining a new operation. Rather, it is referencing the
! previously defined
! <code>opCheckAvailability</code>
! operation in order to specify binding details for it. This
! element can be omitted if defaulting rules are instead used to
! supply the necessary information. (See the SOAP binding in
! <emph>WSDL 2.0 Bindings</emph>
! <bibref ref="WSDL-PART2" />
! section 4.3
! <xspecref
! href="http://www.w3.org/TR/2004/WD-wsdl20-adjuncts/#soap-defaults">
! Default Binding Rules
! </xspecref>.)
! </p>
! </def></gitem><gitem><label><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"></code></label><def><p>This attribute is also specific to WSDL 2.0's SOAP binding. It specifies the SOAP message exchange pattern that will be used to implement the abstract WSDL 2.0 message exchange pattern (<xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803/#in-out">in-out</xspecref>) that was specified when the <code>opCheckAvailability</code> operation was defined. </p></def></gitem><gitem><label><code><fault ref="tns:invalidDataFault"</code></label><def><p>As with a binding operation, this is not declaring a new fault. Rather, it is referencing a fault (<code>invalidDataFault</code>) that was previously defined in the <code>opCheckAvailability</code> interface, in order to specify binding details for it.</p></def></gitem><gitem><label><code>wsoap:code="soap:Sender"/></code></label><def><p>This attribute is also specific to WSDL 2.0's SOAP binding. This specifies te SOAP 1.2 fault code that will cause this fault message to be sent. If desired, an list of subcodes can also be specified using the optional <att>wsoap:subcodes</att> attribute.</p></def></gitem></glist></div3></div2><div2 id="basics-service"><head>Defining a Service</head><p>Now that our binding has specified <emph>how</emph> messages will be transmitted, we are ready to specify <emph>where</emph> the service can be accessed, by use of the <code>service</code> element. </p><p>A WSDL 2.0 <emph>service</emph> specifies a single interface that the service will support, and a list of <emph>endpoint</emph> locations where that service can be accessed. Each endpoint must also reference a previously defined binding in order to indicate the binding details that are to be used at that endpoint. A service is only permitted to have one interface. (However, WSDL 2.0 does not prohibit one from declaring multiple services that use different interfaces but happen to use the same endpoint address. See <specref rf="adv-multiple-docs-describing-same-service"/>.) </p><p>Here is a definition for our GreatH service.</p><example id="example-initial-service">
<head>GreatH Service Definition</head>
<eg><![CDATA[<?xml version="1.0" encoding="utf-8" ?>
***************
*** 1000,1004 ****
interface. The bindings may occur via defaulting rules
which allow one to specify default bindings for all operations
! (for example, see the SOAP binding in <emph>WSDL 2.0 Bindings</emph> <bibref ref="WSDL-PART3"/> section 2.3 <xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-defaults">Default Binding Rules</xspecref>) or by directly
listing each operation of the interface and
defining bindings for them. Thus, it is an error for a binding to not define bindings for all the operations of the corresponding interface.</p>
--- 1084,1091 ----
interface. The bindings may occur via defaulting rules
which allow one to specify default bindings for all operations
! (for example, see the SOAP binding in <emph>WSDL 2.0 Bindings</emph>
! <bibref ref="WSDL-PART2" />
! section 4.3
! <xspecref href="http://www.w3.org/TR/2004/WD-wsdl20-adjuncts/#soap-defaults">Default Binding Rules</xspecref>) or by directly
listing each operation of the interface and
defining bindings for them. Thus, it is an error for a binding to not define bindings for all the operations of the corresponding interface.</p>
***************
*** 2253,2276 ****
<loc href="&part1.latest;">latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"</loc> is available at &part1.latest;.
</bibl>
!
! <bibl key="WSDL 2.0 Predefined Extensions" href="&w3c-designation-part2;" id="WSDL-PART2">
! <titleref>Web Services Description Language (WSDL)
! Version 2.0 Part 2: Predefined Extensions</titleref>,
! M. Gudgin, A. Lewis, and J. Schlimmer, Editors. World
! Wide Web Consortium,
! <!--
! &draft.day; &draft.month;
! &draft.year;.
! -->
! 3 August 2004.
! This version of the "Web Services Description Language (WSDL)
! Version 2.0 Part 2: Predefined Extensions"
! Specification is available at &w3c-designation-part2;. The
! <loc href="&part2.latest;">latest version of "Web Services Description Language (WSDL)
! Version 2.0 Part 2: Predefined Extensions"</loc> is available at &part2.latest;.
! </bibl>
!
!
!
<bibl key="WSDL 2.0 Bindings" href="&w3c-designation-part3;" id="WSDL-PART3">
<titleref>Web Services Description Language (WSDL) Version
--- 2340,2370 ----
<loc href="&part1.latest;">latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language"</loc> is available at &part1.latest;.
</bibl>
!
! <bibl key="WSDL 2.0 Adjuncts"
! href="&w3c-designation-part2;" id="WSDL-PART2">
! <titleref>
! Web Services Description Language (WSDL)
! Version 2.0 Part 2: Adjuncts
! </titleref>, M. Gudgin, H. Haas, P. Le Hégaret, A.
! Lewis, J-J. Moreau, D. Orchard, J. Schlimmer, S.
! Weerawarana, Editors. World Wide Web Consortium,
! <!--
! &draft.day; &draft.month;
! &draft.year;.
! -->
! 3 August 2004. This version of the "Web Services
! Description Language (WSDL) Version 2.0 Part 2:
! Adjuncts" Specification is available at
! &w3c-designation-part2;. The
! <loc href="&part2.latest;">
! latest version of "Web Services Description
! Language (WSDL) Version 2.0 Part 2:
! Adjuncts"
! </loc>
! is available at
! &part2.latest;.
! </bibl>
!
! <!--
<bibl key="WSDL 2.0 Bindings" href="&w3c-designation-part3;" id="WSDL-PART3">
<titleref>Web Services Description Language (WSDL) Version
***************
*** 2281,2288 ****
J. Schlimmer,
S. Weerawarana, Editors. World Wide Web Consortium,
! <!--
! &draft.day; &draft.month;
! &draft.year;.
! -->
3 August 2004.
This version of the "Web
--- 2375,2379 ----
J. Schlimmer,
S. Weerawarana, Editors. World Wide Web Consortium,
!
3 August 2004.
This version of the "Web
***************
*** 2292,2296 ****
Bindings"</loc> is available at &part3.latest;.
</bibl>
!
<!--
<bibl key="WSDL 2.0 RDF Mapping" href="&w3c-designation-part4;" id="WSDL-PART4">
--- 2383,2388 ----
Bindings"</loc> is available at &part3.latest;.
</bibl>
! -->
!
<!--
<bibl key="WSDL 2.0 RDF Mapping" href="&w3c-designation-part4;" id="WSDL-PART4">
Received on Sunday, 27 March 2005 16:49:07 UTC