[contents]
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.
- [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).
- [Hold] Align this section with the EARL 1.0 Guide document once it is available.
- [Hold] Align this section with the EARL 1.0 Guide document once it is available.
- [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).
- [Hold] Align this section with the EARL 1.0 Guide document once it is available.
The are currently no open issues for this section of the document.
The are currently no open issues for this section of the document.
- [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).
The are currently no open issues for this section of the document.
- [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).
- [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).
- [Closed] Synchronize this section with any changes made to the core vocabulary.
- [Closed] This section needs to be revised and improved thoroughly.
- [Closed] This section needs to be updated before Last Call stage.