W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2005

Proposed Text for LC344#5: Operation Style

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Fri, 21 Oct 2005 08:43:37 -0400
To: www-ws-desc@w3.org
Message-ID: <OFB8F4D79C.9084F6C4-ON852570A0.007E6552-852570A1.0045E771@ca.ibm.com>
Here's my proposed text to be incorporated into the section on Operation 
Styles[1] to resolve LC344 comment 5[2]


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 how a client 
interacts 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 {style} property of 
the Operation component contains a set of zero or more URIs that identify 
operation styles. An Operation component MUST satisfy the specification 
defined by each operation style identified by its {style} property. Two 
operation styles are mutually incompatible if no Operation component can 
simultaneously satisfy them both. Any Operation component whose {style} 
property contains a pair of mutually incompatible operation style URIs is 
therefore invalid.

[1] http://www.w3.org/TR/2005/WD-wsdl20-20050803/#InterfaceOperationStyle
[2] http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Received on Friday, 21 October 2005 12:44:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:37 GMT