2002/ws/desc/wsdl20 wsdl20-patterns.html,1.6,1.7 wsdl20-patterns.xml,1.15,1.16

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

Modified Files:
	wsdl20-patterns.html wsdl20-patterns.xml 
Log Message:
Updates following feedback from GlenD, related to content of the Predefined Features part, specifically the Application Data feature and module

Index: wsdl20-patterns.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** wsdl20-patterns.xml	29 Jul 2004 09:45:51 -0000	1.15
--- wsdl20-patterns.xml	29 Jul 2004 15:49:36 -0000	1.16
***************
*** 447,470 ****
  
  <p>
! Web Services Description Language (WSDL) features (hereafter 
! 'features') define properties or behaviors in the scope of a particular
! message exchange.  Scoping rules are outlined in [REFERENCE].  A property
! exposed by a feature is visible to all participants in an exchange.  Bindings
! may have particular preferences for how this information is communicated:
! WSDL features correspond closely with (but are not identical to) SOAP 1.2
! features, as implemented in modules.
  </p>
  
  <p>
! Features may change the behavior described for other components.  In particular,
! note that a feature (or any other extension) may change the semantics of a message
! exchange pattern in some fashion, such as nominating an address for the delivery
! of faults, etc.
  </p>
  
  <p>
! The Web Services Description Working Group provides the following descriptions
! as models of feature descriptions for WSDL, and encourages implementors to support
! these features.
  </p>
  
--- 447,473 ----
  
  <p>
! Web Services Description Language (WSDL) features (hereafter 'features')
! define pieces of extended functionality which typically affect message
! exchanges.  Examples may include "reliability", "security", or
! "correlation", among others.  Features may be self-contained, or may be
! abstract, and thus expressed via bindings or SOAP modules.  These
! components may expose settable properties, named variables which affect
! the behavior of one or more features, bindings or SOAP modules.
  </p>
  
  <p>
! Features may change the behavior described for other components. In
! particular, note that a feature (or any other extension) may change the
! semantics of a message exchange pattern in some fashion, such as
! nominating an address for the delivery of faults, etc.
  </p>
  
  <p>
! The Web Services Description Working Group provides the following
! predefined features and SOAP modules for two reasons - first, we
! encourage implementors to support these features as we believe they
! offer important functionality.  Second, these specifications act as a
! model of how to write feature/module specs.  Some further
! (SOAP-specific) examples can be found in the SOAP 1.2 spec, part 2.
  </p>
  
***************
*** 506,510 ****
  </p>
  
! <div4 id="adf-dp-desc">
  <head>Description</head>
  
--- 509,515 ----
  </p>
  
! </div3>
! 
! <div3 id="adf-dp-desc">
  <head>Description</head>
  
***************
*** 531,544 ****
  
      &lt;!-- These elements are our data --&gt;
!     &lt;element name=&quot;isGoldClubMember&quot;&gt;
!      &lt;complexType&gt;
!       &lt;simpleContent&gt;
!        &lt;extension base=&quot;xs:boolean&quot;/&gt;
!        &lt;attribute xmlns:soap=&quot;http://www.w3.org/2003/05/soap-envelope&quot;
!                   ref=&quot;soap:mustUnderstand&quot;
!                   fixed=&quot;true&quot;/&gt;
!       &lt;/simpleContent&gt;
!      &lt;/complexType&gt;
!     &lt;/element&gt;
  
      &lt;element name=&quot;promotionalCode&quot;
--- 536,541 ----
  
      &lt;!-- These elements are our data --&gt;
!     &lt;element name=&quot;isGoldClubMember&quot; type="xs:boolean"
!          ad:mustUnderstand="true" /&gt;
  
      &lt;element name=&quot;promotionalCode&quot;
***************
*** 566,578 ****
  This example defines two pieces of application data, and associates them
  with the input message of the "reserveCar" operation.  Notice that the
! "promotionalCode" element is optional (minOccurs="0"), and that the
! "isGoldClubMember" element has fixed the value of the SOAP 1.2
! "mustUnderstand" element to "true".
  </p>
  
- </div4>
  </div3>
  
! <div3 id="adf-module">
  <head>Application Data Module</head>
  
--- 563,574 ----
  This example defines two pieces of application data, and associates them
  with the input message of the "reserveCar" operation.  Notice that the
! "promotionalCode" element is optional (minOccurs="0").
  </p>
  
  </div3>
  
! </div2> <!-- appdata feature -->
! 
! <div2 id="adf-module">
  <head>Application Data Module</head>
  
***************
*** 582,601 ****
  </p>
  
! <div4 id="adf-mod-impl">
  <head>Features Implemented</head>
  
  <p>
  This module implements the feature
! &AD-FEATURE;.
  </p>
  
