W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > April 2005

2002/ws/desc/wsdl20 wsdl20.xml,1.213,1.214

From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 19 Apr 2005 12:48:54 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DNs9u-0008BC-LG@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv31435

Modified Files:
	wsdl20.xml 
Log Message:
LC78 part 1

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.213
retrieving revision 1.214
diff -C2 -d -r1.213 -r1.214
*** wsdl20.xml	18 Apr 2005 22:58:10 -0000	1.213
--- wsdl20.xml	19 Apr 2005 12:48:52 -0000	1.214
***************
*** 114,119 ****
  and bindings of features, and 
  a language for describing such concrete details for SOAP 1.2 <bibref
! ref='SOAP12-PART1' />, HTTP <bibref ref='RFC2616'/> and MIME <bibref
! ref='RFC2045' />. </p>
  
  <div2 id="intro_ws">
--- 114,118 ----
  and bindings of features, and 
  a language for describing such concrete details for SOAP 1.2 <bibref
! ref='SOAP12-PART1' /> and HTTP <bibref ref='RFC2616'/>. </p>
  
  <div2 id="intro_ws">
***************
*** 123,127 ****
  WSDL describes a Web service in two fundamental stages: one 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>
--- 122,126 ----
  WSDL describes a Web service in two fundamental stages: one 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>
***************
*** 248,252 ****
  they are given in the following list. Note that the choice of any
  namespace prefix is arbitrary and not semantically significant (see
! <bibref ref="XMLInfoSet"/>).</p>
     
     <glist>
--- 247,251 ----
  they are given in the following list. Note that the choice of any
  namespace prefix is arbitrary and not semantically significant (see
! <bibref ref="XMLNS"/>).</p>
     
     <glist>
***************
*** 463,466 ****
--- 462,466 ----
    Components are typed collections of properties that correspond to  
    different aspects of Web services.
+   <ednote><edtext>Change property to avoid confusion with other meaning in spec.</edtext></ednote>
    Each subsection herein describes a different type of  
    component, its defined properties, and its representation as an XML  
***************
*** 1099,1103 ****
    conforms to the XML Schema for WSDL by recursively mapping  
    Information Items to their identified components, starting with the  
!   <el>description</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>definitions</el> element information item. This includes the  
    application of the mechanisms described in <specref ref="modularize"/>.
    </p>
***************
*** 1117,1121 ****
        
        <p>At the abstract level, the Description component is just a
!       container for two categories of components; WSDL components and
        type system components.</p>
  
--- 1117,1121 ----
        
        <p>At the abstract level, the Description component is just a
!       container for two categories of components: WSDL components and
        type system components.</p>
  
***************
*** 1130,1134 ****
        to WSDL; see <specref ref="language-extensibility"/>.  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>
  
--- 1130,1134 ----
        to WSDL; see <specref ref="language-extensibility"/>.  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>
  
***************
*** 1274,1283 ****
  </z:notation>
  
!        <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>
  
  <z:notation name="DescriptionKeys">
--- 1274,1283 ----
  </z:notation>
  
!        <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>
  
  <z:notation name="DescriptionKeys">
***************
*** 1350,1361 ****
         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
!          <att>targetNamespace</att> &AII; 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
--- 1350,1359 ----
         of related component definitions and represents an unambiguous
         name for the intended semantics of the collection of components.
!        The value of the <att>targetNamespace</att> &AII; 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
***************
*** 1380,1388 ****
         QName. Thus, QNames of components must be unique within the
         space of those components in a given target namespace.</p>
- 	  
-           <p>
-           The targetNamespace URI MUST be an absolute URI (see <bibref
-           ref="RFC3986"/>).
-           </p>
  
  	  <p>The <el>description</el> &EII; has the following Infoset properties:</p>
--- 1378,1381 ----
***************
*** 1405,1410 ****
  			<item>
  			  <p>
! 			  Zero or more namespace qualified &AII;s. The [namespace
! 			  name] of such &AII;s MUST NOT be
  			  <attval>&wsdl-ns;</attval>.
  			  </p>
--- 1398,1403 ----
  			<item>
  			  <p>
! 			  Zero or more namespace qualified &AII;s whose [namespace
! 			  name] is NOT
  			  <attval>&wsdl-ns;</attval>.
  			  </p>
***************
*** 1873,1879 ****
  		<item>
  		  <p>
! 		  Zero or more namespace qualified &AII;s.
! 		  The [namespace name] of such
! 		  &AII;s MUST NOT be <attval>&wsdl-ns;</attval>.
  		  </p>
  		</item>
--- 1866,1872 ----
  		<item>
  		  <p>
! 		  Zero or more namespace qualified &AII;s whose
! 		  [namespace name]
! 		  is NOT <attval>&wsdl-ns;</attval>.
  		  </p>
  		</item>
Received on Tuesday, 19 April 2005 12:48:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:34 UTC