- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 06 May 2006 22:21:54 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv11466/wsdl20
Modified Files:
wsdl20-adjuncts.xml
Log Message:
Finished editorial pass.
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.166
retrieving revision 1.167
diff -C2 -d -r1.166 -r1.167
*** wsdl20-adjuncts.xml 4 May 2006 06:22:40 -0000 1.166
--- wsdl20-adjuncts.xml 6 May 2006 22:21:52 -0000 1.167
***************
*** 2849,2853 ****
tree representation of an input, output or fault message is
called an <term>instance data</term>, and is constrained by
! the schema definition associated the message: the XML element
referenced in the
<prop comp="Interface Message Reference">element declaration</prop>
--- 2849,2853 ----
tree representation of an input, output or fault message is
called an <term>instance data</term>, and is constrained by
! the schema definition associated with the message: the XML element
referenced in the
<prop comp="Interface Message Reference">element declaration</prop>
***************
*** 2959,2963 ****
<p><assert class="component" id="HTTPBinding-5056">When formulating the HTTP message to be transmitted, the
! HTTP request method used MUST be the selected using one of the following:</assert></p>
<ulist>
--- 2959,2963 ----
<p><assert class="component" id="HTTPBinding-5056">When formulating the HTTP message to be transmitted, the
! HTTP request method used MUST be selected using one of the following:</assert></p>
<ulist>
***************
*** 3003,3007 ****
<p><termdef id="serialization_format" term="serialization format">The <term>serialization format</term> 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
--- 3003,3007 ----
<p><termdef id="serialization_format" term="serialization format">The <term>serialization format</term> is a media type token
(<attval>type/subtype</attval>). It identifies rules to
! serialize the payload in an HTTP message. Its value is defined by the following rules. The HTTP
request serialization format MUST be in the media type range
specified by the <prop comp="Binding Operation">http input
***************
*** 3032,3036 ****
<item>
<p>If the value is <attval>#other</attval> then the
! <termref def='serialization_format'>serialization format and its associated media type parameters, if any</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>
--- 3032,3036 ----
<item>
<p>If the value is <attval>#other</attval> then the
! <termref def='serialization_format'>serialization format</termref> and its associated media type parameters, if any, 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>
***************
*** 3044,3048 ****
component is declared using a non-XML type system (as
considered in the Types section of <bibref ref="WSDL-PART1"/>)
! then additional binding rules MUST be defined to indicate how
to map those components into the HTTP envelope.</assert></p>
--- 3044,3048 ----
component is declared using a non-XML type system (as
considered in the Types section of <bibref ref="WSDL-PART1"/>)
! then additional binding rules MUST be defined in an extension specification to indicate how
to map those components into the HTTP envelope.</assert></p>
***************
*** 3078,3082 ****
value of the <termref
def='serialization_format'>serialization
! format and its associated media type parameters, if any</termref>.
</p>
</item>
--- 3078,3082 ----
value of the <termref
def='serialization_format'>serialization
! format</termref> and its associated media type parameters, if any.
</p>
</item>
***************
*** 3231,3238 ****
patterns such as outbound message exchange patterns,
provided that additional semantics are defined, such as with
! an extension or with a Feature.</p>
<p>Each of the supported message exchange patterns involves
! one to two messages or faults being exchanged. <assert class="component" id="HTTPBindingOperation-2605001">The first is
transmitted using an HTTP request, and the second is
transmitted using the corresponding HTTP response.</assert> <assert class="component" id="HTTPBindingOperation-5065">In cases
--- 3231,3238 ----
patterns such as outbound message exchange patterns,
provided that additional semantics are defined, such as with
! an extension or with a <comp>Feature</comp> component.</p>
<p>Each of the supported message exchange patterns involves
! one or two messages or faults being exchanged. <assert class="component" id="HTTPBindingOperation-2605001">The first is
transmitted using an HTTP request, and the second is
transmitted using the corresponding HTTP response.</assert> <assert class="component" id="HTTPBindingOperation-5065">In cases
***************
*** 3356,3366 ****
</item>
</olist>
! <p>These properties allow to indicate the range of media types and/or
associated parameters with which an instance MAY be
serialized. <assert class="component" id="HTTPBindingOperation-2605003">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.</assert>
! Users of this &AII; are urged to
! avoid using wild cards (for example, <attval>application/*</attval>) as it may
! lead to interoperability problems.
</p>
--- 3356,3365 ----
</item>
</olist>
! <p>These properties indicate the range of media types and
associated parameters with which an instance MAY be
serialized. <assert class="component" id="HTTPBindingOperation-2605003">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.</assert>
! <assert class="component" id="HTTPBindingOperation-2604001" required="false">Wild cards (for example, <attval>application/*</attval>) SHOULD NOT be used in this &AII;
! since they may lead to interoperability problems.</assert>
</p>
***************
*** 3644,3648 ****
<head>HTTP Header component</head>
! <p>A <comp>HTTP Header</comp> component describes an abstract piece of
header data (HTTP header field) that is associated with the
exchange of messages between the communicating parties. The
--- 3643,3647 ----
<head>HTTP Header component</head>
! <p>An <comp>HTTP Header</comp> component describes an abstract piece of
header data (HTTP header field) that is associated with the
exchange of messages between the communicating parties. The
***************
*** 3658,3662 ****
<ulist>
<item> <p><propdef comp="HTTP Header">name</propdef> REQUIRED.
! A <emph>xs:string</emph> whose pattern facet is
<emph><attval>[!#-'*+\-.0-9A-Z^-z|~]+</attval></emph>, the name of the HTTP header field. The value of this
property follows the <code>field-name</code> production rules as specified
--- 3657,3661 ----
<ulist>
<item> <p><propdef comp="HTTP Header">name</propdef> REQUIRED.
! An <emph>xs:string</emph> whose pattern facet is
<emph><attval>[!#-'*+\-.0-9A-Z^-z|~]+</attval></emph>, the name of the HTTP header field. The value of this
property follows the <code>field-name</code> production rules as specified
***************
*** 3666,3670 ****
<item> <p><propdef comp="HTTP Header">type definition</propdef> REQUIRED.
! A <emph>xs:QName</emph>, being a reference to a <comp>Type Definition</comp> component in
the <prop comp="Description">type definitions</prop> property of the <comp>Description</comp> component
constraining the value of the HTTP header field. <assert class="component" id="HTTPHeader-5069">This type MUST be a simple type.</assert></p>
--- 3665,3669 ----
<item> <p><propdef comp="HTTP Header">type definition</propdef> REQUIRED.
! An <emph>xs:QName</emph>, being a reference to a <comp>Type Definition</comp> component in
the <prop comp="Description">type definitions</prop> property of the <comp>Description</comp> component
constraining the value of the HTTP header field. <assert class="component" id="HTTPHeader-5069">This type MUST be a simple type.</assert></p>
***************
*** 3672,3676 ****
<item> <p><propdef comp="HTTP Header">required</propdef> REQUIRED.
! A <emph>xs:boolean</emph> indicating if the HTTP
header field is required. <assert class="component" id="HTTPHeader-5070">If the value is <attval>true</attval>, then the HTTP header field MUST be included in the message.</assert> If it is <attval>false</attval>, then the HTTP header field MAY be included.</p> </item>
--- 3671,3675 ----
<item> <p><propdef comp="HTTP Header">required</propdef> REQUIRED.
! An <emph>xs:boolean</emph> indicating if the HTTP
header field is required. <assert class="component" id="HTTPHeader-5070">If the value is <attval>true</attval>, then the HTTP header field MUST be included in the message.</assert> If it is <attval>false</attval>, then the HTTP header field MAY be included.</p> </item>
***************
*** 3678,3682 ****
The <comp>Binding Fault</comp>
or <comp>Binding Message Reference</comp>
! component component that contains this component in its
<prop comp="Binding Message Reference">http headers</prop> property.</p></item>
</ulist>
--- 3677,3681 ----
The <comp>Binding Fault</comp>
or <comp>Binding Message Reference</comp>
! component that contains this component in its
<prop comp="Binding Message Reference">http headers</prop> property.</p></item>
</ulist>
***************
*** 3851,3855 ****
<div3 id="http-headers-decl-fragid">
! <head>IRI Identification Of A HTTP Header component</head>
<p>WSDL Version 2.0 Part 1: Core Language <bibref
--- 3850,3854 ----
<div3 id="http-headers-decl-fragid">
! <head>IRI Identification Of An HTTP Header component</head>
<p>WSDL Version 2.0 Part 1: Core Language <bibref
***************
*** 3903,3909 ****
be returned.</p>
! <p>The fault definition SHOULD NOT go against the definition
of the HTTP error codes, as specified in section 8 of <bibref
! ref='RFC3205'/>.</p>
</div3>
--- 3902,3908 ----
be returned.</p>
! <p><assert class="component" id="HTTPBindingFault-2606003" required="false">The fault definition SHOULD agree with the definition
of the HTTP error codes, as specified in section 8 of <bibref
! ref='RFC3205'/>.</assert></p>
</div3>
***************
*** 3938,3943 ****
</eg>
! <p>The XML representation for binding an HTTP Fault are two
! &AII;s with the following Infoset properties: </p>
<ulist>
--- 3937,3942 ----
</eg>
! <p>The XML representation for binding an HTTP Fault is an
! &AII; with the following Infoset properties: </p>
<ulist>
***************
*** 3986,3992 ****
<head>Serialization Format of Instance Data</head>
<p>
! This section specifies three serialization formats defining 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"/> and <specref ref="http_sfstyles"/> give an overview of
those serialization formats and their constraints. All of them allow serialization of parts of the
--- 3985,3991 ----
<head>Serialization Format of Instance Data</head>
<p>
! This section specifies three serialization formats defining rules to encode the
<termref def="instance_data">instance data</termref>
! of an input or output message as an HTTP
message. <specref ref="http_sftab"/> and <specref ref="http_sfstyles"/> give an overview of
those serialization formats and their constraints. All of them allow serialization of parts of the
***************
*** 4188,4194 ****
than once, the elements are used in the order they
appear in the <termref def="instance_data">instance
! data</termref>. This element MUST NOT
carry an <att>xs:nil</att> attribute whose value is
! <attval>true</attval>.
</p>
</item>
--- 4187,4193 ----
than once, the elements are used in the order they
appear in the <termref def="instance_data">instance
! data</termref>. <assert class="message" id="HTTPSerialization-2607010">This element MUST NOT
carry an <att>xs:nil</att> attribute whose value is
! <attval>true</attval></assert>.
</p>
</item>
***************
*** 4220,4230 ****
<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>
--- 4219,4230 ----
<p>
! <assert class="component" id="HTTPSerialization-2607011">If this format is used then the
! <prop comp="Interface Operation">style</prop> property of <comp>Interface
! Operation</comp> component being bound MUST contain 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.</assert>
</p>
***************
*** 4347,4351 ****
<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
--- 4347,4351 ----
<ulist>
<item>
! <p><propdef comp="Binding Operation">http location ignore uncited</propdef> REQUIRED. A
<emph>xs:boolean</emph>. This boolean indicates
whether elements not cited in the <prop comp="Binding Operation">http location</prop> property
***************
*** 4536,4540 ****
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. <assert class="component" id="HTTPSerialization-2608009">this serialization
--- 4536,4540 ----
XForms clients with <bibref ref="RFC2388"/> servers. This
serialization format may only be used when binding
! <comp>Interface Operation</comp> components 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. <assert class="component" id="HTTPSerialization-2608009">this serialization
***************
*** 4682,4686 ****
<p>The HTTP binding extension specification adds the following
! property to the WSDL component model (as defined in <bibref
ref="WSDL-PART1"/>):</p>
--- 4682,4686 ----
<p>The HTTP binding extension specification adds the following
! properties to the WSDL component model (as defined in <bibref
ref="WSDL-PART1"/>):</p>
***************
*** 5337,5340 ****
--- 5337,5346 ----
<tr>
+ <td>20060506</td>
+ <td>AGR</td>
+ <td>Made more editorial improvements. Done now.</td>
+ </tr>
+
+ <tr>
<td>20060503</td>
<td>AGR</td>
Received on Saturday, 6 May 2006 22:22:02 UTC