- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 15 Feb 2007 09:44:33 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv23988
Modified Files:
wsdl20-adjuncts.xml
Log Message:
CR044: Additional editorial work, item 2 part 2
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.225
retrieving revision 1.226
diff -C 2 -d -r1.225 -r1.226
*** wsdl20-adjuncts.xml 14 Feb 2007 18:36:11 -0000 1.225
--- wsdl20-adjuncts.xml 15 Feb 2007 09:44:30 -0000 1.226
***************
*** 1329,1333 ****
mapping from that representation to the various component
properties.</p>
!
<p>As allowed in <bibref ref="WSDL-PART1"/>, a <comp>Binding</comp> component
can exist without indicating a specific <comp>Interface</comp>
--- 1329,1333 ----
mapping from that representation to the various component
properties.</p>
!
<p>As allowed in <bibref ref="WSDL-PART1"/>, a <comp>Binding</comp> component
can exist without indicating a specific <comp>Interface</comp>
***************
*** 1336,1351 ****
<comp>Binding Fault</comp> component can be present in the <comp>Binding</comp>
component.</p>
-
- <p>The SOAP binding extension is designed with the objective of minimizing
- what needs to be explicitly declared for common cases. This is
- achieved by defining a set of default rules which apply to all
- <comp>Interface Operation</comp> components of an <comp>Interface</comp> component, unless
- specifically overridden on a per Interface Operation basis. Thus,
- if a given <comp>Interface Operation</comp> component is not referred to
- specifically, then all the default rules apply to that
- component. That is, per the requirements of <bibref
- ref="WSDL-PART1"/>, all operations of an <comp>Interface</comp> component are
- bound according to this binding extension.</p>
<p><b>Note:</b> As in other parts of this specification, we could have done
away with "default" properties at the component model level, and have set the value for the
--- 1336,1352 ----
<comp>Binding Fault</comp> component can be present in the <comp>Binding</comp>
component.</p>
+ <p>The SOAP binding extension is designed with the objective of minimizing
+ what needs to be explicitly declared for common cases. This is achieved
+ by defining a set of default rules that affect all <comp>Interface Operation</comp>
+ components of an <comp>Interface</comp> component to which the SOAP binding extension
+ is applied, unless specifically overridden by a <comp>Binding Operation</comp> component.
+ Thus, if a given <comp>Interface Operation</comp> component is not referred to
+ specifically by a <comp>Binding Operation</comp> component, then all the default
+ rules apply to that <comp>Interface Operation</comp> component. As a result, in
+ accordance with the requirements of <bibref ref="WSDL-PART1"/>, all
+ operations of an <comp>Interface</comp> component will be bound by this binding
+ extension.</p>
+
<p><b>Note:</b> As in other parts of this specification, we could have done
away with "default" properties at the component model level, and have set the value for the
***************
*** 1899,1903 ****
default SOAP Message Exchange Pattern (MEP) for all the
<comp>Interface Operation</comp> components of any <comp>Interface</comp> component
! that uses this <comp>Binding</comp> component.</p></item>
<item><p><propdef comp="Binding Operation">soap mep</propdef> OPTIONAL.
--- 1900,1904 ----
default SOAP Message Exchange Pattern (MEP) for all the
<comp>Interface Operation</comp> components of any <comp>Interface</comp> component
! to which this <comp>Binding</comp> is applied.</p></item>
<item><p><propdef comp="Binding Operation">soap mep</propdef> OPTIONAL.
***************
*** 2958,2974 ****
for these additional properties is provided, along with a mapping from
that representation to the various component properties.</p>
<p>As allowed in <bibref ref="WSDL-PART1"/>, a <comp>Binding</comp> component can
exist without indicating a specific <comp>Interface</comp> component that it applies
to and, in this case, no <comp>Binding Operation</comp> or <comp>Binding
Fault</comp> components can be present in the <comp>Binding</comp> component.</p>
! <p>The HTTP binding extension is designed with the objective of minimizing what
! needs to be explicitly declared for common cases. This is achieved by
! defining a set of default rules which apply for all <comp>Interface
! Operation</comp> components of an <comp>Interface</comp> component, unless specifically
! overridden on a per Interface Operation basis. Thus, if a given
! <comp>Interface Operation</comp> component is not referred to specifically, then
! all the default rules apply for that component. That is, per the
! requirements of <bibref ref="WSDL-PART1"/> all operations of an
! <comp>Interface</comp> component are bound by an HTTP binding.</p>
<p><b>Note:</b> As in other parts of this specification, we could have done
--- 2959,2980 ----
for these additional properties is provided, along with a mapping from
that representation to the various component properties.</p>
+
<p>As allowed in <bibref ref="WSDL-PART1"/>, a <comp>Binding</comp> component can
exist without indicating a specific <comp>Interface</comp> component that it applies
to and, in this case, no <comp>Binding Operation</comp> or <comp>Binding
Fault</comp> components can be present in the <comp>Binding</comp> component.</p>
!
! <p>The HTTP binding extension is designed with the objective of minimizing
! what needs to be explicitly declared for common cases. This is achieved
! by defining a set of default rules that affect all <comp>Interface Operation</comp>
! components of an <comp>Interface</comp> component to which the HTTP binding extension
! is applied, unless specifically overridden by a <comp>Binding Operation</comp>
! component.
! Thus, if a given <comp>Interface Operation</comp> component is not referred to
! specifically by a <comp>Binding Operation</comp> component, then all the default
! rules apply to that <comp>Interface Operation</comp> component. As a result, in
! accordance with the requirements of <bibref ref="WSDL-PART1"/>, all
! operations of an <comp>Interface</comp> component will be bound by this binding
! extension.</p>
<p><b>Note:</b> As in other parts of this specification, we could have done
***************
*** 3496,3501 ****
for the HTTP Request Method for all the
<comp>Interface Operation</comp> components of any
! <comp>Interface</comp> component that uses this Binding
! component.</p>
</item>
<item>
--- 3502,3506 ----
for the HTTP Request Method for all the
<comp>Interface Operation</comp> components of any
! <comp>Interface</comp> component to which this <comp>Binding</comp> is applied.</p>
</item>
<item>
***************
*** 3530,3535 ****
parameter separator character for all the
<comp>Interface Operation</comp> components of any
! <comp>Interface</comp> component that uses this Binding
! component.</p>
</item>
<item>
--- 3535,3539 ----
parameter separator character for all the
<comp>Interface Operation</comp> components of any
! <comp>Interface</comp> component to which this <comp>Binding</comp> is applied to.</p>
</item>
<item>
***************
*** 3538,3542 ****
to the <comp>Binding Operation</comp> component, indicating the query parameter
separator character for this <comp>Binding
! Operation</comp> component.</p>
</item>
</ulist>
--- 3542,3546 ----
to the <comp>Binding Operation</comp> component, indicating the query parameter
separator character for this <comp>Binding
! Operation</comp>.</p>
</item>
</ulist>
***************
*** 5652,5655 ****
--- 5656,5668 ----
<td>JJM</td>
<td><loc
+ href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR044">CR044</loc>:
+ Additional editorial work, item 2 part 2
+ </td>
+ </tr>
+
+ <tr>
+ <td>20070214</td>
+ <td>JJM</td>
+ <td><loc
href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR120">CR120</loc>:
SOAP Response and IRI style
Received on Thursday, 15 February 2007 09:44:38 UTC