- From: Hugo Haas <hugo@dev.w3.org>
- Date: Thu, 29 Jul 2004 17:04:25 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv18411
Modified Files:
wsdl20-bindings.xml
Log Message:
Implemented http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0370.html
as discussed in today's call
Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.105
retrieving revision 1.106
diff -C2 -d -r1.105 -r1.106
*** wsdl20-bindings.xml 29 Jul 2004 10:20:07 -0000 1.105
--- wsdl20-bindings.xml 29 Jul 2004 17:04:23 -0000 1.106
***************
*** 1123,1138 ****
<!-- +++++++++ -->
- <div2 id="_http_binding_supported_feature">
- <head>Supported features</head>
-
- <p>This binding specification supports the Application Data
- Feature (<attval>&AD-FEATURE;</attval>) as defined is <bibref
- ref="WSDL-PART2"/> (see <specref
- ref="http-ad-serialization"/>).</p>
-
- </div2>
-
- <!-- +++++++++ -->
-
<div2 id="_http_binding_default_rules">
<head>Default Binding Rules</head>
--- 1123,1126 ----
***************
*** 1449,1455 ****
location of the bound operation.</p>
- <p>"Out-of-band" application data is serialized as explained
- in <specref ref="http-ad-serialization"/>.</p>
-
</div3>
<div3 id="http-operation-decl-relate">
--- 1437,1440 ----
***************
*** 1675,1679 ****
<ednote>
! <edtext>Note that there is still some ed notes in there.</edtext>
</ednote>
--- 1660,1664 ----
<ednote>
! <edtext>This needs to be moved to Part 2</edtext>
</ednote>
***************
*** 1684,1705 ****
<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 indicate a possible &EII;
! that SHOULD [ed: MUST?] be turned into an HTTP header.</p>
<p>Only &EII; of type type <attval>xs:string</attval> type,
including <attval>xs:anyURI</attval>, may be serialized. All
! complex data types are ignored. Each such &EII; is serialized
! as follows:</p>
<ulist>
<item><p>The HTTP header name used is the &EII; local
! name. If an HTTP header corresponding to the &EII; local
! name is set by a mechanism other than the Application Data
! Feature, such as the HTTP stack or another feature, then an
! error MUST be raised.</p></item>
<item><p>The HTTP header content is serialized from the
! &EII; value. Any attributes on data elements are
! ignored. Where the &EII; contains content that cannot be
! directly encoded per the HTTP specification, it MUST be
! escaped. [ed: how?]</p></item>
</ulist>
--- 1669,1693 ----
<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 a &EII;
! that MUST be turned into an HTTP header.</p>
<p>Only &EII; of type type <attval>xs:string</attval> type,
including <attval>xs:anyURI</attval>, may be serialized. All
! complex data types are ignored. Attributes on data elements
! are ignored.</p>
!
! <p>Each such &EII; is serialized as follows:</p>
<ulist>
<item><p>The HTTP header name used is the &EII; local
! name. The &EII; local name MUST follow the field-name
! production rules as specified in section 4.2 of <bibref
! ref="RFC2616"/>; if not, the &EII; MUST be ignored. If an
! HTTP header corresponding to the &EII; local name is set by
! a mechanism other than the Application Data Feature, such as
! the HTTP stack or another feature, then an error MUST be
! raised.</p></item>
<item><p>The HTTP header content is serialized from the
! &EII; value in UTF-8. If this serialization is NOT possible,
! then the &EII; MUST be ignored.</p></item>
</ulist>
***************
*** 1708,1720 ****
<attval>&AD-FEATURE-DATA-P;</attval> property. Typically this
will be accomplished via using some metadata, such as an
! understanding of a <constraint> specified in WSDL [ed:
! constraint is not defined], or out-of-band agreements. The
! contents of each such HTTP header 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?]. Each
! child &EII; is generated by using the HTTP header name as the
! element information item local name [ed: should we define a
! particular namespace?] and the HTTP header value as the &EII;
! value.</p>
</div2>
--- 1696,1713 ----
<attval>&AD-FEATURE-DATA-P;</attval> property. Typically this
will be accomplished via using some metadata, such as an
! understanding of a <constraint> specified in <bibref
! ref="WSDL-PART1"/>, or out-of-band agreements. The contents
! of each such HTTP header will be placed in a child element of
! the data property. Each child &EII; is generated by using the
! HTTP header name as the &EII; local name and the HTTP header
! value as the &EII; value.</p>
!
! <note>
! <p>
! The &EII; local name who's the parent node of the &EII;s
! received as well as the namespace of those &EII;s are
! implementation-specific.
! </p>
! </note>
</div2>
***************
*** 2883,2886 ****
--- 2876,2884 ----
<td>20040729</td>
<td>HH</td>
+ <td>Clarified AD Feature serialization in HTTP.</td>
+ </tr>
+ <tr>
+ <td>20040729</td>
+ <td>HH</td>
<td>Added AD Feature support in HTTP binding.</td>
</tr>
Received on Thursday, 29 July 2004 13:04:25 UTC