- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 07 Apr 2005 15:04:22 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv5103
Modified Files:
wsdl20.xml
Log Message:
Moved paragraphs 6-9 of section 2.1.1 into 2.1.2
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.197
retrieving revision 1.198
diff -C2 -d -r1.197 -r1.198
*** wsdl20.xml 5 Apr 2005 10:31:46 -0000 1.197
--- wsdl20.xml 7 Apr 2005 15:04:20 -0000 1.198
***************
*** 1237,1276 ****
distinction between directly defined components
vs. imported/included components.</p>
-
- <p>The components directly defined or included within a Description
- component are said to belong to the same <emph>target
- namespace</emph>. 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
- <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
- (which may be combined as needed via <specref
- ref='includes'/>), then the <att>targetNamespace</att> &AII;
- SHOULD resolve to a master document which includes all the
- WSDL documents needed for that service description. This
- approach enables the WSDL component designators' fragment
- identifiers to be properly resolvable.</p>
-
- <p>Imported components have different target namespace values
- from the Description component that is importing them. Thus
- importing is the mechanism to use components from one namespace
- in another set of definitions.</p>
-
- <p>Each WSDL or type system component MUST be uniquely
- identified by its qualified name. That is, if two distinct
- components of the same kind (Interface, Binding etc.) are in
- the same target namespace, then their QNames MUST be
- unique. However, different kinds of components (e.g., an
- Interface component and a Binding component) MAY have the same
- QName. Thus, QNames of components must be unique within the
- space of those components in a given target namespace.</p>
<z:notation name="DescriptionKeys">
--- 1237,1240 ----
***************
*** 1337,1341 ****
--- 1301,1342 ----
ref='imports' /> corresponds to a collection with components
drawn from multiple target namespaces.
+
+ <p>The components directly defined or included within a Description
+ component are said to belong to the same <emph>target
+ namespace</emph>. 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
+ <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
+ (which may be combined as needed via <specref
+ ref='includes'/>), then the <att>targetNamespace</att> &AII;
+ SHOULD resolve to a master document which includes all the
+ WSDL documents needed for that service description. This
+ approach enables the WSDL component designators' fragment
+ identifiers to be properly resolvable.</p>
+
+ <p>Imported components have different target namespace values
+ from the Description component that is importing them. Thus
+ importing is the mechanism to use components from one namespace
+ in another set of definitions.</p>
+
+ <p>Each WSDL or type system component MUST be uniquely
+ identified by its qualified name. That is, if two distinct
+ components of the same kind (Interface, Binding etc.) are in
+ the same target namespace, then their QNames MUST be
+ unique. However, different kinds of components (e.g., an
+ Interface component and a Binding component) MAY have the same
+ QName. Thus, QNames of components must be unique within the
+ space of those components in a given target namespace.</p>
</p>
+
<p>
The targetNamespace URI MUST be an absolute URI (see <bibref
***************
*** 8898,8901 ****
--- 8899,8910 ----
<tr>
+ <td>20050407</td>
+ <td>JJM</td>
+ <td>
+ Moved paragraphs 6-9 of section 2.1.1 into 2.1.2.
+ </td>
+ </tr>
+
+ <tr>
<td>20050331</td>
<td>AGR</td>
Received on Thursday, 7 April 2005 15:04:23 UTC