W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > November 2005

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.126,1.127

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 10 Nov 2005 07:31:47 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20051110073147.7F4AE4F04E@homer.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv25345

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
LC345


Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.126
retrieving revision 1.127
diff -C2 -d -r1.126 -r1.127
*** wsdl20-adjuncts.xml	9 Nov 2005 03:37:59 -0000	1.126
--- wsdl20-adjuncts.xml	10 Nov 2005 07:31:45 -0000	1.127
***************
*** 3769,3860 ****
          <head>Serialization Format of Instance Data</head>
          <p>
! 	The following serialization formats can be used to encode the
  	<termref def="instance_data">instance data</termref>
! 	corresponding to the input and output message, as well as the media types
! 	and HTTP headers associated.
        </p>
        <p>
! 	Other serialization formats may be used. Those MAY place
  	restrictions on the style of the Interface Operation bound.
        </p>
-         <div3 id="_http_x-www-form-urlencoded">
-           <head>Serialization as <attval>application/x-www-form-urlencoded</attval>
-           </head>
-           <p>
- 	  This serialization format is designed to allow a client or
- 	  Web service to produce an IRI based on the <termref
- 	  def="instance_data">instance data</termref> of a message.
- 	  It may only be used when binding <comp>Interface
- 	  Operation</comp> whose <prop comp="Interface Operation">style</prop> property has a value of
- 	  <attval>&IRI-STYLE;</attval> as defined in <specref
- 	  ref="_operation_iri_style"/>, i.e. this serialization format
- 	  may only be used to serialize the initial message of an
- 	  interface operation.
- 	  </p>
  
! 	  <p>
! 	    Specifically, for the HTTP binding defined in this section
! 	    (<specref ref="http-binding"/>),
! 	    <attval>application/x-www-form-urlencoded</attval> MAY be
! 	    used as a value for the <prop comp="Binding Operation">http input serialization</prop> property of the
! 	    <comp>Binding Operation</comp> component, but MUST NOT be
! 	    used as a value as a value for the <prop comp="Binding Operation">http output serialization</prop> or <prop
! 	    comp="Binding Operation">http fault serialization</prop>
! 	    properties.
! 	  </p>
  
! 	  <p>Because the IRI Style constrains the instance data not to
! 	  contain multiple children elements declared with the same
! 	  local name, elements can be serialized in the request IRI
! 	  with their local names unambiguously.
! 	  </p>
  
!           <p>
! 	  Elements from the instance data can be inserted into
! 	  the path of the request IRI, or a query parameter, as shown in
! 	  the example below:
! 	</p>
!           <example id="urlencoded_example">
!             <head>Instance data serialized in a IRI</head>
!             <p>
! 	    The following instance data of an input message
! 	  </p>
!             <eg xml:space="preserve">&lt;data&gt;
!   &lt;town&gt;Fréjus&lt;/town&gt;
!   &lt;date&gt;2004-01-16&lt;/date&gt;
!   &lt;unit&gt;C&lt;/unit&gt;
! &lt;/data&gt;</eg>
!             <p>
! 	    with the following <el>operation</el> element
! 	  </p>
!             <eg xml:space="preserve">&lt;operation ref='t:data'
!     whttp:location='temperature/{town}'
!     whttp:method='GET' /&gt;</eg>
!             <p>
! 	    and the following <el>endpoint</el> element
! 	  </p>
!             <eg xml:space="preserve">&lt;endpoint name='e' binding='t:b'
!     address='http://ws.example.com/service1/' /&gt;</eg>
!             <p>
! 	    will serialize the message in the IRI as follow:
! 	  </p>
!             <eg xml:space="preserve">http://ws.example.com/service1/temperature/Fr%C3%A9jus?date=2004-01-16&amp;unit=C</eg>
!           </example>
  
! 	  <p>In this serialization, the value of the <prop
! 	  comp="Binding Operation">http location</prop> property of the
! 	  <comp>Binding Operation</comp> component, if present,
! 	   is used as a template which is combined with the
! 	  <prop comp="Endpoint">address</prop> property of the endpoint element to
! 	  form the full IRI to be used in an HTTP request, as
! 	  specified in section <specref ref="http-operation-decl-relate"/>.</p>
  
! 	  <p>This IRI MUST be mapped to an URI for use in the HTTP
! 	  Request as per section 3.1 "Mapping of IRIs to URIs" of the
! 	  IRI specification <bibref ref="RFC3987"/>.</p>
  
