W3C home > Mailing lists > Public > www-ws-desc@w3.org > September 2006

Re: CR044 update

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Thu, 21 Sep 2006 09:33:24 -0400
To: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
Message-ID: <OF4C4EBCCB.51FC6D09-ON852571F0.004A377A-852571F0.004A77D2@ca.ibm.com>
+1
Looks good.

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



Roberto Chinnici <Roberto.Chinnici@Sun.COM> 
Sent by: www-ws-desc-request@w3.org
09/20/2006 11:41 PM

To
www-ws-desc@w3.org
cc

Subject
CR044 update







With respect to CR044 [1], I'd like to reiterate my proposal [2]  with 
the addition of a change to section 2.9.1 of Part 1 [3], as suggested by 
Jacek in [4] and further discussed in [5].

Here is the proposed change to 2.9.1:

Replace

[[
A  Binding component that defines bindings for an Interface component 
MUST define bindings for all the operations of that Interface 
<
http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-Interface
> 
component. The bindings may occur via defaulting rules which allow one 
to specify default bindings for all operations (see, for example [WSDL 
2.0 Adjuncts]) or by directly listing each Interface Operation component 
of the Interface component and defining bindings for them. Thus, a 
Binding component MUST define bindings for all the Interface Operation 
components of the Interface component that the Binding component 
purportedly defines bindings for.
]]

with

[[
A  Binding component that defines bindings for an Interface component 
MUST define bindings for all the operations and all the faults of that 
Interface component. The bindings may occur via defaulting rules which 
allow one to specify default bindings for all operations and faults 
(see, for example [WSDL 2.0 Adjuncts]) or by directly listing each 
Interface Operation component and each Interface Fault component of the 
Interface component and defining bindings for them. Thus, a Binding 
component MUST define bindings for all the Interface Operation and 
Interface Fault components of the Interface component that the Binding 
component purportedly defines bindings for.

Similarly, whenever a reusable Binding component (i.e. one that does not 
specify an Interface component) is applied to a specific Interface 
component in the context of an Endpoint component, the Binding component 
MUST define bindings for all the Interface Operation and Interface Fault 
components of the Interface component via a combination of properties 
defined on the Binding component itself and default binding rules 
specific to its binding type.
]]

As to the other elements of [2], I stand by my statements in [4] re the 
undesirability of removing all mentions of Interface components from the 
text in [2], which IMO wouldn't make the text either more correct or 
more immediately comprehensible.

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/#CR044
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2006Jul/0046.html
[3] 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html#Binding_details

[4] http://lists.w3.org/Archives/Public/www-ws-desc/2006Jul/0055.html
[5] http://lists.w3.org/Archives/Public/www-ws-desc/2006Jul/0057.html

Thanks,
Roberto
Received on Thursday, 21 September 2006 13:33:36 GMT

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