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

Clarification needed on HTTP Transfer Coding

From: John Kaputin (gmail) <jakaputin@gmail.com>
Date: Fri, 26 May 2006 13:12:36 +0100
Message-ID: <4c2ae8f80605260512m7c946afbj13cd1c361889c1a0@mail.gmail.com>
To: www-ws-desc@w3.org
Cc: woden-dev@ws.apache.org, "John Kaputin" <KAPUTIN@uk.ibm.com>
Can someone please clarify some points about the http transer coding
extension properties defined in Part 2 section 6.8.2 Relationship to WSDL
Component Model [1]?

It says the Binding has a {http transfer coding default} property that is
available to InterfaceMessageReference and InterfaceFaultReference
components. Is this worded correctly? Do components from the abstract
interface need http binding information?

It also says BindingOperation has a {http transfer coding default} property
that is available to BindingMessageReference and BindingFault components. Is
'BindingFault' a mistake, should this say BindingFaultReference?

There are no semantic rules about the relationship between the two {http
transfer coding default}  properties (i.e. in Binding and BindingOperation),
so they could potentially be different. I don't think this would make sense,
but it seems to be possible according to the way this section is described.

Finally, there are no semantic rules about the relationship between
BindingOperation's {http transfer coding default} property and the {http
transfer coding} properties if its two child components. As an implementor I
can infer what that relationship might be, but it would be better if the
spec stated in explicitly as it does for default and actual extension
properties elsewhere.

[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html?content-type=text/html;%20charset=utf-8#http-transfer-coding-relate

regards,
John Kaputin.
Received on Friday, 26 May 2006 20:06:47 GMT

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