!           <div4 id="_http_operation_location_cited_get">
!             <head>Case of elements cited in the {http location}
! 	    property</head>
              <ednote>
                <name>URIPath Feedback Requested</name>
--- 3769,3870 ----
          <head>Serialization Format of Instance Data</head>
          <p>
! 	The following serialization formats define rules to encode an
  	<termref def="instance_data">instance data</termref>
! 	corresponding to an input and output message as an HTTP
! 	message.  <specref ref="http_sftab"/> gives an overview of
! 	those serialization formats.
        </p>
        <p>
! 	Other serialization formats may be defined. Those MAY place
  	restrictions on the style of the Interface Operation bound.
        </p>
  
!       <table border="1" id='http_sftab'>
! 	<caption>Applicability of the serialization
! 	formats for the HTTP binding defined in this
! 	specification</caption>
! 	<tbody>
! 	  <tr>
! 	    <th colspan="3">HTTP message</th>
! 	    <th colspan="4">Serialization of the instance data in
! 	    parts of an HTTP message</th>
! 	  </tr>
! 	  <tr>
! 	    <th rowspan="7">Input message</th>
! 	    <td colspan="2">HTTP request with method:</td>
! 	    <td><emph>application/x-www-form-urlencoded</emph></td>
! 	    <td><emph>application/xml</emph></td>
! 	    <td><emph>multipart/form-data</emph></td>
! 	  </tr>
! 	  <tr>
! 	    <td rowspan="3">Without message body</td>
! 	    <td>GET</td>
! 	    <td rowspan="3">&#x2713;</td>
! 	    <td rowspan="3">-</td>
! 	    <td rowspan="3">-</td>
! 	  </tr>
! 	  <tr>
! 	    <td>DELETE</td>
! 	  </tr>
! 	  <tr>
! 	    <td>Other</td>
! 	  </tr>
! 	  <tr>
! 	    <td rowspan="3">With message body</td>
! 	    <td>POST</td>
! 	    <td rowspan="3">&#x2713;</td>
! 	    <td rowspan="3">&#x2713;</td>
! 	    <td rowspan="3">&#x2713;</td>
! 	  </tr>
! 	  <tr>
! 	    <td>PUT</td>
! 	  </tr>
! 	  <tr>
! 	    <td>Other</td>
! 	  </tr>
! 	  <tr>
! 	    <th>Output message</th>
! 	    <td colspan="2">HTTP response</td>
! 	    <td>-</td>
! 	    <td>&#x2713;</td>
! 	    <td>&#x2713;</td>
! 	  </tr>
! 	</tbody>
!       </table>
  
!       <div3 id="_http_location_template">
! 	<head>Serialization of the instance data in parts of the HTTP request IRI</head>
  
! 	    <p>This section defines templating rules for the <prop comp="Binding Operation">http
! 	    location</prop> property of the <comp>Binding
! 	    Operation</comp> component. It is used by the serialization formats defined in section <specref ref="_http_serialization"/>.</p>
  
! 	    <p>With this HTTP binding, part of the instance data for
! 	    HTTP requests MAY be serialized in the HTTP request IRI,
! 	    and another part MAY be serialized in the HTTP message
! 	    body.</p>
  
! 	    <p>If the <prop comp="Interface Operation">style</prop> property of the <comp>Interface Operation</comp> bound has a value of
! 	  <attval>&IRI-STYLE;</attval> as defined in <specref
! 	  ref="_operation_iri_style"/>, and if the <prop comp="Binding Operation">http
! 	    location</prop> property of the <comp>Binding
! 	    Operation</comp> component is present, the value of the <prop comp="Binding Operation">http
! 	    location</prop> property component is used as a
! 	    template which is combined with the <prop
! 	    comp="Endpoint">address</prop> property of the endpoint
! 	    element to form the full IRI to be used in an HTTP
! 	    request, as specified in section <specref
! 	    ref="http-operation-decl-relate"/>.</p>
  
! 	    <p>The resulting IRI MUST be mapped to an URI for use in
! 	    the HTTP Request as per section 3.1 "Mapping of IRIs to
! 	    URIs" of the IRI specification <bibref
! 	    ref="RFC3987"/>. Additional rules for the serialization of
! 	    the HTTP request IRI MAY be defined by a serialization
! 	    format.</p>
! 
!           <div4 id="_http_operation_location_cited_ser">
!             <head>Construction of the request IRI using the {http
!             location} property</head>
              <ednote>
                <name>URIPath Feedback Requested</name>
