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

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.137,1.138 wsdl20-soap11-binding.xml,1.21,1.22

From: Hugo Haas via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 12 Nov 2005 16:25:22 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20051112162522.BD0E34F2C5@homer.w3.org>

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

Modified Files:
	wsdl20-adjuncts.xml wsdl20-soap11-binding.xml 
Log Message:
Tweaks after rereading

Index: wsdl20-soap11-binding.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-soap11-binding.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -C2 -d -r1.21 -r1.22
*** wsdl20-soap11-binding.xml	11 Nov 2005 07:38:22 -0000	1.21
--- wsdl20-soap11-binding.xml	12 Nov 2005 16:25:20 -0000	1.22
***************
*** 170,175 ****
                of the SOAP 1.1 SOAPAction HTTP request header field, Section
                6.1.1, SOAP 1.1 specification <bibref ref="SOAP11"/>.</p>
! 						<p>The values of <prop comp="Binding Operation">http method</prop>
!               and <prop comp="Binding Operation">http location</prop>
                properties are ignored for SOAP 1.1 HTTP binding.</p>
  						<note>
--- 170,175 ----
                of the SOAP 1.1 SOAPAction HTTP request header field, Section
                6.1.1, SOAP 1.1 specification <bibref ref="SOAP11"/>.</p>
! 						<p>The values of 
!               <prop comp="Binding Operation">http location</prop>
                properties are ignored for SOAP 1.1 HTTP binding.</p>
  						<note>
***************
*** 195,199 ****
  					</item>
  				</ulist>
! 				<p>The values of <prop comp="Binding Operation">soap mep</prop>
          and <prop comp="Binding Fault">soap fault subcodes</prop> properties
            are ignored for SOAP 1.1 binding.</p>
--- 195,199 ----
  					</item>
  				</ulist>
! 				<p>The values of  <prop comp="Binding">soap mep default</prop>, <prop comp="Binding Operation">soap mep</prop>
          and <prop comp="Binding Fault">soap fault subcodes</prop> properties
            are ignored for SOAP 1.1 binding.</p>
***************
*** 419,422 ****
--- 419,429 ----
  	      <td>HH</td>
  	      <td><loc
+ 	      href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC333">LC333</loc>:
+ 	      also ignoring {soap mep default}, and not talking about {http method}</td>
+ 	    </tr>
+             <tr>
+ 	      <td>20051111</td>
+ 	      <td>HH</td>
+ 	      <td><loc
  	      href="http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC300">LC300</loc>:
  	      updated Infoset reference</td>

Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.137
retrieving revision 1.138
diff -C2 -d -r1.137 -r1.138
*** wsdl20-adjuncts.xml	11 Nov 2005 21:30:57 -0000	1.137
--- wsdl20-adjuncts.xml	12 Nov 2005 16:25:20 -0000	1.138
***************
*** 2236,2243 ****
            in <bibref ref="WSDL-PART1"/>):</p>
  
- 	  <ednote>
- 	    <edtext>The propdef mark-up only applies to one component.</edtext>
- 	  </ednote>
- 
            <ulist>
              <item><p><propdef comp="Binding Message Reference">soap headers</propdef> OPTIONAL.
--- 2236,2239 ----
***************
*** 2952,2956 ****
  	  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
--- 2948,2952 ----
  	  serialized as specified by the <termref def='serialization_format'>serialization format</termref> used.</p>
  
! 	  <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
***************
*** 2962,2966 ****
  	range specified by the
  	<prop comp="Binding Operation">http fault serialization</prop>
! 	property.</termdef></p>
  
  	<p>Section <specref ref="_http_serialization"/> defines
--- 2958,2964 ----
  	range specified by the
  	<prop comp="Binding Operation">http fault serialization</prop>
