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

[Bug 2729] Whitespace text nodes

From: <bugzilla@wiggum.w3.org>
Date: Thu, 02 Feb 2006 17:41:33 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1F4iSb-0002St-5C@wiggum.w3.org>

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


davidc@nag.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED




------- Additional Comments From davidc@nag.co.uk  2006-02-02 17:41 -------

I can't say I'm surprised by this decision given the reaction of the WGs
to previous reports on this subject (from me and xml core, at least). However I
think it's a pretty bad decision.

> Option C implies an incompatibility between DTD-based and schema-based
> processing 

Given that processing with or without schema is pretty much completely
incompatible, (or as the XSLT2 spec puts it more delicately "This may lead to a
number of differences in behavior") I am surprised that white space would be
considered an issue here.

As we are finding in the test suite, results of order by expressions (for
example) typically result in completely different orderings (numeric or textual)
depending on whether a schema was used.

If reviewing these specs were my day-job and I had time to carry on the argument
I would certainly re-open this so that it is flagged as an issue at termination
of CR. As neither of those things is true, I am instead going to close this
report which is why I'm taking this last opportunity to complain (if not
formally object) in this comment.


David
Received on Thursday, 2 February 2006 17:41:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:10 UTC