***************
*** 3870,3877 ****
  	    elements from the 
  				<termref def="instance_data">instance data</termref> of the
! 				input message to be serialized in the
! 				path component of the
! 				request IRI ("Syntax Components", <bibref ref="RFC3987"/>,
! 	    Section 3) by enclosing the element name within curly
  				braces (e.g. <attval>temperature/{town}</attval>):
  				</p>
--- 3880,3885 ----
  	    elements from the 
  				<termref def="instance_data">instance data</termref> of the
! 				message to be serialized in 
! 				request IRI by enclosing the element name within curly
  				braces (e.g. <attval>temperature/{town}</attval>):
  				</p>
***************
*** 3893,3902 ****
              <p>An element MUST NOT be cited more than once within
  				the <prop comp="Binding Operation">http location</prop> property.</p>
- 	      <p>An element name MAY be followed by a slash (i.e. "/")
- 	      inside curly braces
- 	      (e.g. <attval>temperature/{town/}</attval>) to indicate that
- 	      no other element must be serialized in the request IRI
- 	      (see <specref
- 	      ref="_http_operation_location_notcited_get"/>).</p>
              <p>Strings enclosed within single curly braces MUST be
  				element names from the <termref def="instance_data">instance
--- 3901,3904 ----
***************
*** 3905,3911 ****
  				within single curly braces are a fatal error.
  				</p>
            </div4>
            <div4 id="_http_operation_location_notcited_get">
!             <head>Case of elements NOT cited in the {http location} property</head>
  	    <p>If not all elements from the <termref
  	    def="instance_data">instance data</termref> are cited in
--- 3907,3961 ----
  				within single curly braces are a fatal error.
  				</p>
+ 
            </div4>
+ 
+ 	</div3>
+ 
+         <div3 id="_http_x-www-form-urlencoded">
+           <head>Serialization as <attval>application/x-www-form-urlencoded</attval>
+           </head>
+           <p>
+ 	  This serialization format is designed to allow a client or
+ 	  Web service to produce an IRI based on the <termref
+ 	  def="instance_data">instance data</termref> of a message and
+ 	  serialize a query string in the HTTP message body as <code>application/x-www-form-urlencoded</code>.
+ 	  </p>
+ 
+ 	  <p>
+ 	  It may only be used when binding <comp>Interface
+ 	  Operation</comp> whose <prop comp="Interface Operation">style</prop> property has a value of
+ 	  <attval>&IRI-STYLE;</attval> as defined in <specref
+ 	  ref="_operation_iri_style"/>, i.e. this serialization format
+ 	  may only be used to serialize the HTTP request corresponding
+ 	  to the initial message of an
+ 	  interface operation.
+ 	  </p>
+ 
+ 	  <p>Because the IRI Style constrains the instance data not to
+ 	  contain multiple children elements declared with the same
+ 	  local name, elements can be serialized in the request IRI
+ 	  with their local names unambiguously.
+ 	  </p>
+ 
+ 	  <p>
+ 	    For the HTTP binding defined in this section
+ 	    (<specref ref="http-binding"/>),
+ 	    <attval>application/x-www-form-urlencoded</attval> MAY be
+ 	    used as a value for the <prop comp="Binding Operation">http input serialization</prop> property of the
+ 	    <comp>Binding Operation</comp> component, but MUST NOT be
+ 	    used as a value as a value for the <prop comp="Binding Operation">http output serialization</prop> or <prop
+ 	    comp="Binding Operation">http fault serialization</prop>
+ 	    properties.
+ 	  </p>
+ 
+           <div4 id="_http_operation_location_cited_get">
+             <head>Case of elements cited in the {http location} property</head>
+ 
+ 	  <p>In this serialization, the rules  for constructing the HTTP request IRI using elements cited in the <prop comp="Binding Operation">http location</prop> property defined in <specref ref="_http_location_template"/> apply. Additional rules for constructing the HTTP request IRI follow.</p>
+ 
+ 	  </div4>
+ 
            <div4 id="_http_operation_location_notcited_get">
!             <head>Serialization of content of the instance data not cited in the {http location} property</head>
  	    <p>If not all elements from the <termref
  	    def="instance_data">instance data</termref> are cited in
***************
*** 3915,3937 ****
  	    serialization rules apply.</p>
  
