- From: <bugzilla@jessica.w3.org>
- Date: Sun, 17 Mar 2013 13:07:22 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21314
Bug ID: 21314
Summary: update dependencies type="feature"
Classification: Unclassified
Product: XPath / XQuery / XSLT
Version: Working drafts
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: XQuery 3 & XPath 3 Test Suite
Assignee: oneil@saxonica.com
Reporter: spungi@gmail.com
QA Contact: public-qt-comments@w3.org
Created attachment 1341
--> https://www.w3.org/Bugs/Public/attachment.cgi?id=1341&action=edit
Report generated using the tools/dependencies.xq
The attached report was generated using the tools/dependencies.xq query
provided in FOTS as of March 17th.
At this moment there are a few questions I would have wrt. dependencies with
type="feature":
1) shouldn't there be a 1 to 1 relation between the official optional features
as defined in the spec
http://www.w3.org/TR/xquery-30/#id-conform-optional-features)
and the features defined in FOTS?
1.1) If not, IMHO the ones that are not defined in the spec should have some
information added in the catalog-schema.xsd such that it's clear for everyone
what they stand for.
For example what does the 'collection-stability' stands for?
How about 'xpath-1.0-compatibility' or 'directory-as-collection-uri' or
'schema-location-hint'?
2) From what I understand, the 'schemaValidation' and 'schemaImport' were
merged into 'schemaAware' right?
If so the test cases need to be updated also.
Also 'moduleImport' should be updated to 'module' for consistency to the spec.
3) Should the spec add an optional feature for 'namespace-axis' ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 17 March 2013 13:07:24 UTC