2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.57,1.58

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv17965

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
LC122: Replaced "binding" by "binding extension" where appropriate.

Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -C2 -d -r1.57 -r1.58
*** wsdl20-adjuncts.xml	7 Jun 2005 08:08:15 -0000	1.57
--- wsdl20-adjuncts.xml	13 Jun 2005 09:12:56 -0000	1.58
***************
*** 81,85 ****
  	<item><p>Message exchange patterns</p></item>
  	<item><p>Operation styles</p></item>
! 	<item><p>Bindings</p></item>
        </ulist>
        <p>
--- 81,85 ----
  	<item><p>Message exchange patterns</p></item>
  	<item><p>Operation styles</p></item>
! 	<item><p>Binding Extensions</p></item>
        </ulist>
        <p>
***************
*** 114,122 ****
  	<item><p>Message exchange patterns: <specref ref='meps'/>)</p></item>
  	<item><p>Operation styles: <specref ref='styles'/>)</p></item>
! 	<item><p>Bindings:</p>
  	<ulist>
! 	  <item><p>A SOAP 1.2 <bibref ref="SOAP12-PART1"/> binding:
  	  <specref ref='soap-binding'/></p></item>
! 	  <item><p>An HTTP/1.1 <bibref ref="RFC2616"/> binding:
  	  <specref ref='http-binding'/></p></item>
  	</ulist>
--- 114,122 ----
  	<item><p>Message exchange patterns: <specref ref='meps'/>)</p></item>
  	<item><p>Operation styles: <specref ref='styles'/>)</p></item>
! 	<item><p>Binding extensions:</p>
  	<ulist>
! 	  <item><p>A SOAP 1.2 <bibref ref="SOAP12-PART1"/> binding extension:
  	  <specref ref='soap-binding'/></p></item>
! 	  <item><p>An HTTP/1.1 <bibref ref="RFC2616"/> binding extension:
  	  <specref ref='http-binding'/></p></item>
  	</ulist>
***************
*** 234,238 ****
  default binding rules for the selection of a SOAP 1.2 message exchange
  pattern based on the WSDL message exchange pattern in use for the SOAP
! binding defined in this specification in section <specref ref='soap-binding'/>).
  </p>
  
--- 234,238 ----
  default binding rules for the selection of a SOAP 1.2 message exchange
  pattern based on the WSDL message exchange pattern in use for the SOAP
! binding extension defined in this specification in section <specref ref='soap-binding'/>).
  </p>
  
***************
*** 325,329 ****
  When a fault is generated, the generating node MUST attempt to 
  propagate the fault, and MUST do so in the direction and to to the 
! recipient specified by the ruleset.  However, extensions or bindings
  may modify these rulesets.  For example, WS-Addressing defines a
  "FaultTo" address for messages, which is used in lieu of the recipient
--- 325,329 ----
  When a fault is generated, the generating node MUST attempt to 
  propagate the fault, and MUST do so in the direction and to to the 
! recipient specified by the ruleset.  However, extensions or binding extensions
  may modify these rulesets.  For example, WS-Addressing defines a
  "FaultTo" address for messages, which is used in lieu of the recipient
***************
*** 332,336 ****
  <p>Generation of a fault, regardless of ruleset, terminates the exchange.</p>
  
! <p>Bindings, features, or extension specifications may override the 
  semantics of a fault propagation ruleset, but this practice is strongly 
  discouraged.</p> 
--- 332,336 ----
  <p>Generation of a fault, regardless of ruleset, terminates the exchange.</p>
  
! <p>Binding extensions, features, or extension specifications may override the 
  semantics of a fault propagation ruleset, but this practice is strongly 
  discouraged.</p> 
***************
*** 640,644 ****
  	<p>
  	  This extension MAY be used for setting defaults in bindings,
! 	  such as in the HTTP binding defined in this document (see
  	  <specref ref="http-operation-decl-mapping"/>).
  	</p>
--- 640,644 ----
  	<p>
  	  This extension MAY be used for setting defaults in bindings,
