- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Apr 2005 22:27:21 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv2897
Modified Files:
wsdl20-soap11-binding.xml properties.dtd wsdl20-primer.xml
httpbinding.xml
Log Message:
Replaced references to Part 3 by Part 2 in text and entities.
Index: wsdl20-soap11-binding.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-soap11-binding.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** wsdl20-soap11-binding.xml 13 Jan 2005 00:09:54 -0000 1.4
--- wsdl20-soap11-binding.xml 13 Apr 2005 22:27:19 -0000 1.5
***************
*** 58,62 ****
1.1 protocol.</p>
<p>This specification depends on WSDL 2.0 <bibref ref="WSDL-PART1"/> and
! WSDL 2.0 Bindings <bibref ref="WSDL-PART3"/>. </p>
<!-- +++++++++ -->
<div2 id="notcon">
--- 58,62 ----
1.1 protocol.</p>
<p>This specification depends on WSDL 2.0 <bibref ref="WSDL-PART1"/> and
! WSDL 2.0 Adjuncts <bibref ref="WSDL-PART2"/>. </p>
<!-- +++++++++ -->
<div2 id="notcon">
***************
*** 141,145 ****
<p>The SOAP 1.1 binding enables Web Service applications to use SOAP 1.1
<bibref ref="SOAP11"/> by extending the SOAP binding in the WSDL
! Bindings Specification <bibref ref="WSDL-PART3"/>. This binding
supports the following: </p>
<ulist>
--- 141,145 ----
<p>The SOAP 1.1 binding enables Web Service applications to use SOAP 1.1
<bibref ref="SOAP11"/> by extending the SOAP binding in the WSDL
! Adjuncts Specification <bibref ref="WSDL-PART2"/>. This binding
supports the following: </p>
<ulist>
***************
*** 313,316 ****
--- 313,317 ----
href="&part1.latest;">latest version of
"&part1.title;"</loc> is available at &part1.latest;. </bibl>
+ <!--
<bibl key="WSDL20 Predefined Extensions"
href="&w3c-designation-part2;" id="WSDL-PART2">
***************
*** 331,334 ****
--- 332,359 ----
href="&part3.latest;">latest version of
"&part3.title;"</loc> is available at &part3.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 id="XMLSchemaP1" key="XSD Structures" href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">
<titleref>XML Schema Part 1: Structures</titleref>, H. Thompson, D.
Index: properties.dtd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/properties.dtd,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** properties.dtd 7 Apr 2005 14:23:34 -0000 1.10
--- properties.dtd 13 Apr 2005 22:27:19 -0000 1.11
***************
*** 36,50 ****
<!ENTITY soap-version
! "<xspecref href='&w3c-designation-part3;#soap-version'>{soap version}</xspecref>">
<!ENTITY soap-underlying-protocol
! "<xspecref href='&w3c-designation-part3;#soap-protocol'>{soap underlying protocol}</xspecref>">
<!ENTITY soap-action
! "<xspecref href='&w3c-designation-part3;#soap-operation-decl-relate'>{soap action}</xspecref>">
<!ENTITY soap-fault-subcodes
! "<xspecref href='&w3c-designation-part3;#soap-fault-decl-relate'>{soap fault subcodes}</xspecref>">
<!ENTITY soap-mep
! "<xspecref href='&w3c-designation-part3;#soap-operation-decl-relate'>{soap mep}</xspecref>">
<!ENTITY http-method
! "<xspecref href='&w3c-designation-part3;#http-operation-decl-relate'>{http method}</xspecref>">
<!ENTITY http-location
! "<xspecref href='&w3c-designation-part3;#http-operation-decl-relate'>{http location}</xspecref>">
\ No newline at end of file
--- 36,50 ----
<!ENTITY soap-version
! "<xspecref href='&w3c-designation-part2;#soap-version'>{soap version}</xspecref>">
<!ENTITY soap-underlying-protocol
! "<xspecref href='&w3c-designation-part2;#soap-protocol'>{soap underlying protocol}</xspecref>">
<!ENTITY soap-action
! "<xspecref href='&w3c-designation-part2;#soap-operation-decl-relate'>{soap action}</xspecref>">
<!ENTITY soap-fault-subcodes
! "<xspecref href='&w3c-designation-part2;#soap-fault-decl-relate'>{soap fault subcodes}</xspecref>">
<!ENTITY soap-mep
! "<xspecref href='&w3c-designation-part2;#soap-operation-decl-relate'>{soap mep}</xspecref>">
<!ENTITY http-method
! "<xspecref href='&w3c-designation-part2;#http-operation-decl-relate'>{http method}</xspecref>">
<!ENTITY http-location
! "<xspecref href='&w3c-designation-part2;#http-operation-decl-relate'>{http location}</xspecref>">
\ No newline at end of file
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -C2 -d -r1.46 -r1.47
*** wsdl20-primer.xml 13 Apr 2005 20:19:44 -0000 1.46
--- wsdl20-primer.xml 13 Apr 2005 22:27:19 -0000 1.47
***************
*** 331,335 ****
<bibref ref="WSDL-PART2"/>, <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. (See <specref ref="adv-extensibility"/> for more on extensibility.) WSDL 2.0 Part 3 <bibref ref="WSDL-PART3"/> 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" ?>
--- 331,355 ----
<bibref ref="WSDL-PART2"/>, <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. (See
! <specref ref="adv-extensibility" />
! for more on extensibility.) WSDL 2.0 Part 2
! <bibref ref="WSDL-PART2" />
! 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" ?>
***************
*** 1233,1237 ****
<p>An <code>endpoint</code> has two required attributes: <att>name</att> and <att>binding</att>. All <code>endpoints</code> within a <code>service</code> must be named uniquely via the <att>name</att> attribute. The required <att>binding</att> attribute refers to, via QName, a <code>binding</code> definition. Note that if the refered <code>binding</code> specifies a particular interface, that interface MUST be the same as the one implmented by the parent <code>service</code>. </p>
<p>Like the WSDL binding constructs explained in section @@@@, the WSDL <code>endpoint</code> construct is also like an anchor for hosting extension elements that are used to provide information specific to a
! particular endpoint in a server. The semantics of such extensions are defined by the specification for those extensions. Such specifications are expected to annotate the WSDL <code>endpoint</code> construct with additional properties and specify the mapping between those properties and the XML representation. For example, the SOAP and HTTP binding extensions defined in WSDL 2.0 Part 3 <bibref ref="WSDL-PART3"/> also provide extensions to be used under a service <code>endpoint</code>. </p>
</div1>
--- 1253,1261 ----
<p>An <code>endpoint</code> has two required attributes: <att>name</att> and <att>binding</att>. All <code>endpoints</code> within a <code>service</code> must be named uniquely via the <att>name</att> attribute. The required <att>binding</att> attribute refers to, via QName, a <code>binding</code> definition. Note that if the refered <code>binding</code> specifies a particular interface, that interface MUST be the same as the one implmented by the parent <code>service</code>. </p>
<p>Like the WSDL binding constructs explained in section @@@@, the WSDL <code>endpoint</code> construct is also like an anchor for hosting extension elements that are used to provide information specific to a
! particular endpoint in a server. The semantics of such extensions are defined by the specification for those extensions. Such specifications are expected to annotate the WSDL <code>endpoint</code>
! construct with additional properties and specify the mapping between
! those properties and the XML representation. For example, the SOAP and
! HTTP binding extensions defined in WSDL 2.0 Part 2
! <bibref ref="WSDL-PART2"/> also provide extensions to be used under a service <code>endpoint</code>. </p>
</div1>
***************
*** 2748,2752 ****
&part2.latest;.
</bibl>
!
<bibl key="WSDL 2.0 Bindings" href="&w3c-designation-part3;" id="WSDL-PART3">
<titleref>Web Services Description Language (WSDL) Version
--- 2772,2776 ----
&part2.latest;.
</bibl>
! <!--
<bibl key="WSDL 2.0 Bindings" href="&w3c-designation-part3;" id="WSDL-PART3">
<titleref>Web Services Description Language (WSDL) Version
***************
*** 2765,2769 ****
Bindings"</loc> is available at &part3.latest;.
</bibl>
!
<!--
<bibl key="WSDL 2.0 RDF Mapping" href="&w3c-designation-part4;" id="WSDL-PART4">
--- 2789,2793 ----
Bindings"</loc> is available at &part3.latest;.
</bibl>
! -->
<!--
<bibl key="WSDL 2.0 RDF Mapping" href="&w3c-designation-part4;" id="WSDL-PART4">
Index: httpbinding.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/httpbinding.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** httpbinding.xml 5 Mar 2004 10:26:17 -0000 1.1
--- httpbinding.xml 13 Apr 2005 22:27:19 -0000 1.2
***************
*** 12,16 ****
<header>
<title>Web Services Description Language (WSDL) Version 2.0: HTTP Binding</title>
! <w3c-designation>&w3c-designation-part3;</w3c-designation>
<w3c-doctype>&document.status;</w3c-doctype>
<pubdate>
--- 12,16 ----
<header>
<title>Web Services Description Language (WSDL) Version 2.0: HTTP Binding</title>
! <w3c-designation>&w3c-designation-part3;</w3c-designation>
<w3c-doctype>&document.status;</w3c-doctype>
<pubdate>
***************
*** 20,28 ****
</pubdate>
<publoc>
! <loc href="&w3c-designation-part3;">&w3c-designation-part3;</loc>
</publoc>
&altlocs;
<latestloc>
! <loc href="&part3.latest;">&part3.latest;</loc>
</latestloc>
<authlist>
--- 20,28 ----
</pubdate>
<publoc>
! <loc href="&w3c-designation-part3;">&w3c-designation-part3;</loc>
</publoc>
&altlocs;
<latestloc>
! <loc href="&part3.latest;">&part3.latest;</loc>
</latestloc>
<authlist>
Received on Wednesday, 13 April 2005 22:27:22 UTC