W3C home > Mailing lists > Public > www-tag@w3.org > April 2003

Re: [xmlProfiles-29] xml subsetting in IETF XMPP

From: Noah Mendelsohn/Cambridge/IBM <noah_mendelsohn@us.ibm.com>
Date: Tue, 1 Apr 2003 13:44:11 -0500
To: Chris Lilley <chris@w3.org>
Cc: Fabrice Desré <fabrice.desre@francetelecom.com>, "Henry S. Thompson" <ht@cogsci.ed.ac.uk>, www-tag@w3.org
Message-ID: <OF12357BCE.44459B67-ON85256CFB.0067134D@lotus.com>

I >think< this means that XMPP has chosen a usage convention for XML 
that's pretty much identical to the one chosen by SOAP.  XMPP may have 
been influenced by SOAP, but I have no reason to believe the reverse is 
true.   Perhaps we came to the same conclusion independently?

(I still prefer the term "usage convention" to "subset" insofar as I am 
not aware of any intention on the part of Soap designers or XMLP to define 
any sort of general purpose subset of XML...the intention was to never 
send soap messages that use XML features inappropriate to our needs, and 
therefore to allow the opportunity for SOAP receivers to optimize 
accordingly should they choose to do so.  Whether or not to use a general 
purpose SOAP parser at a SOAP receiver is an implementation choice at that 
receiver.   Yes, an implementation choosing to use such a general purpose 
parser must ensure that no proscribed constructions have been used.)

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142

Chris Lilley <chris@w3.org>
Sent by: www-tag-request@w3.org
04/01/2003 01:38 PM
Please respond to Chris Lilley

        To:     Fabrice Desré <fabrice.desre@francetelecom.com>
        cc:     "Henry S. Thompson" <ht@cogsci.ed.ac.uk>, www-tag@w3.org, (bcc: Noah 
        Subject:        Re: [xmlProfiles-29] xml subsetting in IETF XMPP

On Tuesday, April 1, 2003, 7:33:13 PM, Fabrice wrote:

FD>   Here's the answer of the draft's editor :

FD>  > This is a typo. What we meant to say is that XML streams should not
FD>  > contain entity references *other than* predefined entities (as we 
FD>  > predefined entities are fine, and are used currently to escape 
FD>  > markup characters [<|>|&|'|"] in CDATA or attribute values).
FD>  >
FD>  > I'll fix this in the 07 draft.


FD>   So there's still subsetting, but not as much...

Yes, and already noted under not allowing internal or external DTD

 Chris                            mailto:chris@w3.org
Received on Tuesday, 1 April 2003 13:50:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:37 UTC