- From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 10 Nov 2005 09:44:54 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv19020
Modified Files:
wsdl20-adjuncts.xml
Log Message:
LC304
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.127
retrieving revision 1.128
diff -C2 -d -r1.127 -r1.128
*** wsdl20-adjuncts.xml 10 Nov 2005 07:31:45 -0000 1.127
--- wsdl20-adjuncts.xml 10 Nov 2005 09:44:52 -0000 1.128
***************
*** 2679,2689 ****
the schema definition associated the message: the XML element
referenced in the
! <!-- <prop comp="Inteface Message Reference"> -->message reference element<!-- </prop> -->
property of the
! <!-- <comp> -->Interface Message Reference<!-- </comp> -->
! component for input and output messages, and in the
! <!-- <prop comp="Interface Fault"> -->element<!-- </prop> -->
property of an
! <!-- <comp> -->Interface Fault<!-- </comp> -->
component for faults.</termdef>
</p>
--- 2679,2689 ----
the schema definition associated the message: the XML element
referenced in the
! <prop comp="Interface Message Reference">element declaration</prop>
property of the
! <comp>Interface Message Reference</comp>
! component for input and output messages (unless the <prop comp="Interface Message Reference">message content model</prop> is <attval>#any</attval>), and in the
! <prop comp="Interface Fault">element declaration</prop>
property of an
! <comp>Interface Fault</comp>
component for faults.</termdef>
</p>
***************
*** 2785,2814 ****
<head>Default Binding Rules</head>
! <ulist>
! <item><p><emph>HTTP Method Declaration.</emph>
! When formulating the HTTP message to be transmitted, the
HTTP request method MUST be the value of the
<prop comp="Binding Operation">http method</prop>
property of the corresponding <comp>Binding Operation</comp> component.</p>
! </item>
! <item><p><emph>Payload construction.</emph>
! When formulating the HTTP message to be transmitted, the
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:</p>
<ulist>
! <item><p><comp>Interface Message Reference</comp> component: if the value of the
<prop comp="Interface Message Reference">message content model</prop> property is
! <attval>#any</attval> then the payload MUST be any one XML
! element. If the value is <attval>#none</attval> then the payload
! MUST be empty. Finally if the value is <attval>#element</attval>
! then the payload will be the &EII; identified by the
! <prop comp="Interface Message Reference">element declaration</prop> property.</p></item>
! <item><p><comp>Interface Fault</comp> component: the payload will be the
! &EII; identified by the <prop comp="Interface Fault">element declaration</prop>
! property.</p></item>
</ulist>
--- 2785,2836 ----
<head>Default Binding Rules</head>
! <div3 id="_http_binding_default_rule_method">
! <head>HTTP Method Declaration</head>
! <p>When formulating the HTTP message to be transmitted, the
HTTP request method MUST be the value of the
<prop comp="Binding Operation">http method</prop>
property of the corresponding <comp>Binding Operation</comp> component.</p>
! </div3>
! <div3 id="_http_binding_default_rule_psf">
! <head>Payload Construction And Serialization Format</head>
!
! <p>When formulating the HTTP message to be transmitted, the
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
! serialization formats supported by this binding extension along with
! their constraints.</p>
<ulist>
! <item><p><comp>Interface Message Reference</comp> component:</p>
! <ulist>
! <item><p>If the value of the
<prop comp="Interface Message Reference">message content model</prop> property is
! <attval>#any</attval> or <attval>#element</attval>, the serialization of the instance data is specified as defined in section <specref ref="_http_ser_xml"/>.</p>
! </item>
! <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>
! </ulist>
! </item>
! <item><p><comp>Interface Fault</comp> component: the serialization of the instance data is specified as defined in section <specref ref="_http_ser_xml"/>.</p>
! </item>
</ulist>
***************
*** 2818,2841 ****
then additional binding rules MUST be defined to indicate how
to map those components into the HTTP envelope.</p>
- </item>
! <item><p><emph>Serialization format.</emph>
!
! 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
! serialization formats supported by this binding extension along with
! their constraints.</p>
! </item>
! <item><p><emph>Default input and output serialization format.</emph>
! <specref ref="method_value"/> defines the default values for
the GET, POST, PUT and DELETE values of the
<prop comp="Binding Operation">http method</prop> property.
--- 2840,2879 ----
then additional binding rules MUST be defined to indicate how
to map those components into the HTTP envelope.</p>
! <div4 id='_http_ser_xml'>
! <head>Serialization rules for XML messages</head>
! <p>The serialization rules for messages whose <prop comp="Interface Message Reference">message content model</prop> is either <attval>#element</attval> or <attval>#any</attval> and for fault messages are as follows:</p>
! <ulist>
! <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>
! </ulist>
! </div4>
! </div3>
!
! <div3 id="_http_binding_default_rule_dsf">
! <head>Default input and output serialization format</head>
!
! <p>Section <specref ref="method_value"/> defines the default values for
the GET, POST, PUT and DELETE values of the
<prop comp="Binding Operation">http method</prop> property.
***************
*** 2923,2931 ****
patterns or binding extensions.
</p>
- </item>
! <item>
!
! <p><emph>HTTP Header Construction.</emph> If the
<prop comp="Binding Message Reference">http headers</prop> property as defined in section <specref
ref="http-headers-decl"/> exists and is not empty in a
--- 2961,2970 ----
patterns or binding extensions.
</p>
!
! </div3>
! <div3 id='_http_default_rule_head'>
! <head>HTTP Header Construction</head>
! <p> If the
<prop comp="Binding Message Reference">http headers</prop> property as defined in section <specref
ref="http-headers-decl"/> exists and is not empty in a
***************
*** 2961,2966 ****
HTTP header field is REQUIRED, otherwise it is OPTIONAL.</p>
! </item>
! </ulist>
</div2>
--- 3000,3004 ----
HTTP header field is REQUIRED, otherwise it is OPTIONAL.</p>
! </div3>
</div2>
***************
*** 3115,3124 ****
<item>
<p><propdef comp="Binding Operation">http input serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating the
! value for the serialization 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 of the HTTP Response message for this specific operation.
Its value MUST be the name of a IANA media type token.
</p>
--- 3153,3162 ----
<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>
***************
*** 3126,3132 ****
<item>
<p><propdef comp="Binding Operation">http fault serialization</propdef> REQUIRED. A <emph>xs:string</emph> indicating
! the value for the serialization 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>
--- 3164,3170 ----
<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>
***************
*** 3137,3140 ****
--- 3175,3180 ----
</item>
</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">
***************
*** 4223,4227 ****
The <code>Content-Type</code> HTTP header MUST have the value
<code>application/xml</code>, or a media type compatible with
! <code>application/xml</code>. Other HTTP headers, such as
<code>Content-Encoding</code> or
<code>Transfer-Encoding</code>, MAY be used.
--- 4263,4267 ----
The <code>Content-Type</code> HTTP header MUST have the value
<code>application/xml</code>, or a media type compatible with
! <code>application/xml</code> as specified in section <specref ref="_http_ser_xml"/>. Other HTTP headers, such as
<code>Content-Encoding</code> or
<code>Transfer-Encoding</code>, MAY be used.
***************
*** 5000,5005 ****
<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>
--- 5040,5053 ----
<td>HH</td>
<td><loc
+ href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC304">LC304</loc>:
+ implemented <loc href='http://lists.w3.org/Archives/Public/www-ws-desc/2005Oct/0063.html'>proposal</loc>
+ </td>
+ </tr>
+ <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-form-urlencoded and reorganized HTTP binding serializations
</td>
</tr>
Received on Thursday, 10 November 2005 09:45:05 UTC