! 	  such as in an HTTP binding per this specification (see
  	  <specref ref="http-operation-decl-mapping"/>).
  	</p>
***************
*** 1139,1149 ****
  
      <div1 id="soap-binding">
!       <head>WSDL SOAP Binding</head> 
  
!       <p>The SOAP binding described in this section is SOAP version
        independent ("1.2" as well as other versions) and an extension
        for <bibref ref="WSDL-PART1"/> to enable Web Services
        applications to use SOAP. This
!       binding extends WSDL 2.0 by adding properties to the <xspecref
        href="&w3c-designation-part1;#Binding">Binding
        component</xspecref> as defined in <bibref
--- 1139,1149 ----
  
      <div1 id="soap-binding">
!       <head>WSDL SOAP Binding Extension</head> 
  
!       <p>The SOAP binding extension described in this section is SOAP version
        independent ("1.2" as well as other versions) and an extension
        for <bibref ref="WSDL-PART1"/> to enable Web Services
        applications to use SOAP. This
!       binding extension extends WSDL 2.0 by adding properties to the <xspecref
        href="&w3c-designation-part1;#Binding">Binding
        component</xspecref> as defined in <bibref
***************
*** 1164,1168 ****
        component.</p>
  
!       <p>The SOAP binding 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
--- 1164,1168 ----
        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 for all
***************
*** 1173,1182 ****
        component. That is, per the requirements of <bibref
        ref="WSDL-PART1"/>, all operations of an Interface component are
!       bound by this binding.</p>
  
        <p>Notice that there are no default binding rules defined for
        <xspecref
        href="&w3c-designation-part1;#InterfaceFault">Interface Fault
!       components</xspecref> by this binding, as no reasonable default
        is applicable to all cases. Thus, if a given
        Interface component has any Fault components, then such
--- 1173,1182 ----
        component. That is, per the requirements of <bibref
        ref="WSDL-PART1"/>, all operations of an Interface component are
!       bound according to this binding extension.</p>
  
        <p>Notice that there are no default binding rules defined for
        <xspecref
        href="&w3c-designation-part1;#InterfaceFault">Interface Fault
!       components</xspecref> by this binding extension, as no reasonable default
        is applicable to all cases. Thus, if a given
        Interface component has any Fault components, then such
***************
*** 1186,1190 ****
        component.</p>
  
!       <p>A subset of the HTTP properties specified in the HTTP binding
        defined in section <specref ref="http-binding"/> may be
        expressed in a SOAP binding when the SOAP binding uses HTTP as
--- 1186,1190 ----
        component.</p>
  
!       <p>A subset of the HTTP properties specified in the HTTP binding extension
        defined in section <specref ref="http-binding"/> may be
        expressed in a SOAP binding when the SOAP binding uses HTTP as
***************
*** 1366,1370 ****
            </ulist>
            
!           <note><p>This SOAP binding only allows one single element in
            SOAP body.</p></note>
  
--- 1366,1370 ----
            </ulist>
            
!           <note><p>This SOAP binding extension only allows one single element in
            SOAP body.</p></note>
  
***************
*** 1571,1575 ****
            <p>Every Binding Operation component of a SOAP binding MUST
            indicate the SOAP Message Exchange Pattern (MEP) to be used for 
!           that operation. This binding specification allows the user to
            indicate a default SOAP MEP to be used for all Binding
            Operation components of this Binding component.</p>
--- 1571,1575 ----
            <p>Every Binding Operation component of a SOAP binding MUST
            indicate the SOAP Message Exchange Pattern (MEP) to be used for 
!           that operation. This binding extension specification allows the user to
            indicate a default SOAP MEP to be used for all Binding
            Operation components of this Binding component.</p>
***************
*** 1629,1633 ****
            <p>For every Interface Fault component contained in an
            Interface component, a mapping to a SOAP Fault must be
!           described. This binding specification allows the user to
            indicate the SOAP fault code and subcodes that are
            transmitted for a given Interface Fault component.</p>
--- 1629,1633 ----
            <p>For every Interface Fault component contained in an
            Interface component, a mapping to a SOAP Fault must be
