W3C home > Mailing lists > Public > public-xqts-comments@w3.org > April 2006

Re: Inspect/implementation defined order fn-trace-*

From: David Carlisle <davidc@nag.co.uk>
Date: Tue, 25 Apr 2006 11:11:06 +0100
Message-Id: <200604251011.k3PAB66o011784@edinburgh.nag.co.uk>
To: public-xqts-comments@w3.org
CC: englich@kde.org


Frans,

I think (as a non WG member) that the reason these are Inspect is that
the point of trace() is that you need to _inspect_ the trace output
(which has gone to some system specific place).

The actual result returned by the query isn't system dependent, but
it's for you to look at the log generated by the trace() function and if
it's empty or if it just says "system error: couldn't write to log file"
or something else other than the expected trace, it's for you to decide
whether that constitutes a pass or fail.

Having said that, I think that this interpretation is really justified
by the Catalogue markup which does, as you say, imply that one should
manually compare the result output with the supplied result file.

The Catalogue format should probably be extended to allow the Catalogue
to specify both the Query result (checked by XML comparisopn) and the
trace log (checked by inspection).

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
Received on Tuesday, 25 April 2006 10:11:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:22:07 GMT