[contents]

About This Document

This pages captures outstanding issues in the EARL 1.0 Schema Working Draft of 27 September, 2006. The Evaluation and Repair Tools Working Group (ERT WG) intends to address these issues in future updates of the working draft. Please send comments and feedback to the the mailing list of the ERT WG. The archives for this list are publicly available. This document is an on-going work in progress and is subject to change at any time without advance notice.

Table of Contents

• Overall Issues
• Chapter 1.: Introduction
  • Chapter 1.1.: Structure of EARL Results
  • Chapter 1.2.: Document Conventions and Audience
  • Chapter 1.3.: About RDF Vocabularies
• Chapter 2.: Core Vocabulary
  • Chapter 2.1.: Assertion
  • Chapter 2.2.: Assertor
  • Chapter 2.3.: Test Subject
  • Chapter 2.4.: Test Criteria
  • Chapter 2.5.: Test Mode
  • Chapter 2.6.: Test Result
    • Chapter 2.6.1.: Validity Level
    • Chapter 2.6.2.: Confidence Level
    • Chapter 2.6.3.: Instance Location
  • Chapter 2.7.: Software Tool
  • Chapter 2.8.: Web Content
• Chapter 3.: Extensibility
• Chapter 4.: Conformance
• Appendix A: EARL 1.0 Schema in RDF/XML
• Appendix B: EARL 1.0 Terms
• Appendix C: Document Changes
• Appendix D: References
• Appendix E: Contributors

Overall Issues

• [Hold] Align this document with the EARL 1.0 Guide document once it is available.
• [Hold] Align this document with the HTTP Vocabulary in RDF document once it is available.
• [Hold] Align this document with the Pointer Vocabulary document once it is available.
• [Closed] Revise UK vs US spelling (for example foaf:Organisation etc.).
• [Closed] Revise traditional namespaces, especially for XML Schema (xsd or xs vs xmls).
• [Closed] Remove all occurences that still reference dc:identifier for use with URIs.
• [Closed] Add brief note to highlight consideration on potential security/privacy issues (see decision from teleconference on 6 December, 2006).

Chapter 1.: Introduction

• [Hold] Align this section with the EARL 1.0 Guide document once it is available.

Chapter 1.1.: Structure of EARL Results

• [Hold] Align this section with the EARL 1.0 Guide document once it is available.

Chapter 1.2.: Document Conventions and Audience

• [Hold] Align this section with the EARL 1.0 Guide document once it is available.
• [Hold] Assign final namespace for EARL 1.0 after Last Call stage.
• [Closed] Check references for external vocabularies and namespaces (add HTTP-in-RDF, pointers, etc).

Chapter 1.3.: About RDF Vocabularies

• [Hold] Align this section with the EARL 1.0 Guide document once it is available.

Chapter 2.: Core Vocabulary

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

Chapter 2.1.: Assertion

• [Closed] There should be exactly one of the following properties per assertion: earl:assertedBy, earl:subject, earl:test, earl:result, and earl:mode (see decision from teleconference on 27 September, 2006).
• [Closed] Fix example 3 as described in the review comments by Carlos Iglesis.

Chapter 2.2.: Assertor

• [Closed] Encourage the usage of foaf:Organization, like the usage of foaf:Person, for describing organizations (see decision from teleconference on 13 December, 2006).
• [Closed] Fix example 5 as described in the review comments by Sean B. Palmer.

Chapter 2.3.: Test Subject

• [Closed] Revise example 7 to clarify the meaning of dc:hasPart and dc:isPartOf as described in the review comments by Phil Archer for ICRA.

Chapter 2.4.: Test Criteria

• [Closed] Fix example 8 as described in the review comments by Carlos Iglesis.

Chapter 2.5.: Test Mode

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

Chapter 2.6.: Test Result

• [Closed] There should be exactly one earl:validity property per test result (see decision from teleconference on 27 September, 2006).
• [Closed] The earl:confidence property should be dropped (see decision from teleconference on 27 September, 2006).
• [Closed] Fix example 10 as described in the review comments by Carlos Iglesis.

Chapter 2.6.1.: Validity Level

• [Closed] add a new property to reflect "warnings", this property should be called "information" and should be a sub-property of dc:description (see decision from teleconference on 20 December, 2006).
• [Closed] Rename "earl:validity" to "earl:outcome" (see decision from teleconference on 20 December, 2006).

Chapter 2.6.2.: Confidence Level

• [Closed] The Confidence Level should be dropped (see decision from teleconference on 27 September, 2006).
• [Dropped] Fix example 11 as described for example 10 in the review comments by Carlos Iglesis.

Chapter 2.6.3.: Instance Location

• [Closed] Move this vocabulary for pointers to a separate and stand-alone WG Note, much like the "HTTP Vocabulary in RDF" (see decision from teleconference on 13 December, 2006).
  • [Dropped] Consider maximum cardinality restrictions for pointer types within pointer collections (what does it mean to have two XPath expressions within a single pointer collection?).
  • [Dropped] Consider minimum and/or maximum cardinality restrictions for various properties within specific pointer types (for example earl:line in earl:LineCharLenPointer, etc.). Also consider recommending the usage of specific properties (to be reflected in Appendix B: EARL 1.0 Terms).

Chapter 2.7.: Software Tool

• [Closed] Fix example 13 as described in the review comments by Carlos Iglesis.

Chapter 2.8.: Web Content

• [Hold] Align this section to the HTTP Vocabulary in RDF document once it is available.
• [Closed] Adopt the proposal of the "Content" class (see decision from teleconference on 6 December, 2006) - reverted by the counter-proposal and decision from the f2f meeting on 23 February, 2007
• [Closed] Describe the meaning of the terms inherited from the earl:TestSubject class in the context of the earl:WebContent class (for example that the date reflects the fetching of the content rather than the testing of it) - see decision from the f2f meeting on 23 February, 2007.
• [Closed] Monitor the WCL method for defining groups of resources unambiguously in order to track significant developments (see decision from teleconference on 13 December, 2006).

Chapter 3.: Extensibility

• [Closed] Move this section to the EARL 1.0 Guide document (see decision from teleconference on 4 October, 2006).

Chapter 4.: Conformance

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

Appendix A: EARL 1.0 Schema in RDF/XML

• [Closed] Synchronize this section with any changes made to the core vocabulary.
• [Closed] Keep this section as normative, additional to a copy at the actual location at the final EARL 1.0 namespace once available (see decision from teleconference on 4 October, 2006).

Appendix B: EARL 1.0 Terms

• [Closed] Synchronize this section with any changes made to the core vocabulary.
• [Closed] consider making this section normative (rejected - see decision from f2f meeting on 23 February, 2007).

Appendix C: Document Changes

• [Closed] Synchronize this section with any changes made to the core vocabulary.

Appendix D: References

• [Closed] This section needs to be revised and improved thoroughly.

Appendix E: Contributors

• [Closed] This section needs to be updated before Last Call stage.