! </div4>
  
! <div4 id="adf-mod-op">
  <head>Operation</head>
  
  <p>
  This module specifies how to transmit "out of band" application data, as
! defined in the Application Data feature, as SOAP headers.
  </p>
  
--- 578,598 ----
  </p>
  
! <div3 id="adf-mod-impl">
  <head>Features Implemented</head>
  
  <p>
  This module implements the feature
! <specref ref="app-data">&AD-FEATURE;</specref>.
  </p>
  
! </div3>
  
! <div3 id="adf-mod-op">
  <head>Operation</head>
  
  <p>
  This module specifies how to transmit "out of band" application data, as
! defined in the <specref ref="app-data">Application Data feature</specref>, 
! as SOAP headers.
  </p>
  
***************
*** 603,608 ****
  As a SOAP sender, if the property
  &AD-FEATURE-DATA-P; has a value then each of the
! top-level child element information items in the value SHOULD [ed:
! MUST?] be turned into a SOAP header.  The elements are serialized
  according to their schemas, which might include the SOAP
  "mustUnderstand" or "role" attributes, which will have the usual meaning
--- 600,605 ----
  As a SOAP sender, if the property
  &AD-FEATURE-DATA-P; has a value then each of the
! top-level child element information items in the value
! MUST be turned into a SOAP header.  The elements are serialized
  according to their schemas, which might include the SOAP
  "mustUnderstand" or "role" attributes, which will have the usual meaning
***************
*** 622,633 ****
  inside that header indicate which other headers are application data.
  The contents of each SOAP header identified as application data will be
! placed in a child element of the data property [ed: should we define a
! particular "wrapper" element here as the top level one?].
  </p>
  
- </div4>
  </div3>
  
! </div2>
  
  </div1> <!-- features -->
--- 619,628 ----
  inside that header indicate which other headers are application data.
  The contents of each SOAP header identified as application data will be
! placed in a child element of the data property.
  </p>
  
  </div3>
  
! </div2> <!-- appdata module -->
  
  </div1> <!-- features -->
***************
*** 712,715 ****
--- 707,716 ----
             <td>20040713</td>
             <td>aal</td>
+            <td>implement editorial changes requested after review by
+            GlenD, in application data feature and module.</td>
+         </tr>
+         <tr>
+            <td>20040713</td>
+            <td>aal</td>
             <td>address issues 233 &amp; 112 all at once, by increasing level 
             of all divs, adding new intro

Index: wsdl20-patterns.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** wsdl20-patterns.html	27 Jul 2004 14:50:11 -0000	1.6
--- wsdl20-patterns.html	29 Jul 2004 15:49:36 -0000	1.7
***************
*** 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 Linux/x86 (vers 1st July 2004), see www.w3.org" />
  <meta http-equiv="Content-Type" content=
  "text/html; charset=utf-8" />
***************
*** 169,180 ****
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href=
  "#adf-data-prop">AD/data Property</a><br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3.1
- <a href="#adf-dp-desc">Description</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.4 <a href=
! "#adf-module">Application Data Module</a><br />
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.4.1
! <a href="#adf-mod-impl">Features Implemented</a><br />
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.4.2
! <a href="#adf-mod-op">Operation</a><br />
  4. <a href="#References">References</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href=
--- 169,180 ----
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href=
  "#adf-data-prop">AD/data Property</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.4 <a href=
! "#adf-dp-desc">Description</a><br />
! &nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#adf-module">Application Data
! Module</a><br />
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href=
! "#adf-mod-impl">Features Implemented</a><br />
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.2 <a href=
! "#adf-mod-op">Operation</a><br />
  4. <a href="#References">References</a><br />
  &nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href=
***************
*** 530,540 ****
  Features</h2>
  <p>Web Services Description Language (WSDL) features (hereafter
! 'features') define properties or behaviors in the scope of a
! particular message exchange. Scoping rules are outlined in
! [REFERENCE]. A property exposed by a feature is visible to all
! participants in an exchange. Bindings may have particular
! preferences for how this information is communicated: WSDL features
! correspond closely with (but are not identical to) SOAP 1.2
! features, as implemented in modules.</p>
  <p>Features may change the behavior described for other components.
  In particular, note that a feature (or any other extension) may
--- 530,540 ----
  Features</h2>
  <p>Web Services Description Language (WSDL) features (hereafter
! 'features') define pieces of extended functionality which typically
! affect message exchanges. Examples may include "reliability",
! "security", or "correlation", among others. Features may be
! self-contained, or may be abstract, and thus expressed via bindings
! or SOAP modules. These components may expose settable properties,
! named variables which affect the behavior of one or more features,
! bindings or SOAP modules.</p>
  <p>Features may change the behavior described for other components.
  In particular, note that a feature (or any other extension) may
