- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Apr 2013 15:27:02 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21719
Bug ID: 21719
Summary: Tests on require-feature/prohibit-feature
Classification: Unclassified
Product: XPath / XQuery / XSLT
Version: Candidate Recommendation
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 3 & XPath 3 Test Suite
Assignee: oneil@saxonica.com
Reporter: christian.gruen@gmail.com
QA Contact: public-qt-comments@w3.org
- well-formed-feature-2:
This test case should also allow XQST0123 as result, because "qname" is no
valid feature. As an alternative, the feature string could be reduced to
"not:a:qname"
- well-formed-feature-4:
I would have expected XPST0081 as error
- require-prohibit-1:
XQST0120 should also be accepted here
- require-prohibit-3:
The current specification says that the "Serialization Feature does
not have a feature name, and cannot be required or prohibited in a module.",
so this test should probably return XQST0123 instead.
- require-prohibit-5:
XQST0120 should also be accepted here
- require-all-optional-features-5-s:
I would suggest to also add XQST0128 as correct result, because the
spec says that a) "it is a static error [err:XQST0128] if a feature name
that an implementation supports appears in a prohibit-feature option
declaration and the implementation is unable to disable the feature" and
b) "all-optional-features corresponds to the set of all named features that
correspond to features listed in 5.2 Optional Features"
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 April 2013 15:27:07 UTC