! 	    <p>If the <prop comp="Binding Operation">http
! 	    location</prop> property exists and if an element name appears
! 	    followed by a slash in its value, then
! 	    the instance data must be serialized in the message body
! 	    (see <specref
! 	    ref="_http_operation_location_notcited_body"/>), otherwise
! 	    the elements not cited must be serialized as parameters in
! 	    the request IRI (see <specref
! 	    ref="_http_operation_location_notcited_iri"/>).</p>
  
- 	    <div5 id="_http_operation_location_notcited_iri">
- 	      <head>Serialization in the request IRI</head>
              <p>Non-nil
    elements with a possibly empty single value of the <termref def="instance_data">instance
! 	    data</termref> from the input message NOT cited by the
! 	    <prop comp="Binding Operation">http location</prop> property
!               are serialized as query parameters appended to the
! 	      request IRI (e.g. <specref
! 	      ref="urlencoded_example"/>) in the order they appear in
  	      the instance data.
  				</p>
--- 3965,3991 ----
  	    serialization rules apply.</p>
  
! 	    <p>The remainder of the instance data is formatted as a
! 	    query string as defined in <specref
! 	    ref="_http_operation_location_query_constr"/>.</p>
! 
! 	    <p>If the HTTP method used for the request, as specified
! 	    by the <prop comp="Binding Operation">http method</prop>,
! 	    does not allow a message body, then this query string is serialized as parameters in the request
! 	    IRI (see <specref
! 	    ref="_http_operation_location_notcited_iri"/>), otherwise
! 	    it is serialized in the message body (see <specref
! 	    ref="_http_operation_location_notcited_body"/>).</p>
! 
! 	    <div5 id='_http_operation_location_query_constr'>
! 	      <head>Construction of the query string</head>
! 
! 	      <p>For elements of the instance data not cited in the
! 	      <prop comp="Binding Operation">http location</prop> property, a query
! 	      string is constructed as follows.</p>
  
              <p>Non-nil
    elements with a possibly empty single value of the <termref def="instance_data">instance
! 	    data</termref> not cited
!               are serialized as query parameters in the order they appear in
  	      the instance data.
  				</p>
***************
*** 3943,3953 ****
  
              <p>
! 	    If the <prop comp="Binding Operation">http location</prop> property
! 	    is not present, or if it is present and its value does not
! 	    contain a <attval>?</attval> (question mark) character, one is
! 	    appended. If it does already contain a question mark
! 	    character, then the value of the
! 	    <prop comp="Binding Operation">http query parameter separator</prop> property
! 	    is appended. Each parameter pair is
  	    separated by the value of the <prop comp="Binding Operation">http query parameter separator</prop> property.
  	  </p>
--- 3997,4001 ----
  
              <p>
! 	    Each parameter pair is
  	    separated by the value of the <prop comp="Binding Operation">http query parameter separator</prop> property.
  	  </p>
***************
*** 3972,3975 ****
--- 4020,4150 ----
              </ulist>
  
