W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2011

[Bug 11738] [FT] thesaurus.xsd wrong (again) or usability.xml wrong

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Jan 2011 18:59:28 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PhRdQ-0003VA-Dm@jessica.w3.org>

--- Comment #3 from Paul J. Lucas <paul@lucasmail.org> 2011-01-24 18:59:27 UTC ---
So, just to clarify, if usability.xml has no nested synonyms, then as far as I
can tell, none of the thesaurus XML data files provided in the test suite
actually have "levels" of synonyms in them.  There are several tests in the
test suite that have "levels" clauses in them.  If there are no levels in the
thesauri data, then what, exactly, are the "levels" in the queries testing?

What I would have expected would be the existence of thesauri data that has
levels like:

=> cat
==> feline

and for a query to limit the levels to, say, "exactly 1 level" while looking
for "feline" -- the "contains text" should then return "false" because "feline"
should *not* be considered because it is too many levels away.

Aside: again, the reason this bug is a "blocker" is because, although the W3C
may consider these data "informational," in order to pass the tests, an
implementation should use the exact thesaurus data specified.  In order to use
the exact data specified, an implementation has to read in the thesaurus XML
data into an internal data-structure according to a schema.  A schema that
allows nested synonyms results in an different internal data structure (and
algorithm) from one that doesn't.  If either the XML file or the schema are
broken, this task is impossible.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 24 January 2011 18:59:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC