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

2002/ws/desc/wsdl20 wsdl20.xml,1.235,1.236

From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 02 May 2005 02:30:35 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DSQhf-0001Be-Vw@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20.xml 
Log Message:
[LC120] Clarified description of include and import, removed contradictions, and added references to QName resolution.

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.235
retrieving revision 1.236
diff -C2 -d -r1.235 -r1.236
*** wsdl20.xml	2 May 2005 00:02:51 -0000	1.235
--- wsdl20.xml	2 May 2005 02:30:33 -0000	1.236
***************
*** 1199,1204 ****
        	Definition components are directly contained in the
        	Description component and are referred to as
!       	<emph>top level components</emph>. 
!       	The top level WSDL 2.0 components contain other components, e.g.
        	Interface Operation and Endpoint, which are referred to as
        	<emph>nested components</emph>. Nested components may contain
--- 1199,1204 ----
        	Definition components are directly contained in the
        	Description component and are referred to as
!       	<emph>top-level components</emph>. 
!       	The top-level WSDL 2.0 components contain other components, e.g.
        	Interface Operation and Endpoint, which are referred to as
        	<emph>nested components</emph>. Nested components may contain
***************
*** 1404,1415 ****
  </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">
  <p>
         Let <z:i>DescriptionKeys</z:i> express the
--- 1404,1428 ----
  </z:notation>
  
!        <p diff="chg">
!        	The set of top-level components contained in the Description
!        	component associated with an initial WSDL 2.0 document
!        	consists of the components defined in the initial document
!        	and the components associated with the documents that the
!        	initial document includes or imports. The component model
!        	makes no distinction between the components that are defined
!        	in the initial document versus those that are defined in the
!        	included or imported documents. However, any WSDL 2.0
!        	document that contains component definitions that refer by
!        	QName to WSDL 2.0 components that belong to a different
!        	namespace MUST contain a
!        	<el>ws:import</el>
!        	&EII;
!        	for that namespace
!        	(see <specref ref="imports" />). 
!        	Furthermore, all QName references, whether to the same or
!        	to different namespaces MUST resolve to components (see <specref ref="qnameres"/>).
!        </p>
  
!        <z:notation name="DescriptionKeys">
  <p>
         Let <z:i>DescriptionKeys</z:i> express the
***************
*** 2190,2194 ****
  			The set of Interface components resolved to
  			by the values in the <att>extends</att> &AII;
! 			if any.
  			</td>
  		  </tr>
--- 2203,2207 ----
  			The set of Interface components resolved to
  			by the values in the <att>extends</att> &AII;
! 			if any (see <specref ref="qnameres"/>).
  			</td>
  		  </tr>
***************
*** 2557,2561 ****
                          <specref ref='Description_details' /> resolved
                          to by the value of the <att>element</att>
!                         &AII; if present, otherwise empty. It is an
                          error for the <att>element</att> &AII; to have
                          a value and for it to not resolve to a global
--- 2570,2575 ----
                          <specref ref='Description_details' /> resolved
                          to by the value of the <att>element</att>
!                         &AII; if present (see <specref ref="qnameres"/>), otherwise empty. 
!                         It is an
                          error for the <att>element</att> &AII; to have
                          a value and for it to not resolve to a global
***************
*** 3445,3449 ****
                          declarations} property of <specref
                          ref='Description_details' /> resolved to by
!                         the value of the <att>element</att> &AII;,
                          otherwise empty. It is an error for the
                          <att>element</att> &AII; to have a value and
--- 3459,3463 ----
                          declarations} property of <specref
                          ref='Description_details' /> resolved to by
!                         the value of the <att>element</att> &AII; (see <specref ref="qnameres"/>),
                          otherwise empty. It is an error for the
                          <att>element</att> &AII; to have a value and
***************
*** 4744,4748 ****
  		    definition from the {type definitions} property of
  		    <specref ref='Description_details' /> resolved to
! 		    by the value of the <el>constraint</el> &EII;.
  		    Otherwise, if the <el>value</el> &EII; is present,
  		    the token <emph>#value</emph>, otherwise empty.
--- 4758,4762 ----
  		    definition from the {type definitions} property of
  		    <specref ref='Description_details' /> resolved to
! 		    by the value of the <el>constraint</el> &EII; (see <specref ref="qnameres"/>).
  		    Otherwise, if the <el>value</el> &EII; is present,
  		    the token <emph>#value</emph>, otherwise empty.
***************
*** 5100,5104 ****
  			<td>
  			The Interface component resolved to by the actual value
! 			of the <att>interface</att> &AII;, if any.
  			</td>
                    </tr>
--- 5114,5118 ----
  			<td>
  			The Interface component resolved to by the actual value
! 			of the <att>interface</att> &AII; (see <specref ref="qnameres"/>), if any.
  			</td>
                    </tr>
***************
*** 6545,6549 ****
  			<phrase>
  			The Interface component resolved to by the actual value of
! 			the <att>interface</att> &AII;.
  			</phrase>
  			</td>