+           <example id="urlencoded_example_querystring">
+             <head>Query string generation</head>
+             <p>
+             The following instance data of an input message
+           </p>
+             <eg xml:space="preserve">&lt;data&gt;
+   &lt;town&gt;Fréjus&lt;/town&gt;
+   &lt;date&gt;&draft.year;-&draft.mm;-&draft.dd;&lt;/date&gt;
+   &lt;unit&gt;C&lt;/unit&gt;
+ &lt;/data&gt;</eg>
+             <p>
+             with the following value of the {http location} property:
+           </p>
+             <eg xml:space="preserve">'temperature/{town}'</eg>
+             <p>
+             and the following value of the {http query parameter separator} property:
+           </p>
+             <eg xml:space="preserve">'&amp;'</eg>
+             <p>
+             will produce the following query string:
+           </p>
+             <eg xml:space="preserve">date=&draft.year;-&draft.mm;-&draft.dd;&amp;unit=C</eg>
+           </example>
+ 
+ 	    </div5>
+ 
+ 	    <div5 id="_http_urlencoded_stop">
+ 	      <head>Controlling the serialization of the request IRI</head>
+ 
+ 	      <p>This serialization format adds the following property to the WSDL component model:</p>
+ 
+ 	      <ulist>
+ 		<item>
+ 		  <p><propdef comp="Binding Operation">http location ignore uncited</propdef> MANDATORY. A
+ 		  <emph>xs:boolean</emph>.  This boolean indicates
+ 		  whether elements not cited in the <prop comp="Binding Operation">http location</prop> property
+ 		  MUST be appended to the request IRI or ignored. If the value of this property is <attval>false</attval>, the rules defined in section <specref ref="_http_operation_location_notcited_iri"/>
+ 		  dictate how to serialize elements not cited in <prop comp="Binding Operation">http location</prop> in the request IRI. Otherwise, those are NOT serialized in the request IRI.</p>
+ 		</item>
+ 	      </ulist>
+ 
+ 	      <p>The XML representation for this property is an 
+ 	      &AII; with the following Infoset properties:</p>
+ 
+ 	      <ulist>
+ 		<item>
+ 		  <p>An OPTIONAL <att>ignoreUncited</att>
+ 		  &AII; with the following
+ 		  Infoset properties:</p>
+ 		  <ulist>
+ 		    <item>
+ 		      <p>A [local name] of <att>ignoreUncited</att>
+                       </p>
+                     </item>
+ 		    <item>
+ 		      <p>A [namespace name] of <attval>&wsdl-http-ns;</attval>
+ 		      </p>
+ 		    </item>
+ 		    <item>
+ 		      <p>A type of <emph>xs:boolean</emph></p>
+ 		    </item>
+                   </ulist>
+                 </item>
+ 	      </ulist>
+ 
+ 	      <p>The mapping from the XML representation to component properties is as follows:</p>
+ 
+           <table border="1" id="tab_HTTP_URLEnc_Ignore">
+             <caption>Mapping from XML Representation to Binding Operation component Extension Properties</caption>
+             <tbody>
+               <tr>
+                 <th rowspan="1" colspan="1">Property</th>
+                 <th rowspan="1" colspan="1">Value</th>
+               </tr>
+               <tr>
+                 <td rowspan="1" colspan="1"><prop comp="Binding Operation">http location ignore uncited</prop></td>
+                 <td rowspan="1" colspan="1">The actual value of the
+ 		<att>whttp:ignoreUncited</att>
+                   &AII;, if present. Otherwise, <attval>false</attval>.</td>
+               </tr>
+ 	    </tbody>
+ 	  </table>
+ 
+ 	    </div5>
+ 
+ 	    <div5 id="_http_operation_location_notcited_iri">
+ 	      <head>Serialization in the request IRI</head>
+ 
+ 	      <p>If the HTTP request method used, specified in the
+ 	      <prop comp="Binding Operation">http method</prop> of
+ 	      the Binding Operation component bound, does not allow
+ 	      HTTP message body (e.g. <attval>GET</attval> and
+ 	      <attval>DELETE</attval>), and if the value of the <prop comp="Binding Operation">http location ignore uncited</prop> property is <attval>false</attval>, then the following rules
+ 	      apply.</p>
+ 
+ 	      <p>If the <prop comp="Binding Operation">http
+ 	      location</prop> property is not present, or if it is
+ 	      present and its value does not contain a
+ 	      <attval>?</attval> (question mark) character, one is
+ 	      appended to the request IRI. If it does already contain
+ 	      a question mark character, then the value of the <prop
+ 	      comp="Binding Operation">http query parameter
+ 	      separator</prop> property is appended.</p>
+ 
+ 	      <p>Finally, the query string computed in <specref ref=
+ 	      "_http_operation_location_query_constr"/> is appended.</p>
+ 
+           <example id="urlencoded_example">
+             <head>Instance data serialized in a IRI</head>
+             <p>
+ 	      The instance data defined in <specref ref="urlencoded_example_querystring"/> with the following <el>operation</el> declaration:
+           </p>
+             <eg xml:space="preserve">&lt;operation ref='t:data'
+     whttp:location='temperature/{town}'
+     whttp:method='GET' /&gt;</eg>
+             <p>
+             and the following <el>endpoint</el> declaration:
+           </p>
+             <eg xml:space="preserve">&lt;endpoint name='e' binding='t:b'
+     address='http://ws.example.com/service1/' /&gt;</eg>
+             <p>
+             will serialize the message in the HTTP request as follows:
+           </p>
+             <eg xml:space="preserve">GET http://ws.example.com/service1/temperature/Fr%C3%A9jus?date=&draft.year;-&draft.mm;-&draft.dd;&amp;unit=C HTTP/1.1
+ Host: ws.example.com</eg>
+           </example>
+ 
  	    </div5>
  
