- From: <bugzilla@jessica.w3.org>
- Date: Tue, 20 Jul 2010 15:13:59 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10207
Oliver Hallam <oliver@cbcl.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|XQuery |XPath 2.1
--- Comment #2 from Oliver Hallam <oliver@cbcl.co.uk> 2010-07-20 15:13:58 ---
I agree with all your comments.
My main discomfort with the current rules is that you can match an element
against a schema type that would fail to validate according to the in-scope
schemas.
Since the rules are in fact clear for 2.0 (and hence there is no pressing need
to fix this), I have changed this bug to be against XPath 2.1.
My personal opinion is that the rules should be equivalent to those in schema
and if possible the spec should reference the rules in schema instead of
redefining them. In a processor that handles schemas statically it is just a
matter of computing the set of element types that are validly substitutable for
an element, but I an unsure of the ramifications of this change for an
implementation that can accept new schemas at runtime.
--
Configure bugmail: http://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 Tuesday, 20 July 2010 15:14:01 UTC