***************
*** 542,547 ****
  such as nominating an address for the delivery of faults, etc.</p>
  <p>The Web Services Description Working Group provides the
! following descriptions as models of feature descriptions for WSDL,
! and encourages implementors to support these features.</p>
  <div class="div2">
  <h3><a name="app-data" id="app-data"></a>3.1 Application Data
--- 542,551 ----
  such as nominating an address for the delivery of faults, etc.</p>
  <p>The Web Services Description Working Group provides the
! following predefined features and SOAP modules for two reasons -
! first, we encourage implementors to support these features as we
! believe they offer important functionality. Second, these
! specifications act as a model of how to write feature/module specs.
! Some further (SOAP-specific) examples can be found in the SOAP 1.2
! spec, part 2.</p>
  <div class="div2">
  <h3><a name="app-data" id="app-data"></a>3.1 Application Data
***************
*** 549,554 ****
  <div class="div3">
  <h4><a name="adf-name" id="adf-name"></a>3.1.1 Name</h4>
! <p>This feature is identified with the URI
! http://www.w3.org/@@@@/@@/features/AD</p>
  </div>
  <div class="div3">
--- 553,558 ----
  <div class="div3">
  <h4><a name="adf-name" id="adf-name"></a>3.1.1 Name</h4>
! <p>This feature is identified with the URI "
! http://www.w3.org/@@@@/@@/wsdl/feature/AD ".</p>
  </div>
  <div class="div3">
***************
*** 558,564 ****
  application-defined additional data declarations outside of the
  normal data channel (e.g. the SOAP body). The senders takes the
! value of the property http://www.w3.org/@@@@/@@/features/AD/data,
! which is defined below, and passes it to the receiver in a manner
! to be defined by the particular bindings/modules implementing this
  specification.</p>
  </div>
--- 562,569 ----
  application-defined additional data declarations outside of the
  normal data channel (e.g. the SOAP body). The senders takes the
! value of the property
! http://www.w3.org/@@@@/@@/wsdl/feature/AD/data, which is defined
! below, and passes it to the receiver in a manner to be defined by
! the particular bindings/modules implementing this
  specification.</p>
  </div>
***************
*** 567,574 ****
  Property</h4>
  <p>This property is identified with the URI
! http://www.w3.org/@@@@/@@/features/AD/data.</p>
! <div class="div4">
! <h5><a name="adf-dp-desc" id="adf-dp-desc"></a>3.1.3.1
! Description</h5>
  <p>The data property consists of a sequence of elements, each of
  which represents an individual piece of application data.
--- 572,580 ----
  Property</h4>
  <p>This property is identified with the URI
! "http://www.w3.org/@@@@/@@/wsdl/feature/AD/data".</p>
! </div>
! <div class="div3">
! <h4><a name="adf-dp-desc" id="adf-dp-desc"></a>3.1.4
! Description</h4>
  <p>The data property consists of a sequence of elements, each of
  which represents an individual piece of application data.
***************
*** 579,583 ****
  <div class="exampleInner">
  <pre>
- 
  &lt;types&gt;
   &lt;schema targetNamespace="http://foo"
--- 585,588 ----
***************
*** 590,603 ****
  
      &lt;!-- These elements are our data --&gt;
!     &lt;element name="isGoldClubMember"&gt;
!      &lt;complexType&gt;
!       &lt;simpleContent&gt;
!        &lt;extension base="xs:boolean"/&gt;
!        &lt;attribute xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
!                   ref="soap:mustUnderstand"
!                   fixed="true"/&gt;
!       &lt;/simpleContent&gt;
!      &lt;/complexType&gt;
!     &lt;/element&gt;
  
      &lt;element name="promotionalCode"
--- 595,600 ----
  
      &lt;!-- These elements are our data --&gt;
!     &lt;element name="isGoldClubMember" type="xs:boolean"
!          ad:mustUnderstand="true" /&gt;
  
      &lt;element name="promotionalCode"
***************
*** 612,616 ****
   &lt;operation name="reserveCar"&gt;
    &lt;input element="myNS:reserveCarRequest"&gt;
!    &lt;property uri="http://www.w3.org/@@@@/@@/features/AD/data"&gt;
      &lt;constraint xmlns:foo="http://foo"&gt;
       foo:myDataType
--- 609,613 ----
   &lt;operation name="reserveCar"&gt;
    &lt;input element="myNS:reserveCarRequest"&gt;
!    &lt;property uri="http://www.w3.org/@@@@/@@/wsdl/feature/AD/data"&gt;
      &lt;constraint xmlns:foo="http://foo"&gt;
       foo:myDataType
***************
*** 620,653 ****
   &lt;/operation&gt;
  &lt;/interface&gt;
