- From: Amelia Lewis <alewis@dev.w3.org>
- Date: Thu, 29 Jul 2004 17:40:50 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv23897 Modified Files: wsdl20-patterns.html wsdl20-patterns.xml Log Message: Moved HTTP serialization of AD Feature into this part. Index: wsdl20-patterns.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** wsdl20-patterns.xml 29 Jul 2004 15:49:36 -0000 1.16 --- wsdl20-patterns.xml 29 Jul 2004 17:40:48 -0000 1.17 *************** *** 626,629 **** --- 626,700 ---- </div2> <!-- appdata module --> + <!-- inconsistent formatting, because we got it from another doc --> + + <div2 id="adf-http-serial"> + <head> + Application data serialization as HTTP headers + </head> + + <div3 id="adf-http-impl"> + <head>Features Implemented</head> + + <p> + This module implements the feature + <specref ref="app-data">&AD-FEATURE;</specref>. + </p> + + </div3> + + <div3 id="adf-http-op"> + <head>Operation</head> + + <p>This section specifies how to transmit "out of band" + application data, defined in the <specref ref="app-data">Application Data Feature</specref> + 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; + that MUST be turned into an HTTP header.</p> + + <p>Only &EII;s of type <attval>xs:string</attval> + or <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 <specref ref="app-data">Application Data Feature</specref>, 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> + + <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 + <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 + 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 local name of the &EII; which is the parent node of the &EII;s + received, as well as the namespace of those &EII;s, are + implementation-specific. + </p> + </note> + + </div3> + </div2> <!-- ad http serialization --> + </div1> <!-- features --> Index: wsdl20-patterns.html =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-patterns.html,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** wsdl20-patterns.html 29 Jul 2004 15:49:36 -0000 1.7 --- wsdl20-patterns.html 29 Jul 2004 17:40:48 -0000 1.8 *************** *** 177,180 **** --- 177,186 ---- 3.2.2 <a href= "#adf-mod-op">Operation</a><br /> + 3.3 <a href="#adf-http-serial">Application + 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 /> 4.1 <a href= *************** *** 663,666 **** --- 669,735 ---- </div> </div> + <div class="div2"> + <h3><a name="adf-http-serial" id="adf-http-serial"></a>3.3 + 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 <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 <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. + Attributes on data elements are ignored.</p> + <p>Each such <em>element information item</em> is serialized as + follows:</p> + <ul> + <li> + <p>The HTTP header name used is the <em>element information + item</em> local name. The <em>element information item</em> local + name MUST follow the field-name production rules as specified in + section 4.2 of [<cite><a href="#">RFC2616</a></cite>]; if not, the + <em>element information item</em> MUST be ignored. If an HTTP + header corresponding to the <em>element information item</em> local + name is set by a mechanism other than the <a href= + "#app-data"><b>3.1 Application Data Feature</b></a>, such as the + HTTP stack or another feature, then an error MUST be raised.</p> + </li> + <li> + <p>The HTTP header content is serialized from the <em>element + information item</em> value in UTF-8. If this serialization is NOT + possible, then the <em>element information item</em> MUST be + ignored.</p> + </li> + </ul> + <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> + <p>The local name of the <em>element information item</em> which is + the parent node of the <em>element information item</em>s received, + as well as the namespace of those <em>element information + item</em>s, are implementation-specific.</p> + </div> + </div> + </div> </div> <div class="div1">
Received on Thursday, 29 July 2004 13:40:51 UTC