- From: Amelia Lewis <alewis@dev.w3.org>
- Date: Fri, 30 Jul 2004 14:56:01 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv22200
Modified Files:
wsdl20-patterns.xml
Log Message:
Updates per Glen's email, mostly ad:mustUnderstand related, but also HTTP feature-binding.
Index: wsdl20-patterns.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** wsdl20-patterns.xml 30 Jul 2004 11:38:07 -0000 1.21
--- wsdl20-patterns.xml 30 Jul 2004 14:55:59 -0000 1.22
***************
*** 530,534 ****
<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 -->
--- 530,535 ----
<schema targetNamespace="http://foo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
! xmlns="http://www.w3.org/2001/XMLSchema"
! xmlns:ad="&AD-FEATURE;">
<import namespace="http://www.w3.org/2003/05/soap-envelope"/>
<!-- Define the data type we'll use later -->
***************
*** 538,542 ****
<!-- These elements are our data -->
<element name="isGoldClubMember" type="xs:boolean"
! ad:mustUnderstand="true" />
<element name="promotionalCode"
--- 539,543 ----
<!-- These elements are our data -->
<element name="isGoldClubMember" type="xs:boolean"
! ad:mustUnderstand="true" />
<element name="promotionalCode"
***************
*** 569,572 ****
--- 570,587 ----
</div3>
+ <div3 id="adf-mu-att">
+ <head>The <att>ad:mustUnderstand</att> Attribute</head>
+
+ <p> You may choose to decorate your application data element declarations
+ with an attribute with the namespace
+ "&AD-FEATURE;" 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 <specref ref="adf-module" />) should mark them as mandatory in an
+ appropriate way.</p>
+
+ </div3>
+
</div2> <!-- appdata feature -->
***************
*** 602,609 ****
&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
! 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
--- 617,626 ----
&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, 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
***************
*** 634,637 ****
--- 651,666 ----
</head>
+ <div3 id="adf-http-name">
+ <head>Name</head>
+
+ <p>
+ This feature-binding is identified with the URI
+ <attval>
+ http://www.w3.org/@@@@/@@/features/AD-HTTP
+ </attval>.
+ </p>
+
+ </div3>
+
<div3 id="adf-http-impl">
<head>Features Implemented</head>
***************
*** 655,659 ****
value for a message to be serialized as an HTTP message, then
each of the top-level child &EII;s indicates an &EII;
! that MUST be turned into an HTTP header.</p>
<p>Only &EII;s of type <attval>xs:string</attval>
--- 684,688 ----
value for a message to be serialized as an HTTP message, then
each of the top-level child &EII;s indicates an &EII;
! that MUST be turned into an HTTP header if possible.</p>
<p>Only &EII;s of type <attval>xs:string</attval>
***************
*** 681,685 ****
<attval>&AD-FEATURE-DATA-P;</attval> property. Typically this
will be accomplished via some metadata, such as a
! <constraint> specified in <bibref
ref="WSDL-PART1"/>, or out-of-band agreements. The content
of each such HTTP header will be placed in a child element of
--- 710,714 ----
<attval>&AD-FEATURE-DATA-P;</attval> property. Typically this
will be accomplished via some metadata, such as a
! property <constraint> specified in <bibref
ref="WSDL-PART1"/>, or out-of-band agreements. The content
of each such HTTP header will be placed in a child element of
Received on Friday, 30 July 2004 10:57:34 UTC