- 
  </pre></div>
  <p>This example defines two pieces of application data, and
  associates them with the input message of the "reserveCar"
  operation. Notice that the "promotionalCode" element is optional
! (minOccurs="0"), and that the "isGoldClubMember" element has fixed
! the value of the SOAP 1.2 "mustUnderstand" element to "true".</p>
  </div>
  </div>
! <div class="div3">
! <h4><a name="adf-module" id="adf-module"></a>3.1.4 Application Data
! Module</h4>
  <p>This module is identified with the URI
  http://www.w3.org/@@@@/@@/modules/AD</p>
! <div class="div4">
! <h5><a name="adf-mod-impl" id="adf-mod-impl"></a>3.1.4.1 Features
! Implemented</h5>
! <p>This module implements the feature
! http://www.w3.org/@@@@/@@/features/AD.</p>
  </div>
! <div class="div4">
! <h5><a name="adf-mod-op" id="adf-mod-op"></a>3.1.4.2 Operation</h5>
  <p>This module specifies how to transmit "out of band" application
! data, as defined in the Application Data feature, as SOAP
! headers.</p>
  <p>As a SOAP sender, if the property
! http://www.w3.org/@@@@/@@/features/AD/data has a value then each of
! the top-level child element information items in the value SHOULD
! [ed: MUST?] be turned into a SOAP header. The elements are
! serialized according to their schemas, which might include the SOAP
  "mustUnderstand" or "role" attributes, which will have the usual
  meaning in the resultant headers. SOAP senders SHOULD also add an
--- 617,648 ----
   &lt;/operation&gt;
  &lt;/interface&gt;
  </pre></div>
  <p>This example defines two pieces of application data, and
  associates them with the input message of the "reserveCar"
  operation. Notice that the "promotionalCode" element is optional
! (minOccurs="0").</p>
  </div>
  </div>
! <div class="div2">
! <h3><a name="adf-module" id="adf-module"></a>3.2 Application Data
! Module</h3>
  <p>This module is identified with the URI
  http://www.w3.org/@@@@/@@/modules/AD</p>
! <div class="div3">
! <h4><a name="adf-mod-impl" id="adf-mod-impl"></a>3.2.1 Features
! Implemented</h4>
! <p>This module implements the feature <a href="#app-data"><b>3.1
! Application Data Feature</b></a>.</p>
  </div>
! <div class="div3">
! <h4><a name="adf-mod-op" id="adf-mod-op"></a>3.2.2 Operation</h4>
  <p>This module specifies how to transmit "out of band" application
! data, as defined in the <a href="#app-data"><b>3.1 Application Data
! Feature</b></a>, as SOAP headers.</p>
  <p>As a SOAP sender, if the property
! http://www.w3.org/@@@@/@@/wsdl/feature/AD/data has a value then
! each of the top-level child element information items in the value
! MUST be turned into a SOAP header. The elements are serialized
! according to their schemas, which might include the SOAP
  "mustUnderstand" or "role" attributes, which will have the usual
  meaning in the resultant headers. SOAP senders SHOULD also add an
***************
*** 658,663 ****
  <p>It is the responsibility of the receiving node to determine
  which, if any, SOAP headers will populate the
! http://www.w3.org/@@@@/@@/features/AD/data property. Typically this
! will be accomplished via using some metadata, such as an
  understanding of a constraint specified in WSDL, or out-of-band
  agreements. If the "dataHeaders" SOAP header (described above) is
--- 653,658 ----
  <p>It is the responsibility of the receiving node to determine
  which, if any, SOAP headers will populate the
! http://www.w3.org/@@@@/@@/wsdl/feature/AD/data property. Typically
! this will be accomplished via using some metadata, such as an
  understanding of a constraint specified in WSDL, or out-of-band
  agreements. If the "dataHeaders" SOAP header (described above) is
***************
*** 665,671 ****
  are application data. The contents of each SOAP header identified
  as application data will be placed in a child element of the data
! property [ed: should we define a particular "wrapper" element here
! as the top level one?].</p>
! </div>
  </div>
  </div>
--- 660,664 ----
  are application data. The contents of each SOAP header identified
  as application data will be placed in a child element of the data
! property.</p>
  </div>
  </div>
***************
*** 779,782 ****
--- 772,781 ----
  <td rowspan="1" colspan="1">20040713</td>
  <td rowspan="1" colspan="1">aal</td>
+ <td rowspan="1" colspan="1">implement editorial changes requested
+ after review by GlenD, in application data feature and module.</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20040713</td>
+ <td rowspan="1" colspan="1">aal</td>
  <td rowspan="1" colspan="1">address issues 233 &amp; 112 all at
  once, by increasing level of all divs, adding new intro div, adding

Received on Thursday, 29 July 2004 11:49:46 UTC