!           described. This binding extension specification allows the user to
            indicate the SOAP fault code and subcodes that are
            transmitted for a given Interface Fault component.</p>
***************
*** 1637,1641 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Fault binding adds the following
            properties to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 1637,1641 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Fault binding extension adds the following
            properties to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 1743,1747 ****
            component, in addition to the default binding rules (for SOAP 1.2,
            see <specref ref="soap12-defaults"/>), there may be additional binding 
!           information to be specified. This binding specification allows the user 
            to indicate the SOAP Message Exchange Pattern (MEP) and a value for the SOAP
            Action Feature on a per-operation basis.</p>
--- 1743,1747 ----
            component, in addition to the default binding rules (for SOAP 1.2,
            see <specref ref="soap12-defaults"/>), there may be additional binding 
!           information to be specified. This binding extension specification allows the user 
            to indicate the SOAP Message Exchange Pattern (MEP) and a value for the SOAP
            Action Feature on a per-operation basis.</p>
***************
*** 1751,1755 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Operation binding specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
--- 1751,1755 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Operation binding extension specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
***************
*** 1863,1868 ****
            implemented as one or more SOAP header blocks), as defined
            by SOAP Modules (see <bibref ref="SOAP12-PART1"/>). This
!           binding specification allows users to indicate which SOAP
!           Modules are in use across the entire binding, on a per
            operation basis or on a per message basis.</p>
          </div3>
--- 1863,1868 ----
            implemented as one or more SOAP header blocks), as defined
            by SOAP Modules (see <bibref ref="SOAP12-PART1"/>). This
!           binding extension specification allows users to indicate which SOAP
!           Modules are in use across an entire binding, on a per
            operation basis or on a per message basis.</p>
          </div3>
***************
*** 2106,2110 ****
  
  	  <p>SOAP allows the use of header blocks in the header part
! 	  of the message. This binding allows users to declare the
  	  SOAP header blocks in use on a per message ond on a per
  	  fault basis.</p>
--- 2106,2110 ----
  
  	  <p>SOAP allows the use of header blocks in the header part
! 	  of the message. This binding extension allows users to declare the
  	  SOAP header blocks in use on a per message ond on a per
  	  fault basis.</p>
***************
*** 2115,2119 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Header Blocks binding specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
--- 2115,2119 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The SOAP Header Blocks binding extension specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
***************
*** 2361,2368 ****
            <head>Description</head>
            
!           <p>The SOAP 1.2 binding defined in this section is an extension of the <specref ref="soap-binding"/>
            to enable Web Service applications to use SOAP 1.2 <bibref ref="SOAP12-PART1"/>.</p>
            
!           <p>The SOAP 1.2 binding  supports
            the SOAP 1.2 HTTP binding defined by the <bibref
            ref="SOAP12-PART2"/> specification. This is indicated by
--- 2361,2368 ----
            <head>Description</head>
            
!           <p>The SOAP 1.2 binding extension defined in this section is an extension of the <specref ref="soap-binding"/>
            to enable Web Service applications to use SOAP 1.2 <bibref ref="SOAP12-PART1"/>.</p>
            
!           <p>The SOAP 1.2 binding extension supports
            the SOAP 1.2 HTTP binding defined by the <bibref
            ref="SOAP12-PART2"/> specification. This is indicated by
***************
*** 2370,2376 ****
            (as defined by <bibref ref="SOAP12-PART2"/>) to the {soap
  	        underlying protocol} property. Other values MAY be used
!           for this property in conjunction with the SOAP 1.2 binding
            defined by this specification provided that the semantics of
!           such protocols are consistent with this binding.</p>
            
  	  <p>Default rules in section <specref ref="soap12-defaults"/>
--- 2370,2376 ----
            (as defined by <bibref ref="SOAP12-PART2"/>) to the {soap
  	        underlying protocol} property. Other values MAY be used
!           for this property in conjunction with the SOAP 1.2 binding extension
            defined by this specification provided that the semantics of