***************
*** 3977,4003 ****
  	      <head>Serialization in the message body</head>
  
! 	      <p>In addition to the serialization in the request IRI
! 	      of the elements cited in the <prop comp="Binding Operation">http location</prop> property,
! 	      the entire <termref def="instance_data">instance
! 	      data</termref> is serialized in the message body
! 	      following the rules of the
! 	      <attval>application/xml</attval> (see <specref
! 	      ref="_http_operation_xml_encoding"/>).</p>
  
! 	      <example id="urlencoded_example_body">
! 		<head>Instance data serialized in a IRI and in a
! 		message body</head>
!             <p>
! 	    The following instance data of an input message
! 	  </p>
!             <eg xml:space="preserve">&lt;data&gt;
!   &lt;town&gt;Fréjus&lt;/town&gt;
!   &lt;date&gt;2004-01-16&lt;/date&gt;
!   &lt;unit&gt;C&lt;/unit&gt;
!   &lt;value&gt;24&lt;/value&gt;
! &lt;/data&gt;</eg>
              <p>
! 	    with the following <el>operation</el> element:
! 	  </p>
              <eg xml:space="preserve">&lt;operation ref='t:data'
      whttp:inputSerialization='application/x-www-form-urlencoded'
--- 4152,4175 ----
  	      <head>Serialization in the message body</head>
  
! 	      <p>If the HTTP request method used, specified in the
! 	      <prop comp="Binding Operation">http method</prop> of
! 	      the Binding Operation component bound, does allow an
! 	      HTTP message body (e.g. <attval>POST</attval> and
! 	      <attval>PUT</attval>), then the following rules
! 	      apply.</p>
  
! 	      <p>Finally, the query string computed in <specref ref=
! 	      "_http_operation_location_query_constr"/> is used as the
! 	      value of the HTTP message body.</p>
! 
! 	      <p>The <code>Content-Type</code> HTTP header field must
! 	      have the value
! 	      <code>application/x-www-form-urlencoded</code>.</p>
! 
!           <example id="urlencoded_example_body">
!             <head>Instance data serialized in the HTTP Request IRI and message body</head>
              <p>
! 	      The instance data defined in <specref ref="urlencoded_example_querystring"/> with the following <el>operation</el> declaration:
!           </p>
              <eg xml:space="preserve">&lt;operation ref='t:data'
      whttp:inputSerialization='application/x-www-form-urlencoded'
***************
*** 4005,4046 ****
      whttp:method='POST' /&gt;</eg>
              <p>
! 	    and the following <el>endpoint</el> element
! 	  </p>
              <eg xml:space="preserve">&lt;endpoint name='e' binding='t:b'
      address='http://ws.example.com/service1/' /&gt;</eg>
              <p>
! 	    will serialize the message in an IRI as follows:
! 	  </p>
!             <eg xml:space="preserve">http://ws.example.com/service1/temperature/Fréjus</eg>
!             <p>
! 	    which will be %-encoded as a URI as follows:
! 	  </p>
!             <eg xml:space="preserve">http://ws.example.com/service1/temperature/Fr%C3%A9jus</eg>
!             <p>
! 	      and in the message as follow:
! 	    </p>
! 
!             <eg xml:space="preserve">Content-Type: application/xml
! Content-Length: xxx
  
! &lt;data&gt;
!   &lt;town&gt;Fréjus&lt;/town&gt;
!   &lt;date&gt;2004-01-16&lt;/date&gt;
!   &lt;unit&gt;C&lt;/unit&gt;
!   &lt;value&gt;24&lt;/value&gt;
! &lt;/data&gt;</eg>
            </example>
  	    </div5>
            </div4>
          </div3>
          <div3 id="_http_operation_xml_encoding">
            <head>Serialization as <attval>application/xml</attval>
            </head>
            <p>
  	  The <termref def="instance_data">instance data</termref> of
  	  the input, output or fault message is serialized as an XML document
! 	  in the message body of the HTTP request, following the
  	  serialization defined in <bibref ref="Canonical"/>.
  	</p>
            <p>
  	  The <code>Content-Type</code> HTTP header MUST have the value
--- 4177,4223 ----
      whttp:method='POST' /&gt;</eg>
              <p>
!             and the following <el>endpoint</el> declaration:
!           </p>
              <eg xml:space="preserve">&lt;endpoint name='e' binding='t:b'
      address='http://ws.example.com/service1/' /&gt;</eg>
              <p>
