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

[Bug 3534] Missing schema imports in LocalNameFromQNameFuncXXX and NamespaceURIFromQNameFuncXXX

From: <bugzilla@wiggum.w3.org>
Date: Fri, 28 Jul 2006 09:15:56 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1G6ORo-0000Aj-Vl@wiggum.w3.org>

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





------- Comment #7 from davidc@nag.co.uk  2006-07-28 09:15 -------
(In reply to comment #6)
> I agree that the query doesn't use user-defined types; but the input document
> doesn't refer to a schema, 

Oh that's probably a bug it used to refer to a schema didn't it?

> and the XQTS instruction doesn't say that an input
> XML should be schema validated only because there is a schema available for the
> namespace that the query or the XML happen to use.

no, but it _could_ say that.

> And, even in that case, I guess that schema validating every input XML will
> break all those queries that expect untyped data.
> So, in my opinion, the easiest way to have PSVI-validated data starting from an
> XML that doesn't point to a schema is by loading the schema from within the
> query.

Nothing in the XQuery spec suggests that using a schema import declaration
should affect the building of input trees, and these tests can be passed by
systems that support building trees from PSVI but do not support Schema Import.
(It's not unlikely that such systems could exist, even if the initially
available XQuery implementations do not support that, as input from a PSVI just
needs an API to build a tree from a 3rd party validating XML parser whereas
schema import requires much tighter integration of XSD support into the Query
engine.
Received on Friday, 28 July 2006 09:16:15 UTC

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