This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As the following QT3TS tests (and maybe some more) include schema imports, I would expect error XQST0009 as valid alternative: - ST-Data001 - CastAsNamespaceSensitiveType-6 - CastAsNamespaceSensitiveType-7 - CastAsNamespaceSensitiveType-8 - CastAsNamespaceSensitiveType-9 - CastAsNamespaceSensitiveType-10 - CastAsNamespaceSensitiveType-11 - CastAsNamespaceSensitiveType-12 - nscons-040 - nscons-041 - Constr-cont-nsmode-11 - instanceof112 - instanceof113 - instanceof114 - instanceof115 - instanceof116 - instanceof117 - instanceof118 - instanceof119 - instanceof120 - instanceof135 - instanceof136 - instanceof137 - instanceof138 - instanceof139 - instanceof140 - instanceof141 - cbcl-module-001 - require-schema-aware-1-s - require-schema-aware-1-ns - require-schema-aware-2-s - require-schema-aware-2-ns - require-schema-aware-3-s - require-all-optional-features-1-s - require-all-optional-features-1-ns1 - require-all-optional-features-1-ns2 - require-all-optional-features-1-ns3 - require-all-optional-features-1-ns4 - prohibit-all-optional-features-2-s - prohibit-all-optional-features-2-ns - prohibit-all-optional-features-3-s - prohibit-all-optional-features-3-ns - typeswitch-112 - typeswitch-113 - typeswitch-114 - typeswitch-115 - typeswitch-116 - extvardef-023 - extvardef-024 - extvardef-025 - extvardef-026 - extvardef-027 - FOTY0012 - XQDY0027 - XQDY0084 - XQST0036_1 - XQST0036_2 - XQST0036_3 - XQST0036_4 - XQST0036_5 - XQST0036_6 - XQST0036_7 - XQST0058 - XQST0059_1 - XQST0059_3 - XQST0059_6
The general policy is not to provide an alternative result for such tests, but rather to document the dependency of the test on optional features, so that a product which does not support the feature does not run the test. In many of these cases (those I checked) there is no explicit dependency on schema-awareness (arguably there should be), but there is an implicit dependency in that the environment contains a <schema> element.
(In reply to comment #1) I believe we can mark this bug as resolved.
Agreed.. Thanks.
I have reopened this issue because a large number of test cases (appr. 6000, or 23%) seem to have an implicit implicit schema dependency. While we could check the necessity of all schema imports for those tests, I believe it is less effort if we explicitly add a schema dependency to the tests that I’ve initially listed.
Created attachment 1351 [details] Patch with schema dependencies I have added a patch that includes all schema dependencies that I believe are missing in the current test suite.
Created attachment 1352 [details] Patch with schema dependencies (updated) The updated patch includes an additional schema-import dependency for the itunes query.
Thanks Christian for the patch. I will apply it
Thanks O'Neil! I noticed two more test cases need to be added: "orderBy29" and "orderBy52" sort their XML input based on a given schema. Feel free to tell me if you need an updated patch, or changes to the given patches.
Patch applied and updated to cvs. I will add the schemaImport dependency to the test cases mentioned in comment #8
Bug fixes complete and committed to subversion
Created attachment 1357 [details] Schema dependencies added to fn:nilled() tests I have stumbled across some more test cases with unspecified schema dependencies; please have a look at my new patch.
I have closed the issues #21937 and #21723, and I am adding five test cases to this issue, which I believe require yet another schema import dependency. - WindowingUseCase07S - WindowingUseCase11S - WindowingUseCase13S - LocalNameFromQNameFunc021 - NamespaceURIFromQNameFunc021 As mentioned in #21937, I’ll be glad to help out (e.g. by updating the patch or directly commit the changes by myself).
Sorry for my persistence; has there been some discussion on this?
thanks for the reminder. I have committed the bug fixes to cvs. I confirm that I have addressed the issues raised in comment #11 and #12
Thanks, O’Neil. I can confirm that all test cases are fixed. I’m embarrassed to notice, however, that I have forgotten the two test cases that had been added by Michael in bug #21723: - NamespaceURIFromQNameFunc021a - LocalNameFromQNameFunc021a They also require a schema import dependency, similar to the two original test cases.
(In reply to comment #15) dependency on schema import added
Thanks; closed.