This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8500 - Priority of validation errors
Summary: Priority of validation errors
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Benjamin Nguyen
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-15 16:18 UTC by Nick Jones
Modified: 2013-06-11 14:39 UTC (History)
3 users (show)

See Also:


Attachments

Description Nick Jones 2009-12-15 16:18:04 UTC
Looking at validateexpr-26:

validate { document { <a/>, <b/> } }

The error XQDY0061 (document node whose children do not consist of exactly one element node ) is expected.

I think it is unclear in the spec whether XQDY0027 (root element information item in the PSVI resulting from validation does not have the expected validity property) might also permitted.

Are the validate rules expected to be followed in order, and errors thrown with precedence from the order listed? If not, could the second error be added.

When streaming results being able to throw the XQDY0027 error is preferable as it would be known before the XQDY0061 error.
Comment 1 Michael Kay 2009-12-15 16:47:42 UTC
Seems reasonable to add the extra error code. Generally the presumption is in favour of allowing alternative error codes if there's a plausible rationale for them.
Comment 2 Andrew Eisenberg 2010-03-08 16:18:37 UTC
The XML Query and XSL WGs discussed this issue at our March 2 meeting. We agreed to add the additional expected error that you have requested and I have made this change.
Comment 3 Oliver Hallam 2011-06-14 13:25:56 UTC
I think the XQDY0027 error code we suggested was wrong.  As far as I can see the problem is that the empty namespace is not in the in scope schema types.

Thus I believe the alternative error code should be XQDY0084, and not XQDY0027.
Comment 4 O'Neil Delpratt 2013-06-11 14:39:43 UTC
This bug has been resolved in QT3