Lists Home |
Date Index |
On Fri, 2005-05-06 at 17:56 +0100, Richard Tobin wrote:
> >Not so weird. As far as I can tell, other than well-formedness
> >and validity errors the XML Rec places no constraints at all on
> >what data a processor must report.
> Not quite. It does mention a few things that must be reported. For example:
> PIs (2.6)
> All non-markup characters (2.10)
> For validating parsers, which characters are element-content-whitespace
> Defaulted attributes (3.3.2)
> Names of unparsed entities and their notations (4)
> Entities not included by non-validating parsers (4.4.3)
> It's fairly clear from this that the authors of the XML spec did not
> attempt to exhaustively list what must be reported, but instead noted
> the fact in cases where there might be doubt.
That's the heart of the matter. It seems to me that the topic of this
thread is one case of such doubt that was missed by the authors missed
(understandably so). I've been surprised to find how much confusion
there is over element parse/report order, but based on what I found I
thought the topic merited discussion, especially to the audience of my
> >That's what the Infoset Rec is for.
> There is no requirement that any system report everything in the
> Infoset, but it is useful as a guide to what is meant to be
> significant. For example, the fact that element order is significant
> but attribute order not is implied by the Infoset making the
> [children] property an ordered list and the [attributes] property an
> unordered set.
Uche Ogbuji Fourthought, Inc.
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html