! 	property. The concept of media type range is defined in Section 14.1 of <bibref ref="RFC2616"/>.
! 	The serialization format MAY have <term>associated media type parameters</term> (specified with the <code>parameter</code> production of <code>media-range</code> in Section 14.1 of <bibref ref="RFC2616"/>.
! 	  </termdef></p>
  
  	<p>Section <specref ref="_http_serialization"/> defines
***************
*** 2981,2985 ****
  	    <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>
--- 2979,2983 ----
  	    <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>
***************
*** 3027,3031 ****
  		value of the <termref
  		def='serialization_format'>serialization
! 		format</termref>.
  	      </p>
  	    </item>
--- 3025,3029 ----
  		value of the <termref
  		def='serialization_format'>serialization
! 		format and its associated media type parameters, if any</termref>.
  	      </p>
  	    </item>
***************
*** 3302,3309 ****
                <prop comp="Binding Operation">http location</prop> before combining it with the
                <prop comp="Endpoint">address</prop> property of the endpoint element to
!               form the HTTP request IRI. For example, the
!               <code>application/x-www-form-urlencoded</code> serialization defined
!               in section <specref ref='_http_x-www-form-urlencoded'/>
!               defines a syntax to use the <prop comp="Binding Operation">http location</prop> as a
                template using elements of the instance data.
  	      </p>
--- 3300,3307 ----
                <prop comp="Binding Operation">http location</prop> before combining it with the
                <prop comp="Endpoint">address</prop> property of the endpoint element to
!               form the HTTP request IRI. For example, the three
!               serialization formats defined
!               in section <specref ref='_http_serialization'/>
!               define a syntax to use the <prop comp="Binding Operation">http location</prop> as a
                template using elements of the instance data.
  	      </p>
***************
*** 3376,3380 ****
        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
--- 3374,3378 ----
        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 the HTTP
        1.1 specification, Section 14.1 (see <bibref ref="RFC2616"/>)
        and MUST follow the production rules defined in that section
***************
*** 4023,4031 ****
          <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>
--- 4021,4031 ----
          <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"/> gives an overview of
! 	those serialization formats. All of them allow serialization of parts of the 
! 	<termref def="instance_data">instance data</termref> in the HTTP Request IRI,
! 	as defined in section <specref ref="_http_location_template"/>.
        </p>
        <p>
***************
*** 4062,4066 ****
  	  </tr>
  	  <tr>
! 	    <td>Other</td>
  	  </tr>
  	  <tr>
--- 4062,4066 ----
  	  </tr>
  	  <tr>
! 	    <td>&#x2026;</td>
  	  </tr>
  	  <tr>
***************
*** 4075,4079 ****
  	  </tr>
  	  <tr>
! 	    <td>Other</td>
  	  </tr>
  	  <tr>
--- 4075,4079 ----
  	  </tr>
  	  <tr>
! 	    <td>&#x2026;</td>
  	  </tr>
  	  <tr>
***************
*** 4092,4096 ****
  	    <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
--- 4092,4096 ----
  	    <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"/>, and MAY be reused by other serialization formats.</p>
  
  	    <p>With this HTTP binding, part of the instance data for
***************
*** 4304,4308 ****
  
  	    <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>
--- 4304,4308 ----
  
  	    <div5 id="_http_urlencoded_stop">
! 	      <head>Controlling the serialization of the query string in the request IRI</head>
  
  	      <p>This serialization format adds the following property to the WSDL component model:</p>
***************
*** 4379,4383 ****
  	      separator</prop> property, if present, or the value of
  	      the <prop comp="Binding">http query parameter separator
! 	      default</prop> property, is appended.</p>
  
  	      <p>Finally, the query string computed in <specref ref=
--- 4379,4383 ----
  	      separator</prop> property, if present, or the value of
  	      the <prop comp="Binding">http query parameter separator
! 	      default</prop> property otherwise, is appended.</p>
  
  	      <p>Finally, the query string computed in <specref ref=
***************
*** 4471,4475 ****
  	  HTTP method selected
  	    has
! 	  a body), and for HTTP responses (i.e. output messages for
  	  the HTTP binding defined in this specification).
  	</p>
--- 4471,4475 ----
  	  HTTP method selected
  	    has
! 	  a body), and for HTTP responses (i.e. output and fault messages for
  	  the HTTP binding defined in this specification).
  	</p>
Received on Saturday, 12 November 2005 16:25:25 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Saturday, 12 November 2005 16:25:25 GMT