--- 6559,6563 ----
  			<phrase>
  			The Interface component resolved to by the actual value of
! 			the <att>interface</att> &AII; (see <specref ref="qnameres"/>).
  			</phrase>
  			</td>
***************
*** 6872,6876 ****
  			<td>
  			The Binding component resolved to by the actual value of
! 			the <att>binding</att> &AII;.
  			</td>
  		  </tr>
--- 6886,6890 ----
  			<td>
  			The Binding component resolved to by the actual value of
! 			the <att>binding</att> &AII; (see <specref ref="qnameres"/>).
  			</td>
  		  </tr>
***************
*** 7378,7382 ****
  		
  		<p diff="add">
! 			It is an error if a QName is not resolved. When resolving
  			QNames references for schema definitions, the namespace MUST
  			be imported by the referring WSDL 2.0 document. If the namespace
--- 7392,7396 ----
  		
  		<p diff="add">
! 			It is an error if a QName is not resolved (see <specref ref="qnameres"/>). When resolving
  			QNames references for schema definitions, the namespace MUST
  			be imported by the referring WSDL 2.0 document. If the namespace
***************
*** 7566,7571 ****
  A mutual include is direct inclusion by one WSDL 2.0 document of another
  WSDL 2.0 document which includes the first.  A circular include achieves
! the same effect with greater indirection (WSDL 2.0 document A includes WSDL 2.0 document B
! includes WSDL 2.0 document A, for instance).  Multiple inclusion of a single WSDL 2.0
  document resolves to a single set of components.  Mutual, multiple,
  and circular includes are explicitly permitted, and do not represent
--- 7580,7585 ----
  A mutual include is direct inclusion by one WSDL 2.0 document of another
  WSDL 2.0 document which includes the first.  A circular include achieves
! the same effect with greater indirection (A includes  B
! includes C includes A, for instance).  Multiple inclusion of a single WSDL 2.0
  document resolves to a single set of components.  Mutual, multiple,
  and circular includes are explicitly permitted, and do not represent
***************
*** 7648,7653 ****
  </eg>
  
! <p>Every top level WSDL 2.0 component is associated with a target namespace. 
! On its <el>description</el> &EII;, WSDL 2.0 document carries a 
  <att>targetNamespace</att> &AII; that associates the document with a 
  target namespace. This section describes the syntax and mechanisms by 
--- 7662,7667 ----
  </eg>
  
! <p>Every top-level WSDL 2.0 component is associated with a target namespace. 
! On its <el>ws:description</el> &EII;, WSDL 2.0 documents carries a 
  <att>targetNamespace</att> &AII; that associates the document with a 
  target namespace. This section describes the syntax and mechanisms by 
***************
*** 7660,7668 ****
  
  <p>The WSDL 2.0 <el>import</el> &EII; is modeled after the 
! XML Schema <el>import</el> &EII; (see <bibref ref="XMLSchemaP1"/>, 
  section 4.2.3 "References to schema components across namespaces"). 
! The WSDL 2.0 <el>import</el> &EII; identifies namespaces used in 
! foreign references. The existence of the WSDL 2.0 <el>import</el> &EII; 
  signals that the WSDL 2.0 document may contain references to foreign components.
  </p>
  
--- 7674,7683 ----
  
  <p>The WSDL 2.0 <el>import</el> &EII; is modeled after the 
! XML Schema <el>xs:import</el> &EII; (see <bibref ref="XMLSchemaP1"/>, 
  section 4.2.3 "References to schema components across namespaces"). 
! The WSDL 2.0 <el>ws:import</el> &EII; identifies namespaces used in 
! foreign references. The existence of the WSDL 2.0 <el>ws:import</el> &EII; 
  signals that the WSDL 2.0 document may contain references to foreign components.
+ The <el>ws:import</el> &EII; is therefore like a forward declaration for other namespaces.
  </p>
  
***************
*** 7670,7674 ****
  components from another namespace available to a WSDL 2.0 document. 
  That is, a WSDL 2.0 document can only refer to components in a 
! namespace other than its own target namespace if and only if the 
  WSDL 2.0 document contains an <el>import</el> &EII; for 
  that foreign namespace.
--- 7685,7689 ----
  components from another namespace available to a WSDL 2.0 document. 
  That is, a WSDL 2.0 document can only refer to components in a 
! namespace other than its own target namespace if the 
  WSDL 2.0 document contains an <el>import</el> &EII; for 
  that foreign namespace.
***************
*** 9590,9593 ****
--- 9605,9615 ----
      	<td>20050501</td>
      	<td>AGR</td>
+     	<td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC120">LC120</loc>:
+     	Clarified description of include and import, removed contradictions, and added references to QName resolution.</td>
+     </tr>
+ 
+     <tr>
+     	<td>20050501</td>
+     	<td>AGR</td>
      	<td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC116">LC116</loc>:
      	Clarified that <att>schemaLocation</att> is not required if the namespace has been resolved in the component model.
Received on Monday, 2 May 2005 02:30:39 UTC

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