W3C home > Mailing lists > Public > public-earl10-comments@w3.org > May 2011

Bug 022: OutcomeValue Problems

From: Sean B. Palmer <sean@miscoranda.com>
Date: Wed, 11 May 2011 16:46:30 +0100
Message-ID: <BANLkTi=QaPPNeCbBK6rqdeccX1mF3SwqQw@mail.gmail.com>
To: public-earl10-comments@w3.org
This is feedback on a Last Call Working Draft:

Evaluation and Report Language (EARL) 1.0 Schema
W3C Working Draft 10 May 2011
http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/

Especially of the OutcomeValue instances in a subsection of ยง 2.7:

http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/#OutcomeValueInstances

And the table of instances in Appendix A:

http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/#terms-instances

There are three issues:

* Why are the instances lowercase, earl:passes instead of earl:Passes
or earl:PASSES?
* Why is the instance of earl:CannotTell called earl:cantTell instead
of earl:cannotTell?
* Why does the table of instances refer to "Title" when all the other
similar table columns refer to "Label"?

This would seem to be some kind of attempt to carefully disambiguate
between schema data and instance data. These instances are, however,
really being used as schema vocabulary terms, and are part of the core
set of the EARL vocabulary.

This bug is moot if, as claimed in Bug 018 and Bug 020, OutcomeValue
instances are redundant altogether. Bug 020 in particular, though, may
be partly caused by the suspected motivation described above; that
this is the result of some attempt to disambiguate schema and instance
data.

If that was indeed the rationale, then this bug should be taken as
also claiming that the rationale is misguided. If that was not the
rationale, then this bug should be taken as being solely about the
capitalisation, spelling, and instance column header issues.

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Wednesday, 11 May 2011 15:46:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 May 2011 15:46:58 GMT