- From: Kevin Liu <kliu@dev.w3.org>
- Date: Fri, 10 Sep 2004 07:36:42 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv22831/ws/desc/wsdl20
Modified Files:
wsdl20-primer.xml
Log Message:
fixes some typos/errors in examples. add more ednotes identifying places where more examples are desired
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** wsdl20-primer.xml 3 Aug 2004 14:26:38 -0000 1.10
--- wsdl20-primer.xml 10 Sep 2004 07:36:40 -0000 1.11
***************
*** 197,202 ****
</item>
</ulist>
! <eg xml:space="preserve">
! <definitions targetNamespace="<emph>xs:anyURI</emph>" >
<documentation />?
--- 197,203 ----
</item>
</ulist>
!
! <eg xml:space="preserve">
! <definitions targetNamespace="<emph>xs:anyURI</emph>" >
<documentation />?
***************
*** 213,240 ****
</types>
! <interface name="<emph>xs:NCName</emph>" extends="<emph>list of xs:QName</emph>"? styleDefault="<emph>xs:anyURI</emph>"? >
<documentation />?
<fault name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>"? >
<documentation />?
</fault>*
! <operation name="<emph>xs:NCName</emph>" pattern="<emph>xs:anyURI</emph>" style="<emph>xs:anyURI</emph>"? safe="<emph>xs:boolean</emph>"? >
<documentation />?
<input messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
<documentation />?
</input>*
<output messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
<documentation />?
</output>*
<infault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
</infault>*
<outfault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
</outfault>*
--- 214,261 ----
</types>
! <interface name="<emph>xs:NCName</emph>" extends="<emph>list of xs:QName</emph>"? styleDefault="<emph>list of xs:anyURI</emph>"? >
<documentation />?
<fault name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</fault>*
! <operation name="<emph>xs:NCName</emph>" pattern="<emph>xs:anyURI</emph>" style="<emph>list of xs:anyURI</emph>"? safe="<emph>xs:boolean</emph>"? >
<documentation />?
<input messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</input>*
<output messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</output>*
<infault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</infault>*
<outfault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</outfault>*
***************
*** 257,265 ****
</interface>*
! <binding name="<emph>xs:NCName</emph>" interface="<emph>xs:QName</emph>"? >
<documentation />?
<fault ref="<emph>xs:QName</emph>" >
<documentation />?
</fault>*
--- 278,290 ----
</interface>*
! <binding name="<emph>xs:NCName</emph>" interface="<emph>xs:QName</emph>"? type="<emph>xs:anyURI</emph>" >
<documentation />?
<fault ref="<emph>xs:QName</emph>" >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</fault>*
***************
*** 269,276 ****
--- 294,309 ----
<input messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</input>*
<output messageLabel="<emph>xs:NCName</emph>"? >
<documentation />?
+
+ <feature ... />*
+
+ <property ... />*
</output>*
***************
*** 285,297 ****
</binding>*
! <service name="<emph>xs:NCName</emph>" interface="<emph>xs:QName</emph>"
<documentation />?
! <endpoint name="<emph>xs:NCName</emph>" binding="<emph>xs:QName</emph>" >
<documentation />?
! </endpoint>+
</service>*
</definitions>
</eg>
<p>As specified in section 6 of Part1, WSDL allows extensions to be defined in terms of both elements and attributes. Firstly, WSDL allows namespace-qualified elements
whose namespace is NOT "http://www.w3.org/2004/03/wsdl" to appear among the children of specific elements whose [namespace name] is "http://www.w3.org/2004/03/wsdl". Secondly, WSDL allows qualified attributes whose namespace is NOT "http://www.w3.org/2004/03/wsdl" to appear on any elements whose namespace is "http://www.w3.org/2004/03/wsdl". See more about extensibility in section@@@@. Since extensions can appear in all the places, they are not explicitly indicated in the above syntax and will not be mentioned again in later sections where a particular construct is explained. </p>
--- 318,339 ----
</binding>*
! <service name="<emph>xs:NCName</emph>" interface="<emph>xs:QName</emph>" >
<documentation />?
! <endpoint name="<emph>xs:NCName</emph>" binding="<emph>xs:QName</emph>" address="<emph>xs:anyURI</emph>"? >
<documentation />?
!
! <feature ... />*
!
! <property ... />*
! </endpoint>*
!
! <feature ... />*
!
! <property ... />*
</service>*
</definitions>
</eg>
+
<p>As specified in section 6 of Part1, WSDL allows extensions to be defined in terms of both elements and attributes. Firstly, WSDL allows namespace-qualified elements
whose namespace is NOT "http://www.w3.org/2004/03/wsdl" to appear among the children of specific elements whose [namespace name] is "http://www.w3.org/2004/03/wsdl". Secondly, WSDL allows qualified attributes whose namespace is NOT "http://www.w3.org/2004/03/wsdl" to appear on any elements whose namespace is "http://www.w3.org/2004/03/wsdl". See more about extensibility in section@@@@. Since extensions can appear in all the places, they are not explicitly indicated in the above syntax and will not be mentioned again in later sections where a particular construct is explained. </p>
***************
*** 432,436 ****
<date>20040517</date>
<edtext>
! Need clarification - what should be the "appropriate value" for schemalocation in this case? Also need provide more explanation and examples to cover different importing cases
</edtext>
</ednote>
--- 474,480 ----
<date>20040517</date>
<edtext>
! <p>Add Example - illustrate use of xs:import and xs:include for embedded schema</p>
!
! <p>Clarification - what should be the "appropriate value" for schemalocation, especially when its's xs:include? </p>
</edtext>
</ednote>
***************
*** 454,458 ****
<eg xml:space="preserve">
! <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl" >
<documentation>
--- 498,506 ----
<eg xml:space="preserve">
! <definitions
! targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
<documentation>
***************
*** 543,546 ****
--- 591,603 ----
</ulist>
<p>While the in-bound MEPs are easier to understand, there have been questions concerning the usefulness of out-bound MEPs, especially how a service can specify the endpoint information for the target node of the initial out-bound message. In their typical use cases, such as in large scale intergration projects where endpoint information is most likely specified at deployment or runtime by mapping and routing facilities, or/and in languages that facilitate services composition where only abstract interfaces are concerned, Out-bound MEPs are useful in the abstract level for fully specifying the functionality of a service, including its requirements for its potential customers, so application integrator can gain a better understanding of how multiple services may be used together, wherea binding and endpoint information may be provided by integration infrastructure in application deployment and runtime.</p>
+ <ednote>
+ <name>KevinL</name>
+ <date>20040910</date>
+ <edtext>
+ <p>Add more use cases and example - illustrate use of outbound meps</p>
+
+ </edtext>
+ </ednote>
+
<p>Equipped with the knowledge of all the MEPs defined in WSDL2.0, Joe has analyzed the list of requirements he has in hand and decided that the in-out MEP covers his requirement pretty well. Now he can move on to define the interface for the reservation Web service.</p>
</div2>
***************
*** 552,598 ****
<definitions targetNamespace="<emph>xs:anyURI</emph>" >
! <<b>interface</b> name="<emph>xs:NCName</emph>" extends="<emph>list of xs:QName</emph>"? styleDefault="<emph>xs:anyURI</emph>"? >
! <documentation />?
! <fault name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>"? >
! <documentation />?
! </fault>*
! <operation name="<emph>xs:NCName</emph>" pattern="<emph>xs:anyURI</emph>" style="<emph>xs:anyURI</emph>"? safe="<emph>xs:boolean</emph>"? >
! <documentation />?
! <input messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
! <documentation />?
! </input>*
! <output messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
! <documentation />?
! </output>*
! <infault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
! <documentation />?
! </infault>*
! <outfault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
! <documentation />?
! </outfault>*
! <feature ... />*
! <property ... />*
! </operation>*
! <feature uri="<emph>xs:anyURI</emph>" required="<emph>xs:boolean</emph>"? >
! <documentation />?
! </feature>*
! <property uri="<emph>xs:anyURI</emph>" required="<emph>xs:boolean</emph>"? >
! <documentation />?
- <value> <emph>xs:anyType</emph> </value>?
-
- <constraint> <emph>xs:QName</emph> </constraint>?
- </property>*
- </<b>interface</b>>*
</definitions >
--- 609,676 ----
<definitions targetNamespace="<emph>xs:anyURI</emph>" >
! <interface name="<emph>xs:NCName</emph>" extends="<emph>list of xs:QName</emph>"? styleDefault="<emph>list of xs:anyURI</emph>"? >
! <documentation />?
! <fault name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>"? >
! <documentation />?
! <feature ... />*
! <property ... />*
! </fault>*
! <operation name="<emph>xs:NCName</emph>" pattern="<emph>xs:anyURI</emph>" style="<emph>list of xs:anyURI</emph>"? safe="<emph>xs:boolean</emph>"? >
! <documentation />?
! <input messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
! <documentation />?
! <feature ... />*
! <property ... />*
! </input>*
! <output messageLabel="<emph>xs:NCName</emph>"? element="<emph>union of xs:QName, xs:Token</emph>"? >
! <documentation />?
! <feature ... />*
! <property ... />*
! </output>*
!
! <infault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
! <documentation />?
!
! <feature ... />*
!
! <property ... />*
! </infault>*
!
! <outfault ref="<emph>xs:QName</emph>" messageLabel="<emph>xs:NCName</emph>"? >
! <documentation />?
!
! <feature ... />*
!
! <property ... />*
! </outfault>*
!
! <feature ... />*
!
! <property ... />*
! </operation>*
!
! <feature uri="<emph>xs:anyURI</emph>" required="<emph>xs:boolean</emph>"? >
! <documentation />?
! </feature>*
!
! <property uri="<emph>xs:anyURI</emph>" required="<emph>xs:boolean</emph>"? >
! <documentation />?
!
! <value> <emph>xs:anyType</emph> </value>?
!
! <constraint> <emph>xs:QName</emph> </constraint>?
! </property>*
! </interface>*
</definitions >
***************
*** 606,609 ****
--- 684,695 ----
<p>Two things about extending interfaces deserve some attention. The first is about name collision. There may be cases where, due to an interface extending one or more other interfaces,operations from different interface may have name collision. More precisely, within a same namespace, two or more interface operations may have the same name. In such cases, WSDL2.0 requires that the component models of those Interface Operation components MUST be equivalent (Component Equivalence is defined in Part 1 section 2.15 Equivalence of Components. For operations, basically equivalence means the two operations in question have same set of attributes and decedents). If the collisional operations are equivalent then they are considered to collapse into a single operation. It is an error if they are not equivalent. In other words, if two interfaces have name collisional operations, then those two interfaces cannot both form part of the derivation chain of a derived interface unless those operations are exactly he same. For the above reason, it is considered good practic to ensure that all operations within a same namespace are named uniquely whenever possible. Since faults, features and properties can also be defined as children of <el>interface</el> as one can see in later sections, the same name-collision resolution rules apply to those constructs.</p>
<p>The second is about recursive extension of interfaces. It's disallowed. The interfaces a given interface extends MUST NOT themselves extend that interface either directly or indirectly.</p>
+ <ednote>
+ <name>KevinL</name>
+ <date>20040910</date>
+ <edtext>
+ <p>Add Example - illustrate use extends attribute</p>
+ </edtext>
+ </ednote>
+
<p>Now let's have a look at the children of <el>interface</el>. An <el>interface</el> can contain zero or more <el>fault</el>, zero or more <el>operation</el>, zero or more <el>feature</el>, and zero or more <el>property</el>. <el>feature</el> and <el>property</el> will be examined in section @@@@. We will explain the <el>fault</el> and <el>operation</el> constructs in the following sections. </p>
</div3>
***************
*** 617,622 ****
<eg xml:space="preserve">
! <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd">
<documentation>
--- 703,711 ----
<eg xml:space="preserve">
! <definitions
! targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
<documentation>
***************
*** 681,684 ****
--- 770,783 ----
<p>An optional <att>style</att> attribute</p>
<p>it's an absolute URI identifying the rules that were used to construct the message type definitions used by the <el>operation</el>. Note that the attribute MAY not present, but if it is present, then the rules implied by that value MUST be followed or it is an error. For example, WSDL 2.0 defines a set of rules for constructing so called RPC style messages(See section@@@@). If this attribute is set to "http://www.w3.org/2004/03/wsdl/style/rpc", then all the rules defined for RPC style must be followed. We will have a closer look at RPC style in section@@@. </p>
+ <ednote>
+ <name>KevinL</name>
+ <date>20040910</date>
+ <edtext>
+ <p>Add Example and more text - illustrate use of RPC style</p>
+
+ <p> </p>
+ </edtext>
+ </ednote>
+
</item>
<item>
***************
*** 693,699 ****
<head>Defining Interface Operations</head>
<eg xml:space="preserve">
! <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns = "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd">
<documentation>
--- 792,800 ----
<head>Defining Interface Operations</head>
<eg xml:space="preserve">
! <definitions
! targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
<documentation>
***************
*** 857,864 ****
<head>SOAP binding example placeholder - to be completed</head>
<eg xml:space="preserve">
- <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
- xmlns = "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
- xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd">
</definitions>
--- 958,967 ----
<head>SOAP binding example placeholder - to be completed</head>
<eg xml:space="preserve">
+ <definitions
+ targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
+ xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
+ xmlns = "http://www.w3.org/@@@@/@@/wsdl"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema">
</definitions>
***************
*** 871,878 ****
<head>HTTP Binding example placeholder - to be completed</head>
<eg xml:space="preserve">
! <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns = "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd">
!
</definitions>
--- 974,982 ----
<head>HTTP Binding example placeholder - to be completed</head>
<eg xml:space="preserve">
! <definitions
! targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
</definitions>
***************
*** 907,914 ****
<head>place holder - to be completed</head>
<eg xml:space="preserve">
! <definitions targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns = "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd">
!
--- 1011,1019 ----
<head>place holder - to be completed</head>
<eg xml:space="preserve">
! <definitions
! targetNamespace= "http://www.greath.com/2004/05/wsdl/reservationService.wsdl"
! xmlns:ghns = "http://www.greath.com/2004/05/schemas/reservationService.xsd"
! xmlns = "http://www.w3.org/@@@@/@@/wsdl"
! xmlns:xs="http://www.w3.org/2001/XMLSchema">
Received on Friday, 10 September 2004 07:36:43 UTC