[contents]

About This Document

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.

Related Issues Lists

Table of Contents

  1. Overall Comments
  2. 0. Front Matter
  3. Introduction
  4. What is the Evaluation and Report Language?
  5. An EARL report: basics
  6. Advanced usage
  7. Conclusions

Appendices

  1. References
  2. Document changes
  3. Contributors

Overall Comments

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).

0. Front Matter

The are currently no open issues for this section of the document.

1 Introduction

The are currently no open issues for this section of the document.

2 What is the Evaluation and Report Language?

The are currently no open issues for this section of the document.

2.1 Use cases and audience

The are currently no open issues for this section of the document.

2.2 Fitting EARL to the testing process

The are currently no open issues for this section of the document.

3 An EARL report: basics

The are currently no open issues for this section of the document.

3.1 Basic report components

[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.

3.2 Putting the pieces together

[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.

3.3 An accessibility example

The are currently no open issues for this section of the document.

3.4 Identifying unambiguously the resource

[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.

4 Advance usage

The are currently no open issues for this section of the document.

4.1 Extending the vocabularies

[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.

4.2 Merging reports from different sources

[HOLD] - incorrect use of "dct:hasVersion" (from Pete Johnston on 3 Nove 2009).
Status: wait until reuse of DOAP has been settled.

5 Conclusions

The are currently no open issues for this section of the document.

Appendix A: References

The are currently no open issues for this section of the document.

Appendix B: Document changes

The are currently no open issues for this section of the document.

Appendix C: Contributors

The are currently no open issues for this section of the document.