- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 10 Nov 2005 05:38:21 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv14000
Modified Files:
wsdl20.xml
Log Message:
LC344#5: Incorporated text regarding mutually exclusive operation styles, as per Tokyo f2f.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.346
retrieving revision 1.347
diff -C2 -d -r1.346 -r1.347
*** wsdl20.xml 9 Nov 2005 01:20:00 -0000 1.346
--- wsdl20.xml 10 Nov 2005 05:38:19 -0000 1.347
***************
*** 3440,3447 ****
<div4 id="InterfaceOperationStyle">
<head>Operation Style</head>
<p>If the <prop comp="Interface Operation">style</prop> property of an
<comp>Interface Operation</comp> component
! has a value then that value (a set of IRIs) implies the rules that
were used to define the
<prop comp="Interface Message Reference">element declaration</prop> properties (or other
--- 3440,3461 ----
<div4 id="InterfaceOperationStyle">
<head>Operation Style</head>
+ <p>An operation style specifies additional information about an operation.
+ For example, an operation style may define constraints on the element
+ declarations used by the interface message reference components of the
+ operation. This additional information in no way affects the messages
+ exchanged with the service and it may therefore be safely ignored in that
+ context. However, the additional information may be used for other
+ purposes, for example, improved code generation. The
+ <prop comp="Interface Operation">style</prop> property of
+ the <comp>Interface Operation</comp> component contains a set of zero or more IRIs that identify
+ operation styles. An <comp>Interface Operation</comp> component MUST satisfy the specification
+ defined by each operation style identified by its
+ <prop comp="Interface Operation">style</prop> property.
+ If no <comp>Interface Operation</comp> component can simultaneously satisfy all of the styles,
+ the document is invalid.</p>
<p>If the <prop comp="Interface Operation">style</prop> property of an
<comp>Interface Operation</comp> component
! does have a value, then that value (a set of IRIs) implies the rules that
were used to define the
<prop comp="Interface Message Reference">element declaration</prop> properties (or other
***************
*** 3454,3468 ****
for an operation, it MAY choose to contrain only the former or
the latter or any combination thereof.</p>
-
- <p>Note that the property MAY not have any value. If this
- property has a value (a set of IRIs), then for each individual
- IRI that is an element of that set, the rules implied by
- that IRI (such as rules that govern the schemas) MUST be followed
- or it is an error. So, if the set of IRIs has more than one item in
- it, then the rules implied by ALL the IRIs must be adhered to
- by the content definitions.</p>
! <p>Refer to the <emph>WSDL Version 2.0 Part 2: Adjuncts</emph> specification <bibref ref="WSDL-PART2"/>
! for operation style definitions.</p>
</div4>
--- 3468,3475 ----
for an operation, it MAY choose to contrain only the former or
the latter or any combination thereof.</p>
! <p>Please refer to the <emph>WSDL Version 2.0 Part 2: Adjuncts</emph>
! specification <bibref ref="WSDL-PART2"/>
! for particular operation style definitions.</p>
</div4>
***************
*** 12403,12406 ****
--- 12410,12420 ----
<tr>
+ <td>20051110</td>
+ <td>JJM</td>
+ <td><loc href="http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344">LC344#5</loc>
+ : Incorporated text regarding mutually exclusive operation styles, as per Tokyo f2f.</td>
+ </tr>
+
+ <tr>
<td>20051103</td>
<td>AGR</td>
Received on Thursday, 10 November 2005 05:38:25 UTC