W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2005

[Bug 1309] white space in the DM

From: <bugzilla@wiggum.w3.org>
Date: Thu, 09 Jun 2005 11:57:58 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DgLfa-0000J3-Gy@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1309





------- Additional Comments From davidc@nag.co.uk  2005-06-09 11:57 -------
> Please let us know if you accept this resolution.

I object to this resolution.

If a breaking change is going to be introduced between 1.0
and 2.0 then the least that could be done is document that fact.

Even if this is documented I object to the resolution.

It's not just incompatibility with XSLT1 that must be documented: it's
incompatibility between XSLT2 (and Xquery) systems. As whether or not
[element content whitespace] is reported by a
non-validating-parser-that-reads-a-dtd is entirely parser specific as
far as I can see, and parsers of this type have traditionally been the
ones most commonly used with XSLT.

If the resolution is to keep the currently specified behaviour, the
editorial change to change from referencing Element content[XML] to
referencing [element content whitespace] should be made as Element
content[XML] is a property of an XML document (a sequence of Unicode
characters) not a property of an infoset ie it's not a property of the
input to the mapping being defined.

I also don't understand the WG's intention to specify a mapping from the
Xquery data model that always sets [element content whitespace] to
unknown.  Do they disagree with the analysis that this produces an
infoset that violates a constraint specified on the infoset
recommendation?

David
Received on Thursday, 9 June 2005 11:58:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:38 GMT