- From: Sanjiva Weerawarana <sweeraw@dev.w3.org>
- Date: Fri, 18 Jun 2004 19:14:45 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv5991
Modified Files:
wsdl20-bindings.html wsdl20-bindings.xml wsdl20.html
wsdl20.xml
Log Message:
various updates; see email to list
Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** wsdl20-bindings.xml 10 Jun 2004 15:47:32 -0000 1.33
--- wsdl20-bindings.xml 18 Jun 2004 19:14:43 -0000 1.34
***************
*** 193,225 ****
<!-- ******************************************************************* -->
<div1 id="soap-binding">
! <head>WSDL SOAP Binding</head>
! <p>The SOAP binding described in this section is an extension for
! <bibref ref="WSDL-PART1"/> to enable Web Services applications to use
! SOAP 1.2 <bibref ref="SOAP12-PART1"/>. This binding extends WSDL 2.0
! by adding properties to the component model defined in <bibref ref="WSDL-PART1"/> at two places: to the Binding component and to the
! Service Endpoint component. In addition an XML Infoset representation
! for these additional properties is provided, along with a mapping from
! that representation to the various component properties.</p>
[...1497 lines suppressed...]
! <!-- template
<tr>
<td>2004</td>
***************
*** 2331,2334 ****
--- 2357,2370 ----
</tr>
-->
+ <tr>
+ <td>20040618</td>
+ <td>SW</td>
+ <td>Re-introduced AII and EII entity refs.</td>
+ </tr>
+ <tr>
+ <td>20040618</td>
+ <td>SW</td>
+ <td>Made soap:module compose with nearest-wins rule.</td>
+ </tr>
<tr>
<td rowspan="1" colspan="1">20040606</td>
Index: wsdl20-bindings.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** wsdl20-bindings.html 10 Jun 2004 15:47:32 -0000 1.28
--- wsdl20-bindings.html 18 Jun 2004 19:14:43 -0000 1.29
***************
*** 1,4 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
! <html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0
Part 3: Bindings</title><style type="text/css">
code { font-family: monospace; }
--- 1,4 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
! <html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0
Part 3: Bindings</title><style type="text/css">
code { font-family: monospace; }
***************
*** 46,51 ****
div.exampleHeader { font-weight: bold;
margin: 4px}
! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="
! " href="" type=""><link rel="contents" href="#contents"></head><body>
<div class="head">
<h1>Web Services Description Language (WSDL) Version 2.0
--- 46,51 ----
div.exampleHeader { font-weight: bold;
margin: 4px}
! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="
! " rel="alternate"><link href="#contents" rel="contents"></head><body>
<div class="head">
<h1>Web Services Description Language (WSDL) Version 2.0
***************
*** 64,68 ****
<dd>Sanjiva Weerawarana, IBM Research</dd>
</dl><p>This document is also available in these non-normative formats: <a href="">
! </a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a> rules apply.</p></div><hr><div>
<h2><a name="abstract">Abstract</a></h2>
<p>
--- 64,68 ----
<dd>Sanjiva Weerawarana, IBM Research</dd>
</dl><p>This document is also available in these non-normative formats: <a href="">
! </a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a> rules apply.</p></div><hr><div>
<h2><a name="abstract">Abstract</a></h2>
<p>
***************
*** 83,98 ****
<hr><div class="toc">
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br>4. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br> 2.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br> 2.2 <a href="#soap-binding-decl">Indicating a SOAP Binding</a><br> 2.2.1 <a href="#soap-binding-decl-relate">Relationship to WSDL Component Model</a><br> 2.2.2 <a href="#soap-binding-decl-property">SOAP Binding Component</a><br> 2.2.3 <a href="#soap-binding-decl-xml">XML Representation of SOAP Binding Component</a><br> 2.2.4 <a href="#soap-binding-decl-mapping">Mapping Between SOAP Binding's XML Representation to Component
! Properties</a><br> 2.3 <a href="#soap-defaults">Default Binding Rules</a><br> 2.4 <a href="#soap-module-decl">SOAP Module</a><br> 2.4.1 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br> 2.4.2 <a href="#soap-module-decl-property">SOAP Module Component</a><br> 2.4.3 <a href="#soap-module-decl-xml">XML Representation of SOAP Module Component</a><br> 2.4.4 <a href="#soap-module-decl-mapping">Mapping Between SOAP Module's XML Representation to Component
! Properties</a><br> 2.5 <a href="#soap-fault-decl">Indicating a SOAP Fault</a><br> 2.5.1 <a href="#soap-fault-decl-relate">Relationship to WSDL Component Model</a><br> 2.5.2 <a href="#soap-fault-decl-property">SOAP Fault Component</a><br> 2.5.3 <a href="#soap-fault-decl-xml">XML Representation of SOAP Fault Component</a><br> 2.5.4 <a href="#soap-fault-decl-mapping">Mapping Between SOAP Fault's XML Representation to Component
! Properties</a><br> 2.6 <a href="#soap-operation-decl">Indicating a SOAP Operation</a><br> 2.6.1 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br> 2.6.2 <a href="#soap-operation-decl-property">SOAP Operation Component</a><br> 2.6.3 <a href="#soap-operation-decl-xml">XML Representation of SOAP Operation Component</a><br> 2.6.4 <a href="#soap-operation-decl-mapping">Mapping Between SOAP Operation's XML Representation to Component
! Properties</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br> 3.1 <a href="#http-syntax">HTTP Syntax Summary (Non-Normative)</a><br> 3.2 <a href="#http-binding-decl">Indicating an HTTP Binding</a><br> 3.2.1 <a href="#http-binding-decl-relate">Relationship to WSDL Component Model</a><br> 3.2.2 <a href="#http-binding-decl-property">HTTP Binding Component</a><br> 3.2.3 <a href="#http-binding-decl-xml">XML Representation of HTTP Binding Component</a><br> 3.2.4 <a href="#http-binding-decl-mapping">Mapping Between HTTP Binding's XML Representation to Component
! Properties</a><br> 3.3 <a href="#_http_binding_methodDefault">Default Binding Rules</a><br> 3.4 <a href="#http-operation-decl">Indicating an HTTP Operation</a><br> 3.4.1 <a href="#http-operation-decl-relate">Relationship to WSDL Component Model</a><br> 3.4.2 <a href="#http-operation-decl-property">HTTP Operation Component</a><br> 3.4.3 <a href="#http-operation-decl-xml">XML Representation of HTTP Operation Component</a><br> 3.4.4 <a href="#http-operation-decl-mapping">Mapping Between HTTP Operation's XML Representation to Component
! Properties</a><br> 3.5 <a href="#_operation_styles">Operation Styles</a><br> 3.5.1 <a href="#_operation_uri_style">URI Style</a><br> 3.5.2 <a href="#_operation_multipart_style">Multipart style</a><br> 3.6 <a href="#_http_serialization">Serialization format of instance data</a><br> 3.6.1 <a href="#_http_x-www-form-urlencoded">Serialization as application/x-www-form-urlencoded
! </a><br> 3.6.1.1 <a href="#_http_operation_location_cited_get">Case of elements cited in location attribute</a><br> 3.6.1.2 <a href="#_http_operation_location_notcited_get">Case elements NOT cited in location attribute</a><br> 3.6.2 <a href="#_http_operation_xml_encoding">Serialization as application/xml
! </a><br> 3.6.3 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
! </a><br> 3.7 <a href="#http-service-decl">Indicating an HTTP Service</a><br> 3.7.1 <a href="#http-service-decl-relate">Relationship to WSDL Component Model</a><br> 3.7.2 <a href="#http-service-decl-property">HTTP Service Component</a><br> 3.7.3 <a href="#http-service-decl-xml">XML Representation of HTTP Service Component</a><br> 3.7.4 <a href="#http-service-decl-mapping">Mapping Between HTTP Service's XML Representation to Component
! Properties</a><br>4. <a href="#References">References</a><br> 4.1 <a href="#Normative-References">Normative References</a><br> 4.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br> B.1 <a href="#wsdl-spec-changelog">WSDL Specification Changes</a><br> B.2 <a href="#xml-schema-changes">XML Schema Changes</a><br></p></div><hr><div class="body">
<div class="div1">
--- 83,98 ----
<hr><div class="toc">
<h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br>4. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br> 2.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br> 2.2 <a href="#soap-binding-decl">Indicating a SOAP Binding</a><br> 2.3 <a href="#soap-protocol">Specifying the SOAP Protocol</a><br> 2.3.1 <a href="#soap-binding-decl-xml">XML Representation of SOAP Binding Component</a><br> 2.3.2 <a href="#soap-binding-decl-mapping">Mapping Between SOAP Binding's XML Representation to Component
! Properties</a><br> 2.4 <a href="#soap-defaults">Default Binding Rules</a><br> 2.5 <a href="#soap-module-decl">SOAP Module</a><br> 2.5.1 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br> 2.5.2 <a href="#soap-module-decl-property">SOAP Module Component</a><br> 2.5.3 <a href="#soap-module-decl-xml">XML Representation of SOAP Module Component</a><br> 2.5.4 <a href="#soap-module-decl-mapping">Mapping Between SOAP Module's XML Representation to Component
! Properties</a><br> 2.6 <a href="#soap-fault-decl">Indicating a SOAP Fault</a><br> 2.6.1 <a href="#soap-fault-decl-relate">Relationship to WSDL Component Model</a><br> 2.6.2 <a href="#soap-fault-decl-property">SOAP Fault Component</a><br> 2.6.3 <a href="#soap-fault-decl-xml">XML Representation of SOAP Fault Component</a><br> 2.6.4 <a href="#soap-fault-decl-mapping">Mapping Between SOAP Fault's XML Representation to Component
! Properties</a><br> 2.7 <a href="#soap-operation-decl">Indicating a SOAP Operation</a><br> 2.7.1 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br> 2.7.2 <a href="#soap-operation-decl-property">SOAP Operation Component</a><br> 2.7.3 <a href="#soap-operation-decl-xml">XML Representation of SOAP Operation Component</a><br> 2.7.4 <a href="#soap-operation-decl-mapping">Mapping Between SOAP Operation's XML Representation to Component
! Properties</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br> 3.1 <a href="#http-syntax">HTTP Syntax Summary (Non-Normative)</a><br> 3.2 <a href="#http-binding-decl">Indicating an HTTP Binding</a><br> 3.2.1 <a href="#http-binding-decl-relate">Relationship to WSDL Component Model</a><br> 3.2.2 <a href="#http-binding-decl-property">HTTP Binding Component</a><br> 3.2.3 <a href="#http-binding-decl-xml">XML Representation of HTTP Binding Component</a><br> 3.2.4 <a href="#http-binding-decl-mapping">Mapping Between HTTP Binding's XML Representation to Component
! Properties</a><br> 3.3 <a href="#_http_binding_methodDefault">Default Binding Rules</a><br> 3.4 <a href="#http-operation-decl">Indicating an HTTP Operation</a><br> 3.4.1 <a href="#http-operation-decl-relate">Relationship to WSDL Component Model</a><br> 3.4.2 <a href="#http-operation-decl-property">HTTP Operation Component</a><br> 3.4.3 <a href="#http-operation-decl-xml">XML Representation of HTTP Operation Component</a><br> 3.4.4 <a href="#http-operation-decl-mapping">Mapping Between HTTP Operation's XML Representation to Component
! Properties</a><br> 3.5 <a href="#_operation_styles">Operation Styles</a><br> 3.5.1 <a href="#_operation_uri_style">URI Style</a><br> 3.5.2 <a href="#_operation_multipart_style">Multipart style</a><br> 3.6 <a href="#_http_serialization">Serialization format of instance data</a><br> 3.6.1 <a href="#_http_x-www-form-urlencoded">Serialization as application/x-www-form-urlencoded
! </a><br> 3.6.1.1 <a href="#_http_operation_location_cited_get">Case of elements cited in location attribute</a><br> 3.6.1.2 <a href="#_http_operation_location_notcited_get">Case elements NOT cited in location attribute</a><br> 3.6.2 <a href="#_http_operation_xml_encoding">Serialization as application/xml
! </a><br> 3.6.3 <a href="#_http_operation_multipart_encoding">Serialization as multipart/form-data
! </a><br> 3.7 <a href="#http-service-decl">Indicating an HTTP Service</a><br> 3.7.1 <a href="#http-service-decl-relate">Relationship to WSDL Component Model</a><br> 3.7.2 <a href="#http-service-decl-property">HTTP Service Component</a><br> 3.7.3 <a href="#http-service-decl-xml">XML Representation of HTTP Service Component</a><br> 3.7.4 <a href="#http-service-decl-mapping">Mapping Between HTTP Service's XML Representation to Component
! Properties</a><br>4. <a href="#References">References</a><br> 4.1 <a href="#Normative-References">Normative References</a><br> 4.2 <a href="#Informative-References">Informative References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br> B.1 <a href="#wsdl-spec-changelog">WSDL Specification Changes</a><br> B.2 <a href="#xml-schema-changes">XML Schema Changes</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 214,246 ****
<div class="div1">
! <h2><a name="soap-binding"></a>2. WSDL SOAP Binding</h2>
! <p>The SOAP binding described in this section is an extension for
! [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] to enable Web Services applications to use
! SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]. This binding extends WSDL 2.0
! by adding properties to the component model defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] at two places: to the Binding component and to the
! Service Endpoint component. In addition an XML Infoset representation
! for these additional properties is provided, along with a mapping from
! that representation to the various component properties.</p>
! <p>As allowed in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>], a Binding component MAY
! exist without indicating a specific Interface component that it applies
! to. In this case there MUST NOT be any Binding Operation or Binding
! Fault components present in the Binding 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 Interface
! Operation components of an Interface component, unless specifically
! overidden on a per Interface Operation basis. Thus, if a given
! Interface Operation component is not referred to specifically, then
! all the default rules apply for that component. That is, per the
! requirements of [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] 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. Thus, if a given Interface component has
! any Fault components, then such Interface components MUST be bound
! via Binding components which indicate a specific interface and contain
! as many Binding Fault components as there are Fault components in the
! Interface Fault component.</p>
! <p>A subset of the the HTTP components specified in the HTTP Binding may be expressed in a SOAP binding when the SOAP binding uses HTTP as the underlying protocol. The components that are allowed are the ones that contain properties that describe the underlying protocol. The components and allowed properties are: http:binding with version, cookies, defaultTransferCoding; http:operation with defaultTransferCoding; http:input with transferCoding; http:output with transferCoding; and http:service with authenticationType and authenticationRealm.</p>
! <p>When the SOAP Message Exchange Pattern is the SOAP Response MEP, the binding operation may contain an http:operation with a location attribute that follows the http:operation location attributes construction rules. When such a location is specified, the wsdl:endpoint also follows the rules for constructing the address from the wsdl:address and http:operation location values.</p>
<div class="div2">
--- 214,271 ----
<div class="div1">
! <h2><a name="soap-binding"></a>2. WSDL SOAP Binding</h2>
!
! <p>The SOAP binding described in this section is an extension
! for [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] to enable Web Services
! applications to use SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]. This
! binding extends WSDL 2.0 by adding properties to the Binding
! component as defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]. In addition,
! an XML Infoset representation for these additional properties is
! provided, along with a mapping from that representation to the
! various component properties.</p>
!
! <p>As allowed in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>], a Binding component
! MAY exist without indicating a specific Interface component that
! it applies to. In this case there MUST NOT be any Binding
! Operation or Binding Fault components present in the Binding
! 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
! Interface Operation components of an Interface component, unless
! specifically overidden on a per Interface Operation basis. Thus,
! if a given Interface Operation component is not referred to
! specifically, then all the default rules apply for that
! component. That is, per the requirements of [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>] 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. Thus, if a given Interface
! component has any Fault components, then such Interface
! components MUST be bound via Binding components which indicate a
! specific interface and contain as many Binding Fault components
! as there are Fault components in the Interface Fault
! component.</p>
!
! <p>A subset of the the HTTP components specified in the HTTP
! Binding may be expressed in a SOAP binding when the SOAP binding
! uses HTTP as the underlying protocol. The components that are
! allowed are the ones that contain properties that describe the
! underlying protocol. The components and allowed properties are:
! http:binding with version, cookies, defaultTransferCoding;
! http:operation with defaultTransferCoding; http:input with
! transferCoding; http:output with transferCoding; and
! http:service with authenticationType and
! authenticationRealm.</p>
!
! <p>When the SOAP Message Exchange Pattern is the SOAP Response
! MEP, the binding operation may contain an http:operation with a
! location attribute that follows the http:operation location
! attributes construction rules. When such a location is
! specified, the wsdl:endpoint also follows the rules for
! constructing the address from the wsdl:address and
! http:operation location values.</p>
!
<div class="div2">
***************
*** 300,352 ****
</pre></div>
</div>
<div class="div2">
<h3><a name="soap-binding-decl"></a>2.2 Indicating a SOAP Binding</h3>
<div class="div3">
! <h4><a name="soap-binding-decl-relate"></a>2.2.1 Relationship to WSDL Component Model</h4>
! <p>The SOAP Binding component adds a new property named {soap binding}
! to the Binding component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
! </div>
! <div class="div3">
!
! <h4><a name="soap-binding-decl-property"></a>2.2.2 SOAP Binding Component</h4>
! <p>A given Binding component is declared to be a SOAP binding by the
! presence of the SOAP Binding component.</p>
! <p>The properties of the SOAP Binding component are as follows:</p>
! <ul>
! <li>
! <p>{protocol} An absolute URI as defined by [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>]. The value of this property identifies the specific
! SOAP binding that is in use, as defined in the SOAP Protocol Binding
! Framework section of [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].</p>
! <p>The SOAP binding defined by this specification supports the SOAP
! HTTP Binding defined by the [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]
! specification. This is indicated by assigning the URI
! "http://www.w3.org/2003/05/soap/bindings/HTTP/" (as defined by [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]) to the {protocol} property. Other values MAY
! be used for this property in conjunction with the SOAP binding
! defined by this specification provided that the semantics of such
! protocols are consistent with this binding.</p>
! </li>
! <li>
! <p>{default message exchange pattern} An absolute URI as
! defined by [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>]. The value of this property
! identifies the default SOAP Message Exchange Pattern (MEP) (as
! defined by [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]) for all the operations of
! the interface that this binding applies to.</p>
! <p>The SOAP MEP idenfied by {default message exchange pattern}
! MUST be compatible with the {pattern} of the Interface Operation
! component (see [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
! </li>
! <li>
! <p>{default Web method} A string value indicating the default
! value for the SOAP Web Method Feature (as defined by [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]) for all operations of the interface that this
! binding applies to.</p>
! </li>
! </ul>
! </div>
! <div class="div3">
!
! <h4><a name="soap-binding-decl-xml"></a>2.2.3 XML Representation of SOAP Binding Component</h4>
<div class="exampleInner"><pre><definitions >
<binding >
--- 325,370 ----
</pre></div>
</div>
+
+
<div class="div2">
<h3><a name="soap-binding-decl"></a>2.2 Indicating a SOAP Binding</h3>
+
+ <p>A Binding component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>])
+ is identified as a SOAP binding by the presence of the {soap
+ protocol} property.</p>
+ </div>
+
+
+
+ <div class="div2">
+
+ <h3><a name="soap-protocol"></a>2.3 Specifying the SOAP Protocol</h3>
+
+ <p>The SOAP protocol (see SOAP Protocol Binding Framework
+ section of [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]) for this SOAP binding
+ is indicated by the {soap protocol} property added to the
+ Binding component.</p>
+
+ <p>The {soap protocol} property is an absolute URI as defined
+ by [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>]. The value of this property
+ identifies the specific SOAP protocol that is in use, as
+ defined in the SOAP Protocol Binding Framework section of
+ [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].</p>
+
+ <p>The SOAP binding defined by this specification supports the
+ SOAP HTTP Binding defined by the [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]
+ specification. This is indicated by assigning the URI
+ "http://www.w3.org/2003/05/soap/bindings/HTTP/"
+ (as defined by [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]) to the {soap
+ protocol} property. Other values MAY be used for this property
+ in conjunction with the SOAP binding defined by this
+ specification provided that the semantics of such protocols
+ are consistent with this binding.</p>
+
<div class="div3">
! <h4><a name="soap-binding-decl-xml"></a>2.3.1 XML Representation of SOAP Binding Component</h4>
<div class="exampleInner"><pre><definitions >
<binding >
***************
*** 441,445 ****
<div class="div3">
! <h4><a name="soap-binding-decl-mapping"></a>2.2.4 Mapping Between SOAP Binding's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Binding component
--- 459,463 ----
<div class="div3">
! <h4><a name="soap-binding-decl-mapping"></a>2.3.2 Mapping Between SOAP Binding's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Binding component
***************
*** 479,483 ****
<div class="div2">
! <h3><a name="soap-defaults"></a>2.3 Default Binding Rules</h3>
<p>When formulating the SOAP envelope to be transmitted the contents
of the payload (i.e., the contents of the <code>soap:Body</code>
--- 497,501 ----
<div class="div2">
! <h3><a name="soap-defaults"></a>2.4 Default Binding Rules</h3>
<p>When formulating the SOAP envelope to be transmitted the contents
of the payload (i.e., the contents of the <code>soap:Body</code>
***************
*** 495,507 ****
indicate how to map those components into the SOAP envelope. </p>
</div>
<div class="div2">
! <h3><a name="soap-module-decl"></a>2.4 SOAP Module</h3>
<div class="div3">
! <h4><a name="soap-module-decl-relate"></a>2.4.1 Relationship to WSDL Component Model</h4>
! <p>The SOAP Module component adds the properties below to the
! following components (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]):</p>
<ul>
<li>
--- 513,530 ----
indicate how to map those components into the SOAP envelope. </p>
</div>
+
+
<div class="div2">
! <h3><a name="soap-module-decl"></a>2.5 SOAP Module</h3>
!
<div class="div3">
! <h4><a name="soap-module-decl-relate"></a>2.5.1 Relationship to WSDL Component Model</h4>
!
! <p>The SOAP Module component adds the properties below to
! the following components (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]):</p>
!
<ul>
<li>
***************
*** 509,559 ****
</li>
<li>
! <p>{soap modules} to the Operation component.</p>
! </li>
! <li>
! <p>{soap modules} to the Input component.</p>
! </li>
! <li>
! <p>{soap modules} to the Output component.</p>
! </li>
! </ul>
! <p>The SOAP modules in use for any given service and a particular
! interaction consists of the combined set of ALL module declarations in
! the following scope (the list is in order of decreasing
! specificity):</p>
! <ul>
! <li>
! <p>The Input or Output component.</p>
! </li>
! <li>
! <p>The Operation component.</p>
</li>
<li>
! <p>The Binding component.</p>
</li>
</ul>
</div>
<div class="div3">
! <h4><a name="soap-module-decl-property"></a>2.4.2 SOAP Module Component</h4>
! <p>The SOAP Module component identifies a SOAP module that is in use.
! A SOAP module (see [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]) realizes zero or more
! SOAP features implemented as one or more SOAP header blocks.</p>
! <p>The properties of the SOAP Module component are as follows:</p>
<ul>
! <li>
! <p>{uri} An absolute URI as defined by [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>]. The value of this property identifies the specific
! SOAP module that is in use, as defined in the SOAP Protocol Binding
! Framework section of [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].</p>
! </li>
! <li>
! <p>{required} A boolean indicating if the SOAP module is
! required.</p>
! </li>
</ul>
</div>
<div class="div3">
! <h4><a name="soap-module-decl-xml"></a>2.4.3 XML Representation of SOAP Module Component</h4>
<div class="exampleInner"><pre><definitions >
<binding >
--- 532,576 ----
</li>
<li>
! <p>{soap modules} to the Binding Operation component.</p>
</li>
<li>
! <p>{soap modules} to the Binding Message Reference component.</p>
</li>
</ul>
+
+ <p>The SOAP modules applicable for a particular operation of
+ any service consists of all modules specified in the input
+ or output Binding Message reference components, and those
+ specified within the Binding Operation components and those
+ specified within the Binding component. If any module is
+ declared in multiple components, then the requiredness of
+ that module is defined by the lexically nearest
+ declaration.</p>
</div>
+
<div class="div3">
! <h4><a name="soap-module-decl-property"></a>2.5.2 SOAP Module Component</h4>
!
! <p>The SOAP Module component identifies a SOAP module that
! is in use. A SOAP module (see [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>])
! realizes zero or more SOAP features implemented as one or
! more SOAP header blocks.</p> <p>The properties of the SOAP
! Module component are as follows:</p>
!
<ul>
! <li> <p>{uri} An absolute URI as defined by [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>]. The value of this property identifies the
! specific SOAP module that is in use, as defined in the
! SOAP Protocol Binding Framework section of [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>].</p> </li>
!
! <li> <p>{required} A boolean indicating if the SOAP
! module is required.</p> </li>
</ul>
</div>
+
<div class="div3">
! <h4><a name="soap-module-decl-xml"></a>2.5.3 XML Representation of SOAP Module Component</h4>
!
<div class="exampleInner"><pre><definitions >
<binding >
***************
*** 574,577 ****
--- 591,595 ----
</definitions>
</pre></div>
+
<p>The XML representation for a SOAP Module component is an <em>element information item</em>
with the following Infoset properties: </p>
***************
*** 644,648 ****
<div class="div3">
! <h4><a name="soap-module-decl-mapping"></a>2.4.4 Mapping Between SOAP Module's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Module component
--- 662,666 ----
<div class="div3">
! <h4><a name="soap-module-decl-mapping"></a>2.5.4 Mapping Between SOAP Module's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Module component
***************
*** 672,682 ****
</div>
</div>
<div class="div2">
! <h3><a name="soap-fault-decl"></a>2.5 Indicating a SOAP Fault</h3>
<div class="div3">
! <h4><a name="soap-fault-decl-relate"></a>2.5.1 Relationship to WSDL Component Model</h4>
<p>The SOAP Fault component adds a new property named {soap fault}
to the Fault component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
--- 690,702 ----
</div>
</div>
+
+
<div class="div2">
! <h3><a name="soap-fault-decl"></a>2.6 Indicating a SOAP Fault</h3>
<div class="div3">
! <h4><a name="soap-fault-decl-relate"></a>2.6.1 Relationship to WSDL Component Model</h4>
<p>The SOAP Fault component adds a new property named {soap fault}
to the Fault component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
***************
*** 684,688 ****
<div class="div3">
! <h4><a name="soap-fault-decl-property"></a>2.5.2 SOAP Fault Component</h4>
<p>A given Fault component is declared to be a SOAP fault by the
presence of the SOAP Fault component.</p>
--- 704,708 ----
<div class="div3">
! <h4><a name="soap-fault-decl-property"></a>2.6.2 SOAP Fault Component</h4>
<p>A given Fault component is declared to be a SOAP fault by the
presence of the SOAP Fault component.</p>
***************
*** 703,707 ****
<div class="div3">
! <h4><a name="soap-fault-decl-xml"></a>2.5.3 XML Representation of SOAP Fault Component</h4>
<div class="exampleInner"><pre><fault ref="xs:QName"
<b>wsoap:code</b>="xs:QName"
--- 723,727 ----
<div class="div3">
! <h4><a name="soap-fault-decl-xml"></a>2.6.3 XML Representation of SOAP Fault Component</h4>
<div class="exampleInner"><pre><fault ref="xs:QName"
<b>wsoap:code</b>="xs:QName"
***************
*** 783,787 ****
<div class="div3">
! <h4><a name="soap-fault-decl-mapping"></a>2.5.4 Mapping Between SOAP Fault's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Fault component
--- 803,807 ----
<div class="div3">
! <h4><a name="soap-fault-decl-mapping"></a>2.6.4 Mapping Between SOAP Fault's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Fault component
***************
*** 814,821 ****
<div class="div2">
! <h3><a name="soap-operation-decl"></a>2.6 Indicating a SOAP Operation</h3>
<div class="div3">
! <h4><a name="soap-operation-decl-relate"></a>2.6.1 Relationship to WSDL Component Model</h4>
<p>The SOAP Operation component adds a new property named {soap operation}
to the Operation component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
--- 834,841 ----
<div class="div2">
! <h3><a name="soap-operation-decl"></a>2.7 Indicating a SOAP Operation</h3>
<div class="div3">
! <h4><a name="soap-operation-decl-relate"></a>2.7.1 Relationship to WSDL Component Model</h4>
<p>The SOAP Operation component adds a new property named {soap operation}
to the Operation component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]).</p>
***************
*** 823,827 ****
<div class="div3">
! <h4><a name="soap-operation-decl-property"></a>2.6.2 SOAP Operation Component</h4>
<p>A given Operation component is declared to be a SOAP message exchange
by the presence of the SOAP Operation component.</p>
--- 843,847 ----
<div class="div3">
! <h4><a name="soap-operation-decl-property"></a>2.7.2 SOAP Operation Component</h4>
<p>A given Operation component is declared to be a SOAP message exchange
by the presence of the SOAP Operation component.</p>
***************
*** 853,857 ****
<div class="div3">
! <h4><a name="soap-operation-decl-xml"></a>2.6.3 XML Representation of SOAP Operation Component</h4>
<div class="exampleInner"><pre><definitions>
<binding>
--- 873,877 ----
<div class="div3">
! <h4><a name="soap-operation-decl-xml"></a>2.7.3 XML Representation of SOAP Operation Component</h4>
<div class="exampleInner"><pre><definitions>
<binding>
***************
*** 946,950 ****
<div class="div3">
! <h4><a name="soap-operation-decl-mapping"></a>2.6.4 Mapping Between SOAP Operation's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Operation component
--- 966,970 ----
<div class="div3">
! <h4><a name="soap-operation-decl-mapping"></a>2.7.4 Mapping Between SOAP Operation's XML Representation to Component
Properties</h4>
<p>The mapping between the properties of the SOAP Operation component
***************
*** 986,990 ****
<h2><a name="http-binding"></a>3. WSDL HTTP Binding</h2>
! <table border="1" summary="Editorial note: Revised HTTP Binding"><tr><td align="left" valign="top" width="50%"><b>Editorial note: Revised HTTP Binding</b></td><td align="right" valign="top" width="50%">26 March 2004</td></tr><tr><td colspan="2" align="left" valign="top">The HTTP binding in this section has been considerably
revised. The WSD WG is especially interested in feedback
on this binding. In particular, the WG would like to
--- 1006,1010 ----
<h2><a name="http-binding"></a>3. WSDL HTTP Binding</h2>
! <table border="1" summary="Editorial note: Revised HTTP Binding"><tr><td width="50%" valign="top" align="left"><b>Editorial note: Revised HTTP Binding</b></td><td width="50%" valign="top" align="right">26 March 2004</td></tr><tr><td valign="top" align="left" colspan="2">The HTTP binding in this section has been considerably
revised. The WSD WG is especially interested in feedback
on this binding. In particular, the WG would like to
***************
*** 1019,1023 ****
Interface Fault component.</p>
<p>
! [<a name="instance_data" title="instance_data">Definition</a>: The internal tree representation of an input or an output message is called an <b>instance data</b>, and is constrained by the schema definition associated the message.]
</p>
<div class="div2">
--- 1039,1043 ----
Interface Fault component.</p>
<p>
! [<a title="instance_data" name="instance_data">Definition</a>: The internal tree representation of an input or an output message is called an <b>instance data</b>, and is constrained by the schema definition associated the message.]
</p>
<div class="div2">
***************
*** 1618,1622 ****
as the Interface operation component's name.
</p>
! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">
Not sure why we need this but we probably have good
reasons to keep in RPC style, so I guess the reasons
--- 1638,1642 ----
as the Interface operation component's name.
</p>
! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">
Not sure why we need this but we probably have good
reasons to keep in RPC style, so I guess the reasons
***************
*** 1738,1747 ****
</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><a name="urlencoded_example"></a><i><span>Example 3-1. </span>instance data serialized in a URI</i></p>
<p>
The following instance data of an input message
</p>
<div class="exampleInner"><pre><data>
! <town>Fréjus</town>
<date>2004-01-16</date>
<unit>C</unit>
--- 1758,1767 ----
</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="urlencoded_example"></a><i><span>Example 3-1. </span>instance data serialized in a URI</i></p>
<p>
The following instance data of an input message
</p>
<div class="exampleInner"><pre><data>
! <town>Fréjus</town>
<date>2004-01-16</date>
<unit>C</unit>
***************
*** 1768,1772 ****
<h5><a name="_http_operation_location_cited_get"></a>3.6.1.1 Case of elements cited in <code>location</code> attribute</h5>
! <table border="1" summary="Editorial note: URIPath Feedback Requested"><tr><td align="left" valign="top" width="50%"><b>Editorial note: URIPath Feedback Requested</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">The inclusion of elements of the instance data
in the path of the request URI, whilst supported by WSDL 1.1,
is not supported by XForms 1.0. Hence this mechanism MAY be
--- 1788,1792 ----
<h5><a name="_http_operation_location_cited_get"></a>3.6.1.1 Case of elements cited in <code>location</code> attribute</h5>
! <table border="1" summary="Editorial note: URIPath Feedback Requested"><tr><td width="50%" valign="top" align="left"><b>Editorial note: URIPath Feedback Requested</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">The inclusion of elements of the instance data
in the path of the request URI, whilst supported by WSDL 1.1,
is not supported by XForms 1.0. Hence this mechanism MAY be
***************
*** 1906,1910 ****
</li>
</ul>
! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">We need media type handling here.</td></tr></table>
</li>
<li>
--- 1926,1930 ----
</li>
</ul>
! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">We need media type handling here.</td></tr></table>
</li>
<li>
***************
*** 1920,1924 ****
</ol>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Example of multipart/form-data</i></p>
<p>
The following instance data of an input message:
--- 1940,1944 ----
</ol>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Example of multipart/form-data</i></p>
<p>
The following instance data of an input message:
***************
*** 1926,1930 ****
<div class="exampleInner"><pre><data>
<town>
! <name>Fréjus</name>
<country>France</country>
</town>
--- 1946,1950 ----
<div class="exampleInner"><pre><data>
<town>
! <name>Fréjus</name>
<country>France</country>
</town>
***************
*** 1947,1951 ****
Content-Type: application/xml
<town>
! <name>Fréjus</name>
<country>France</country>
</town>
--- 1967,1971 ----
Content-Type: application/xml
<town>
! <name>Fréjus</name>
<country>France</country>
</town>
***************
*** 2306,2310 ****
Mike McHugh (W. W. Grainger),
Paul Downey (BT),
! Philippe Le Hégaret (W3C),
Prasad Yendluri (webMethods, Inc.),
Roberto Chinnici (Sun Microsystems),
--- 2326,2330 ----
Mike McHugh (W. W. Grainger),
Paul Downey (BT),
! Philippe Le Hégaret (W3C),
Prasad Yendluri (webMethods, Inc.),
Roberto Chinnici (Sun Microsystems),
***************
*** 2334,2339 ****
Barbara Zengler (DaimlerChrysler Research and Technology),
Tim Finin (University of Maryland)
! Laurent De Teneuille (L'Échangeur),
! Johan Pauhlsson (L'Échangeur),
Mark Jones (AT&T),
Steve Lind (AT&T),
--- 2354,2359 ----
Barbara Zengler (DaimlerChrysler Research and Technology),
Tim Finin (University of Maryland)
! Laurent De Teneuille (L'Échangeur),
! Johan Pauhlsson (L'Échangeur),
Mark Jones (AT&T),
Steve Lind (AT&T),
***************
*** 2344,2347 ****
--- 2364,2368 ----
are also gratefully acknowledged.</p>
</div>
+
<div class="div1">
***************
*** 2357,2361 ****
<th rowspan="1" colspan="1">Description</th>
</tr>
!
<tr>
<td rowspan="1" colspan="1">20040606</td>
--- 2378,2392 ----
<th rowspan="1" colspan="1">Description</th>
</tr>
!
! <tr>
! <td rowspan="1" colspan="1">20040618</td>
! <td rowspan="1" colspan="1">SW</td>
! <td rowspan="1" colspan="1">Re-introduced AII and EII entity refs.</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">20040618</td>
! <td rowspan="1" colspan="1">SW</td>
! <td rowspan="1" colspan="1">Made soap:module compose with nearest-wins rule.</td>
! </tr>
<tr>
<td rowspan="1" colspan="1">20040606</td>
***************
*** 2829,2831 ****
</div>
</div>
! </body></html>
--- 2860,2862 ----
</div>
</div>
! </body></html>
\ No newline at end of file
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.81
retrieving revision 1.82
diff -C2 -d -r1.81 -r1.82
*** wsdl20.html 26 May 2004 14:50:57 -0000 1.81
--- wsdl20.html 18 Jun 2004 19:14:43 -0000 1.82
***************
*** 91,95 ****
or outfault [owner]</a><br> 2.6.2.2 <a href="#FaultReference_messageReference_attribute">messageLabel attribute information item with infault,
or outfault [owner]</a><br> 2.6.3 <a href="#FaultReference_Mapping">Mapping Fault Reference's XML Representation to
! Component Properties</a><br> 2.7 <a href="#Feature">Feature</a><br> 2.7.1 <a href="#Feature_details">The Feature Component</a><br> 2.7.1.1 <a href="#Feature_composition_model">Feature Composition Model</a><br> 2.7.1.1.1 <a href="#Feature_composition_model_example">Example of Feature Composition Model</a><br> 2.7.2 <a href="#Feature_XMLRep">XML Representation of Feature Component</a><br> 2.7.2.1 <a href="#Feature_uri_attribute">uri attribute information item with feature [owner]</a><br> 2.7.2.2 <a href="#Feature_required_attribute">required attribute info
rmation item with feature [owner]</a><br> 2.7.3 <a href="#Feature_Mapping">Mapping Feature's XML Representation to Component Properties</a><br> 2.8 <a href="#Property">Property</a><br> 2.8.1 <a href="#Property_details">The Property Component</a><br> 2.8.1.1 <a href="#Property_composition_model">Property Composition Model</a><br> 2.8.2 <a href="#Property_XMLRep">XML Representation of Property Component</a><br> 2.8.2.1 <a href="#Property_uri_attribute">uri attribute information item with property [owner]</a><br> 2.8.2.2 <a href="#Property_required_attribute">required attribute information item with feature
[owner]</a><br> 2.8.2.3 <a href="#Property_value_element">value element information item with property [parent]</a><br> 2.8.2.4 <a href="#Property_constraint_element">constraint element information item with property [parent]</a><br> 2.8.3 <a href="#Property_Mapping">Mapping Property's XML Representation to Component Properties</a><br> 2.9 <a href="#Binding">Binding</a><br> 2.9.1 <a href="#Binding_details">The Binding Component</a><br> 2.9.2 <a href="#Binding_XMLRep">XML Representation of Binding Component</a><br> 2.9.2.1 <a href="#Binding_name_attribute">name attribute information item with binding [owne
r]</a><br> 2.9.2.2 <a href="#Binding_interface_attribute">interface attribute information item with binding [owner]</a><br> 2.9.2.3 <a href="#Binding_type_attribute">type attribute information item with binding [owner]</a><br> 2.9.2.4 <a href="#Binding_extension_elements">Binding extension elements</a><br> 2.9.3 <a href="#Binding_Mapping">Mapping Binding's XML Representation to Component
Properties</a><br> 2.10 <a href="#Binding_Fault">Binding Fault</a><br> 2.10.1 <a href="#Binding_Fault_details">The Binding Fault Component</a><br> 2.10.2 <a href="#Binding_Fault_XMLRep">XML Representation of Binding Fault Component</a><br> 2.10.2.1 <a href="#Binding_Fault_ref_attribute">ref attribute information item with fault [owner]</a><br> 2.10.2.2 <a href="#Binding_Fault_extension_elements">Binding Fault extension elements</a><br> 2.10.3 <a href="#Binding_Fault_Mapping">Mapping Binding Fault's XML Representation to Component
Properties</a><br> 2.11 <a href="#Binding_Operation">Binding Operation</a><br> 2.11.1 <a href="#Binding_Operation_details">The Binding Operation Component</a><br> 2.11.2 <a href="#Binding_Operation_XMLRep">XML Representation of Binding Operation Component</a><br> 2.11.2.1 <a href="#Binding_Operation_ref_attribute">ref attribute information item with operation [owner]</a><br> 2.11.2.2 <a href="#Binding_Operation_extension_elements">Binding Operation extension elements</a><br> 2.11.3 <a href="#Binding_Operation_Mapping">Mapping Binding Operation's XML Representation to Component
--- 91,95 ----
or outfault [owner]</a><br> 2.6.2.2 <a href="#FaultReference_messageReference_attribute">messageLabel attribute information item with infault,
or outfault [owner]</a><br> 2.6.3 <a href="#FaultReference_Mapping">Mapping Fault Reference's XML Representation to
! Component Properties</a><br> 2.7 <a href="#Feature">Feature</a><br> 2.7.1 <a href="#Feature_details">The Feature Component</a><br> 2.7.1.1 <a href="#Feature_composition_model">Feature Composition Model</a><br> 2.7.1.1.1 <a href="#Feature_composition_model_example">Example of Feature Composition Model</a><br> 2.7.2 <a href="#Feature_XMLRep">XML Representation of Feature Component</a><br> 2.7.2.1 <a href="#Feature_uri_attribute">uri attribute information item with feature [owner]</a><br> 2.7.2.2 <a href="#Feature_required_attribute">required attribute info
rmation item with feature [owner]</a><br> 2.7.3 <a href="#Feature_Mapping">Mapping Feature's XML Representation to Component Properties</a><br> 2.8 <a href="#Property">Property</a><br> 2.8.1 <a href="#Property_details">The Property Component</a><br> 2.8.1.1 <a href="#Property_composition_model">Property Composition Model</a><br> 2.8.2 <a href="#Property_XMLRep">XML Representation of Property Component</a><br> 2.8.2.1 <a href="#Property_uri_attribute">uri attribute information item with property [owner]</a><br> 2.8.2.2 <a href="#Property_required_attribute">required attribute information item with property
[owner]</a><br> 2.8.2.3 <a href="#Property_value_element">value element information item with property [parent]</a><br> 2.8.2.4 <a href="#Property_constraint_element">constraint element information item with property [parent]</a><br> 2.8.3 <a href="#Property_Mapping">Mapping Property's XML Representation to Component Properties</a><br> 2.9 <a href="#Binding">Binding</a><br> 2.9.1 <a href="#Binding_details">The Binding Component</a><br> 2.9.2 <a href="#Binding_XMLRep">XML Representation of Binding Component</a><br> 2.9.2.1 <a href="#Binding_name_attribute">name attribute information item with binding [own
er]</a><br> 2.9.2.2 <a href="#Binding_interface_attribute">interface attribute information item with binding [owner]</a><br> 2.9.2.3 <a href="#Binding_type_attribute">type attribute information item with binding [owner]</a><br> 2.9.2.4 <a href="#Binding_extension_elements">Binding extension elements</a><br> 2.9.3 <a href="#Binding_Mapping">Mapping Binding's XML Representation to Component
Properties</a><br> 2.10 <a href="#Binding_Fault">Binding Fault</a><br> 2.10.1 <a href="#Binding_Fault_details">The Binding Fault Component</a><br> 2.10.2 <a href="#Binding_Fault_XMLRep">XML Representation of Binding Fault Component</a><br> 2.10.2.1 <a href="#Binding_Fault_ref_attribute">ref attribute information item with fault [owner]</a><br> 2.10.2.2 <a href="#Binding_Fault_extension_elements">Binding Fault extension elements</a><br> 2.10.3 <a href="#Binding_Fault_Mapping">Mapping Binding Fault's XML Representation to Component
Properties</a><br> 2.11 <a href="#Binding_Operation">Binding Operation</a><br> 2.11.1 <a href="#Binding_Operation_details">The Binding Operation Component</a><br> 2.11.2 <a href="#Binding_Operation_XMLRep">XML Representation of Binding Operation Component</a><br> 2.11.2.1 <a href="#Binding_Operation_ref_attribute">ref attribute information item with operation [owner]</a><br> 2.11.2.2 <a href="#Binding_Operation_extension_elements">Binding Operation extension elements</a><br> 2.11.3 <a href="#Binding_Operation_Mapping">Mapping Binding Operation's XML Representation to Component
***************
*** 577,581 ****
related messages into operations. An operation is a sequence
of input and output messages, an interface is a set of
! operations.</p>
<p> An interface can optionally extend one or more other
--- 577,582 ----
related messages into operations. An operation is a sequence
of input and output messages, an interface is a set of
! operations. Thus, an interface defines the design of the
! application.</p>
<p> An interface can optionally extend one or more other
***************
*** 1141,1145 ****
fault) messages exchanged between the service and the other
roles involved in the interaction, in particular the service
! requestor. The sequencing and cardinality of the messages
involved in a particular interaction is governed by the
<em>message exchange pattern</em> used by the operation
--- 1142,1146 ----
fault) messages exchanged between the service and the other
roles involved in the interaction, in particular the service
! requester. The sequencing and cardinality of the messages
involved in a particular interaction is governed by the
<em>message exchange pattern</em> used by the operation
***************
*** 2356,2395 ****
<h5><a name="Feature_composition_model"></a>2.7.1.1 Feature Composition Model</h5>
! <p>The set of features which are required or available for a given
! service and a particular interaction consists of the combined
! set of ALL feature declarations in the following scope. The list is
! in order of increasing specificity.</p>
!
<ul>
! <li><p>The interface component.</p></li>
! <li><p>The specific interface operation component.</p></li>
! <li><p>The specific message reference component.</p></li>
! <li><p>The binding component.</p></li>
! <li><p>The specific binding operation component.</p></li>
! <li><p>The specific binding message or fault reference component.</p></li>
!
</ul>
- <p>Note that multiple declarations of the same feature have no effect on the
- combined set of active features, since features are either in use or not,
- with no multiplicity. If multiple declarations of the same feature are in
- scope for a given interaction, the feature is required if ANY of the in
- scope declarations have the <code>required</code> attribute set to
- "true".</p>
-
<div class="div5">
<h6><a name="Feature_composition_model_example"></a>2.7.1.1.1 Example of Feature Composition Model</h6>
! <p>In the following example, the <code>depositFunds</code> operation
! on the <code>BankService</code> has to be used with the <code>ISO9001</code> ,
! the <code>notarization</code> and the <code>secure-channel</code> features;
! they are all in scope. The fact that the <code>notarization</code> feature
! is declared both in the operation and in the service has no effect.</p>
<div class="exampleInner"><pre><definitions targetNamespace="http://example.com/bank"
xmlns:ns1="http://example.com/bank">
<interface name="ns1:Bank">
! <!-- All uses of this interface must be secure -->
<feature uri="http://example.com/secure-channel"
required="true"/>
--- 2357,2417 ----
<h5><a name="Feature_composition_model"></a>2.7.1.1 Feature Composition Model</h5>
! <p>The set of features which are required or available for
! a given component consists of the combined set of ALL
! feature declarations applicable to that componment. A
! feature is applicable to a component if:</p>
!
! <ul>
! <li><p>it is asserted directly within that component,
! or</p></li>
!
! <li><p>it is asserted in a containing component, or</p></li>
!
! <li><p>it is asserted in a component referred to by
! the current component.</p></li>
! </ul>
!
! <p>If a given feature is asserted at multiple locations,
! then the value of that feature at a particular component
! is that given by the nearest assertion in lexical scoping
! order. Following these rules, the set of features
! applicable at each component are as follows:</p>
!
<ul>
! <li><p>Interface component: all features asserted
! within the interface component.</p></li>
!
! <li><p>Interface Operation component: all features
! asserted within the interface operation component and
! those within the parent interface component.</p></li>
!
! <li><p>Binding component: all features asserted within
! the binding component and those within the interface
! component referred to by the binding component (if
! any).</p></li>
!
! <li><p>Binding Operation component: all features
! asserted within the binding operation component, those
! within the parent binding component and those within the
! interface component referred to by the binding component
! (if any).</p></li>
</ul>
<div class="div5">
<h6><a name="Feature_composition_model_example"></a>2.7.1.1.1 Example of Feature Composition Model</h6>
! <p>In the following example, the <code>depositFunds</code>
! operation on the <code>BankService</code> has to be used
! with the <code>ISO9001</code> , the <code>notarization</code>
! and the <code>secure-channel</code> features; they are all
! in scope. The fact that the <code>notarization</code>
! feature is declared both in the operation and in the
! binding has no effect.</p>
<div class="exampleInner"><pre><definitions targetNamespace="http://example.com/bank"
xmlns:ns1="http://example.com/bank">
<interface name="ns1:Bank">
! <!-- All implementations of this interface must be secure -->
<feature uri="http://example.com/secure-channel"
required="true"/>
***************
*** 2407,2424 ****
</operation>
</interface>
<binding name="ns1:BankSOAPBinding">
</binding>
<service name="ns1:BankService"
interface="tns:Bank">
! <!-- This particular service requires ISO9001
! compliance to be verifiable -->
! <feature uri="http://example.com/ISO9001"
! required="true"/>
! <!-- This service also requires notarization -->
! <feature uri="http://example.com/notarization"
! required="true"/>
! <endpoint>
! ...
! </endpoint>
</service>
</definitions></pre></div>
--- 2429,2448 ----
</operation>
</interface>
+
<binding name="ns1:BankSOAPBinding">
+ <!-- This particular binding requires ISO9001
+ compliance to be verifiable -->
+ <feature uri="http://example.com/ISO9001"
+ required="true"/>
+ <!-- This binding also requires notarization -->
+ <feature uri="http://example.com/notarization"
+ required="true"/>
</binding>
+
<service name="ns1:BankService"
interface="tns:Bank">
! <endpoint binding="ns1:BankSOAPBinding">
! ...
! </endpoint>
</service>
</definitions></pre></div>
***************
*** 2606,2635 ****
<h5><a name="Property_composition_model"></a>2.8.1.1 Property Composition Model</h5>
! <p>At runtime, the behaviour of features, (SOAP) modules and bindings may be
! affected by the values of in-scope properties. Properties combine into a
! virtual "execution context" which maps property names (URIs) to
! constraints. Each property URI MAY therefore be associated with AT MOST one
! property constraint for a given interaction.</p>
!
! <p>The particular set of constraints for a given service and
! a particular interaction consists of the combined set of ALL
! constraints in the following scope. The list is in order of
! increasing specificity, and if a given property URI is constrained
! in a later scope, it overrides the earlier constraint.</p>
<ul>
! <li><p>The interface component.</p></li>
! <li><p>The specific interface operation component.</p></li>
! <li><p>The specific message reference component.</p></li>
! <li><p>The binding component.</p></li>
! <li><p>The specific binding operation component.</p></li>
! <li><p>The specific binding message or fault reference component.</p></li>
!
</ul>
! <p>Note that, in the text above, "property constraint" (or, simply, "constraint")
! is used to mean EITHER a <code>constraint</code> inside a property component OR
! a <code>value</code> , since <code>value</code> may be considered a special case of
! <code>constraint</code> .</p>
--- 2630,2687 ----
<h5><a name="Property_composition_model"></a>2.8.1.1 Property Composition Model</h5>
! <p>At runtime, the behavior of features, (SOAP) modules
! and bindings may be affected by the values of in-scope
! properties. Properties combine into a virtual "execution
! context" which maps property names (URIs) to
! constraints. Each property URI MAY therefore be associated
! with AT MOST one property constraint for a given
! interaction.</p>
+ <p>The set of properties which are required or available for
+ a given component consists of the combined set of ALL
+ property declarations applicable to that componment. A
+ property is applicable to a component if:</p>
+
+ <ul>
+ <li><p>it is asserted directly within that component,
+ or</p></li>
+
+ <li><p>it is asserted in a containing component, or</p></li>
+
+ <li><p>it is asserted in a component referred to by
+ the current component.</p></li>
+ </ul>
+
+ <p>If a given property is asserted at multiple locations,
+ then the value of that property at a particular component
+ is that given by the nearest assertion in lexical scoping
+ order. Following these rules, the set of properties
+ applicable at each component are as follows:</p>
+
<ul>
! <li><p>Interface component: all properties asserted
! within the interface component.</p></li>
!
! <li><p>Interface Operation component: all properties
! asserted within the interface operation component and
! those within the parent interface component.</p></li>
!
! <li><p>Binding component: all properties asserted within
! the binding component and those within the interface
! component referred to by the binding component (if
! any).</p></li>
!
! <li><p>Binding Operation component: all properties
! asserted within the binding operation component, those
! within the parent binding component and those within the
! interface component referred to by the binding component
! (if any).</p></li>
</ul>
! <p>Note that, in the text above, "property constraint"
! (or, simply, "constraint") is used to mean EITHER a
! <code>constraint</code> inside a property component OR a
! <code>value</code> , since <code>value</code> may be considered a
! special case of <code>constraint</code> .</p>
***************
*** 2669,2673 ****
<p>
An OPTIONAL <code>required</code> <em>attribute information item</em> as described
! below in <a href="#Property_required_attribute"><b>2.8.2.2 required attribute information item with feature [owner]</b></a>.
</p>
</li>
--- 2721,2725 ----
<p>
An OPTIONAL <code>required</code> <em>attribute information item</em> as described
! below in <a href="#Property_required_attribute"><b>2.8.2.2 required attribute information item with property [owner]</b></a>.
</p>
</li>
***************
*** 2731,2735 ****
<div class="div4">
! <h5><a name="Property_required_attribute"></a>2.8.2.2 <code>required</code> <em>attribute information item</em> with <code>feature</code> [owner]</h5>
<p>
The <code>required</code> <em>attribute information item</em> specifies whether use of the property
--- 2783,2787 ----
<div class="div4">
! <h5><a name="Property_required_attribute"></a>2.8.2.2 <code>required</code> <em>attribute information item</em> with <code>property</code> [owner]</h5>
<p>
The <code>required</code> <em>attribute information item</em> specifies whether use of the property
***************
*** 2858,2868 ****
<p> A Binding component describes a concrete message format and
transmission protocol which may be used to define an endpoint
! (see <a href="#Endpoint"><b>2.14 Endpoint</b></a>). Binding components can be used
! to describe such information in a re-usable manner for any
! interface or specifically for a given interface. Furthermore,
! binding information MAY be specified on a per-operation basis
! (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) within an
! interface in addition to across all operations of an
! interface. </p>
<p> If a Binding component specifies any operation-specific
--- 2910,2922 ----
<p> A Binding component describes a concrete message format and
transmission protocol which may be used to define an endpoint
! (see <a href="#Endpoint"><b>2.14 Endpoint</b></a>). That is, a Binding component
! defines the implementation details necessary to accessing the
! service. </p>
!
! <p> Binding components can be used to describe such information
! in a re-usable manner for any interface or specifically for a
! given interface. Furthermore, binding information MAY be
! specified on a per-operation basis (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) within an interface in
! addition to across all operations of an interface. </p>
<p> If a Binding component specifies any operation-specific
***************
*** 3720,3726 ****
<p>A Service component describes a set of endpoints (see
! <a href="#Endpoint"><b>2.14 Endpoint</b></a>) at which the single interface of the
! service is provided. The endpoints thus are in effect alternate
! places at which the service is provided. </p>
<p> Services are named constructs and can be referred to by QName
--- 3774,3781 ----
<p>A Service component describes a set of endpoints (see
! <a href="#Endpoint"><b>2.14 Endpoint</b></a>) at which a particular deployed
! implementation of the service is provided. The endpoints thus
! are in effect alternate places at which the service is
! provided. </p>
<p> Services are named constructs and can be referred to by QName
***************
*** 4196,4200 ****
characteristics (for example, operation message exchange patterns
and styles). When such absolute URIs are being compared to determine
! equivalency (see <a href="#compequiv"><b>2.15 Equivalence of Components</b></a>) the URIs MUST be
compared character-by-character as indicated in [<cite><a href="#tag-uri-comp">TAG URI FINDING</a></cite>].</p>
--- 4251,4255 ----
characteristics (for example, operation message exchange patterns
and styles). When such absolute URIs are being compared to determine
! equivalence (see <a href="#compequiv"><b>2.15 Equivalence of Components</b></a>) the URIs MUST be
compared character-by-character as indicated in [<cite><a href="#tag-uri-comp">TAG URI FINDING</a></cite>].</p>
***************
*** 4530,4534 ****
occur in WSDL.</p>
-
<p>
A mutual include is direct inclusion by one WSDL document of another
--- 4585,4588 ----
***************
*** 4646,4650 ****
for that namespace is present. The same considerations apply to schemas
embedded in an imported WSDL description (see <a href="#embed-xsd"><b>3.1.2 Embedding XML Schema</b></a>).
! More explicitely, components defined by an XML schema document
embedded inside an imported WSDL description are NOT made available
to the importer unless the latter contains an explicit
--- 4700,4704 ----
for that namespace is present. The same considerations apply to schemas
embedded in an imported WSDL description (see <a href="#embed-xsd"><b>3.1.2 Embedding XML Schema</b></a>).
! More explicitly, components defined by an XML schema document
embedded inside an imported WSDL description are NOT made available
to the importer unless the latter contains an explicit
***************
*** 5036,5040 ****
WSDL namespace name, and, the second a hint as to the location
of a WSDL document defining WSDL components for that namespace
! name. The second URI of a pair MAY be abolute or relative.
</p>
</div>
--- 5090,5094 ----
WSDL namespace name, and, the second a hint as to the location
of a WSDL document defining WSDL components for that namespace
! name. The second URI of a pair MAY be absolute or relative.
</p>
</div>
***************
*** 5379,5383 ****
<dt class="label"><a name="tag-uri-comp"></a>[TAG URI FINDING] </dt><dd>
! <cite><a href="http://www.w3.org/2001/tag/findings">TAG Finding on URI Comparisn</a></cite>, X. Foo, Y. Bar,
Authors. W3C Technical Architecture Group, Month, Year.
Available at http://www.w3.org/2001/tag/findings/ZZZZ.
--- 5433,5437 ----
<dt class="label"><a name="tag-uri-comp"></a>[TAG URI FINDING] </dt><dd>
! <cite><a href="http://www.w3.org/2001/tag/findings">TAG Finding on URI Comparison</a></cite>, X. Foo, Y. Bar,
Authors. W3C Technical Architecture Group, Month, Year.
Available at http://www.w3.org/2001/tag/findings/ZZZZ.
***************
*** 5803,5807 ****
properties rather the XML Infoset representation of the
component model.</p>
-
</div>
--- 5857,5860 ----
***************
*** 6136,6139 ****
--- 6189,6202 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20040618</td>
+ <td rowspan="1" colspan="1">SW</td>
+ <td rowspan="1" colspan="1">Changed F&P composition model to nearest enclosing scope.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20040618</td>
+ <td rowspan="1" colspan="1">SW</td>
+ <td rowspan="1" colspan="1">Incorporated Jacek's purpose of bindings text as appropriate.</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20040526</td>
<td rowspan="1" colspan="1">SW</td>
***************
*** 6296,6300 ****
<td rowspan="1" colspan="1">Mapping to component model for {message} of Fault Reference
component indicated that <code>message</code> <em>attribute information item</em> was optional,
! but the pseudo syntax and XML reprsentation indicated it was
required. Made uniformly optional to allow other type systems as
was previously done for {message} of Message Reference component.
--- 6359,6363 ----
<td rowspan="1" colspan="1">Mapping to component model for {message} of Fault Reference
component indicated that <code>message</code> <em>attribute information item</em> was optional,
! but the pseudo syntax and XML representation indicated it was
required. Made uniformly optional to allow other type systems as
was previously done for {message} of Message Reference component.
***************
*** 6547,6551 ****
<td rowspan="1" colspan="1">MJG</td>
<td rowspan="1" colspan="1">Various edits to <a href="#eii-types"><b>3. Types</b></a>, <a href="#other-schemalang"><b>E. Examples of Specifications of Extension Elements for Alternative Schema
! Language Support.</b></a> to accomadate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
--- 6610,6614 ----
<td rowspan="1" colspan="1">MJG</td>
<td rowspan="1" colspan="1">Various edits to <a href="#eii-types"><b>3. Types</b></a>, <a href="#other-schemalang"><b>E. Examples of Specifications of Extension Elements for Alternative Schema
! Language Support.</b></a> to accommodate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.90
retrieving revision 1.91
diff -C2 -d -r1.90 -r1.91
*** wsdl20.xml 15 Jun 2004 17:54:39 -0000 1.90
--- wsdl20.xml 18 Jun 2004 19:14:43 -0000 1.91
***************
*** 573,577 ****
related messages into operations. An operation is a sequence
of input and output messages, an interface is a set of
! operations.</p>
<p> An interface can optionally extend one or more other
--- 573,578 ----
related messages into operations. An operation is a sequence
of input and output messages, an interface is a set of
! operations. Thus, an interface defines the design of the
! application.</p>
<p> An interface can optionally extend one or more other
***************
*** 2359,2397 ****
<head>Feature Composition Model</head>
! <p>The set of features which are required or available for a given
! service and a particular interaction consists of the combined
! set of ALL feature declarations in the following scope. The list is
! in order of increasing specificity.</p>
!
<ulist>
! <item><p>The interface component.</p></item>
! <item><p>The specific interface operation component.</p></item>
! <item><p>The specific message reference component.</p></item>
! <item><p>The binding component.</p></item>
! <item><p>The specific binding operation component.</p></item>
! <item><p>The specific binding message or fault reference component.</p></item>
! <!-- item><p>The service component.</p></item -->
</ulist>
- <p>Note that multiple declarations of the same feature have no effect on the
- combined set of active features, since features are either in use or not,
- with no multiplicity. If multiple declarations of the same feature are in
- scope for a given interaction, the feature is required if ANY of the in
- scope declarations have the <att>required</att> attribute set to
- <attval>true</attval>.</p>
-
<div5 id="Feature_composition_model_example">
<head>Example of Feature Composition Model</head>
! <p>In the following example, the <att>depositFunds</att> operation
! on the <att>BankService</att> has to be used with the <att>ISO9001</att>,
! the <att>notarization</att> and the <att>secure-channel</att> features;
! they are all in scope. The fact that the <att>notarization</att> feature
! is declared both in the operation and in the service has no effect.</p>
<eg xml:space="preserve"><definitions targetNamespace="http://example.com/bank"
xmlns:ns1="http://example.com/bank">
<interface name="ns1:Bank">
! <!-- All uses of this interface must be secure -->
<feature uri="http://example.com/secure-channel"
required="true"/>
--- 2360,2419 ----
<head>Feature Composition Model</head>
! <p>The set of features which are required or available for
! a given component consists of the combined set of ALL
! feature declarations applicable to that componment. A
! feature is applicable to a component if:</p>
!
! <ulist>
! <item><p>it is asserted directly within that component,
! or</p></item>
!
! <item><p>it is asserted in a containing component, or</p></item>
!
! <item><p>it is asserted in a component referred to by
! the current component.</p></item>
! </ulist>
!
! <p>If a given feature is asserted at multiple locations,
! then the value of that feature at a particular component
! is that given by the nearest assertion in lexical scoping
! order. Following these rules, the set of features
! applicable at each component are as follows:</p>
!
<ulist>
! <item><p>Interface component: all features asserted
! within the interface component.</p></item>
!
! <item><p>Interface Operation component: all features
! asserted within the interface operation component and
! those within the parent interface component.</p></item>
!
! <item><p>Binding component: all features asserted within
! the binding component and those within the interface
! component referred to by the binding component (if
! any).</p></item>
!
! <item><p>Binding Operation component: all features
! asserted within the binding operation component, those
! within the parent binding component and those within the
! interface component referred to by the binding component
! (if any).</p></item>
</ulist>
<div5 id="Feature_composition_model_example">
<head>Example of Feature Composition Model</head>
! <p>In the following example, the <att>depositFunds</att>
! operation on the <att>BankService</att> has to be used
! with the <att>ISO9001</att>, the <att>notarization</att>
! and the <att>secure-channel</att> features; they are all
! in scope. The fact that the <att>notarization</att>
! feature is declared both in the operation and in the
! binding has no effect.</p>
<eg xml:space="preserve"><definitions targetNamespace="http://example.com/bank"
xmlns:ns1="http://example.com/bank">
<interface name="ns1:Bank">
! <!-- All implementations of this interface must be secure -->
<feature uri="http://example.com/secure-channel"
required="true"/>
***************
*** 2409,2426 ****
</operation>
</interface>
<binding name="ns1:BankSOAPBinding">
</binding>
<service name="ns1:BankService"
interface="tns:Bank">
! <!-- This particular service requires ISO9001
! compliance to be verifiable -->
! <feature uri="http://example.com/ISO9001"
! required="true"/>
! <!-- This service also requires notarization -->
! <feature uri="http://example.com/notarization"
! required="true"/>
! <endpoint>
! ...
! </endpoint>
</service>
</definitions></eg>
--- 2431,2450 ----
</operation>
</interface>
+
<binding name="ns1:BankSOAPBinding">
+ <!-- This particular binding requires ISO9001
+ compliance to be verifiable -->
+ <feature uri="http://example.com/ISO9001"
+ required="true"/>
+ <!-- This binding also requires notarization -->
+ <feature uri="http://example.com/notarization"
+ required="true"/>
</binding>
+
<service name="ns1:BankService"
interface="tns:Bank">
! <endpoint binding="ns1:BankSOAPBinding">
! ...
! </endpoint>
</service>
</definitions></eg>
***************
*** 2604,2633 ****
<head>Property Composition Model</head>
! <p>At runtime, the behavior of features, (SOAP) modules and bindings may be
! affected by the values of in-scope properties. Properties combine into a
! virtual "execution context" which maps property names (URIs) to
! constraints. Each property URI MAY therefore be associated with AT MOST one
! property constraint for a given interaction.</p>
!
! <p>The particular set of constraints for a given service and
! a particular interaction consists of the combined set of ALL
! constraints in the following scope. The list is in order of
! increasing specificity, and if a given property URI is constrained
! in a later scope, it overrides the earlier constraint.</p>
<ulist>
! <item><p>The interface component.</p></item>
! <item><p>The specific interface operation component.</p></item>
! <item><p>The specific message reference component.</p></item>
! <item><p>The binding component.</p></item>
! <item><p>The specific binding operation component.</p></item>
! <item><p>The specific binding message or fault reference component.</p></item>
! <!-- item><p>The service component.</p></item -->
</ulist>
! <p>Note that, in the text above, "property constraint" (or, simply, "constraint")
! is used to mean EITHER a <el>constraint</el> inside a property component OR
! a <el>value</el>, since <el>value</el> may be considered a special case of
! <el>constraint</el>.</p>
<!-- Commented out for now, until we define a proper example.
--- 2628,2685 ----
<head>Property Composition Model</head>
! <p>At runtime, the behavior of features, (SOAP) modules
! and bindings may be affected by the values of in-scope
! properties. Properties combine into a virtual "execution
! context" which maps property names (URIs) to
! constraints. Each property URI MAY therefore be associated
! with AT MOST one property constraint for a given
! interaction.</p>
+ <p>The set of properties which are required or available for
+ a given component consists of the combined set of ALL
+ property declarations applicable to that componment. A
+ property is applicable to a component if:</p>
+
+ <ulist>
+ <item><p>it is asserted directly within that component,
+ or</p></item>
+
+ <item><p>it is asserted in a containing component, or</p></item>
+
+ <item><p>it is asserted in a component referred to by
+ the current component.</p></item>
+ </ulist>
+
+ <p>If a given property is asserted at multiple locations,
+ then the value of that property at a particular component
+ is that given by the nearest assertion in lexical scoping
+ order. Following these rules, the set of properties
+ applicable at each component are as follows:</p>
+
<ulist>
! <item><p>Interface component: all properties asserted
! within the interface component.</p></item>
!
! <item><p>Interface Operation component: all properties
! asserted within the interface operation component and
! those within the parent interface component.</p></item>
!
! <item><p>Binding component: all properties asserted within
! the binding component and those within the interface
! component referred to by the binding component (if
! any).</p></item>
!
! <item><p>Binding Operation component: all properties
! asserted within the binding operation component, those
! within the parent binding component and those within the
! interface component referred to by the binding component
! (if any).</p></item>
</ulist>
! <p>Note that, in the text above, "property constraint"
! (or, simply, "constraint") is used to mean EITHER a
! <el>constraint</el> inside a property component OR a
! <el>value</el>, since <el>value</el> may be considered a
! special case of <el>constraint</el>.</p>
<!-- Commented out for now, until we define a proper example.
***************
*** 2736,2740 ****
<div4 id="Property_required_attribute">
! <head><att>required</att> &AII; with <el>feature</el> [owner]</head>
<p>
The <att>required</att> &AII; specifies whether use of the property
--- 2788,2792 ----
<div4 id="Property_required_attribute">
! <head><att>required</att> &AII; with <el>property</el> [owner]</head>
<p>
The <att>required</att> &AII; specifies whether use of the property
***************
*** 2858,2868 ****
<p> A Binding component describes a concrete message format and
transmission protocol which may be used to define an endpoint
! (see <specref ref="Endpoint"/>). Binding components can be used
! to describe such information in a re-usable manner for any
! interface or specifically for a given interface. Furthermore,
! binding information MAY be specified on a per-operation basis
! (see <specref ref='Binding_Operation_details'/>) within an
! interface in addition to across all operations of an
! interface. </p>
<p> If a Binding component specifies any operation-specific
--- 2910,2923 ----
<p> A Binding component describes a concrete message format and
transmission protocol which may be used to define an endpoint
! (see <specref ref="Endpoint"/>). That is, a Binding component
! defines the implementation details necessary to accessing the
! service. </p>
!
! <p> Binding components can be used to describe such information
! in a re-usable manner for any interface or specifically for a
! given interface. Furthermore, binding information MAY be
! specified on a per-operation basis (see <specref
! ref='Binding_Operation_details'/>) within an interface in
! addition to across all operations of an interface. </p>
<p> If a Binding component specifies any operation-specific
***************
*** 3725,3731 ****
<p>A Service component describes a set of endpoints (see
! <specref ref="Endpoint"/>) at which the single interface of the
! service is provided. The endpoints thus are in effect alternate
! places at which the service is provided. </p>
<p> Services are named constructs and can be referred to by QName
--- 3780,3787 ----
<p>A Service component describes a set of endpoints (see
! <specref ref="Endpoint"/>) at which a particular deployed
! implementation of the service is provided. The endpoints thus
! are in effect alternate places at which the service is
! provided. </p>
<p> Services are named constructs and can be referred to by QName
***************
*** 6128,6131 ****
--- 6184,6197 ----
</tr>
<tr>
+ <td>20040618</td>
+ <td>SW</td>
+ <td>Changed F&P composition model to nearest enclosing scope.</td>
+ </tr>
+ <tr>
+ <td>20040618</td>
+ <td>SW</td>
+ <td>Incorporated Jacek's purpose of bindings text as appropriate.</td>
+ </tr>
+ <tr>
<td>20040526</td>
<td>SW</td>
Received on Friday, 18 June 2004 15:31:29 UTC