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

Bug 020: OutcomeValue as a Constrained Literal

From: Sean B. Palmer <sean@miscoranda.com>
Date: Wed, 11 May 2011 14:38:40 +0100
Message-ID: <BANLkTikam_m-7w0ftsb5fHqyoFt7bZkARA@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/

Bug 018 proposes removing the earl:OutcomeValue instances and
replacing earl:TestResult with earl:OutcomeValue. If this approach be
found undesirable, however, it may be convenient to use constrained
literal values instead. So in other words the following example taken
from Bug 018:

:assertion earl:result [ a earl:TestResult;
   dct:date "..."; # required for no obvious reason
   earl:outcome earl:passed;
   earl:info "passed for the first time" ].
   # not clear if this is a valid use of earl:info, compare Bug 011

Would become in this proposal:

:assertion earl:result [ a earl:TestResult;
   earl:outcome "passed";
   earl:info "passed for the first time" ].

This would have the effect that Bug 019 would disappear as an issue,
since it would not be feasible in RDF/XML to give literals as subjects
for annotation with dct:title and dct:description.

-- 
Sean B. Palmer, http://inamidst.com/sbp/
Received on Wednesday, 11 May 2011 13:39:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 May 2011 13:39:08 GMT