- From: Roberto Chinnici via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 19 Apr 2005 17:55:23 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv10654
Modified Files:
wsdl20-z.html wsdl20.html wsdl20.xml
Log Message:
Replaced obsolete reference to the definitions EII with one to the wsdl:description EII.
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** wsdl20-z.html 18 Apr 2005 22:58:10 -0000 1.19
--- wsdl20-z.html 19 Apr 2005 17:55:20 -0000 1.20
***************
*** 656,662 ****
modules and bindings of features, and a language for describing
such concrete details for SOAP 1.2 [<cite><a href=
! "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>],
! HTTP [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>] and MIME
! [<cite><a href="#RFC2045">IETF RFC 2045</a></cite>].</p>
<div class="div2">
<h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3>
--- 656,661 ----
modules and bindings of features, and a language for describing
such concrete details for SOAP 1.2 [<cite><a href=
! "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]
! and HTTP [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>].</p>
<div class="div2">
<h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3>
***************
*** 664,668 ****
abstract and one concrete. Within each stage, the description uses
a number of constructs to promote reusability of the description
! and separate independent design concerns.</p>
<p>At an abstract level, WSDL describes a Web service in terms of
the messages it sends and receives; messages are described
--- 663,667 ----
abstract and one concrete. Within each stage, the description uses
a number of constructs to promote reusability of the description
! and to separate independent design concerns.</p>
<p>At an abstract level, WSDL describes a Web service in terms of
the messages it sends and receives; messages are described
***************
*** 768,773 ****
throughout; they are given in the following list. Note that the
choice of any namespace prefix is arbitrary and not semantically
! significant (see [<cite><a href="#XMLInfoSet">XML Information
! Set</a></cite>]).</p>
<dl>
<dt class="label">wsdl</dt>
--- 767,772 ----
throughout; they are given in the following list. Note that the
choice of any namespace prefix is arbitrary and not semantically
! significant (see [<cite><a href="#XMLNS">XML
! Namespaces</a></cite>]).</p>
<dl>
<dt class="label">wsdl</dt>
***************
*** 939,946 ****
WSDL.</p>
<p>Components are typed collections of properties that correspond
! to different aspects of Web services. Each subsection herein
! describes a different type of component, its defined properties,
! and its representation as an XML Infoset [<cite><a href=
! "#XMLInfoSet">XML Information Set</a></cite>].</p>
<a name="zed-Component" id="zed-Component"></a>
<div class="twisty-head" id="twisty-head-zed-Component"><img class=
--- 938,956 ----
WSDL.</p>
<p>Components are typed collections of properties that correspond
! to different aspects of Web services.</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">Change property to avoid
! confusion with other meaning in spec.</td>
! </tr>
! </table>
! Each subsection herein describes a different type of component, its
! defined properties, and its representation as an XML Infoset
! [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>].
<a name="zed-Component" id="zed-Component"></a>
<div class="twisty-head" id="twisty-head-zed-Component"><img class=
***************
*** 2948,2954 ****
which conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <code>description</code> element information item. This includes
! the application of the mechanisms described in <a href=
! "#modularize"><b>4. Modularizing WSDL descriptions</b></a>.</p>
<p>This document does not specify a means of producing an XML
Infoset representation from a component model instance. In
--- 2958,2965 ----
which conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <code>wsdl:description</code> <em>element information item</em>.
! This includes the application of the mechanisms described in
! <a href="#modularize"><b>4. Modularizing WSDL
! descriptions</b></a>.</p>
<p>This document does not specify a means of producing an XML
Infoset representation from a component model instance. In
***************
*** 2961,2965 ****
"Description_details"></a>2.1.1 The Description Component</h4>
<p>At the abstract level, the Description component is just a
! container for two categories of components; WSDL components and
type system components.</p>
<p>WSDL components are interfaces, bindings and services.</p>
--- 2972,2976 ----
"Description_details"></a>2.1.1 The Description Component</h4>
<p>At the abstract level, the Description component is just a
! container for two categories of components: WSDL components and
type system components.</p>
<p>WSDL components are interfaces, bindings and services.</p>
***************
*** 2973,2977 ****
Language Extensibility</b></a>. In the case where they define
information equivalent to that of a XML Schema global element
! declaration, they can more simply be treated as if they were such a
declaration.</p>
<p>This specification does not define the behavior of a WSDL
--- 2984,2988 ----
Language Extensibility</b></a>. In the case where they define
information equivalent to that of a XML Schema global element
! declaration, they can be treated as if they were such a
declaration.</p>
<p>This specification does not define the behavior of a WSDL
***************
*** 3333,3341 ****
</ul>
</div>
! <p>The set of interfaces/binding/services/etc. available in the
Description component include those that are defined within the
component itself and those that are imported and/or included. Note
that at the component model level, there is no distinction between
! directly defined components vs. imported/included components.</p>
<a name="zed-DescriptionKeys" id="zed-DescriptionKeys"></a>
<div class="twisty-head" id="twisty-head-zed-DescriptionKeys">
--- 3344,3353 ----
</ul>
</div>
! <p>The set of interfaces, binding, services, etc. available in the
Description component include those that are defined within the
component itself and those that are imported and/or included. Note
that at the component model level, there is no distinction between
! directly defined components versus imported and/or included
! components.</p>
<a name="zed-DescriptionKeys" id="zed-DescriptionKeys"></a>
<div class="twisty-head" id="twisty-head-zed-DescriptionKeys">
***************
*** 3530,3541 ****
The target namespace therefore groups a set of related component
definitions and represents an unambiguous name for the intended
! semantics of the collection of components. The target namespace URI
! SHOULD point to a human or machine processable document that
! directly or indirectly defines the intended semantics of those
! components.</p>
! <p>Note that it is RECOMMENDED that the value of the
! <code>targetNamespace</code> <em>attribute information item</em> be
! a dereferencable URI and that it resolves to a WSDL document which
! provides service description information for that namespace.</p>
<p>If a service description is split into multiple documents (which
may be combined as needed via <a href="#includes"><b>4.1 Including
--- 3542,3552 ----
The target namespace therefore groups a set of related component
definitions and represents an unambiguous name for the intended
! semantics of the collection of components. The value of the
! <code>targetNamespace</code> <em>attribute information item</em>
! SHOULD be a dereferenceable URI. It SHOULD resolve to a human or
! machine processable document that directly or indirectly defines
! the intended semantics of those components. It MAY resolve to a
! WSDL document which provides service description information for
! that namespace.</p>
<p>If a service description is split into multiple documents (which
may be combined as needed via <a href="#includes"><b>4.1 Including
***************
*** 3557,3562 ****
be unique within the space of those components in a given target
namespace.</p>
- <p>The targetNamespace URI MUST be an absolute URI (see
- [<cite><a href="#RFC3986">IETF RFC 3986</a></cite>]).</p>
<p>The <code>description</code> <em>element information item</em>
has the following Infoset properties:</p>
--- 3568,3571 ----
***************
*** 3580,3585 ****
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s. The [namespace name] of such <em>attribute information
! item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
--- 3589,3594 ----
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s whose [namespace name] is NOT
! "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
***************
*** 4470,4475 ****
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s. The [namespace name] of such <em>attribute information
! item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
--- 4479,4484 ----
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s whose [namespace name] is NOT
! "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.175
retrieving revision 1.176
diff -C2 -d -r1.175 -r1.176
*** wsdl20.html 18 Apr 2005 22:58:10 -0000 1.175
--- wsdl20.html 19 Apr 2005 17:55:21 -0000 1.176
***************
*** 656,662 ****
modules and bindings of features, and a language for describing
such concrete details for SOAP 1.2 [<cite><a href=
! "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>],
! HTTP [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>] and MIME
! [<cite><a href="#RFC2045">IETF RFC 2045</a></cite>].</p>
<div class="div2">
<h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3>
--- 656,661 ----
modules and bindings of features, and a language for describing
such concrete details for SOAP 1.2 [<cite><a href=
! "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]
! and HTTP [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>].</p>
<div class="div2">
<h3><a name="intro_ws" id="intro_ws"></a>1.1 Web Service</h3>
***************
*** 664,668 ****
abstract and one concrete. Within each stage, the description uses
a number of constructs to promote reusability of the description
! and separate independent design concerns.</p>
<p>At an abstract level, WSDL describes a Web service in terms of
the messages it sends and receives; messages are described
--- 663,667 ----
abstract and one concrete. Within each stage, the description uses
a number of constructs to promote reusability of the description
! and to separate independent design concerns.</p>
<p>At an abstract level, WSDL describes a Web service in terms of
the messages it sends and receives; messages are described
***************
*** 768,773 ****
throughout; they are given in the following list. Note that the
choice of any namespace prefix is arbitrary and not semantically
! significant (see [<cite><a href="#XMLInfoSet">XML Information
! Set</a></cite>]).</p>
<dl>
<dt class="label">wsdl</dt>
--- 767,772 ----
throughout; they are given in the following list. Note that the
choice of any namespace prefix is arbitrary and not semantically
! significant (see [<cite><a href="#XMLNS">XML
! Namespaces</a></cite>]).</p>
<dl>
<dt class="label">wsdl</dt>
***************
*** 939,946 ****
WSDL.</p>
<p>Components are typed collections of properties that correspond
! to different aspects of Web services. Each subsection herein
! describes a different type of component, its defined properties,
! and its representation as an XML Infoset [<cite><a href=
! "#XMLInfoSet">XML Information Set</a></cite>].</p>
<a name="zed-Component" id="zed-Component"></a> <a name="zed-ID"
id="zed-ID"></a> <a name="zed-Identifier" id="zed-Identifier"></a>
--- 938,956 ----
WSDL.</p>
<p>Components are typed collections of properties that correspond
! to different aspects of Web services.</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">Change property to avoid
! confusion with other meaning in spec.</td>
! </tr>
! </table>
! Each subsection herein describes a different type of component, its
! defined properties, and its representation as an XML Infoset
! [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>].
<a name="zed-Component" id="zed-Component"></a> <a name="zed-ID"
id="zed-ID"></a> <a name="zed-Identifier" id="zed-Identifier"></a>
***************
*** 992,998 ****
which conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <code>description</code> element information item. This includes
! the application of the mechanisms described in <a href=
! "#modularize"><b>4. Modularizing WSDL descriptions</b></a>.</p>
<p>This document does not specify a means of producing an XML
Infoset representation from a component model instance. In
--- 1002,1009 ----
which conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <code>wsdl:description</code> <em>element information item</em>.
! This includes the application of the mechanisms described in
! <a href="#modularize"><b>4. Modularizing WSDL
! descriptions</b></a>.</p>
<p>This document does not specify a means of producing an XML
Infoset representation from a component model instance. In
***************
*** 1005,1009 ****
"Description_details"></a>2.1.1 The Description Component</h4>
<p>At the abstract level, the Description component is just a
! container for two categories of components; WSDL components and
type system components.</p>
<p>WSDL components are interfaces, bindings and services.</p>
--- 1016,1020 ----
"Description_details"></a>2.1.1 The Description Component</h4>
<p>At the abstract level, the Description component is just a
! container for two categories of components: WSDL components and
type system components.</p>
<p>WSDL components are interfaces, bindings and services.</p>
***************
*** 1017,1021 ****
Language Extensibility</b></a>. In the case where they define
information equivalent to that of a XML Schema global element
! declaration, they can more simply be treated as if they were such a
declaration.</p>
<p>This specification does not define the behavior of a WSDL
--- 1028,1032 ----
Language Extensibility</b></a>. In the case where they define
information equivalent to that of a XML Schema global element
! declaration, they can be treated as if they were such a
declaration.</p>
<p>This specification does not define the behavior of a WSDL
***************
*** 1049,1057 ****
<a name="zed-Description" id="zed-Description"></a> <a name=
"zed-DescriptionRI" id="zed-DescriptionRI"></a>
! <p>The set of interfaces/binding/services/etc. available in the
Description component include those that are defined within the
component itself and those that are imported and/or included. Note
that at the component model level, there is no distinction between
! directly defined components vs. imported/included components.</p>
<a name="zed-DescriptionKeys" id="zed-DescriptionKeys"></a>
<p>In addition to WSDL components and type system components,
--- 1060,1069 ----
<a name="zed-Description" id="zed-Description"></a> <a name=
"zed-DescriptionRI" id="zed-DescriptionRI"></a>
! <p>The set of interfaces, binding, services, etc. available in the
Description component include those that are defined within the
component itself and those that are imported and/or included. Note
that at the component model level, there is no distinction between
! directly defined components versus imported and/or included
! components.</p>
<a name="zed-DescriptionKeys" id="zed-DescriptionKeys"></a>
<p>In addition to WSDL components and type system components,
***************
*** 1087,1098 ****
The target namespace therefore groups a set of related component
definitions and represents an unambiguous name for the intended
! semantics of the collection of components. The target namespace URI
! SHOULD point to a human or machine processable document that
! directly or indirectly defines the intended semantics of those
! components.</p>
! <p>Note that it is RECOMMENDED that the value of the
! <code>targetNamespace</code> <em>attribute information item</em> be
! a dereferencable URI and that it resolves to a WSDL document which
! provides service description information for that namespace.</p>
<p>If a service description is split into multiple documents (which
may be combined as needed via <a href="#includes"><b>4.1 Including
--- 1099,1109 ----
The target namespace therefore groups a set of related component
definitions and represents an unambiguous name for the intended
! semantics of the collection of components. The value of the
! <code>targetNamespace</code> <em>attribute information item</em>
! SHOULD be a dereferenceable URI. It SHOULD resolve to a human or
! machine processable document that directly or indirectly defines
! the intended semantics of those components. It MAY resolve to a
! WSDL document which provides service description information for
! that namespace.</p>
<p>If a service description is split into multiple documents (which
may be combined as needed via <a href="#includes"><b>4.1 Including
***************
*** 1114,1119 ****
be unique within the space of those components in a given target
namespace.</p>
- <p>The targetNamespace URI MUST be an absolute URI (see
- [<cite><a href="#RFC3986">IETF RFC 3986</a></cite>]).</p>
<p>The <code>description</code> <em>element information item</em>
has the following Infoset properties:</p>
--- 1125,1128 ----
***************
*** 1137,1142 ****
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s. The [namespace name] of such <em>attribute information
! item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
--- 1146,1151 ----
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s whose [namespace name] is NOT
! "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
***************
*** 1417,1422 ****
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s. The [namespace name] of such <em>attribute information
! item</em>s MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
--- 1426,1431 ----
<li>
<p>Zero or more namespace qualified <em>attribute information
! item</em>s whose [namespace name] is NOT
! "http://www.w3.org/@@@@/@@/wsdl".</p>
</li>
</ul>
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.214
retrieving revision 1.215
diff -C2 -d -r1.214 -r1.215
*** wsdl20.xml 19 Apr 2005 12:48:52 -0000 1.214
--- wsdl20.xml 19 Apr 2005 17:55:21 -0000 1.215
***************
*** 1099,1103 ****
conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <el>definitions</el> element information item. This includes the
application of the mechanisms described in <specref ref="modularize"/>.
</p>
--- 1099,1103 ----
conforms to the XML Schema for WSDL by recursively mapping
Information Items to their identified components, starting with the
! <el>wsdl:description</el> &EII;. This includes the
application of the mechanisms described in <specref ref="modularize"/>.
</p>
Received on Tuesday, 19 April 2005 17:55:24 UTC