EARL 1.0 Guide - Outline
This is a draft outline for the EARL 1.0 Guide, which is currently under development by the Evaluation and Repair Tools Working Group (ERT WG). It as discussed during the 6-7 November 2008 face-to-face meeting. This is a draft work in progress and may be updated without prior notification. Progress on this work will be announced through the ERT WG home page.
1. Introduction
1.1. Audience
- Primary audience: developers of tools such as accessibility checkers, validators, or other quality assurance tools
- Secondary audience: metadata applications, accessibility researchers, semantic Web practitioners
1.2. Purpose
- describe how to use the EARL 1.0 Schema
- describe how to use HTTP-in-RDF, Content-in-RDF, and PointerMethods to supplement EARL 1.0 Schema
- It is *NOT* the purpose to teach developers RDF
- We also want to describe some of the benefits and use-cases for EARL
1.3. Structure
2. What is EARL
2.1. Use Cases
2.2. Vocabularies
EARL 1.0 Schema is RDF and reuses DC, FOAF; it also uses the following as extensions
- HTTP-in-RDF
- Content-in-RDF
- Pointer Methods
2.3. How EARL fits into a testing process
3. EARL Structure
The Assertion is the most basic component
3.1. Assertor
who has tested, can be a person or tool or a combination etc.
3.2. Test Subject
is what has been tested, can be extended by HTTP-in-RDF (see section 4.1)
3.3. Test Criterion
3.4. Test Result
4. Supplementing EARL
4.1. Recording HTTP Exchanges
explain how to use HTTP-in-RDF together with EARL 1.0 Schema
4.2. Representing the Tested Content
4.3. Pointing to the Errors