[contents]
This document describes the formal schema of the Evaluation and Report Language (EARL) 1.0. The Evaluation and Report Language is a standardized vocabulary to express test results. The primary motivation for developing this language is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor neutral and platform independent format. It also provides reusable vocabulary for generic quality assurance and validation purposes. While this document focuses on the technical details of the specification, a companion document [Guide] describes the motivations for EARL and provides a tutorial introduction to its use.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This 5 September 2006 Editors' Draft of the Evaluation and Report Language (EARL) 1.0 Schema is and update for the previous EARL 1.0 Working Draft of 9 September 2005. It meets the requirements specified in the Requirements for the Evaluation and Report Language (EARL) 1.0, and incorporates change requests received since the September 2005 Working Draft, in particular implementing the decisions of the EARL Working Group at its face to face meetings in October 2005 and February 2006 (see history of document changes). This document is intended to be published and maintained as a W3C Recommendation after review and refinement.
The working group encourages feedback about this document, Evaluation and Report Language (EARL) 1.0 Schema, by developers and researchers who have interest in software-supported evaluation and validation of Web sites. In particular, the group is looking for feedback on the following questions:
- Does the language provide sufficient vocabulary to describe Web content that has been subject of testing? In particular, is dynamically generated Web content, content that is served after client-server negotiation, as well as whole groups of related content (sometimes also refered to as "Delivery Units" or "Web Units") sufficiently addressed?
- Are there incompatability or inconsistency issues with the vocabulary for "Web Content Labeling" that is currently being explored by the W3C Content Label Incubator Group, or with the "Test Description Metadata" currently being developed by the W3C Quality Assurance Activity? Can the interoperability be enhanced?
- Additional questions about more specific aspects of the EARL 1.0 Schema are also highlighted within the relevant sections of this document.
Please send comments on this document to the public email list of the working group public-wai-ert@w3.org. The archives of the working group mailing list are publicly available.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document has been produced by the Evaluation and Repair Tools Working Group as part of the WAI Technical Activity.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
[Editor's note: this section will be synchronized with the EARL 1.0 Guide [Guide] as it is being developed.]
The Evaluation and Report Language (EARL) is a format to express test results. Test results include bug reports, test suite evaluations, and conformance claims. The test subject might be a Web site, an authoring tool, a user agent or some other entity. Thus, EARL is flexible. It enables any person, entity, or organization to state test results for any thing tested against any set of criteria.
Stating test results in EARL creates a variety of opportunities. The data can be:
- aggregated from different sources
- exchanged between tools
- used to create customized reports
- combined to compare how different test subjects fared on the same test.
A companion document [Guide] to this specification provides more introductory material and explanation of the use cases for EARL.
EARL statements contain the following types of information:
- Context
- This can include information about who or what ran the test, the date the test was run, and other information about the test was performed.
- Test subject
- This can include: Web pages, tools (e.g. accessibility checkers, validators), and user agents
- Test result
- Did the test subject pass or fail the test? How certain can we be?
- Test requirement
- What are we evaluating the test subject against? This could be a specification, a set of guidelines, a test from a test suite, or some other test criteria.
Prose examples that demonstrate the above structure:
Example 1: a person carries out a manual evaluation of a Web page against a test requirement.
- Context
- Mary Thompson claims on the 17th December
- Test Subject
- A Web page at
http://www.example.org/mypage
- Test Result
- Passed
- Test requirement
- Checkpoint 1.1 of the Web Content Accessibility Guidelines 1.0
Example 2: an evaluation tool carries out automated evaluation of a Web page against a test criteria.
- Context
- The W3C Markup Validator claims as of
2004-04-14T14:00:04+1000
- Test Subject
- The XHTML returned from a GET request to the URI
http://www.example.org/yourpage
- Test Result
- Failed
- Test requirement
- The validity of the XHTML
There are a niumber of known issues in this draft, that need to be resolved in future drafts. Comments are specifically requested on any of these issues, which are marked as follows:
[Editor's note: there are some items that the working group has discussed but not reached consensus, and others that are known issues that have not yet been discussed]
This subsection will be removed from the final version of the document, and editorial comments will have been resolved.
This document is intended as a brief complete specification of the EARL 1.0 vocabulary. It assumes that the reader is familiar with the ideas of RDF and can read its XML serialisation as bare code. The assumed audience is developers who are implementing EARL in software or processes, or are seeking to understand the ideas, models, or properties and classes used in the EARL vocabulary. Readers who would like a more tutorial introduction to the language, with more explanation of its foreseen use cases, are referred to the EARL 1.0 Guide [Guide]. Readers who wish to understand more about RDF are advised to consider reading a general introduction, or reading the RDF Primer [RDF-PRIMER].
The key words must, required, recommended, should, may, and optional are used in accordance with RFC 2119 [RFC2119].
The namespace for EARL as specified in this draft is http://www.w3.org/WAI/ER/EARL/nmg-strawman#.
[Editor's note: Versioning terms during the process of developing the vocabulary is an issue the group is working on. It is possible that a new namespace will be used for a final version of the vocabulary]
Where RDF terms are used in their abbreviated form (e.g. Assertion or foaf:Person), if no namespace is provided the term is in the EARL namespace. The following prefixes are used in examples throughout this document:
earl- The EARL namespace
http://www.w3.org/WAI/ER/EARL/nmg-strawman# which is described in this document
foaf- The FOAF namespace
http://xmlns.com/foaf/0.1/ which is also where the terms are described [FOAF]
dc- The Dublin Core elements namespace
http://purl.org/dc/elements/1.1/ whose terms are described in [DC]
dct- The Dublin Core terms namespace
http://purl.org/dc/terms/ described at [DCT]
rdf- The RDF namespace
http://www.w3.org/1999/02/22-rdf-syntax-ns# described in [RDF]
rdfs- The RDF Schema namespace
http://www.w3.org/2000/01/rdf-schema# described in [RDFS]
owl- The OWL namespace
http://www.w3.org/2002/07/owl# described in [OWL]
xmls- The XMLS namespace
http://www.w3.org/2001/XMLSchema# described in [Editors' Note: TBD]
EARL is defined as an RDF vocabulary. The Resource Description Framework (RDF) [RDF] is a general-purpose language for describing information in a way that is machine-understandable.
EARL is an RDF vocabulary used to make statements about how a resource performed against a test. In common with other RDF it assumes that other vocabularies will be used as appropriate.
For more information on RDF, please refer to the following references:
- RDF Primer [RDF-PRIMER]
- Resource Description Framework (RDF) Model and Syntax Specification [RDF]
- Why RDF model is different from the XML model [RDF-XML-DIFFS]
The EARL 1.0 specification defines an RDF Vocabulary that consists of classes and properties. This section describes the core vocabulary and gives brief examples of its usage. Later sections describe extensibility of EARL 1.0; and conformance to EARL 1.0.
An Assertion is a statement about the results of performing a test. The earl:Assertion class relates the required instances of an Assertor, Test Subject, Test Requirement, and Test Result to a specific Assertion. It is the fundamental unit of an EARL statement or set of statements.
An Assertion must have at least the
following properties:
earl:assertedBy- The Assertor is a human or software, or groups of these, that determine the result.
earl:subject- The thing that is being tested against some requirement is the Subject of the assertion.
earl:test- The criteria that is used to test a subject is the Test Statment of the assertion.
earl:result- The Result of the test - whether the subject passes or fails the test requirement (or there is some other result).
An Assertion may also include the following optional properties:
earl:mode- The mode in which the test was performed - as an automated computer process, by a human, or otherwise.
Example 3: instance of an assertion expressed as an RDF/XML fragment.
<earl:Assertion rdf:ID="#assertion">
<earl:assertedBy rdf:resource="#assertor" />
<earl:subject rdf:resource="#subject" />
<earl:test rdf:resource="#testcase" />
<earl:result rdf:resource="#result" />
</earl:Assertion>
An Assertor determines the results of a test (i.e. an assertor asserts and assertion). An earl:Assertor must belong to one of the following types:
earl:SingleAssertor- There is a single entity responsible for making the Assertion, it must be one of the following types:
foaf:Person- The Assertor is a human being. This uses the FOAF vocabulary term
foaf:Person to describe a person. There should be identifying information including a name, and a uniquely identifying property such as email address or preferably an encrypted email address. The properties foaf:name, foaf:mbox and foaf:mbox_sha1sum are defined by FOAF [FOAF].
foaf:Agent- The Assertor is an Agent, as defined in [FOAF]. An Agent is a super class of
foaf:Person, foaf:Organisation and foaf:Group which can all be used to describe an Assertor.
earl:Software- The Assertor is a piece of Software, such as a black box testing tool of some sort or an evaluation tool.
earl:CompoundAssertor- The Assertor is a compound group of persons and/or softwares. Each group must have at least one primary Assertor identified by the
earl:mainAssertor property, and may, have secondary Assertor identified by the earl:helpAssertor property, as well as optional title and description identified by the [DC] dc:title and dc:description properties respectively.
Note: since the range of both the earl:mainAssertor and the earl:helpAssertor properties of the Compound Assertor reference earl:Assertor classes, these instances can be a Person, Agent, Software, or recursively another Compound Assertor.
Example 4: an Assertor that is a person called Bob B. Bobbington.
<foaf:Person rdf:ID="bob">
<foaf:name>Bob B. Bobbington</foaf:name>
<foaf:mbox rdf:resource="mailto:bob@example.org"/>
<foaf:mbox_sha1sum>1a9daad476f0158b81bc66b7b27b438b4b4c19c0</foaf:mbox_sha1sum>
</foaf:Person>
Example 5: an Assertor that is a piece of software called Cool Tool (see also example 13).
<earl:Software rdf:ID="tool">
<dc:title xml:lang="en">Cool Tool</dc:title>
<dc:description xml:lang="en">My favorite tool!</dc:description>
<foaf:homepage>http://example.org/tools/#cool</foaf:homepage>
<dct:hasVersion>1.0.3</dct:hasVersion>
</earl:Software>
Example 6: a Compund Assertor of the person from example 4 using the software from example 5.
<earl:compoundAssertor rdf:ID="assertor">
<dc:title xml:lang="en">Bob using Cool Tool</dc:title>
<dc:description xml:lang="en">Bob doing semi-automated testing</dc:description>
<earl:mainAssertor rdf:resource="#bob"/>
<earl:helpAssertor rdf:resource="#tool"/>
</earl:compoundAssertor>
The Test Subject is the class of things that have been tested. This class is intentionally generic to serve a wide variety of usages. For more specific use cases, the EARL earl:WebContent or earl:Software classes can be used in place to describe Web Content or Software that is being tested.
The earl:TestSubject class may have any of the following properties:
dc:title- Human readable title for the subject (e.g. "Home Page")
dc:description- Human readable description of the subject (e.g. "Main entry page to the Web site")
dc:date- Date on which the subject was tested (or when it was identified if more appropriate)
dct:hasPart- Relationship to other subjects that are part of this subject
dct:isPartOf- Relationship to other subjects of which this subject is a part of
Example 7: Java applet that is part of a Web application.
<earl:TestSubject rdf:ID="subject">
<dc:title xml:lang="en">Login Applet</dc:title>
<dc:description xml:lang="en">Java applet that is used for system login</dc:description>
<dc:date rdf:datatype="http://www.w3.org/2001/XMLSchema#gDate">2005-06-25</dc:date>
<dct:isPartOf rdf:resource="http://example.org/"/>
</earl:TestSubject>
A Test Criteria is a testable statement - usually one that can be passed or failed. It is a super class for all types of tests including things such as validation requirements, code test cases, checkpoints from guidelines such as Web Content Accessibility Guidelines 1.0 [WCAG10], or others.
While the generic earl:Testable class can be used directly, one of the following types should be used:
earl:TestRequirement- A higher-level requirement that is tested by executing one or more sub-tests. For example WCAG 1.0 Checkpoint 1.1 which is tested by executing several sub-tests and combining the results.
earl:TestCase- An atomic test - usually one that is a partial test for a requirement. For example, checking if an image has an
alt attribute which could be part of testing WCAG 1.0 Checkpoint 1.1.
Any Test Criteria such as Test Requirement or Test Case should be identified with a URI using the Dublin Core dc:identifier property. A Test Criteria may be a single test, or part of a larger compound test suite. These relations may be described using Dublin Core's dct:hasPart or dct:isPartOf properties. Additionally, a title or description for the test criteria may be included by using the Dublin Core dc:title or dc:description properties.
[Editor's note: The earl:Testable, earl:TestRequirement, and earl:TestCase classes are included for convenience, since this allows various useful properties to be described in simple standard RDF. The working group will deprecate these classes if they find an appropriate replacement from a language designed for describing test criteria (including test requirements and test cases), something which is beyond the scope of the current specification.]
Example 8: instance of a test case that is described with a title and its relationship to a test suite.
<earl:TestCase rdf:ID="testcase">
<dc:title xml:lang="en">HTML Test 282</dc:title>
<dc:description xml:lang="en">Test 282 of the HTML test suite</dc:title>
<dct:isPartOf rdf:resource="http://example.org/tests/html/"/>
<dct:hasPart rdf:resource="http://example.org/tests/html/#617"/>
<dc:identifier>http://example.org/tests/html/#282</dc:identifier>
</earl:TestCase>
The (optional) Test Mode information is used to simplify some commonly used querries on how the testing was carried out. When provided, it must reflect the information provided by the Assertor, and it must be exactly one of the following pre-defined values (or subclasses of them):
earl:manual- Where the test was performed based on a person's judgement. This includes the case where that judgement was aided through the use of a tool, although this should be additionally noted through the
earl:compoundAssertor class of the Assertor.
earl:automatic- Where a computer program or similar has done an automated test and generated a result without human assistance.
earl:semiauto- Where a computer program or similar was primarily responsible for generating a result, even if with some human assistance. This should be additionally noted through the
earl:compoundAssertor class of the Assertor.
earl:mixed- Where there is no detailed information about the test mode available. This includes when testing is carried out by organizations or groups of assertors, and the exact testing process is not disclosed.
earl:heuristic- This property was designed to cover assertions which are made by inference, for example based on several existing test results.
Example 9: the assertion from example 3 was carried out in semi-automatic mode.
<earl:Assertion rdf:about="#assertion">
<earl:mode rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#semiauto"/>
</earl:Assertion>
The actual result of the test. It includes both machine-readable values as well as human-readable description of the results (typically error messages).
A Test Result must have exactly one of the following properties:
earl:validity- The Validity Level is a machine-readable value that describes the result.
A Test Result should include the following properties:
dc:title- A short title for the result, for example the error code generated by an evaluation tool.
dc:description- A human-readable text or markup (for example HTML included as an XML Literal), and should therefore include an identification for the natural language.
A Test Result may also include the following properties:
earl:confidence- The Confidence Level is an application-specific value to describe the accuracy of the result. This is especially useful for results based on heuristics.
earl:instance- Each Instance Location can contain several types of pointers to locate the occurence of the result within the Test Subject. A Test Result may contain several instances of this class to describe any number of occurences
Example 10: A test result with a validity of fail and a description of the problem in English, and encoded in XHTML format.
<earl:result rdf:ID="result">
<earl:validity rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#fail"/>
<dc:title xml:lang="en">Invalid Markup (code #353)</dc:title>
<dc:description rdf:parseType="Literal" xml:lang="en">
<div xmlns="http://www.w3.org/1999/xhtml">
<p>The <code>table</code> element is not allowed to appear
inside a <code>p</code> element</p>
</div>
</dc:description>
<earl:instance rdf:resource="#instance"/>
</earl:result>
Outcome of a test. The Validity Level must be one of the following pre-defined values (or subclasses of them):
earl:pass- An assertor claims a test passed successfully.
earl:fail- The Test Subject did not meet the criteria defined by the Test Statement.
earl:cannotTell- An Assertor can not tell for sure what the outcome of the test is. Usually this happens when an automated test requires human judgement to make a definite decision.
earl:notApplicable- The Test Statement is not applicable to the given Test Subject.
earl:notTested- Test has not been carried out. This is useful for reporting as well as for other uses of progress monitoring.
Confidence in the result by an Assertor. This may be used where a tool wants to assert that it has different levels of confidence about two possible results (for example low confidence that a test has been passed, but also high confidence that it is not applicable). The values of the confidence level should be defined either as RDF values, or using a datatype, in order to allow others to work interoperably with them.
Example 11: The result from example 10 has a confidence level of 87 (the interpretation of this value is application specific)
<earl:result rdf:about="#result">
<earl:confidence rdf:datatype="http://www.w3.org/2001/XMLSchema#int">87</earl:confidence>
</earl:result>
An Instance Location is a an area within the Test Subject that triggered or primarily influenced the Test Result. These areas could be described using a variety of different types of pointers that re grouped by Pointer Collection classes. Each instance of such a collection must describe exactly one occurence of an area.
Each earl:instance property must reference a earl:PointerCollection, each of which must contain one or more of the following properties:
earl:xPointer- An XPointer string expression [Editors' Note: reference to the XPointer specification]
earl:htmlPointer- An HTML Pointer string expression [Editors' Note: reference to the HTML Pointer specification]
earl:xPath- References an
earl:XPathPointer class which must include an XPath string expression using the earl:expression property, and may include a namespace definition using the earl:ns and earl:Namespace property and class respectively.
earl:lineCharLen- References a
earl:LineCharLenPointer class which must include earl:line and earl:char integer values, and may also include a earl:len integer value. The integer values for earl:line, earl:char, and earl:len must start with the value "0" to denote the first position.
earl:charSnippet- A copy of the relevant part of the Test Subject as a character string. The referenced
earl:CharSnippetPointer class must include a earl:charContent property and may also include a earl:charOffset integer value. The integer value for earl:charOffset must start with the value "0" to denote the first position.
earl:byteSnippet- A copy of the relevant part of the Test Subject encoded as a Base64 string. The referenced
earl:ByteSnippetPointer class must include a earl:byteContent property and may also include a earl:byteOffset integer value. The integer value for earl:byteOffset must start with the value "0" to denote the first position.
Note: all the above pointer types (except for xPointer and htmlPointer which are string expressions expressed as simple properties) are subclasses of a generic earl:Pointer class. If new pointers are defined to extend this core selection of pointers, they should also be subclasses of the generic class and be referenceable from the earl:PointerCollection class by defining appropriate properties.
[Editor's note: the working group is interested in getting feedback on the selected variety of pointers and if they have missed other crucial types.]
Example 12: The result from example 10 references a Pointer Collection that contains three different types of pointers, each of which points to the same Location Instance within the Test Subject.
<earl:PointerCollection rdf:about="#instance">
<earl:xPointer rdf:datatype="http://www.w3.org/2001/XMLSchema#string">@@@TBD</earl:xPointer>
<earl:htmlPointer rdf:datatype="http://www.w3.org/2001/XMLSchema#string">@@@TBD</earl:htmlPointer>
<earl:xPath>
<earl:expression rdf:datatype="http://www.w3.org/2001/XMLSchema#string">@@@TBD</earl:expression>
</earl:xPath>
</earl:PointerCollection>
A Software Tool is any software such as an authoring tool, browser, or evaluation tool. Software should have a title using the Dublin Core property dc:title; and may have descriptions, version information, and a home page using the Dublin Core terms dc:description, dct:hasVersion, as well as the FOAF term foaf:homepage.
While the software class is often used to describe evaluation tool assertors, a software could also be a Test Subject (for example to test compliance of an authoring tool to the Authoring Tool Accessibility Guidelines). In this case, it inherits the optional properties dc:date, dct:isPartOf and dct:hasPart from the Test Subject class.
Example 13: The software which was an Assertor in example 5 is now a Test Subject.
<earl:Software rdf:about="#tool">
<dc:date rdf:datatype="http://www.w3.org/2001/XMLSchema#gDate">2005-06-25</dc:date>
<dct:isPartOf rdf:resource="http://example.org/tools/"/>
<dct:hasPart rdf:resource="http://example.org/tools/cool/#module-1"/>
</earl:Software>
Information on the World Wide Web. This should include enough information to identify the content actually tested, taking account of content type and language negotiation and similar factors that can change the content actually served. This class is intended to be used as a test subject but can be reused for other purposes (outside EARL) as well. The Web content class has the following properties:
dc:format- Format of the Web resource. For example "text/HTML", "image/PNG" or other mime types that are returned from the Web server.
- Term for URI
- [Editor's note: the Working Group will be defining a term to identify the Web location (a.k.a. URL).]
earl:httpRequest- HTTP request sent by the client to the server in order to initiate a response
earl:httpResponse- HTTP response (except the actual payload of the date) sent by the server to the client
Note: an instance of the Web Content class may include several request/response sequences to document the content and language negotiation that took place before the content was finally sent.
[Editor's note: the request/response properties of this class are intended to make use of HTTP vocabulary in RDF that will be published in a separate document.]
[Editor's note: Is this section suitable for this document or should it be rather moved to the Guide document?]
Because EARL is written as an RDF vocabulary, it is extensible; that is, it is simple to add new terms or otherwise modify (for example by subclassing) them to fit your own specific application demands more closely. EARL was designed to be generic for usages in quality assurance but can be extended to fit particular domains better. EARL is a core set of structures and terms. In addition, the working group expects to work on at least a couple of areas and perhaps extend the specification (especially with respect to Web accessibility evaluation) before publishing it as a Recommendation.
[Editor's note: need to make a schema available at the namespace URI, which includes OWL information on deprecated terms]
<?xml version="1.0" encoding='UTF-8'?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:earl="http://www.w3.org/WAI/ER/EARL/nmg-strawman#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:xmls="http://www.w3.org/2001/XMLSchema#">
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion">
<rdfs:label xml:lang="en">An assertion</rdfs:label>
<rdfs:comment xml:lang="en">Parent node that contains all parts of an assertion</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#assertedBy"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<!--// @@@ EDITORS' NOTE: decision regarding maxCardinality restriction pending //-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#subject"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<!--// @@@ EDITORS' NOTE: decision regarding maxCardinality restriction pending //-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#test"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<!--// @@@ EDITORS' NOTE: decision regarding maxCardinality restriction pending //-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#result"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<!--// @@@ EDITORS' NOTE: decision regarding maxCardinality restriction pending //-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#assertedBy">
<rdfs:label xml:lang="en">Is Asserted By</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertor"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#subject">
<rdfs:label xml:lang="en">Has Test Subject</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestSubject"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#test">
<rdfs:label xml:lang="en">Has Test Criteria</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Testable"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#result">
<rdfs:label xml:lang="en">Has Test Result</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestResult"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#mode">
<rdfs:label xml:lang="en">Has Test Mode</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestMode"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertor">
<rdfs:label xml:lang="en">Assertor</rdfs:label>
<rdfs:comment xml:lang="en">Persons or evaluation tools that claim assertions</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#SingleAssertor"/>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CompoundAssertor"/>
</owl:oneOf>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#SingleAssertor">
<rdfs:label xml:lang="en">Single Assertor</rdfs:label>
<rdfs:comment xml:lang="en">One person or evaluation tool that claims assertions</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:type="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Software"/>
<owl:Thing rdf:type="http://xmlns.com/foaf/0.1/Person"/>
<owl:Thing rdf:type="http://xmlns.com/foaf/0.1/Agent"/>
</owl:oneOf>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CompoundAssertor">
<rdfs:label xml:lang="en">Compound Assertor</rdfs:label>
<rdfs:comment xml:lang="en">Group of persons or evaluation tools that claim assertions</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#mainAssertor"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#mainAssertor">
<rdfs:label xml:lang="en">Has Main Assertor</rdfs:label>
<rdfs:comment xml:lang="en">Assertor mainly responsible for determining assertion result</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CompoundAssertor"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertor"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#helpAssertor">
<rdfs:label xml:lang="en">Has Help Assertor</rdfs:label>
<rdfs:comment xml:lang="en">Assertor assisting to determine assertion result</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CompoundAssertor"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertor"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestSubject">
<rdfs:label xml:lang="en">Test Subject</rdfs:label>
<rdfs:comment xml:lang="en">Subject of the assertion</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Testable">
<rdfs:label xml:lang="en">Test Criteria</rdfs:label>
<rdfs:comment xml:lang="en">A testable statement against which subjects are tested</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestRequirement">
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Testable"/>
<rdfs:label xml:lang="en">Test Requirement</rdfs:label>
<rdfs:comment xml:lang="en">A requirement against which subjects are tested</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestCase">
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Testable"/>
<rdfs:label xml:lang="en">Test Case</rdfs:label>
<rdfs:comment xml:lang="en">A test case against which subjects are tested</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestMode">
<rdfs:label xml:lang="en">Test Mode</rdfs:label>
<rdfs:comment xml:lang="en">Mode in which tests were conducted</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#manual">
<rdfs:label xml:lang="en">Manual</rdfs:label>
<rdfs:comment xml:lang="en">Test was performed by a human only</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#automatic">
<rdfs:label xml:lang="en">Automatic</rdfs:label>
<rdfs:comment xml:lang="en">Test was performed by a tool only</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#semiauto">
<rdfs:label xml:lang="en">Semi-Automatic</rdfs:label>
<rdfs:comment xml:lang="en">Test was performed primarily by a tool, and human assistance</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#mixed">
<rdfs:label xml:lang="en">Mixed</rdfs:label>
<rdfs:comment xml:lang="en">Test was performed by a combination of persons and tools</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#heuristic">
<rdfs:label xml:lang="en">Heuristic</rdfs:label>
<rdfs:comment xml:lang="en">Result was derived from other results</rdfs:comment>
</owl:Thing>
</owl:oneOf>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestResult">
<rdfs:label xml:lang="en">Test Result</rdfs:label>
<rdfs:comment xml:lang="en">Result from conducting test cases on subjects</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#validity"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#validity">
<rdfs:label xml:lang="en">Has Validity Level</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestResult"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ValidityLevel"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#confidence">
<rdfs:label xml:lang="en">Has Confidence Level</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestResult"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ConfidenceLevel"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#instance">
<rdfs:label xml:lang="en">Has Location Instance</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestResult"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ValidityLevel">
<rdfs:label xml:lang="en">Validity Level</rdfs:label>
<rdfs:comment xml:lang="en">Nominal value of the result</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#pass">
<rdfs:label xml:lang="en">Pass</rdfs:label>
<rdfs:comment xml:lang="en">Test passed</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#fail">
<rdfs:label xml:lang="en">Fail</rdfs:label>
<rdfs:comment xml:lang="en">Test failed</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#cannotTell">
<rdfs:label xml:lang="en">Can Not Tell</rdfs:label>
<rdfs:comment xml:lang="en">Outcome of the test is uncertain</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#notApplicable">
<rdfs:label xml:lang="en">Not Applicable</rdfs:label>
<rdfs:comment xml:lang="en">Test is not applicable to the subject</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#notTested">
<rdfs:label xml:lang="en">Not Tested</rdfs:label>
<rdfs:comment xml:lang="en">Test has not been carried out</rdfs:comment>
</owl:Thing>
</owl:oneOf>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ConfidenceLevel">
<rdfs:label xml:lang="en">Confidence Level</rdfs:label>
<rdfs:comment xml:lang="en">Level of confidence in the given result</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer">
<rdfs:label xml:lang="en">Pointer</rdfs:label>
<rdfs:comment xml:lang="en">A pointer to a location within the Test Subject</rdfs:comment>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection">
<rdfs:label xml:lang="en">Pointer Collection</rdfs:label>
<rdfs:comment xml:lang="en">A collection of pointers, all pointing to the same thing</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<!--// @@@ EDITORS' NOTE: decision regarding Min/Max cardinality restriction on properties pending //-->
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#expression">
<rdfs:label xml:lang="en">Has Pointer Expression</rdfs:label>
<rdfs:comment xml:lang="en">String based pointer to be used in subclasses of Pointer</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#xPointer">
<rdfs:label xml:lang="en">Has XPointer Expression</rdfs:label>
<rdfs:comment xml:lang="en">XPointer expression pointing into the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#htmlPointer">
<rdfs:label xml:lang="en">Has HTML Pointer Expression</rdfs:label>
<rdfs:comment xml:lang="en">HTML Pointer expression pointing into the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#lineCharLen">
<rdfs:label xml:lang="en">Has LineCharLen Values</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#LineCharLenPointer"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#xPath">
<rdfs:label xml:lang="en">Has XPath Expression</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#XPathPointer"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charSnippet">
<rdfs:label xml:lang="en">Has Char Snippet</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CharSnippetPointer"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteSnippet">
<rdfs:label xml:lang="en">Has Byte Snippet</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#PointerCollection"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ByteSnippetPointer"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#LineCharLenPointer">
<rdfs:label xml:lang="en">LineCharLen Pointer</rdfs:label>
<rdfs:comment xml:lang="en">Line/character and optionally the length of a region within the Test Subject</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#line"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#char"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#len"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#line">
<rdfs:label xml:lang="en">Has Line Number</rdfs:label>
<rdfs:comment xml:lang="en">Line number within the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#LineCharLength"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#char">
<rdfs:label xml:lang="en">Has Char Number</rdfs:label>
<rdfs:comment xml:lang="en">Char or column number within the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#LineCharLength"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#len">
<rdfs:label xml:lang="en">Has Length Value</rdfs:label>
<rdfs:comment xml:lang="en">Length of a region within the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#LineCharLength"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#XPathPointer">
<rdfs:label xml:lang="en">XPath Pointer</rdfs:label>
<rdfs:comment xml:lang="en">XPath expression (including namespace) pointing into the Test Subject</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#expression"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ns"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
//-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ns">
<rdfs:label xml:lang="en">Has Namespace</rdfs:label>
<rdfs:comment xml:lang="en">A namespace used in a particular XPath expression</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#XPath"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Namespace"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Namespace">
<rdfs:label xml:lang="en">Namespace</rdfs:label>
<rdfs:comment xml:lang="en">Prefix and namespace URI for an XPath expression</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#prefix"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#nsURI"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#prefix">
<rdfs:label xml:lang="en">Has Namespace Prefix</rdfs:label>
<rdfs:comment xml:lang="en">A namespace prefix</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Namespace"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#nsURI">
<rdfs:label xml:lang="en">Has Namespace URI</rdfs:label>
<rdfs:comment xml:lang="en">A namespace URI</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Namespace"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#CharSnippetPointer">
<rdfs:label xml:lang="en">Char Snippet Pointer</rdfs:label>
<rdfs:comment xml:lang="en">Character based part of the Test Subject</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charContent"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charOffset"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charContent">
<rdfs:label xml:lang="en">Has Char Content</rdfs:label>
<rdfs:comment xml:lang="en">Character content that is part of the Test Subject</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charSnippet"/>
<!--// @@@ EDITORS' NOTE: range here could be a string or a parsed XML document... //-->
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charOffset">
<rdfs:label xml:lang="en">Has Char Offset</rdfs:label>
<rdfs:comment xml:lang="en">Number of characters into the Char Content</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#charSnippet"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#ByteSnippetPointer">
<rdfs:label xml:lang="en">Byte Snippet Pointer</rdfs:label>
<rdfs:comment xml:lang="en">Byte based part of the Test Subject (encoded in Base64)</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Pointer"/>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteContent"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteOffset"/>
<!--// @@@ EDITORS' NOTE: Min/Max cardinality restrictions have been commented out until a decision is made
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">0</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
//-->
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteContent">
<rdfs:label xml:lang="en">Has Byte Content</rdfs:label>
<rdfs:comment xml:lang="en">Byte content that is part of the Test Subject (encoded in Base64)</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteSnippet"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteOffset">
<rdfs:label xml:lang="en">Has Byte Offset</rdfs:label>
<rdfs:comment xml:lang="en">Number of bytes into the Byte Content</rdfs:comment>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#byteSnippet"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</rdf:Property>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Software">
<rdfs:label xml:lang="en">Software Tool</rdfs:label>
<rdfs:comment xml:lang="en">A tool that can perform tests or be the subject of testing</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.org/dc/elements/1.1/title"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdfs:Class rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#WebContent">
<rdfs:label xml:lang="en">Web Content</rdfs:label>
<rdfs:comment xml:lang="en">Subjects that are available on the Web</rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#httpRequest">
<rdfs:label xml:lang="en">With HTTP Request</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#WebContent"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#httpResponse">
<rdfs:label xml:lang="en">With HTTP Response</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#WebContent"/>
</rdf:Property>
<!-- Deprecated Terms -->
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#evidence">
<rdfs:label xml:lang="en">evidence</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#methodology">
<rdfs:label xml:lang="en">methodology</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
</rdf:Property>
<rdf:Property rdf:about="http://www.w3.org/WAI/ER/EARL/nmg-strawman#requirement">
<rdfs:label xml:lang="en">Has Requirement</rdfs:label>
<rdfs:domain rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#Assertion"/>
<rdfs:range rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#TestRequirement"/>
</rdf:Property>
<!-- Replaced Terms -->
<rdf:Description rdf:about="#singleAssertor">
<owl:sameAs rdf:resource="#SingleAssertor" />
</rdf:Description>
<rdf:Description rdf:about="#compoundAssertor">
<owl:sameAs rdf:resource="#CompoundAssertor" />
</rdf:Description>
</rdf:RDF>
The following terms are defined by this specification:
This section records current changes and future plans for changes as the the working draft matures to Recommendation level.
This section describes differences between this draft and the EARL 1.0 Schema draft of 9 September 2005.
- The former Appendix B: EARL 1.0 Schema in N3 has been removed.
- Redundant constraints on optional properties have been removed from the schema.
- Added a subsection on the expected audience of this document.
- Made namespace and use of RFC 2119 terms normative.
earl:requirement and earl:TestRequirement have replaced earl:testCase and earl:Testcase.- Added
earl:mixed and earl:semiauto values for the earl:TestMode class.
- Made the
earl:mode property of earl:Assertion optional.
- Made the
dc:date property of earl:TestSubject optional.
- Made the
dc:title property of earl:Software recommended.
- Removed
high, medium and low values of earl:confidence.
- Added
foaf:Agent to the list of allowable Assertor types.
- Replaced
dc:location with dc:identifier in earl:TestRequirement and with foaf:homepage in earl:Software.
- Added
earl:Testable as a super class of earl:TestRequirement and earl:TestCase
- Added
earl:instance as a place holder for the upcoming earl:InstanceLocation class.
- Added table column for recommended properties in the terms section.
- Several typographical edits including naming of the property and class labels, checking and optimizing the examples, as well as rewording of several sections.
Difference to the first published Working Draft
This section describes the changes made since the EARL 1.0 draft of 12 December 2002.
- Document split into a specification (this document) and a companion document. Most content stripped out of specification document, and new issues under discussion noted.
- Schema presented without the use of XML entities.
- Typographical errors in schema fixed, so it validates.
- Re-ordering of the Schema and document. Instead of being organised as a list of classes, then properties, then instance classes, the document and the schema are both organised around the key classes as the framework for defining their use.
- Redundant (rdf:Resource) and incorrect (rdfs:Resource) sub-class declarations removed.
- Schema labels given xml:lang attributes as appropriate.
- Labels converted to grammatical english (from camelCaseAlmostWords).
- Schema encoded in default UTF-8.
- Removed
earl:Platform class.
- Replaced
earl:message, earl:format, earl:Person, earl:name, earl:email, and earl:contactInfo with equivalent terms from the Dublin Core and FOAF vocabularies.
- Added
earl:Software class to replace the deprecated earl:Tool and earl:UserAgent classes. It can be used to decribe a assertor tools or test subjects.
- Added
earl:SingleAssertor, earl:CompoundAssertor, earl:mainAssertor, and earl:helpAssertor to better describe different kinds of assertors.
- Added
earl:WebContent to replace the deprecated earl:ReprOf class.
- Added
earl:httpRequest and earl:httpResponse properties in earl:WebContent class to describe the request/response sequences that were exchanged.
New terms have been introduced to the vocabulary, sometimes as replacements for deprecated terms that existed in earlier drafts, sometimes to introduce new funtionality
Terms added since the previous published Working Draft
earl:mixed and earl:semiauto- These values extend the range of allowed values of the test
earl:TestMode.
earl:test and earl:Testable- Super class of
earl:TestCase and earl:TestRequirement.
earl:instance- This property is part of the
earl:InstanceLocation class which will be added in later drafts.
Terms added since the first published Working Draft
earl:Software- This class replaces the deprecated
earl:Tool. It can be used to decribe a assertor tools or test subjects.
earl:SingleAssertor, earl:CompoundAssertor- These classes are derivatives of an Assertor to help describe complex groups of person and/or tool evaluators.
earl:mainAssertor, earl:helpAssertor- These properties of a compound assertor can be used to describe the specific roles of evaluators within a group.
earl:httpRequest, earl:httpResponse- These are placeholder properties for describing
WebContent (or a Delivery Unit on the Web).
A number of terms that existed in earlier drafts have been deprecated, either in favour of terms from existing widely-used vocabularies, or because their use is somehow problematic. While this deprecation is provisional, no RDF has been published formally noting them as deprecated (for example through OWL). A quick guide to terms that have been provisionally deprecated:
earl:evidence- This was intended to provide a method for describing the justification used to infer a claim based on other claims. It has been deprecated for now.
earl:methodology- This was intended to provide a link for what method was used for a particular test. It has been deprecated as unnecessary.
earl:requirement- This term was deprecated in favor of a more generic approach with a Testable Statement super class
high, medium and earl:low- These values for the
earl:confidence property were deprecated in favour of authors defining their usage in a way that encourages interoperability.
earl:reprOf- This term was deprecated in favour of a more comprehensive approach to describing Web content.
earl:testCase- This property was replaced by the
earl:requirement property.
earl:Testcase- This class was replaced by the
earl:TestRequirement class.
earl:UserAgent, earl:Tool- These terms were deprecated in favour of the more generic
earl:Software class.
earl:platform- This term was deprecated as it did not seem to be widely accepted and implemented.
earl:message, earl:format- These terms were deprecated in favour of the Dublin Core terms
dc:description and dc:format.
earl:Person, earl:name, earl:email, earl:contactInfo- These terms were deprecated in favour of equivalent terms from the FOAF vocabulary.
The working group is considering several open issues which would lead to extending the current vocabulary before it reaches recommendation. As well as issues noted in the draft, the following issues are under active consideration:
A mechanism to provide further evidence used to make a claim. The working group has included the evidence property but has not yet determined the most useful model for the list of statements used in evidence of an inferred result.
Within Web content, for the use case of testing accessibility, it is very valuable to point to the location(s) that cause the test to pass or fail. This is also true of software interfaces and various other kinds of subject. The working group has agreed in principle to include a mechanism for recording this information in an EARL report, but has not yet developed or found the necessary terms.
There are currently placeholder properties httpRequest and httpResponse for HTTP transaction information. The group expects to develop these further, either themselves or with an existing vocabulary. An extensive amount of work has been done on such vocabularies, and this material couldd be included as soon as the next draft of this specification.
This is under review by the working group. The current draft requires that developers who use this property provide some means of identifying the way its values are determined in order to allow interoperable use of those values.
- [DC]
- The Dublin Core Metadata Element Set - DC Recommendation, 20 December 2004.
http://www.dublincore.org/documents/dces/
- [DCT]
- The Dublin Core Metadata Terms - DC Recommendation, 13 June 2005.
http://www.dublincore.org/documents/dcmi-terms/
- [FOAF]
- FOAF Vocabulary Specification
- Working Draft, 3 June 2005.
http://xmlns.com/foaf/0.1/
- [Guide]
- Evaluation and Report Language (EARL) 1.0 Guide - Editors' Draft 14 December 2005. C. Velasco, J. Koch, S. Abou-Zahra eds.
http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Guide-20051214
- [OWL]
- OWL Web Ontology Language - W3C Recommendation, 10 February 2004.
http://www.w3.org/TR/owl-features/
- [RDF]
- RDF/XML Syntax Specification (Revised) - W3C Recommendation, 10 February 2004. D. Beckett ed.
http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/
- [RDF-PRIMER]
- RDF Primer - W3C Recommendation, 10 February 2004. F. Manola, E.Miller eds.
http://www.w3.org/TR/rdf-primer/
- [RDFS]
- RDF Vocabulary Description Language 1.0: RDF Schema - W3C Recommendation, 10 February 2004. D. Brickley, R.V. Guha eds.
http://www.w3.org/TR/rdf-schema/
- [RDF-XML-DIFFS]
- Why RDF model is different from the XML model - Paper, September 1998. T. Berners-Lee.
http://www.w3.org/DesignIssues/RDF-XML
- [RFC2119]
- Key words for use in RFCs to Indicate Requirement Levels - IETF RFC, March 1997.
http://www.ietf.org/rfc/rfc2119.txt
- [WCAG10]
- Web Content Accessibility Guidelines 1.0 - W3C Recommendation, 5 May 1999. W. Chisholm, I. Jacobs, G. Vanderheiden eds.
http://www.w3.org/TR/WCAG10/
EARL is the result of the work of many people over the past. The editors would particularly like to thank Wendy Chisholm, Sean B Palmer, and Daniel Dardailler, whose contributions have included editing the first versions of the EARL specifications, and the late Leonard Kasday who set the work in motion to develop EARL. The editors apologise for any names left out of this list, and will endeavour to rectify any errors noted in comments.
Shadi Abou-Zahra, Chrisoula Alexandraki, Myriam Arrue, Gabriele Bartolini, Giorgio Brajnik, Dan Brickley, Karl Dubost, Nick Gibbins, Al Gilman, Dominique Hazaël-Massieux, Nadia Heninger, Sandor Herramhof, Ian Hickson, Björn Höhrmann, Carlos Iglesias, Nick Kew, Johannes Koch, Jim Ley, William Loughborough, John Lutts, Charles McCathieNevile, Libby Miller, Tom Martin, Yehya Mohamed, Dave Pawson, Eric Prud'hommeaux, Pierre Queinnec, Chris Ridpath, Romain Roure, Christophe Strobbe, Aaron Swartz, Olivier Thoreaux, Carlos Velasco and Rob Yonaitis.