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

RE: Closing XML Protocol Last Call issue 395

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Thu, 5 Dec 2002 11:26:07 -0800
Message-ID: <68B95AA1648D1840AB0083CC63E57AD6097C68D4@red-msg-06.redmond.corp.microsoft.com>
To: <noah_mendelsohn@us.ibm.com>
Cc: "Martin Gudgin" <mgudgin@microsoft.com>, <xml-dist-app@w3.org>

>Exactly my concern.  I think we should rule this out clearly 
>and unambigously in the HTTP binding and or the RFC, as 
>appopriate.  We should NOT rule out the possibility that 
>someone would do this in other bindings, as it's a potentially 
>reasonable compression trick

Just to clarify, I think the concern is with respect to the definition
of the "application/soap+xml" media type that defines the only encoding
provided by us of the SOAP message infoset. This media type is of course
*used* by the HTTP binding but is otherwise independent from the HTTP

>I'm less worried about that, as in many critical situations 
>we're fairly clear that the Infoset for a message must contain 
>ONLY what we call for. 
>If there's any doubt, then we should put in an appropriate 
>general indication to that effect, I think (though we should 
>be a bit careful not to gratiutiously rule out things like 
>PSVI...I would probably say something like "Infoset items not 
>explicitly provided for here SHOULD NOT appear;  if they do 
>appear, they MUST NOT affect the results of SOAP processing or 
>message transmission."  In other words, don't act on them, 
>don't transmit them.  Make sense?

Not sure as this seems to imply that there is some notion of
implementation-based conformance to the infoset which is not the case.
The infoset only talks about conformance in the context of

In addition, the infoset does not provide any notion of filtering or
transformation and hence it is not, IMO, possible to talk about infoset
properties not being exposed to the application: if a property is
present then it is exposed. Given that the definition of the media type
"application/soap+xml" talks about the serialization of the SOAP message
infoset and not any filtered or transformed version of that infoset, I
don't see how DTD can ever show up using that media type.

It may be possible to define other media types that provide such
filtering and/or transformation but that is outside our domain and would
require explicit definition of such filters and/or transformations which
I think is above and beyond what infoset provides.

Received on Thursday, 5 December 2002 14:27:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:22 UTC