- From: Amelia Lewis <alewis@dev.w3.org>
- Date: Fri, 30 Jul 2004 19:31:06 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv24156
Modified Files:
wsdl20-patterns.html
Log Message:
updated version, corresponding with xml commit
Index: wsdl20-patterns.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** wsdl20-patterns.html 30 Jul 2004 15:00:53 -0000 1.9
--- wsdl20-patterns.html 30 Jul 2004 19:31:04 -0000 1.10
***************
*** 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" />
***************
*** 106,112 ****
<div>
<h2><a name="abstract" id="abstract">Abstract</a></h2>
! <p>This document describes Web Services Description Language (WSDL)
! Version 2.0 message exchange patterns. These patterns are intended
! for use with the Web Services Description Language (WSDL).</p>
</div>
<div>
--- 106,115 ----
<div>
<h2><a name="abstract" id="abstract">Abstract</a></h2>
! <p>This document describes extensions for the Web Services
! Description Language (WSDL) Version 2.0 . These extensions include
! Message Exchange Patterns (MEPs), features, SOAP modules, and
! bindings of features. The Working Group has discussed and approved
! these extensions, and recommends their use with the Web Services
! Description Language (WSDL).</p>
</div>
<div>
***************
*** 171,174 ****
--- 174,179 ----
3.1.4 <a href=
"#adf-dp-desc">Description</a><br />
+ 3.1.5 <a href=
+ "#adf-mu-att">The ad:mustUnderstand Attribute</a><br />
3.2 <a href="#adf-module">Application Data
Module</a><br />
***************
*** 180,185 ****
data serialization as HTTP headers</a><br />
3.3.1 <a href=
! "#adf-http-impl">Features Implemented</a><br />
3.3.2 <a href=
"#adf-http-op">Operation</a><br />
4. <a href="#References">References</a><br />
--- 185,192 ----
data serialization as HTTP headers</a><br />
3.3.1 <a href=
! "#adf-http-name">Name</a><br />
3.3.2 <a href=
+ "#adf-http-impl">Features Implemented</a><br />
+ 3.3.3 <a href=
"#adf-http-op">Operation</a><br />
4. <a href="#References">References</a><br />
***************
*** 559,564 ****
<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">
--- 566,571 ----
<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">
***************
*** 569,573 ****
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
--- 576,580 ----
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
***************
*** 578,582 ****
Property</h4>
<p>This property is identified with the URI
! "http://www.w3.org/@@@@/@@/wsdl/feature/AD/data".</p>
</div>
<div class="div3">
--- 585,589 ----
Property</h4>
<p>This property is identified with the URI
! 'http://www.w3.org/@@@@/@@/wsdl/feature/AD/data'.</p>
</div>
<div class="div3">
***************
*** 594,599 ****
<schema targetNamespace="http://foo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns="http://www.w3.org/2001/XMLSchema">
! <import namespace="http://www.w3.org/2003/05/soap-envelope"/>
<!-- Define the data type we'll use later -->
<complexType name="myDataType">
--- 601,606 ----
<schema targetNamespace="http://foo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns="http://www.w3.org/2001/XMLSchema"
! xmlns:ad="http://www.w3.org/@@@@/@@/wsdl/feature/AD">
<!-- Define the data type we'll use later -->
<complexType name="myDataType">
***************
*** 602,606 ****
<!-- These elements are our data -->
<element name="isGoldClubMember" type="xs:boolean"
! ad:mustUnderstand="true" />
<element name="promotionalCode"
--- 609,613 ----
<!-- These elements are our data -->
<element name="isGoldClubMember" type="xs:boolean"
! ad:mustUnderstand="true" />
<element name="promotionalCode"
***************
*** 629,632 ****
--- 636,652 ----
(minOccurs="0").</p>
</div>
+ <div class="div3">
+ <h4><a name="adf-mu-att" id="adf-mu-att"></a>3.1.5 The
+ <code>ad:mustUnderstand</code> Attribute</h4>
+ <p>You may choose to decorate your application data element
+ declarations with an attribute with the namespace
+ 'http://www.w3.org/@@@@/@@/wsdl/feature/AD' and the local name
+ "mustUnderstand". This indicates at the abstract level that the
+ particular element thus decorated is mandatory, and implementations
+ of this feature which support expression of mandatory data (i.e.
+ the Application Data SOAP Module, see <a href="#adf-module"><b>3.2
+ Application Data Module</b></a>) should mark them as mandatory in
+ an appropriate way.</p>
+ </div>
</div>
<div class="div2">
***************
*** 634,643 ****
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
! http://www.w3.org/@@@@/@@/wsdl/feature/AD (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>).</p>
</div>
--- 654,663 ----
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
! 'http://www.w3.org/@@@@/@@/wsdl/feature/AD' (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>).</p>
</div>
***************
*** 649,672 ****
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
! additional header, with namespace
! "http://www.w3.org/@@@@/@@/modules/AD" and local name "dataHeaders"
! - this header contains a list of element QNames, one for each
! application data header created in the first step.</p>
<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
! present, the QNames 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>
</div>
</div>
--- 669,693 ----
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, and if the "ad:mustUnderstand"
! attribute exists with the value "true" on any given element
! declaration, that particular SOAP header should be marked as
! "mustUnderstand='true'" or "mustUnderstand='1'" as per the SOAP
! specification. SOAP senders SHOULD also add an additional header,
! with namespace 'http://www.w3.org/@@@@/@@/modules/AD' and local
! name "dataHeaders" - this header contains a list of element QNames,
! one for each application data header created in the first step.</p>
<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 present, the QNames 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>
</div>
</div>
***************
*** 675,695 ****
Application data serialization as HTTP headers</h3>
<div class="div3">
! <h4><a name="adf-http-impl" id="adf-http-impl"></a>3.3.1 Features
Implemented</h4>
<p>This module implements the feature
! http://www.w3.org/@@@@/@@/wsdl/feature/AD (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>).</p>
</div>
<div class="div3">
! <h4><a name="adf-http-op" id="adf-http-op"></a>3.3.2 Operation</h4>
<p>This section specifies how to transmit "out of band" application
data, defined in the Application Data Feature (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>) as HTTP
headers.</p>
! <p>If the property "http://www.w3.org/@@@@/@@/wsdl/feature/AD/data"
has a value for a message to be serialized as an HTTP message, then
each of the top-level child <em>element information item</em>s
indicates an <em>element information item</em> that MUST be turned
! into an HTTP header.</p>
<p>Only <em>element information item</em>s of type "xs:string" or
"xs:anyURI" may be serialized. All complex data types are ignored.
--- 696,721 ----
Application data serialization as HTTP headers</h3>
<div class="div3">
! <h4><a name="adf-http-name" id="adf-http-name"></a>3.3.1 Name</h4>
! <p>This feature-binding is identified with the URI
! 'http://www.w3.org/@@@@/@@/features/AD-HTTP'</p>
! </div>
! <div class="div3">
! <h4><a name="adf-http-impl" id="adf-http-impl"></a>3.3.2 Features
Implemented</h4>
<p>This module implements the feature
! 'http://www.w3.org/@@@@/@@/wsdl/feature/AD' (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>).</p>
</div>
<div class="div3">
! <h4><a name="adf-http-op" id="adf-http-op"></a>3.3.3 Operation</h4>
<p>This section specifies how to transmit "out of band" application
data, defined in the Application Data Feature (see <a href=
"#app-data"><b>3.1 Application Data Feature</b></a>) as HTTP
headers.</p>
! <p>If the property 'http://www.w3.org/@@@@/@@/wsdl/feature/AD/data'
has a value for a message to be serialized as an HTTP message, then
each of the top-level child <em>element information item</em>s
indicates an <em>element information item</em> that MUST be turned
! into an HTTP header if possible.</p>
<p>Only <em>element information item</em>s of type "xs:string" or
"xs:anyURI" may be serialized. All complex data types are ignored.
***************
*** 719,731 ****
<p>It is the responsibility of the receiving node to determine
which, if any, HTTP headers will populate the
! "http://www.w3.org/@@@@/@@/wsdl/feature/AD/data" property.
Typically this will be accomplished via some metadata, such as a
! <constraint> specified in [<cite><a href="#WSDL-PART1">WSDL
! 2.0 Core Language</a></cite>], or out-of-band agreements. The
! content of each such HTTP header will be placed in a child element
! of the data property. Each child <em>element information item</em>
! is generated by using the HTTP header name as the <em>element
! information item</em> local name and the HTTP header value as the
! <em>element information item</em> value.</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
--- 745,757 ----
<p>It is the responsibility of the receiving node to determine
which, if any, HTTP headers will populate the
! 'http://www.w3.org/@@@@/@@/wsdl/feature/AD/data' property.
Typically this will be accomplished via some metadata, such as a
! {property constraint} specified in [<cite><a href=
! "#WSDL-PART1">WSDL 2.0 Core Language</a></cite>], or out-of-band
! agreements. The content of each such HTTP header will be placed in
! a child element of the data property. Each child <em>element
! information item</em> is generated by using the HTTP header name as
! the <em>element information item</em> local name and the HTTP
! header value as the <em>element information item</em> value.</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
Received on Friday, 30 July 2004 15:31:20 UTC