!           such protocols are consistent with this binding extension.</p>
            
  	  <p>Default rules in section <specref ref="soap12-defaults"/>
***************
*** 2392,2396 ****
          
          <p>These default binding rules 
!           are applicable to SOAP 1.2 binding. 
          </p>
  
--- 2392,2396 ----
          
          <p>These default binding rules 
!           are applicable to SOAP 1.2 bindings. 
          </p>
  
***************
*** 2450,2454 ****
            <attval>&soap12-soap-response-mep-uri;</attval>
            then the IRI to execute the HTTP GET against MUST be
!           generated using the HTTP binding's rules for generating a
            IRI for HTTP GET (see <specref ref="_http_x-www-form-urlencoded"/>). The
            input serialization format of
--- 2450,2454 ----
            <attval>&soap12-soap-response-mep-uri;</attval>
            then the IRI to execute the HTTP GET against MUST be
!           generated using the HTTP binding extension's rules for generating a
            IRI for HTTP GET (see <specref ref="_http_x-www-form-urlencoded"/>). The
            input serialization format of
***************
*** 2487,2491 ****
  	<p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval>
  	and whose local part is <el>description</el> conforms to this
! 	binding specification if the &EII;s and &AII;s whose namespace
  	is &wsdl-soap-ns; conform to the XML Schema for that element
  	or attribute as defined by this specification and additionally
--- 2487,2491 ----
  	<p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval>
  	and whose local part is <el>description</el> conforms to this
! 	binding extension specification if the &EII;s and &AII;s whose namespace
  	is &wsdl-soap-ns; conform to the XML Schema for that element
  	or attribute as defined by this specification and additionally
***************
*** 2500,2508 ****
  
      <div1 id="http-binding">
!       <head>WSDL HTTP Binding</head>
  
!       <p>The HTTP binding described in this section is an extension for
  <bibref ref="WSDL-PART1"/> to enable Web Services applications to use
! HTTP 1.1 <bibref ref="RFC2616"/> (as well as other versions of HTTP) and HTTPS <bibref ref="RFC2818"/>.  This binding extends WSDL 2.0
  by adding properties to the component model defined in <bibref ref="WSDL-PART1"/>. In addition an XML Infoset representation
  for these additional properties is provided, along with a mapping from
--- 2500,2508 ----
  
      <div1 id="http-binding">
!       <head>WSDL HTTP Binding Extension</head>
  
!       <p>The HTTP binding extension described in this section is an extension for
  <bibref ref="WSDL-PART1"/> to enable Web Services applications to use
! HTTP 1.1 <bibref ref="RFC2616"/> (as well as other versions of HTTP) and HTTPS <bibref ref="RFC2818"/>.  This binding extension extends WSDL 2.0
  by adding properties to the component model defined in <bibref ref="WSDL-PART1"/>. In addition an XML Infoset representation
  for these additional properties is provided, along with a mapping from
***************
*** 2512,2516 ****
  to. In this case there MUST NOT be any Binding Operation or Binding
  Fault components present in the Binding component. </p>
!       <p>The HTTP binding 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 Interface
--- 2512,2516 ----
  to. In this case there MUST NOT be any Binding Operation or Binding
  Fault components present in the Binding 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 Interface
***************
*** 2520,2526 ****
  all the default rules apply for that component. That is, per the
  requirements of <bibref ref="WSDL-PART1"/> all operations of an
! Interface component are bound by this binding.</p>
        <p>Notice that there are no default binding rules defined for Fault
! components by this binding, as no HTTP fault code is suitable as a
  default for all possible cases. Thus, if a given Interface component has
  any Fault components, then such Interface components MUST be bound
--- 2520,2526 ----
  all the default rules apply for that component. That is, per the
  requirements of <bibref ref="WSDL-PART1"/> all operations of an
! Interface component are bound by an HTTP binding.</p>
        <p>Notice that there are no default binding rules defined for Fault
! components by this binding extension, as no HTTP fault code is suitable as a
  default for all possible cases. Thus, if a given Interface component has
  any Fault components, then such Interface components MUST be bound
