- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 11 Nov 2005 09:07:27 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv15795
Modified Files:
wsdl20-adjuncts.xml
Log Message:
LC337
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.132
retrieving revision 1.133
diff -C2 -d -r1.132 -r1.133
*** wsdl20-adjuncts.xml 11 Nov 2005 08:02:55 -0000 1.132
--- wsdl20-adjuncts.xml 11 Nov 2005 09:07:24 -0000 1.133
***************
*** 2689,2693 ****
<p>
! <termdef id="instance_data" term="instance_data">The internal
tree representation of an input, output or fault message is
called an <term>instance data</term>, and is constrained by
--- 2689,2693 ----
<p>
! <termdef id="instance_data" term="instance data">The internal
tree representation of an input, output or fault message is
called an <term>instance data</term>, and is constrained by
***************
*** 2815,2827 ****
contents of the payload (i.e. the contents of the HTTP message
body) MUST be what is defined by the corresponding <comp>Interface Message
! Reference</comp> or <comp>Interface Fault</comp> components, serialized as specified by the serialization used.</p>
! <p>The serialization format is specified as follows. The HTTP request serialization format MUST be what is
! defined by the <prop comp="Binding Operation">http input
serialization</prop> property. The HTTP response serialization
! format MUST be what is defined by the <prop comp="Binding Operation">http output serialization</prop> property. The HTTP
! serialization format of a fault MUST be what is defined by the
<prop comp="Binding Operation">http fault serialization</prop>
! property.</p>
<p>Section <specref ref="_http_serialization"/> defines
--- 2815,2832 ----
contents of the payload (i.e. the contents of the HTTP message
body) MUST be what is defined by the corresponding <comp>Interface Message
! Reference</comp> or <comp>Interface Fault</comp> components,
! serialized as specified by the <termref def='serialization_format'>serialization format</termref> used.</p>
! <p><termdef id="serialization_format" term="serialization format">The serialization format is a media type token
! (<attval>type/subtype</attval>). It identifies rules to
! serialize a message in an HTTP message. Its value follows the following rules. The HTTP
! request serialization format MUST be in the media type range
! specified by the <prop comp="Binding Operation">http input
serialization</prop> property. The HTTP response serialization
! format MUST be in the media type range specified by the <prop comp="Binding Operation">http output serialization</prop> property. The HTTP
! serialization format of a fault MUST be in the media type
! range specified by the
<prop comp="Binding Operation">http fault serialization</prop>
! property.</termdef></p>
<p>Section <specref ref="_http_serialization"/> defines
***************
*** 2838,2845 ****
<item>
<p>If the value is <attval>#none</attval> then the
! payload MUST be empty and the value of the corresponding serialization format property (<prop comp="Binding Operation">http input serialization</prop> or <prop comp="Binding Operation">http output serialization</prop>) is ignored.</p>
</item>
<item>
! <p>If the value is <attval>#other</attval> then the corresponding serialization format property (<prop comp="Binding Operation">http input serialization</prop> or <prop comp="Binding Operation">http output serialization</prop>) specifies the value of the HTTP <code>Content-Type</code> entity-header field as defined in section 14.17 of <bibref
ref="RFC2616"/>. The serialization of the payload is undefined.</p>
</item>
--- 2843,2851 ----
<item>
<p>If the value is <attval>#none</attval> then the
! payload MUST be empty and the value of the corresponding serialization property (<prop comp="Binding Operation">http input serialization</prop> or <prop comp="Binding Operation">http output serialization</prop>) is ignored.</p>
</item>
<item>
! <p>If the value is <attval>#other</attval> then the
! <termref def='serialization_format'>serialization format</termref> specifies the value of the HTTP <code>Content-Type</code> entity-header field as defined in section 14.17 of <bibref
ref="RFC2616"/>. The serialization of the payload is undefined.</p>
</item>
***************
*** 2864,2883 ****
<item>
<p>
! If the value of the serialization property is <attval>application/x-www-form-urlencoded</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_x-www-form-urlencoded"/>.
</p>
</item>
<item>
<p>
! If the value of the serialization property is <attval>multipart/form-data</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_operation_multipart_encoding"/>.
</p>
</item>
<item>
<p>
! If the value of the serialization property is <attval>application/xml</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_operation_xml_encoding"/>.
</p>
</item>
<item>
<p>
! If the value of the serialization property has another value, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_operation_xml_encoding"/> with the following additional rule: the value of the HTTP <code>Content-Type</code> entity-header field is the value of the serialization property.
</p>
</item>
--- 2870,2897 ----
<item>
<p>
! If the <termref def='serialization_format'>serialization format</termref> is <attval>application/x-www-form-urlencoded</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_x-www-form-urlencoded"/>.
</p>
</item>
<item>
<p>
! If the <termref def='serialization_format'>serialization format</termref> is <attval>multipart/form-data</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_operation_multipart_encoding"/>.
</p>
</item>
<item>
<p>
! If the <termref def='serialization_format'>serialization format</termref> is <attval>application/xml</attval>, then the serialization of the <termref def='instance_data'>instance data</termref> is defined by section <specref ref="_http_operation_xml_encoding"/>.
</p>
</item>
<item>
<p>
! Otherwise, then the serialization of the <termref
! def='instance_data'>instance data</termref> is defined
! by section <specref
! ref="_http_operation_xml_encoding"/> with the
! following additional rule: the value of the HTTP
! <code>Content-Type</code> entity-header field is the
! value of the <termref
! def='serialization_format'>serialization
! format</termref>.
</p>
</item>
***************
*** 3167,3186 ****
</item>
<item>
! <p><propdef comp="Binding Operation">http input serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating the
! value for the serialization rules of the HTTP Request message for this specific operation.
! Its value MUST be the name of a IANA media type token. </p>
</item>
<item>
! <p><propdef comp="Binding Operation">http output serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating the
! value for the serialization rules of the HTTP Response message for this specific operation.
! Its value MUST be the name of a IANA media type token.
! </p>
</item>
<item>
<p><propdef comp="Binding Operation">http fault serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating
! the value for the serialization rules of the HTTP Response
message for this specific operation in case a fault is
! returned. Its value MUST be the name of a IANA media
! type token.</p>
</item>
<item>
--- 3181,3199 ----
</item>
<item>
! <p><propdef comp="Binding Operation">http input
! serialization</propdef> REQUIRED. A
! <emph>xs:string</emph> indicating allowed serialization
! rules of the HTTP Request message for this specific
! operation, as described in section <specref ref='_http_ser_val'/>.</p>
</item>
<item>
! <p><propdef comp="Binding Operation">http output serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating
! allowed serialization rules of the HTTP Response message for this specific operation, as described in section <specref ref='_http_ser_val'/>.</p>
</item>
<item>
<p><propdef comp="Binding Operation">http fault serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating
! allowed serialization rules of the HTTP Response
message for this specific operation in case a fault is
! returned, as described in section <specref ref='_http_ser_val'/>.</p>
</item>
<item>
***************
*** 3191,3196 ****
</ulist>
- <p>The use of <prop comp="Binding Operation">http input serialization</prop>, <prop comp="Binding Operation">http output serialization</prop> and <prop comp="Binding Operation">http fault serialization</prop> is specified in section <specref ref='_http_binding_default_rule_psf'/>.</p>
</div3>
<div3 id="http-operation-decl-xml">
<head>XML Representation</head>
--- 3204,3248 ----
</ulist>
</div3>
+
+
+ <div3 id="_http_ser_val">
+ <head>Specification of serialization rules allowed</head>
+
+ <p>The value of the <prop comp="Binding Operation">http input
+ serialization</prop>, <prop comp="Binding Operation">http output
+ serialization</prop> and <prop comp="Binding Operation">http
+ fault serialization</prop> properties is similar to the value
+ allowed for the <code>Accept</code> HTTP header defined by HTTP
+ 1.1 specification, Section 14.1 (see <bibref ref="RFC2616"/>)
+ and MUST follow the production rules defined in that section
+ except for the following:
+ </p>
+ <olist>
+ <item>
+ <p>The prefix <code>"Accept:"</code> MUST NOT be used.</p>
+ </item>
+ <item>
+ <p>The rule <code>qdtext</code> is changed from:</p>
+ <p><code>qdtext = <any TEXT except<">></code></p>
+ <p>to:</p>
+ <p><code>qdtext = <any CHAR except<">></code></p>
+ <p>This change is made to disallow non-US-ASCII OCTETs.</p>
+ </item>
+ </olist>
+
+ <p>These properties allow to indicate the range of media types and/or
+ associated parameters with which an instance MAY be
+ serialized. The value of the <termref def='serialization_format'>serialization format</termref> used for a
+ message is a media type which MUST be covered by this range.
+ Users of this &AII; are urged to
+ avoid using wild cards (for example, <attval>application/*</attval>) as it may
+ lead to interoperability problems.
+ </p>
+
+ <p>The use of <prop comp="Binding Operation">http input serialization</prop>, <prop comp="Binding Operation">http output serialization</prop> and <prop comp="Binding Operation">http fault serialization</prop> is specified in section <specref ref='_http_binding_default_rule_psf'/>.</p>
+
+ </div3>
+
<div3 id="http-operation-decl-xml">
<head>XML Representation</head>
***************
*** 3413,3422 ****
value of the <prop comp="Binding Operation">http
method</prop> property.
- It is an ERROR for this property
- to have the value
- <attval>application/x-www-form-urlencoded</attval> (see
- section <specref ref="_http_x-www-form-urlencoded"/>) or
- <attval>multipart/form-data</attval> (see
- section <specref ref="_http_operation_multipart_encoding"/>).
</td>
</tr>
--- 3465,3468 ----
***************
*** 3426,3434 ****
&AII;, if present; otherwise
<attval>application/xml</attval>.
- It is an ERROR for this property
- to have the value <attval>application/x-www-form-urlencoded</attval> (see
- section <specref ref="_http_x-www-form-urlencoded"/>) or
- <attval>multipart/form-data</attval> (see
- section <specref ref="_http_operation_multipart_encoding"/>).
</td>
</tr>
--- 3472,3475 ----
***************
*** 3997,4005 ****
(<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>
--- 4038,4046 ----
(<specref ref="http-binding"/>),
<attval>application/x-www-form-urlencoded</attval> MAY be
! used as a <termref
! def="serialization_format">serialization format</termref>
! for an input message (HTTP Request), but MUST NOT be used as a <termref
! def="serialization_format">serialization format</termref>
! for an output or fault message (HTTP Response).
</p>
***************
*** 4310,4319 ****
(<specref ref="http-binding"/>),
<attval>multipart/form-data</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. 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>
--- 4351,4361 ----
(<specref ref="http-binding"/>),
<attval>multipart/form-data</attval> MAY be
! used as a <termref
! def="serialization_format">serialization format</termref>
! for an input message (HTTP Request), but MUST NOT be used as a <termref
! def="serialization_format">serialization format</termref>
! for an output or fault message (HTTP Response).
! This format serializes the instance
! data 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>
***************
*** 5082,5092 ****
<tr>
! <td>20051111</td>
! <td>AGR</td>
! <td>Added assertion tables. Added Fault Propagation Rule assertions.</td>
</tr>
<tr>
! <td>20051110</td>
<td>HH</td>
<td><loc
--- 5124,5137 ----
<tr>
! <td>20051111</td>
! <td>HH</td>
! <td><loc
! href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC337">LC337</loc>:
! added media type range
! </td>
</tr>
<tr>
! <td>20051111</td>
<td>HH</td>
<td><loc
***************
*** 5095,5098 ****
--- 5140,5150 ----
</td>
</tr>
+
+ <tr>
+ <td>20051111</td>
+ <td>AGR</td>
+ <td>Added assertion tables. Added Fault Propagation Rule assertions.</td>
+ </tr>
+
<tr>
<td>20051110</td>
Received on Friday, 11 November 2005 09:07:30 UTC