- From: Sean B. Palmer <sean@miscoranda.com>
- Date: Wed, 11 May 2011 14:35:25 +0100
- To: public-earl10-comments@w3.org
This is feedback on these Last Call Working Drafts: Evaluation and Report Language (EARL) 1.0 Schema W3C Working Draft 10 May 2011 http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/ Developer Guide for Evaluation and Report Language (EARL) 1.0 W3C Working Draft 10 May 2011 http://www.w3.org/TR/2011/WD-EARL10-Guide-20110510/ Specifically on OutcomeValue, which is defined in § 2.7 in the Schema: http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/#OutcomeValue In this section the dct:title and dc:description metadata is said to be recommended which implies some level of optionality. However in the Guide these properties are said to be mandatory: § 4.1 Conforming EARL 1.0 Reports http://www.w3.org/TR/2011/WD-EARL10-Guide-20110510/#EARL10Reports This has been filed as Bug 016. Compare also Bug 002. For the purposes of this bug, it shall be assumed that the Guide has precedence and that dct:title and dct:description are required. Given that dct:title and dct:description are required, and given that the enumerated EARL instances of earl:OutcomeValue are given values of these properties in the EARL schema: http://www.w3.org/ns/earl Does that mean that a conforming EARL report still has to include its own versions of what can be found in the schema? Would it not be conformant against the Guide § 4.1 if values which are different from those found in the schema are used? If it is valid to omit them because the data is implied in the schema, why isn't this stated? And does that apply for any other terms in the vocabulary? This is a serious issue because it is an unresolved issue in compliance, making it impossible to tell whether certain documents are compliant against the Guide § 4.1 or not. Bug 004 is also relevant here. -- Sean B. Palmer, http://inamidst.com/sbp/
Received on Wednesday, 11 May 2011 13:35:53 UTC