***************
*** 2680,2684 ****
  
  	<p>Section <specref ref="_http_serialization"/> defines
! 	serialization formats supported by this binding along with
  	their constraints.</p>
  	  </item>
--- 2680,2684 ----
  
  	<p>Section <specref ref="_http_serialization"/> defines
! 	serialization formats supported by this binding extension along with
  	their constraints.</p>
  	  </item>
***************
*** 2759,2763 ****
  	  the message. An example of such modification is the WSDL
  	  SOAP Binding HTTP IRI Serialization rules specified in
! 	  <specref ref="soap-defaults"/>. This binding specifies that
  	  the <xspecref
  	  href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapresmep">SOAP-Response
--- 2759,2763 ----
  	  the message. An example of such modification is the WSDL
  	  SOAP Binding HTTP IRI Serialization rules specified in
! 	  <specref ref="soap-defaults"/>. This binding extension specifies that
  	  the <xspecref
  	  href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapresmep">SOAP-Response
***************
*** 2767,2771 ****
  	  <code>application/x-www-form-urlencoded</code>.  Other
  	  examples of such mechanisms are other message exchange
! 	  patterns or bindings.
  	  </p>
  	  </item>
--- 2767,2771 ----
  	  <code>application/x-www-form-urlencoded</code>.  Other
  	  examples of such mechanisms are other message exchange
! 	  patterns or binding extensions.
  	  </p>
  	  </item>
***************
*** 2807,2812 ****
  		  4.2 of <bibref ref="RFC2616"/>; if not, the &EII;
  		  MUST be ignored. If an HTTP header corresponding to
! 		  the &EII; local name is set by a different mechanism
! 		  other than the HTTP Binding, such as the HTTP stack
  		  or another feature, then an error MUST be raised.
  		</p>
--- 2807,2812 ----
  		  4.2 of <bibref ref="RFC2616"/>; if not, the &EII;
  		  MUST be ignored. If an HTTP header corresponding to
! 		  the &EII; local name is set by a mechanism
! 		  other than the HTTP binding, such as the HTTP stack
  		  or another feature, then an error MUST be raised.
  		</p>
***************
*** 2845,2849 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 2845,2849 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding extension specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 2923,2927 ****
  	  <p>Every Binding Operation component MUST indicate what HTTP method
  	  is in use for the operations of the interface that this
! 	  binding applies to.  This binding specification allows the user to
            indicate a default HTTP method to be used for all Binding
            Operation components of this Binding component.</p> 
--- 2923,2927 ----
  	  <p>Every Binding Operation component MUST indicate what HTTP method
  	  is in use for the operations of the interface that this
! 	  binding applies to.  This binding extension specification allows the user to
            indicate a default HTTP method to be used for all Binding
            Operation components of this Binding component.</p> 
***************
*** 2977,2986 ****
            <head>Description</head>
  
! 	  <p>This binding specification provides a binding to HTTP of
  	  Interface Operation components whose
  	  &interface_operation-message_exchange_pattern-p; property
  	  has the value '&wsdl-mep-in-only;',
  	  '&wsdl-mep-robust-in-only;' or '&wsdl-mep-in-out;'. This
! 	  HTTP binding MAY be used with other message exchange
  	  patterns such as outbound message exchange patterns,
  	  provided that additional semantics are defined, such as with
--- 2977,2986 ----
            <head>Description</head>
  
! 	  <p>This binding extension specification provides a binding to HTTP of
  	  Interface Operation components whose
  	  &interface_operation-message_exchange_pattern-p; property
  	  has the value '&wsdl-mep-in-only;',
  	  '&wsdl-mep-robust-in-only;' or '&wsdl-mep-in-out;'. This
! 	  HTTP binding extension MAY be used with other message exchange
  	  patterns such as outbound message exchange patterns,
  	  provided that additional semantics are defined, such as with
***************
*** 2995,2999 ****
  
  	  <p>For every Binding operation component corresponding to
! 	  such Interface Operation components, this binding
  	  specification allows the user to indicate the HTTP method to
  	  use, the input, output and fault serialization, and the