!             will serialize the message in the HTTP request as follow:
!           </p>
!             <eg xml:space="preserve">POST http://ws.example.com/service1/temperature/Fr%C3%A9jus HTTP/1.1
! Host: ws.example.com
! Content-Type: application/x-www-form-urlencoded
! Content-Length: &#x2026;
  
! date=&draft.year;-&draft.mm;-&draft.dd;&amp;unit=C</eg>
            </example>
  	    </div5>
            </div4>
          </div3>
+ 
          <div3 id="_http_operation_xml_encoding">
            <head>Serialization as <attval>application/xml</attval>
            </head>
+ 
+ 	  <p>In this serialization, for HTTP requests, the rules  for constructing the HTTP request IRI
+ 	  defined in <specref ref="_http_location_template"/> apply if
+ 	  the <prop comp="Interface Operation">style</prop> property
+ 	  of the <comp>Interface Operation</comp> bound has a value of
+ 	  <attval>&IRI-STYLE;</attval> as defined in <specref
+ 	  ref="_operation_iri_style"/>.</p>
+ 
            <p>
  	  The <termref def="instance_data">instance data</termref> of
  	  the input, output or fault message is serialized as an XML document
! 	  in the message body of the HTTP message, following the
  	  serialization defined in <bibref ref="Canonical"/>.
+ 	  Therefore, it is only suitable for HTTP requests using
+ 	  methods allowing message bodies (i.e., for the HTTP binding
+ 	  defined in this specification, input messages when the
+ 	  method specified in the <prop comp="Binding Operation">http
+ 	  method</prop> property of a Binding Operation component has
+ 	  a body), and for HTTP responses (i.e. output messages for
+ 	  the HTTP binding defined in this specification).
  	</p>
+ 
            <p>
  	  The <code>Content-Type</code> HTTP header MUST have the value
***************
*** 4055,4066 ****
            </head>
  
            <p>
  	  This format is for legacy compatibility to permit the use of
! 	  XForms clients with <bibref ref="RFC2388"/> servers.  This
  	  serialization format may only be used when binding
  	  <comp>Interface Operation</comp> whose <prop comp="Interface Operation">style</prop> property has a value of
  	  <attval>&MULTIPART-STYLE;</attval> as defined in <specref
  	  ref="_operation_multipart_style"/>, i.e. this serialization
! 	  format may only be used to serialize the initial message of
  	  an interface operation.
  	  </p>
--- 4232,4251 ----
            </head>
  
+ 	  <p>In this serialization, for HTTP requests, the rules for constructing the HTTP request IRI
+ 	  defined in <specref ref="_http_location_template"/> apply if
+ 	  the <prop comp="Interface Operation">style</prop> property
+ 	  of the <comp>Interface Operation</comp> bound has a value of
+ 	  <attval>&IRI-STYLE;</attval> as defined in <specref
+ 	  ref="_operation_iri_style"/>.</p>
+ 
            <p>
  	  This format is for legacy compatibility to permit the use of
! 	  XForms clients with <bibref ref="RFC2388"/> servers. This 
  	  serialization format may only be used when binding
  	  <comp>Interface Operation</comp> whose <prop comp="Interface Operation">style</prop> property has a value of
  	  <attval>&MULTIPART-STYLE;</attval> as defined in <specref
  	  ref="_operation_multipart_style"/>, i.e. this serialization
! 	  format may only be used to serialize the HTTP request
! 	  corresponding to the initial message of
  	  an interface operation.
  	  </p>
***************
*** 4074,4079 ****
  	    used as a value as a value for the <prop comp="Binding Operation">http output serialization</prop> or <prop
  	    comp="Binding Operation">http fault serialization</prop>
! 	    properties.
! 	  </p>
  
            <p>
--- 4259,4266 ----
  	    used as a value as a value for the <prop comp="Binding Operation">http output serialization</prop> or <prop
  	    comp="Binding Operation">http fault serialization</prop>
! 	    properties. This format serializes the instance
! data entirely in the HTTP message body, making it only suitable for
! HTTP requests using methods, specified in the <prop comp="Binding Operation">http method</prop> property
! of a Binding Operation component, allowing message bodies.</p>
  
            <p>
***************
*** 4142,4146 ****
      &lt;country&gt;France&lt;/country&gt;
    &lt;/town&gt;
