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

[Bug 3756] Pre-canonicalize the testsuite

From: <bugzilla@wiggum.w3.org>
Date: Thu, 21 Sep 2006 16:11:14 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1GQR8s-0001iZ-0O@wiggum.w3.org>

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


frans.englich@telia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|namespaces not in canonical |Pre-canonicalize the
                   |order in expected output    |testsuite




------- Comment #4 from frans.englich@telia.com  2006-09-21 16:11 -------
I think it is a reasonable suggestion, and I wouldn't mind to see it done
either, I think. The question is whether it's feasible:

How would fragments be handled? Those are messy since c14n tools will choke on
non-XML input(I guess). One could wrap them with an element and leave it there
but that would require existing drivers to be changed, and also require them to
wrap their output in a particular way. Another approach is to try to remove the
document element afterwards, but this is all getting messy. As I currently see
it, XML fragments are a show stopper for this enhancement.

It should probably be implemented as a tool that the task force run on the
suite(just like all our other scripts), to ensure maintainability. The smartest
thing would probably be to extract the K-* tests into the CVS rep., as
suggested by several(including me), otherwise they would pose a problem.

But again, in principle the idea is good. Especially since it feels like this
test infrastructure will be used for future XQuery extensions. However, there's
a general conservatism towards changes in the XQTS(understandably), so I
wouldn't expect anything to change any time soon.
Received on Thursday, 21 September 2006 16:11:23 UTC

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