W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

New Issues

From: Marc Hadley <marc.hadley@sun.com>
Date: Mon, 21 Jan 2002 16:23:29 +0000
Message-ID: <3C4C4081.6040605@sun.com>
To: XML dist app <xml-dist-app@w3c.org>
While rolling in suggested editorial changes from John Ibbotson I came 
across the following issues in the latest editors draft of part 1[1].

(i) encodingStyle attribute on Body element

4.1.1 SOAP encodingStyle Attribute
"It may appear on any element information item in the SOAP message."

4.3 SOAP Body Element
(Ednote) "The description of Body does not allow additional attributes."

Which of these two conflicting statements is true.

(ii) Non-opaque URI for encodingStyle value

4.1.1 SOAP encodingStyle Attribute
"In addition, all URIs syntactically beginning with 
'http://www.w3.org/2001/12/soap-encoding' indicate conformance with the 
SOAP encoding rules defined in [1](SOAP Encoding), though with 
potentially tighter rules added."

I recall seeing this raised previously on the list but couldn't find the 
post in the archives. I believe that the above use of a URI is unusual, 
   are the semantics described above desirable ?

(iii) Binding framework implies negotiation

5.1 (last paragraph and ednote)

"It is up to the communicating nodes to decide how best to express 
particular features; often when a binding-level implementation for a 
particular feature is available, utilizing it when appropriate will 
provide for optimized processing."

Is it not up to the binding specification to specify how particular 
features are expressed ?

Regards,
Marc.


[1] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part1.html

-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.
Received on Monday, 21 January 2002 11:26:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT