W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2015

[Bug 28639] [QT3] fn-element-with-id-1 to xxx-5 should be schema-aware

From: <bugzilla@jessica.w3.org>
Date: Wed, 15 Jul 2015 16:20:47 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28639-523-RIA1j5UTpH@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28639

--- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I find it a rather unfortunate decision, as it makes it harder to find out what
a test is about, and it breaks the general rule that the metadata must be
complete. Now you need to browse to wherever the dependencies are to find out
whether a test requires the schemaImport or Validation feature.

And what happens in the case that the schemaValidation or schemaImport
dependencies are set with satisfies="false" and the test uses a schema in its
metadata?

<dependency type="feature" value="schemaImport" satisfied="false"/>

I would assume that at the test-level this would override whether or not there
is a <schema> component in the environment, such that it enables you to test
behavior of processors with tests that require schema's but that themselves do
not support, or have switched off schema-import/validation.

But at the global level(s) it becomes trickier: if the test-set contains a
dependency, does it override "soft dependencies" such as the one proposed, or
does the soft-dependency take precedence? And what for the catalog level?

I would personally prefer this decision to be reverted and to have tests in
"good shape", but I was not present at the meeting...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 15 July 2015 16:20:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:55 UTC