!   &lt;date&gt;2004-01-16&lt;/date&gt;
  &lt;/data&gt;</eg>
              <p>
--- 4329,4333 ----
      &lt;country&gt;France&lt;/country&gt;
    &lt;/town&gt;
!   &lt;date&gt;&draft.year;-&draft.mm;-&draft.dd;&lt;/date&gt;
  &lt;/data&gt;</eg>
              <p>
***************
*** 4169,4173 ****
  Content-Type: text/plain; charset=utf-8
  
! 2004-01-16
  --AaB03x--</eg>
            </example>
--- 4356,4360 ----
  Content-Type: text/plain; charset=utf-8
  
! &draft.year;-&draft.mm;-&draft.dd;
  --AaB03x--</eg>
            </example>
***************
*** 4772,4776 ****
      &acknowledgements;
  
!     <inform-div1>
      	<head>Component Summary</head>
      	<p>
--- 4959,4963 ----
      &acknowledgements;
  
!     <inform-div1 id='component_summary'>
      	<head>Component Summary</head>
      	<p>
***************
*** 4810,4813 ****
--- 4997,5008 ----
  	    -->
              <tr>
+ 	      <td>20051110</td>
+ 	      <td>HH</td>
+ 	      <td><loc
+ 	      href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC345">LC345</loc>:
+ 	      allowed POST as application/x-www-urlencoded and reorganized HTTP binding serializations
+ 	      </td>
+ 	    </tr>
+             <tr>
  	      <td>20051109</td>
  	      <td>HH</td>
***************
*** 6341,6452 ****
                <td rowspan="1" colspan="1">20020621</td>
                <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Simplified abstract and introduction.</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Obtain the list of WG members from a separate file.</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Updated stylesheet and DTDs to latest XMLP stylesheet and DTDs.</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Deleted placeholder for appendix C "Location of Extensibility Elements",
         since this is part 1 stuff and extensibility has been reworked anyway.</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Corrected link to issues lists</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Updated title from "WSDL" to "Web Services Description Language".
         Now refer to part 1 as "Web Services... Part 1: Framework</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020621</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Added Jeffrey as an editor :-). Removed Gudge (now on Part 2) :-(</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020411</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Fixed typos noticed by Kevin Liu</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "Schemas" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "Wire WSDL examples" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "Notes on URIs" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "Notational Conventions" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "References" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020301</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "MIME Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "HTTP Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Added placeholders for the "Wire examples" and "Schema" sections</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Converted the "SOAP Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Added the Change Log</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Added the Status section</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Simplified the introduction; referred to Part1 for a longer introduction</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Renamed to "Part 2: Bindings"</td>
              </tr>
              <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Created from http://www.w3.org/TR/2001/NOTE-wsdl-20010315</td>
              </tr>
            </tbody>
--- 6536,6647 ----
                <td rowspan="1" colspan="1">20020621</td>
                <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1">Simplified abstract and introduction.</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Obtain the list of WG members from a separate file.</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Updated stylesheet and DTDs to latest XMLP stylesheet and DTDs.</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Deleted placeholder for appendix C "Location of Extensibility Elements",
         since this is part 1 stuff and extensibility has been reworked anyway.</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Corrected link to issues lists</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Updated title from "WSDL" to "Web Services Description Language".
         Now refer to part 1 as "Web Services... Part 1: Framework</td>
              </tr>
              <tr>
!               <td rowspan="1">20020621</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Added Jeffrey as an editor :-). Removed Gudge (now on Part 2) :-(</td>
              </tr>
              <tr>
!               <td rowspan="1">20020411</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Fixed typos noticed by Kevin Liu</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "Schemas" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "Wire WSDL examples" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "Notes on URIs" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "Notational Conventions" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "References" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020301</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "MIME Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "HTTP Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Added placeholders for the "Wire examples" and "Schema" sections</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Converted the "SOAP Binding" section to XML</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Added the Change Log</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Added the Status section</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Simplified the introduction; referred to Part1 for a longer introduction</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Renamed to "Part 2: Bindings"</td>
              </tr>
              <tr>
!               <td rowspan="1">20020221</td>
!               <td rowspan="1">JJM</td>
!               <td rowspan="1">Created from http://www.w3.org/TR/2001/NOTE-wsdl-20010315</td>
              </tr>
            </tbody>
Received on Thursday, 10 November 2005 07:31:53 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 10 November 2005 07:31:54 GMT