[contents]
Copyright © 2011 W3C ® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use rules apply.
This document captures outstanding issues in the Evaluation and Report Language (EARL) 1.0 Guide, Working Draft of 29 October, 2009. The Evaluation and Repair Tools Working Group (ERT WG) intends to address these issues in future working drafts. Comments and feedback welcome to public-earl10-comments@w3.org.
The document name will be changed from "EARL 1.0 Guide" to "Developer Guide for EARL 1.0", and the conformance sections from "EARL 1.0 Schema" and "HTTP-in-RDF" will be moved here (see Resolution in Minutes of 13 April 2011 Meeting.
[PENDING] - (moved from Issues for EARL 1.0 Schema) consider separating semantic definitions from conformance constraints (from Dominique Hazael-Massieux on 10 Dec 2009).
Resolution: accepted by moving conformance from the vocabulary definition to this document.
[PENDING] - (moved from Issues for EARL 1.0 Schema) avoid use of MUST/SHOULD keywords (from Dominique Hazael-Massieux on 10 Dec 2009).
Status: re-visit issue after document rewrite.
Proposed resolution: avoid use of MUST/SHOULD where possible.
[PENDING] - (moved from Issues for EARL 1.0 Schema) use OWL constrains for machine-readable modelling (from Dominique Hazael-Massieux on 10 Dec 2009).
Status: re-visit issue after document rewrite.
Proposed resolution: reject - we are aiming at syntax rather than semantic constraints.
[PENDING] - (moved from Issues for EARL 1.0 Schema) avoid requiring other serializations, especially without listing them (from Dominique Hazael-Massieux on 10 Dec 2009).
Status: re-visit issue after document rewrite.
Proposed resolution: needs discussion - we want to support XML serialization.
[PENDING] - (moved from Issues for EARL 1.0 Schema) requiring producers to generate all known information is unreasonable (from Dominique Hazael-Massieux on 10 Dec 2009).
Status: re-visit issue after document rewrite.
Proposed resolution: accept - reconsider intent.
[PENDING] - (moved from Issues for EARL 1.0 Schema) definition for consumers is vague (from Dominique Hazael-Massieux on 10 Dec 2009).
Status: re-visit issue after document rewrite.
Proposed resolution: needs discussion - can we say more?
[PENDING] - (moved from Issues for HTTP-in-RDF) clarify if the constraints apply to the syntax or semantics; discourge syntax constraints (from Dan Connolly on 15 Dec 2009.
Status: re-visit issue after document rewrite.
Proposed resolution: clarify we mean syntax constraints, and need to better explain the rationale.
[PENDING] - change FOAF namespace from http://xmlns.com/foaf/spec/# to http://xmlns.com/foaf/0.1/ (from Johannes Koch on 9 Dec 2009).
Resolution: accepted (see related thread).
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.
[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.
The are currently no open issues for this section of the document.
[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.
The are currently no open issues for this section of the document.
[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.
[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.