2002/ws/desc/wsdl20 wsdl20.html,1.117,1.118 wsdl20.xml,1.128,1.129

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

Modified Files:
	wsdl20.html wsdl20.xml 
Log Message:
Added explanatory text at the beginning of section 2.8.1.
Added operation name mapping requirement.


Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -C2 -d -r1.117 -r1.118
*** wsdl20.html	30 Jul 2004 15:00:52 -0000	1.117
--- wsdl20.html	2 Aug 2004 14:50:54 -0000	1.118
***************
*** 4,8 ****
  <head>
  <meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1st March 2004), see www.w3.org" />
  <meta http-equiv="Content-Type" content=
  "text/html; charset=utf-8" />
--- 4,8 ----
  <head>
  <meta name="generator" content=
! "HTML Tidy for Cygwin (vers 1st August 2004), see www.w3.org" />
  <meta http-equiv="Content-Type" content=
[...3661 lines suppressed...]
! <td colspan="1" rowspan="1">Added sections for references and
  change log.</td>
  </tr>
  <tr>
! <td colspan="1" rowspan="1">20020624</td>
! <td colspan="1" rowspan="1">JJM</td>
! <td colspan="1" rowspan="1">Removed Jeffrey from authors :-( Added
  Gudge :-)</td>
  </tr>
  <tr>
! <td colspan="1" rowspan="1">20020620</td>
! <td colspan="1" rowspan="1">SW</td>
! <td colspan="1" rowspan="1">Started adding abstract model</td>
  </tr>
  <tr>
! <td colspan="1" rowspan="1">20020406</td>
! <td colspan="1" rowspan="1">SW</td>
! <td colspan="1" rowspan="1">Created document from WSDL 1.1</td>
  </tr>
  </tbody>

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.128
retrieving revision 1.129
diff -C2 -d -r1.128 -r1.129
*** wsdl20.xml	30 Jul 2004 11:03:53 -0000	1.128
--- wsdl20.xml	2 Aug 2004 14:50:54 -0000	1.129
***************
*** 1,3 ****
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
--- 1,3 ----
! <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
  <!-- $Id$ -->
  <?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
***************
*** 759,766 ****
  	  </ulist>
  
! 	  <p> For each Interface component in the {interfaces}
  	  property of a definitions container, the combination of
  	  {name} and {target namespace} properties MUST be unique.
  	  </p>
      </div3>
  
--- 759,813 ----
  	  </ulist>
  
! 	  <p>For each Interface component in the {interfaces}
  	  property of a definitions container, the combination of
  	  {name} and {target namespace} properties MUST be unique.
  	  </p>
+ 	  
+ 	  <p>Additionally, an Interface component MUST satisfy the Operation Name
+ 	  Mapping requirement, as defined below. This requirement is intended
+ 	  to ensure that a received message can be uniquely mapped to a
+ 	  corresponding wsdl:operation. 
+ 	  </p>
+ 
+           <div4 id="Interface_OperationName">
+           <head>Operation Name Mapping Requirement</head>
+ 	  
+ 	  <p>Consider all Interface Operation components specified in the
+ 	  {operations} property of an Interface component.  Further, consider
+ 	  all Message Reference components specified in the {message references}
+ 	  properties of said Interface Operation components.  Further, consider
+ 	  all said Message Reference components that have the same value for
+ 	  their {direction} property (i.e., either the token <emph>in</emph>
+ 	  or the token <emph>out</emph>).  If the {message content model}
+ 	  property of any of these Message Reference components has a value
+ 	  of "#any", or if more than one of these Message Reference components
+ 	  has a value of "#none", or if the qualified names of the global
+ 	  element declarations specified by the values of the {element}
+ 	  properties of these Message Reference components are not unique
+ 	  when considered together, then either one of the following two
+ 	  conditions MUST apply: 
+ 	  </p>
+ 	  <olist>
+ 	    <item><p>the {features} property of the Interface component MUST
+ 	      contain a Feature component, having a {required} property with
+ 	      a value of <emph>true</emph>, that unambiguously identifies the mechanism
+ 	      that a message sender is required to support in order to enable
+ 	      the message recipient to unambiguously determine the name of the
+ 	      Interface Operation component that is intended to be associated
+ 	      with the received message; or
+ 	      </p>
+ 	    </item>
+ 	    <item><p>the &EII; for the Interface component
+ 	    MUST contain an extension element (i.e., an element that is not
+ 	    in the &wsdl-ns; namespace), having a wsdl:required &AII; with
+ 	    a value of <attval>true</attval>, that unambiguously identifies
+ 	    the mechanism that a message sender is required to support in
+ 	    order to enable the message recipient to unambiguously determine
+ 	    the name of the Interface Operation component that is intended
+ 	    to be associated with the received message.
+ 	      </p>
+ 	    </item>
+ 	  </olist>
+ 	  </div4>
      </div3>
  
***************
*** 2889,2898 ****
        <head>The Property Component</head>
  	  
! 	  <p>A Property component describes the set of possible values
! 	  for a particular property. The permissible values are
! 	  specified by references to a Schema description.  A property
! 	  is typically used to control a feature's
! 	  behavior. Properties, and hence property values, can be
! 	  shared amongst features.</p>
  
  	  <p>The properties of the Property component are as follows:</p>
--- 2936,2950 ----
        <head>The Property Component</head>
  	  
!           <p>A "property" in the Features and Properties architecture
!           represents a named runtime value which affects the behaviour
!           of some aspect of a Web service interaction, much like an
!           environment variable.  For example, a reliable messaging SOAP
!           module may specify a property to control the number of retries
!           in the case of network failure.  WSDL documents may specify the
!           value constraints for these properties by referring to a Schema
!           type, or by specifying a particular value.  Properties, and hence
!           property values, can be shared amongst features/bindings/modules, and
!           are named with URIs precisely to allow this type of sharing.
!           </p>
  
  	  <p>The properties of the Property component are as follows:</p>
***************
*** 6941,6944 ****
--- 6993,7007 ----
      </tr>
          <tr>
+ 	  <td>20040802</td>
+           <td>RRC</td>
+           <td>Added operation name requirement to the Interface component section.</td>
+         </tr>
+         <tr>
+ 	  <td>20040802</td>
+           <td>RRC</td>
+           <td>Added introductory text for the Property Component (per action item 2 of
+           the 2004-07-29 concall).</td>
+         </tr>
+         <tr>
  	  <td>20040727</td>
            <td>RRC</td>

Received on Monday, 2 August 2004 10:51:00 UTC