- From: Amelia Lewis <alewis@dev.w3.org>
- Date: Fri, 30 Jul 2004 19:29:04 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv23943
Modified Files:
wsdl20-patterns.xml
Log Message:
Update abstract, fix attval abuse, quote URIs, fix example per Asir
Index: wsdl20-patterns.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** wsdl20-patterns.xml 30 Jul 2004 14:55:59 -0000 1.22
--- wsdl20-patterns.xml 30 Jul 2004 19:29:02 -0000 1.23
***************
*** 48,55 ****
<abstract id='Abstract'>
<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>
</abstract>
--- 48,57 ----
<abstract id='Abstract'>
<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>
</abstract>
***************
*** 481,487 ****
<p>
This feature is identified with the URI
! <attval>
! &AD-FEATURE;
! </attval>.
</p>
--- 483,487 ----
<p>
This feature is identified with the URI
! '&AD-FEATURE;'
</p>
***************
*** 495,499 ****
application-defined additional data declarations outside of the normal
data channel (e.g. the SOAP body). The senders takes the value of the
! property &AD-FEATURE-DATA-P;, which is defined
below, and passes it to the receiver in a manner to be defined by the
particular bindings/modules implementing this specification.
--- 495,499 ----
application-defined additional data declarations outside of the normal
data channel (e.g. the SOAP body). The senders takes the value of the
! property '&AD-FEATURE-DATA-P;', which is defined
below, and passes it to the receiver in a manner to be defined by the
particular bindings/modules implementing this specification.
***************
*** 507,511 ****
<p>
This property is identified with the URI
! <attval>&AD-FEATURE-DATA-P;</attval>.
</p>
--- 507,511 ----
<p>
This property is identified with the URI
! '&AD-FEATURE-DATA-P;'.
</p>
***************
*** 532,536 ****
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 -->
<complexType name="myDataType">
--- 532,535 ----
***************
*** 575,579 ****
<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
--- 574,578 ----
<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
***************
*** 591,595 ****
<p>
This module is identified with the URI
! http://www.w3.org/@@@@/@@/modules/AD
</p>
--- 590,594 ----
<p>
This module is identified with the URI
! 'http://www.w3.org/@@@@/@@/modules/AD'
</p>
***************
*** 599,603 ****
<p>
This module implements the feature
! &AD-FEATURE; (see <specref ref="app-data"/>).
</p>
--- 598,602 ----
<p>
This module implements the feature
! '&AD-FEATURE;' (see <specref ref="app-data"/>).
</p>
***************
*** 615,619 ****
<p>
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.
--- 614,618 ----
<p>
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.
***************
*** 623,627 ****
"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.
--- 622,626 ----
"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.
***************
*** 631,635 ****
It is the responsibility of the receiving node to determine which, if
any, SOAP headers will populate the
! &AD-FEATURE-DATA-P; 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
--- 630,634 ----
It is the responsibility of the receiving node to determine which, if
any, SOAP headers will populate the
! '&AD-FEATURE-DATA-P;' 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
***************
*** 656,662 ****
<p>
This feature-binding is identified with the URI
! <attval>
! http://www.w3.org/@@@@/@@/features/AD-HTTP
! </attval>.
</p>
--- 655,659 ----
<p>
This feature-binding is identified with the URI
! 'http://www.w3.org/@@@@/@@/features/AD-HTTP'
</p>
***************
*** 668,672 ****
<p>
This module implements the feature
! &AD-FEATURE; (see <specref ref="app-data"/>).
</p>
--- 665,669 ----
<p>
This module implements the feature
! '&AD-FEATURE;' (see <specref ref="app-data"/>).
</p>
***************
*** 681,685 ****
as HTTP headers.</p>
! <p>If the property <attval>&AD-FEATURE-DATA-P;</attval> has a
value for a message to be serialized as an HTTP message, then
each of the top-level child &EII;s indicates an &EII;
--- 678,682 ----
as HTTP headers.</p>
! <p>If the property '&AD-FEATURE-DATA-P;' has a
value for a message to be serialized as an HTTP message, then
each of the top-level child &EII;s indicates an &EII;
***************
*** 708,714 ****
<p>It is the responsibility of the receiving node to determine
which, if any, HTTP headers will populate the
! <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
--- 705,711 ----
<p>It is the responsibility of the receiving node to determine
which, if any, HTTP headers will populate the
! '&AD-FEATURE-DATA-P;' 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 15:29:13 UTC