--- 2995,2999 ----
  
  	  <p>For every Binding operation component corresponding to
! 	  such Interface Operation components, this binding extension
  	  specification allows the user to indicate the HTTP method to
  	  use, the input, output and fault serialization, and the
***************
*** 3003,3007 ****
          <div3 id="http-operation-decl-relate">
            <head>Relationship to WSDL Component Model</head>
!           <p>The HTTP binding adds the following property
  	  to the Binding Operation component of the WSDL component model (as defined in <bibref ref="WSDL-PART1"/>):</p>
            <ulist>
--- 3003,3007 ----
          <div3 id="http-operation-decl-relate">
            <head>Relationship to WSDL Component Model</head>
!           <p>The HTTP binding extension adds the following property
  	  to the Binding Operation component of the WSDL component model (as defined in <bibref ref="WSDL-PART1"/>):</p>
            <ulist>
***************
*** 3252,3256 ****
            <head>Description</head>
  
! 	  <p>HTTP allows the use of headers in messages. This binding
  	  allows users to declare the HTTP headers in use on a per
  	  message ond on a per fault basis.</p>
--- 3252,3256 ----
            <head>Description</head>
  
! 	  <p>HTTP allows the use of headers in messages. This binding extension
  	  allows users to declare the HTTP headers in use on a per
  	  message ond on a per fault basis.</p>
***************
*** 3261,3265 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP Header binding specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
--- 3261,3265 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP Header binding extension specification adds the
            following property to the WSDL component model (as defined
            in <bibref ref="WSDL-PART1"/>):</p>
***************
*** 3489,3493 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP Fault binding adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 3489,3493 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP Fault binding extension adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 3966,3970 ****
  	  message.</p>
  
! 	  <p>The HTTP binding provides a mechanism for indicating a
  	  default value at the Binding component and Binding Operation
  	  levels.</p>
--- 3966,3970 ----
  	  message.</p>
  
! 	  <p>The HTTP binding extension provides a mechanism for indicating a
  	  default value at the Binding component and Binding Operation
  	  levels.</p>
***************
*** 3977,3981 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 3977,3981 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding extension specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 4103,4107 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 4103,4107 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding extension specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 4178,4182 ****
  	  ref="RFC2616"/>) for the endpoint described.</p>
  
! 	  <p>This binding specification allows the authentication
  	  scheme and realm to be specified.</p>
  
--- 4178,4182 ----
  	  ref="RFC2616"/>) for the endpoint described.</p>
  
! 	  <p>This binding extension specification allows the authentication
  	  scheme and realm to be specified.</p>
  
***************
*** 4186,4190 ****
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
--- 4186,4190 ----
            <head>Relationship to WSDL Component Model</head>
  
!           <p>The HTTP binding extension specification adds the following
            property to the WSDL component model (as defined in <bibref
            ref="WSDL-PART1"/>):</p>
***************
*** 4299,4303 ****
  	<p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval>
  	and whose local part is <el>description</el> conforms to this
! 	binding specification if the &EII;s and &AII;s whose namespace
  	is &wsdl-http-ns; conform to the XML Schema for that element
  	or attribute as defined by this specification and additionally
--- 4299,4303 ----
  	<p>An &EII; whose namespace name is <attval>&wsdl-ns;</attval>
  	and whose local part is <el>description</el> conforms to this
! 	binding extension specification if the &EII;s and &AII;s whose namespace
  	is &wsdl-http-ns; conform to the XML Schema for that element
  	or attribute as defined by this specification and additionally
***************
*** 4829,4832 ****
--- 4829,4840 ----
        <th>Description</th>
      </tr>
+     	<tr>
+     		<td>20050613</td>
+     		<td>JJM</td>
+     		<td>
+     			<loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC122">LC122</loc>: 
+     			Replaced "binding" by "binding extension" where appropriate.
+     		</td>
+     	</tr>
          <tr>
             <td>20050222</td>

Received on Monday, 13 June 2005 09:13:07 UTC