W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2004

RE: [Serialization] IBM-SE-004: XML Output Method

From: Michael Kay <mhk@mhk.me.uk>
Date: Tue, 3 Feb 2004 09:49:00 -0000
To: "'XML Query'" <xmlquery@us.ibm.com>, <public-qt-comments@w3.org>
Message-ID: <007a01c3ea3a$f389c140$6401a8c0@pcukmka>
The serialization process doesn't choose between these two alternatives
(indeed, the set of well-formed XML document entities and the set of
well-formed EGPEs have a large overlap). Rather, this sentence is
stating a constraint. If the document node contains multiple elements or
text nodes among its children then the result cannot be a well-formed
document entity, therefore it must be a well-formed EGPE. If a
standalone attribute is requested in the serialization parameters, then
the result cannot be a well-formed EGPE, therefore it must be a
well-formed document entity. If both conditions are true, there is a
conflict, and I think there are rules later on about how this conflict
should be resolved.
 
Michael Kay
 
-----Original Message-----
From: public-qt-comments-request@w3.org
[mailto:public-qt-comments-request@w3.org] On Behalf Of XML Query
Sent: 03 February 2004 00:15
To: public-qt-comments@w3.org
Subject: [Serialization] IBM-SE-004: XML Output Method




Serialization Section 4, "XML Output Method": The first paragraph states
that serialization produces either an XML document entity or an external
general parsed entity. No indication is given about how the
serialization process chooses between these alternatives. The
normalization rules in Section 2 always reduce the data model instance
to exactly one document, so it is not clear how the second alternative
is ever invoked. 

Also in this section, the second paragraph adds nothing that is not
already said in the first paragraph. It should be deleted. 

--Don Chamberlin 
Received on Tuesday, 3 February 2004 04:52:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:57 UTC