- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 29 Sep 2005 20:47:30 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv7103
Modified Files:
Tag: http_serialization_reworking
wsdl20-adjuncts.xml
Log Message:
Implemented decision of the WG except for parameter serialization property
(unneeded, I think)
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.105.2.1
retrieving revision 1.105.2.2
diff -C2 -d -r1.105.2.1 -r1.105.2.2
*** wsdl20-adjuncts.xml 29 Sep 2005 18:12:30 -0000 1.105.2.1
--- wsdl20-adjuncts.xml 29 Sep 2005 20:47:28 -0000 1.105.2.2
***************
*** 3730,3745 ****
<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>
! <table border="1">
! <caption>Table 6-6. Applicability and features of the serialization
formats for the HTTP binding defined in this
specification</caption>
--- 3730,3746 ----
<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 and features of the serialization
formats for the HTTP binding defined in this
specification</caption>
***************
*** 3778,3783 ****
<td rowspan="3">With message body</td>
<td>POST</td>
! <td rowspan="3">Some or all</td>
! <td rowspan="3">Some or all</td>
<td rowspan="3">All</td>
<td rowspan="3">All</td>
--- 3779,3784 ----
<td rowspan="3">With message body</td>
<td>POST</td>
! <td rowspan="3">None, some or all</td>
! <td rowspan="3">None, some or all</td>
<td rowspan="3">All</td>
<td rowspan="3">All</td>
***************
*** 3806,3820 ****
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
--- 3807,3832 ----
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
***************
*** 3826,3835 ****
</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>
-
<div4 id="_http_urlencoded_where">
<head>Serialization of the instance data in parts of the
--- 3838,3841 ----
***************
*** 3849,3853 ****
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>
--- 3855,3859 ----
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"/>.</p>
***************
*** 3875,3882 ****
elements from the
<termref def="instance_data">instance data</termref> of the
! 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>
--- 3881,3886 ----
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>
***************
*** 3914,3934 ****
serialization rules apply.</p>
! <p>If the <prop comp="Binding Operation">http
! location</prop> property exists @@@, then the remainder of the
! instance data is serialized as parameters in the request
IRI (see <specref
ref="_http_operation_location_notcited_iri"/>), otherwise
! it is serialized in the message body, if applicable.</p>
<div5 id='_http_operation_location_query_constr'>
<head>Construction of the query string</head>
! <p>For elements of the instance data not cited, 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 by the
! <prop comp="Binding Operation">http location</prop> property
are serialized as query parameters in the order they appear in
the instance data.
--- 3918,3943 ----
serialization rules apply.</p>
! <p>The remainder of the instance data is serialized 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.
***************
*** 3971,3975 ****
<eg xml:space="preserve"><data>
<town>Fréjus</town>
! <date>2004-01-16</date>
<unit>C</unit>
</data></eg>
--- 3980,3984 ----
<eg xml:space="preserve"><data>
<town>Fréjus</town>
! <date>&draft.year;-&draft.mm;-&draft.dd;</date>
<unit>C</unit>
</data></eg>
***************
*** 3985,3989 ****
will produce the following query string:
</p>
! <eg xml:space="preserve">date=2004-01-16&unit=C</eg>
</example>
--- 3994,3998 ----
will produce the following query string:
</p>
! <eg xml:space="preserve">date=&draft.year;-&draft.mm;-&draft.dd;&unit=C</eg>
</example>
***************
*** 4028,4032 ****
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=2004-01-16&unit=C HTTP/1.1
Host: ws.example.com</eg>
</example>
--- 4037,4041 ----
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;&unit=C HTTP/1.1
Host: ws.example.com</eg>
</example>
***************
*** 4074,4078 ****
Content-Length: …
! date=2004-01-16&unit=C</eg>
</example>
</div5>
--- 4083,4087 ----
Content-Length: …
! date=&draft.year;-&draft.mm;-&draft.dd;&unit=C</eg>
</example>
</div5>
***************
*** 4116,4120 ****
<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>
--- 4125,4130 ----
<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>
***************
*** 4198,4202 ****
<country>France</country>
</town>
! <date>2004-01-16</date>
</data></eg>
<p>
--- 4208,4212 ----
<country>France</country>
</town>
! <date>&draft.year;-&draft.mm;-&draft.dd;</date>
</data></eg>
<p>
***************
*** 4225,4229 ****
Content-Type: text/plain; charset=utf-8
! 2004-01-16
--AaB03x--</eg>
</example>
--- 4235,4239 ----
Content-Type: text/plain; charset=utf-8
! &draft.year;-&draft.mm;-&draft.dd;
--AaB03x--</eg>
</example>
Received on Thursday, 29 September 2005 20:47:40 UTC