W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2012

[Bug 17267] [QT3TS] K2-SeqDeepEqualFunc-38, 39

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 May 2012 11:53:43 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Sa3wl-0003ev-LG@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17267

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> 2012-05-31 11:53:43 UTC ---
The interpretation of "import schema" and in-scope schema components has been
subject to quite a lot of drift over the years. I've always had the view that
it should be possible to validate using schema components that are available at
execution time even though they were not imported into a specific module of the
query at compile time, so long as the names of the schema components don't
appear statically in the query; but I agree there's limited support for that
theory in XQuery 1.0 and perhaps even less in 3.0. My thinking is that if a
schema appears in the test environment then it is available for validating
instance documents even though it is not in the static context of the query. We
have plenty of tests that do that in relation to validation of input documents,
though perhaps not in relation to validation initiated within the query itself.

However, I guess there is nothing to lose by adding a schema import here, so
we'll add it.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 31 May 2012 11:53:46 UTC

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