- From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
- Date: Thu, 07 Sep 2006 12:00:12 +0200
- To: "John Kaputin (gmail)" <jakaputin@gmail.com>
- Cc: www-ws-desc@w3.org, John Kaputin <KAPUTIN@uk.ibm.com>, woden-dev@ws.apache.org
Looks good to me. Thanks John. JJ. John Kaputin (gmail) wrote: > Jean-Jacques suggestion is fine by me - same semantics, just moved to > a different place. > > However, I had a look at the way defaulting relationships are > described elsewhere in Part 2:- > The relationship between {soap mep} and {soap mep default} is > described in section 5.10.3 SOAP 1.2 Binding Rules. > The reletationship between {http method} and {http method default} is > described in section 6.3.1 HTTP Binding Rules. > > Perhaps for consistency the defaulting rules for {http transfer > coding} and {http tansfer coding default} should be described in a > similar section. The correct section seems to be 6.3.1 HTTP Binding > Rules. This section appears before HTTP transfer coding is formerly > introduced in section 6.8, but the same situation exists for HTTP > method which is not formerly introduced until section 6.4 but has its > defaulting rules described in section 6.3 (one solution would be to > move the entire section 6.3 further down the document). > > So, I'd like to make a third suggestion for http transfer coding: > insert a new section 6.3.2 HTTP Transfer Coding Selection (and > renumber the subsequent 6.3.x sections), thus: > > <begin> > > 6.3.2 HTTP Transfer Coding Selection > > When formulating the HTTP message to be transmitted, the HTTP transfer > coding used MUST be selected using one of the following: > > * > > For a given Binding Message Reference component whose {http > transfer coding} property has a value, then the value of the > {http transfer coding} property. > > * > > Otherwise, the value of the parent Binding Operation component's > {http transfer coding default} property, if any. > > * Otherwise, the value of the grandparent Binding component's > {http transfer coding default} property, if any. > > > When formulating the HTTP fault message to be transmitted, the HTTP > transfer coding used MUST be selected using one of the following: > > * > > For a given Binding Fault component whose {http transfer coding} > property has a value, then the value of the {http transfer > coding} property. > > * Otherwise, the value of the parent Binding component's {http > transfer coding default} property, if any. > > > <end> > > You could add an "Otherwise none" or "Otherwise empty" at the end of > each list per Jean-Jacques suggestion if that is the correct HTTP > behaviour. > > regards, > John Kaputin. > > > On 9/7/06, *Jean-Jacques Moreau* <jean-jacques.moreau@crf.canon.fr > <mailto:jean-jacques.moreau@crf.canon.fr>> wrote: > > > Regarding the last 2 bullets, I suggest we move the defaulting instead > to Table 6-8, part 1 style (incidentally, I notice we don't follow > that > convention in most of Part 2): > > Part 2, table 6-8, {http transfer coding} property@Binding Message > Reference component: > <current> > The actual value of the |whttp:transferCoding| /attribute information > item/ of the |input| or |output| /element information item/, if > present. > </current> > <suggested> > The actual value of the |whttp:transferCoding| /attribute information > item/ of the |input| or |output| /element information item/, if > present. > Otherwise, the value of the {http transfer coding default} > property of > the parent Binding Operation component, if present. Otherwise the > value > of the {http transfer coding default} property of the grandparent > Binding component, if present. Otherwise empty. > </suggested> > > Similary, {http transfer coding} property@Binding Fault component: > <current> > The actual value of the |whttp:transferCoding| /attribute information > item/ of the |fault| /element information item/, if present. > </current> > <suggested> > The actual value of the |whttp:transferCoding| /attribute information > item/ of the |fault| /element information item/, if present. > Otherwise, > the value of the {http transfer coding default} property of the > parent > Binding component. Otherwise empty. > </suggested> > > The "Otherwise empty" may be overkill. > > JJ. > > John Kaputin (gmail) wrote: > > I have an action item for CR055 to propose some new text for Part 2 > > Section 6.8.2. based on a mailing list thread [1] I started on May > > 26th 2006 to clarify the way {http transfer coding} and {http > transfer > > coding default} are described. My proposal follows, based on > responses > > from Jacek on June 8th & 9th. > > > > <begin> > > > > > > 6.8.2 Relationship to WSDL Component Model > > > > The HTTP binding extension specification adds the following > properties > > to the WSDL component model (as defined in [WSDL 2.0 Core Language > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20-adjuncts.html?content-type=text/html;%20charset=utf-8#WSDL-PART1>]): > > > > * > > > > {http transfer coding default} OPTIONAL. A /xs:string/ to the > > Binding > > > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-Binding > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-Binding>> > > component. This property indicates the default transfer > codings > > available for all Binding Message Reference > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-InterfaceMessageReference> > > and Binding Fault > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-InterfaceFaultReference> > > components of this Binding > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-Binding> > > component. > > > > * > > > > {http transfer coding default} OPTIONAL. A /xs:string/ to the > > Binding Operation > > > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingOperation > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingOperation>> > > component. This property indicates the default transfer > codings > > available for all Binding Message Reference > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingMessageReference> > > components of this Binding Operation > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingOperation> > > component. > > > > * > > > > {http transfer coding} OPTIONAL. A /xs:string/ to the Binding > > Message Reference > > > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingMessageReference > <http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingMessageReference>> > > component. This property indicates the transfer codings > > available for this Binding Message Reference > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingMessageReference> > > component. If this property is not present, transfer > coding for > > this Binding Message Reference defaults to the {http transfer > > coding default} property of the parent Binding Operation > > component and if that property is not present, then to the > {http > > transfer coding default} property of the grandparent Binding > > component, if present. > > > > * > > > > Similarly, {http transfer coding} OPTIONAL, to the Binding > Fault > > < > http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/ws/desc/wsdl20/wsdl20.html#component-BindingFault> > > component. If this property is not present, transfer > coding for > > this Binding Fault defaults to the {http transfer coding > > default} property of the parent Binding component. > > > > These properties are not relevant when HTTP 1.0 is used. > > > > > > <end> > > > > I think this text describes the data relationships correctly, but > > please rewrite it if it doesn't conform to the style or structure > > conventions of the spec. > > > > > [1] http://lists.w3.org/Archives/Public/www-ws-desc/2006May/0087.html > <http://lists.w3.org/Archives/Public/www-ws-desc/2006May/0087.html> > > > > regards, > > John Kaputin > > (Apache Woden developer) > > > > >
Received on Thursday, 7 September 2006 10:00:37 UTC