风清扬

测试与报告语言

1楼 风清扬


Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/1/16

[contents]

Evaluation and Report Language (EARL) 1.0 Schema

W3C Working Draft 10 May 2011

This version:

http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/

Latest version:

http://www.w3.org/TR/EARL10-Schema/

Previous version:

http://www.w3.org/TR/2009/WD-EARL10-Schema-20091029/

Editors:

Shadi Abou-Zahra, W3C/WAI

Previous Editors:

Michael Squillace (until October 2009 while at IBMCorporation)

The terms defined by this document are also provided in RDF Schema format.

Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use

rules apply.

Abstract

This document describes the formal schema of theEvaluation and Report Language (EARL) 1.0.

EARL is a vocabulary, the terms of which are definedacross a set of specifications and

technical notes, and that is used to describe testresults. The primary motivation for

developing this vocabulary is to facilitate the exchangeof test results between Web

accessibility evaluation tools in a vendor-neutral andplatform-independent format. It also

provides reusable terms for generic quality assurance andvalidation purposes.

Status of this document

This section describes the status of this documentat the time of its publication. Other

documents may supersede this document. A listof current W3C publications and the latest

revision of this technical report can befound in the W3C technical reports index at

http://www.w3.org/TR/.

This 10 May 2011 Last Call Working Draft of theEvaluation and Report Language (EARL) 1.0

Schema is an update of the previous EARL 1.0 LastCall Working Draft of 29 October 2009. It

meets the requirements specified in the Requirementsfor the Evaluation and Report Language

(EARL) 1.0, and incorporates all comments received.This document is intended to be published

and maintained as a W3C Recommendation after review andrefinement.

The Evaluation and Repair Tools Working Group (ERT WG)believes it has addressed all issues

brought forth through previous Working Draft iterations.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 evaluationand validation of websites, and

by developers and researchers who have interest inSemantic Web technologies for content

description, annotation, and adaptation. In particular,the Working Group is looking for

feedback on the following items which are alsohighlighted within the document:

Use cases for foaf:Document as a furtherrefinement for earl:TestSubject (see Editor Note

1)

Use of DOAP terms and definition of earl:Softwareas a subclassof doap:Project (see

comments onthis Evaluation and Report Language (EARL) 1.0 Schema document by 10

June 2011 to public-earl10-comments@w3.org (publicly visible mailing list archive).

Publication asa Working Draft does not imply endorsement by the W3C Membership. This is a

draft documentand may be updated, replaced or obsoleted by other documents at any time. It is

inappropriateto cite this document as other than work in progress.

This documenthas been produced by the Evaluation and Repair Tools Working Group (ERT WG) as

part of the Web Accessibility Initiative (WAI)Technical Activity.

This documentwas produced by a group operating under the 5 February 2004 W3C Patent Policy.

W3C maintainsa public list of any patentdisclosures made in connectionwith the deliverables

of the group;that page also includes instructions for disclosing a patent. An individual who

has actualknowledge of a patent which the individual believes contains Essential Claim(s) must

disclose theinformation in accordance with section 6 of the W3C Patent Policy.

Table ofContents

1. Introduction

1.1.Audience of this Document

1.2.Document Conventions

2. Classes

2.1.Assertion Class

2.2.Assertor Class

2.3.TestSubject Class

2.4.TestCriterion Class

2.5.TestResult Class

2.6.TestMode Class

2.7.OutcomeValue Class

2.8.Software Class

3. Properties

3.1.assertedBy Property

3.2.subject Property

3.3. testProperty

3.4.result Property

3.5. modeProperty

3.6.mainAssertor Property

3.7.outcome Property

3.8.pointer Property

3.9. infoProperty

Appendices

A. Terms

B. References

C. Contributors

D. Document Changes

1.Introduction

The Evaluationand Report Language (EARL) defines a vocabulary for expressing test results. It

enables anyperson, software application, or organization to assert test results for anytest

subject testedagainst any set of criteria. The test subject might be a website, an authoring

tool, a useragent, or some other entity. The set of criteria may be accessibilityguidelines,

formalgrammars, or other types of quality assurance requirements. Thus, EARL isflexible with

regard to thecontexts in which it can be applied.

This documentprovides the core schema of EARL. Other parts of the EARL suite of specifications

include:

HTTPVocabulary in RDF 1.0

RepresentingContent in RDF 1.0

PointerMethods in RDF 1.0

The Developer Guide for Evaluation andReport Language (EARL) 1.0 explainshow to implement and

use EARL,including conformance requirements for software tools. An Evaluation and Report

Language(EARL) Overview is alsoavailable.

EARL is not acomprehensive vocabulary for describing test procedures, test criteria, or test

requirementsbut, rather, for describing the outcomes from such testing. EARL can be

supplementedby test description vocabularies or other vocabularies for different aspects of

the testingcycle.

1.1.Audience of this Document

The assumedaudience of this specification is developers of software tools and processeswho

want toexpress test results in a machine readable format that is semantically rich.More

introductorybackground about EARL as well as specific guidance for quality assurance tool

developers, inparticular for web accessibility evaluation tool developers, is provided in the

Evaluationand Report Language (EARL) 1.0 Guide.

This documentassumes that the reader is familiar with the Resource Description Framework(RDF)

and can readits XML serialization. Readers who wish to understand more about RDF shouldread a

generalintroduction or the RDF Primer [RDF-PRIMER].

1.2.Document conventions

The RDFrepresentation of the vocabulary defined by this document uses the namespace

http://www.w3.org/ns/earl#. The prefix earl is used throughout this document to denote this

namespace.Other prefixes used throughout this document include:

cnt - Representing Content in RDF namespace http://www.w3.org/2011/content# (defined by

[Content])

dct - Dublin Core (DC) namespace http://purl.org/dc/terms/ (defined by [DC])

doap - Description of a Project (DOAP) namespace http://usefulinc.com/ns/doap# (defined by

[DOAP])

foaf - Friend of a Friend (FOAF) namespace http://xmlns.com/foaf/0.1/# (defined by [FOAF])

http - HTTP Vocabulary in RDF namespace http://www.w3.org/2011/http# (defined by [HTTP])

ptr - Pointer Methods in RDF namespace http://www.w3.org/2009/pointers# (defined by

[Pointers])

rdf - RDF namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#(defined by [RDF])

rdfs - RDF Schema namespace http://www.w3.org/2000/01/rdf-schema# (defined by [RDFS])

xsd - XMLS namespace http://www.w3.org/2001/XMLSchema# (defined by [XMLS])

2. Classes

This sectiondescribes the classes defined by this document. Every test result in EARL is

expressed asan assertion. An EARL Assertion contains the following information:

Assertor

This caninclude information about who or what ran the test. For example humanevaluators,

automatedaccessibility checkers, or combinations of these.

TestSubject

This caninclude web content (such as web pages, videos, applets, etc.), software (suchas

authoringtools, user agents, etc.), or other things being tested.

TestCriterion

What are we evaluatingthe test subject against? This could be a specification, a set of

guidelines, atest from a test suite, or some other testable statement.

TestResult

What was theoutcome of the test? A test result could also include contextual information

such as errormessages or relevant locations within the test subject.

EARL providesflexibility to describe different types of assertions, such as those carriedout

by automatedtesting tools or by human evaluators, or those made about generic testing

requirementsor specific test cases.

Examples

Example 1: A personcarries out a manual evaluation of a web page to an

Assertor

Bob B.Bobbington

Test Subject

A web pagelocated at http://www.example.org/page.html

Test Criterion

SuccessCriterion 1.1.1 of the Web Content Accessibility Guidelines (WCAG) 2.0

Test Result

Passed

Example 2: Asoftware application carries out automated validation of a web page to

a technicalspecification.

Assertor

The W3C MarkupValidator located at http://validator.w3.org/

Test Subject

The XHTMLreturned from a GET request to the URI http://www.example.org/page.html

at 2004-04-14T14:00:04+1000

Test Criterion

The validityof the XHTML code

Test Result

Failed, the <li> element on line 53, char 7 was not closed.

2.1.Assertion Class

Assertion- a statement thatembodies the results of a test.

RelatedProperties

Domain of:

earl:assertedBy

earl:subject

earl:test

earl:result

earl:mode

Range of: none

Examples

Example 3:Instance of an assertion expressed as an RDF/XML fragment.

<earl:Assertionrdf:about="#assertion">

<earl:assertedByrdf:resource="#assertor"/>

<earl:subjectrdf:resource="http://www.example.org/"/>

<earl:testrdf:resource="http://www.w3.org/TR/WCAG20-TECHS/H36"/>

<earl:resultrdf:resource="#result"/>

</earl:Assertion>

2.2. AssertorClass

Assertor- an entity such asa person, a software tool, an organization, or any other grouping

that carriesout a test collectively.

RelatedClasses

Rather thanspecifying only an earl:Assertortype, it is recommended that one of thefollowing

types beemployed in addition:

earl:Software

Software - theassertor is a piece of software.

foaf:Agent

Agent - theassertor is an agent, as defined by [FOAF].

Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/5/16

foaf:Person

Person -the assertor is a person, as defined by [FOAF].

foaf:Organization

Organization - the assertor is an organization, asdefined by [FOAF].

foaf:Group

Group - the assertor is a group of agents, as defined by[FOAF].

Related Properties

Domain of:

earl:mainAssertor

Range of:

earl:assertedBy

earl:mainAssertor

It is recommended to provide additional information aboutthe Assertor by using the following

properties from external vocabularies:

dct:title

Human readable title for the assertor.

dct:description

Human readable description of the assertor.

foaf:name

Name of the assertor. This could be supplemented withfurther refinements such as

foaf:firstName or foaf:surname if the assertor isa person.

foaf:nick

Nick name of the assertor

foaf:mbox

E-mail address of the responsible assertor, which ispreferably provided in an encrypted

format using the foaf:mbox_sha1sumproperty.

foaf:homepage

Homepage of the assertor.

foaf:member

Member of the assertor, such as an individual in a groupof testers or a tool used by an

agent.

Examples

Example 4: An Assertor that is a person called BobB. Bobbington.

<foaf:Personrdf:about="http://www.example.org/people/#bob">

<foaf:name>Bob B. Bobbington</foaf:name>

<foaf:mboxrdf:resource="mailto:bob@example.org"/>

<foaf:mbox_sha1sum>1a9daad476f0158b81bc66b7b27b438b4b4c19c0</foaf:mbox_sha1sum>

</foaf:Person>

Example 5: An Assertor that is a piece of softwarecalled Cool Tool.

<earl:Softwarerdf:about="http://www.example.org/tools/#cooltool">

<doap:name xml:lang="en">Cool Tool</doap:name>

<doap:description xml:lang="en">Myfavorite tool!</doap:description>

<doap:created>2011-04-27</doap:created>

<doap:homepagerdf:resource="http://example.org/tools/cool/"/>

<doap:release>

<doap:revision>1.0.3</doap:revision>

</doap:release>

</earl:Software>

Example 6: An Assertor that is the person from example 4 using the softwaretool

from example 5.

<foaf:Group rdf:about="#assertor">

<dct:title xml:lang="en">Bob using CoolTool</dct:title>

<dct:description xml:lang="en">Bob doing semi-automatedtesting</dct:description>

<earl:mainAssertorrdf:resource="http://www.example.org/people/#bob"/>

<foaf:memberrdf:resource="http://www.example.org/tool/#cooltool"/>

Note:According to this example, "Cool Tool" is a resource of type foaf:Agent.

According to example 5, it is also a resource of type earl:Software. These are not

contradictorystatements and are valid RDF representations.

2.3.TestSubject Class

TestSubject - the class ofthings that have been tested against some test criterion.

RelatedClasses

Rather thanspecifying only an earl:TestSubjecttype, it is recommended that one of thefollowing

types beemployed in addition:

earl:Software

Software - thetest subject is a piece of software being tested.

cnt:Content

Content - thetest subject is a representation of the content as defined by [Content].

http:Response

HTTP Response- the test subject is the response from an HTTP server as defined by [HTTP].

foaf:Document

Document - thetest subject is a document, such as electronic file, as defined by [FOAF].

[Editor's note1: ERT WG is considering to remove foaf:Document unlesscompelling use-cases

can bepresented; feedback on this consideration is welcome.]

RelatedProperties

Domain of:none

Range of:

earl:subject

It isrecommended to provide additional information about the Test Subject byusing the

followingproperties from external vocabularies:

dct:title

Human readabletitle for the subject.

dct:description

Human readabledescriptions of the subject.

dct:date

Date on whichthe subject was created or identified.

dct:hasPart

Reference toanother subject that are part of this subject.

dct:isPartOf

Reference toanother subject of which this subject is a part of.

Examples

Example 7: Agroup of resources that have been tested together as a single test

subject.

<earl:TestSubjectrdf:about="http://www.example.org/">

<dct:titlexml:lang="en">example.org Web site</dct:title>

<dct:descriptionxml:lang="en">Each page on the example.org Website</dct:description>

<dct:hasPartrdf:resource="http://www.example.org/style.css"/>

<dct:hasPartrdf:resource="http://www.example.org/page1.html"/>

<dct:hasPartrdf:resource="http://www.example.org/page2.html"/>

<dct:hasPartrdf:resource="http://www.example.org/image1.png"/>

<dct:hasPartrdf:resource="http://www.example.org/image2.png"/>

</earl:TestSubject>

2.4.TestCriterion Class

TestCriterion - a testablestatement, usually one that can be passed or failed. It is a super

class for alltypes of tests including things such as validation requirements, code testcases,

checkpoints fromguidelines such as Web Content Accessibility Guidelines [WCAG], or others

RelatedClasses

Rather thanspecifying only an earl:TestCriteriontype, it is recommended that one of the

followingtypes be employed in addition:

earl:TestRequirement

TestRequirement - a higher-level requirement that is tested by executing one ormore subtests.

For example WCAG 2.0 Success Criterion 1.1.1, which is evaluated using several

Techniquesfor Success Criterion 1.1.1 andcombining the results.

earl:TestCase

Test Case - anatomic test, usually one that is a partial test for a requirement. For

example, Technique H36: Using alt attributes onimages used as submit buttons providesa

partial testfor WCAG 2.0Success Criterion 1.1.1.

RelatedProperties

Domain of:none

Range of:

earl:test

It isrecommended to provide additional information about the Test Subject byusing the

followingproperties from external vocabularies:

dct:title

Human readabletitle for the test criterion.

dct:description

Human readabledescription of the test criterion.

dct:hasPart

Relationshipto other test criteria that are part of this criterion.

dct:isPartOf

Relationshipto other test criteria of which this criterion is a part of.

Examples

Example 8:Instance of a test case that is described with a title and its

relationshipto a test suite.

<earl:TestCaserdf:about="http://www.w3.org/TR/WCAG20-TECHS/H36">

<dct:titlexml:lang="en">H36</dct:title>

<dct:descriptionxml:lang="en">Technique H36 - Using alt attributes

on imagesused as submit buttons </dct:description>

<dct:isPartOfrdf:resource="http://www.w3.org/TR/WCAG20-TECHS/"/>

<dct:hasPartrdf:resource="http://www.w3.org/TR/WCAG20-TECHS/H36#H36-tests"/>

</earl:TestCase>

2.5.TestResult Class

TestResult - the actual resultof performing the test. It includes both machine-readable

values as wellas human-readable description of the results (typically error messages).

RelatedProperties

Domain of:

earl:info

earl:outcome

earl:pointer

Range of:

earl:result

It isrecommended to provide additional information about the Test Result byusing the

followingproperties from external vocabularies:

dct:title

Human readabletitle for the result.

dct:description

Human readabledescription of the result.

dct:date

Date on whichthe result was obtained (typically when the subject was tested).

Examples

Example 9: Atest result with a validity of fail and a description of the problem

in English,and encoded in XHTML format.

<earl:TestResultrdf:about="#result">

<earl:outcomerdf:resource="http://www.w3.org/ns/earl#failed"/>

<dct:titlexml:lang="en">Invalid Markup (code #353)</dct:title>

<dct:descriptionrdf:parseType="Literal" xml:lang="en">

<divxmlns="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>

</dct:description>

<earl:pointerrdf:resource="#pointer"/>

<earl:infordf:parseType="Literal" xml:lang="en">

<divxmlns="http://www.w3.org/1999/xhtml">

<p>Itseems the <code>p</code> element has not been closed</p>

</div>

</earl:info>

</earl:TestResult>

2.6.TestMode Class

TestMode - describes how atest was carried out. It reflects the information provided by the

Assertor and is used tosimplify some commonly used queries.

RelatedInstances

Whereapplicable it is recommended to use one of the following instances of earl:TestMode, to

categorize themode in which the test was carried out:

earl:automatic

Automatic -where the test was carried out automatically by the software tool and without

any humanintervention.

earl:manual

Manual - wherethe test was carried out by human evaluators. This includes the case where

the evaluatorsare aided by instructions or guidance provided by software tools, but where

the evaluatorscarried out the actual test procedure.

earl:semiAuto

Semi-Automatic- where the test was partially carried out by software tools, but where

human input orjudgment was still required to decide or help decide the outcome of the

test.

earl:undisclosed

Undisclosed -where the exact testing process is undisclosed.

earl:unknownMode

Unknown -where the testing process is unknown or undetermined.

RelatedProperties

Domain of:none

Range of:

earl:mode

It isrecommended to provide additional information about the Test Mode byusing the following

propertiesfrom external vocabularies:

dct:title

Human readabletitle for the test mode.

dct:description

Human readabledescription of the test mode.

Examples

Example 10:The assertion from example 3was carried out in semi-automatic mode.

<earl:Assertionrdf:about="#assertion">

<earl:moderdf:resource="http://www.w3.org/ns/earl#semiAuto"/>

</earl:Assertion>

2.7.OutcomeValue Class

OutcomeValue - a value orexpression that describes a resulting condition from carrying out

the test.

RelatedInstances

Whereapplicable it is recommended to use one of the following instances of earl:OutcomeValue, to

categorize theoutcome of carrying out the test:

earl:passed

Passed - thesubject passed the test.

earl:failed

Failed - thesubject failed the test.

earl:cantTell

Cannot tell -it is unclear if the subject passed or failed the test.

earl:inapplicable

Inapplicable -the test is not applicable to the subject.

earl:untested

Untested - thetest has not been carried out.

RelatedClasses

In cases whereit is necessary to create further instances of earl:OutcomeValue, it is

recommendedthat one of the following types be employed in addition:

earl:Pass

Pass - theclass of outcomes to denote passing a test. Subclasses may include ordinal,

nominal, orcontinuous values or expressions.

earl:Fail

Fail - theclass of outcomes to denote failing a test. Subclasses may include ordinal,

nominal, orcontinuous values or expressions.

earl:CannotTell

Undetermined -the class of outcomes to denote an undetermined outcome. Usually this

happens whenan automated test requires human judgement to make a definite decision.

earl:NotApplicable

Not applicable- the class of outcomes to denote the test is not applicable. This could be

due to amismatch between the test and the subject or for any other reason.

earl:NotTested

Not tested -the class of outcomes to denote the test has not been carried out. This is

useful forreporting as well as for other uses of progress monitoring.

Related Properties

Domain of:none

Range of:

earl:outcome

It isrecommended to provide additional information about the Outcome Value byusing the

followingproperties from external vocabularies:

dct:title

Human readabletitle for the outcome value.

dct:description

Human readabledescription of the outcome value.

Examples

Example 11: A testresult with an outcome of "Passed", using the corresponding

instance of earl:OutcomeValue.

<earl:TestResultrdf:about="#result">

<earl:outcomerdf:resource="http://www.w3.org/ns/earl#passed"/>

</earl:TestResult>

Example 12: Atest result with a non-standard outcome of "Warning", which is a type

earl:Pass.

<rdf:Descriptionrdf:about="http://example.org/my/warning#warning">

<rdf:typerdf:resource="http://www.w3.org/ns/earl#Pass"/>

<dc:titlexml:lang="en">Warning</dc:title>

<dc:descriptionxml:lang="en">the subject passed the test but there arewarnings</dc:description>

</rdf:Description>

<earl:TestResultrdf:about="#result">

<earl:outcomerdf:resource="http://example.org/my/terms#warning"/>

</earl:TestResult>

2.8.Software Class

[Editor's note2: ERT WG is looking for feedback on the use of DOAP Project to describe

Software; feedback on this issue is welcome.]

A Software isany piece of software such as an authoring tool, browser, or evaluation tool.It

can be used todescribe an Assertor, such as a validation or other qualityassurance tool, and

it can be usedto describe a TestSubject (for example totest compliance of an authoring tool

to AuthoringTool Accessibility Guidelines [ATAG] or of a browserto User Agent Accessibility

Guidelines [UAAG]).

Note: earl:Software is a sublass of doap:Project to denote thenarrower meaning of executable

"Software",that is an outcome of a "Project".

RelatedProperties

It isrecommended to provide information about the Software by using thefollowing properties

from externalvocabularies:

doap:name

Human readablename of the software.

doap:description

Human readabledescription of the software.

doap:homepage

Homepage forthe software.

doap:created

Date when thesoftware was created or released, in YYYY-MM-DD form. e.g. 2004-04-05.

doap:release

Versioninformation about the software release.

Examples

Example 13:Description of a software tool.

<earl:Softwarerdf:about="#cooltool">

<doap:namexml:lang="en">Cool Tool</doap:name>

<doap:descriptionxml:lang="en">My favorite tool!</doap:description>

<doap:created>2011-04-27</doap:created>

<doap:homepagerdf:resource="http://example.org/tools/cool/"/>

<doap:release>

<doap:revision>1.0.3</doap:revision>

</doap:release>

</earl:Software>

3. Properties

This sectiondescribes the properties defined by this document. EARL also uses propertiesfrom

externalvocabularies to provide additional information where necessary.

3.1.assertedBy Property

AssertedBy - the assertor ofan assertion.

Domain:

earl:Assertion

Range:

earl:Assertor

3.2. subjectProperty

Subject- the test subjectof an assertion.

Domain:

earl:Assertion

Range:

earl:TestSubject

3.3. testProperty

Test- the testcriterion of an assertion.

Domain:

earl:Assertion

Range:

earl:TestCriterion

3.4. resultProperty

Result- the result of anassertion.

Domain:

earl:Assertion

Range:

earl:TestResult

3.5. modeProperty

Mode- the mode in whichthe test was performed.

Domain:

earl:Assertion

Range:

earl:TestMode

3.6.mainAssertor Property

MainAssertor - the assertor thatis primarily responsible for performing the test. It is a

refinement ofthe term foaf:member defined by [FOAF].

Domain:

earl:Assertor

Range:

earl:Assertor

3.7. outcomeProperty

Outcome- the outcome ofperforming the test.

Domain:

earl:TestResult

Range:

earl:OutcomeValue

3.8. pointerProperty

Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/12/16

Pointer - the locationwithin a test subject that are most relevant to a test result.

Domain:

earl:TestResult

Range:

ptr:Pointer

3.9. info Property

Info - additionalwarnings or error messages in a human-readable form.

Domain:

earl:TestResult

Range:

Literal

Appendix A: Terms

This section summarizes the terms defined and used bythis EARL 1.0 Schema specification.

Classes

EARL 1.0 Classes

Class Name Label Comment Refinements Related

Properties

earl:Assertion Assertion a statement

that embodies

the results

of a test

- earl:assertedBy

earl:subject

earl:test

earl:result

earl:mode

earl:Assertor Assertor an entity

such as a

person, a

software

tool, an

organization,

or any other

grouping that

carries out a

test

collectively

earl:Software

foaf:Agent

foaf:Person

foaf:Organization

foaf:Group

earl:assertedBy

earl:mainAssertor

dct:title

dct:description

foaf:name

foaf:firstName

foaf:surname

foaf:nick

foaf:mbox

foaf:mbox_sha1sum

foaf:homepage

foaf:member

earl:TestSubject Test Subject theclass of

things that

have been

tested

against some

test

criterion

earl:Software

cnt:Content

http:Response

foaf:Document

earl:subject

dct:title

dct:description

dct:date

dct:hasPart

dct:isPartOf

earl:TestCriterion Test

Criterion

a testable

statement,

usually one

that can be

passed or

failed

earl:TestRequirement

earl:TestCase

earl:test

dct:title

dct:description

dct:hasPart

dct:isPartOf

earl:TestRequirement

(subclass of

earl:TestCriterion)

Test

Requirement

a higherlevel

requirement

that is

tested by

executing one

or more sub-

- earl:test

dct:title

dct:description

dct:hasPart

dct

(subclass of

earl:TestCriterion)

Test Case anatomic

test, usually

one that is a

partial test

for a

requirement

- earl:test

dct:title

dct:description

dct:hasPart

dct:isPartOf

earl:TestResultTest Result the actual

result of

performing

the test

- earl:result

earl:info

earl:outcome

earl:pointer

dct:title

dct:description

dct:date

earl:TestModeTest Mode describes how

a test was

carried out

- earl:mode

dct:title

dct:description

earl:OutcomeValueOutcome

Value

a discrete

value that

describes a

resulting

condition

from carrying

out the test

earl:Pass

earl:Fail

earl:CannotTell

earl:NotApplicable

earl:NotTested

earl:outcome

dct:title

dct:description

earl:Pass

(subclass of

earl:OutcomeValue)

Pass the classof

outcomes to

denote

passing a

test

- earl:outcome

earl:Fail

(subclass of

earl:OutcomeValue)

Fail the classof

outcomes to

denote

failing a

test

- earl:outcome

earl:CannotTell

(subclass of

earl:OutcomeValue)

Undeterminedthe class of

outcomes to

denote an

undetermined

outcome

- earl:outcome

earl:NotApplicable

(subclass of

earl:OutcomeValue)

Not

applicable

the class of

outcomes to

denote the

test is not

applicable

- earl:outcome

earl:NotTested

(subclass of

earl:OutcomeValue)

Not tested theclass of

outcomes to

denote the

test has not

been carried

out

- earl:outcome

earl:SoftwareSoftware any piece of

software such

as an

authoring

tool,

browser, or

evaluation

tool

- dct:title

dct:description

foaf:homepage

dct:hasVersion

dct:hasPart

dct:isPartOf

Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/14/16

EARL 1.0 Properties

Property Name Label Comment Domain Range

earl:assertedBy Asserted

By

assertor of an

assertion

earl:Assertion earl:Assertor

earl:subject Subject test subject of

an assertion

earl:Assertion earl:TestSubject

earl:test Test test criterion of

an assertion

earl:Assertion earl:TestCriterion

earl:result Result result of an

assertion

earl:Assertion earl:TestResult

earl:mode Mode mode in which the

test was

performed

earl:Assertion earl:TestMode

earl:mainAssertor

(subproperty of

foaf:member )

Main

Assertor

assertor that is

primarily

responsible for

performing the

test

earl:Assertor earl:Assertor

earl:outcome Outcome outcome of

performing the

test

earl:TestResult earl:OutcomeValue

earl:pointer Pointer location within a

test subject that

are most relevant

to a test result

earl:TestResult ptr:Pointer

earl:info Info additional

warnings or error

messages in a

human-readable

form

earl:TestResult Literal

Instances

EARL 1.0 Instances

Instance Name Title Description

earl:automatic

(instance of

earl:TestMode)

Automatic where the test was carried out automatically by

the software tool and without any human

intervention

earl:manual

(instance of

earl:TestMode)

Manual where the test was carried out by human evaluators

earl:semiAuto

(instance of

earl:TestMode)

Semi-

Automatic

where the test was partially carried out by

software tools, but where human input or judgment

was still required to decide or help decide the

outcome of the test

earl:undisclosed

(instance of

earl:TestMode)

Undisclosed where the exact testing process isundisclosed

earl:unknownMode

(instance of

earl:TestMode)

Unknown where the testing process is unknown or

undetermined

earl:passed

(instance of

earl:Pass)

Passed the subject passed the test

earl:failed

(instance of

earl:Fail)

Failed the subject failed the test

earl:cantTell

(instance of

earl:CannotTell)

Cannot tell it is unclear if the subject passed or failedthe

test

earl:inapplicable Inapplicable thetest is not applicable to the subject

Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/15/16

(instance of

earl:NotApplicable)

earl:untested

(instance of

earl:NotTested)

Untested the test has not been carried out

Appendix B: References

This section provides references to related documents andspecifications.

[ATAG]

Authoring Tool Accessibility Guidelines

[Content]

Representing Content in RDF

[DC]

Dublin Core (DC) Metadata

[DOAP]

Description of a Project (DOAP) Vocabulary

[FOAF]

Friend of a Friend (FOAF) Vocabulary

[Guide]

Evaluation and Report Language (EARL) 1.0 Guide

[HTTP]

HTTP Vocabulary in RDF

[Pointers]

Pointer Methods in RDF

[RDF]

Resource Description Framework (RDF): Concepts andAbstract Syntax

[RDFS]

RDF Vocabulary Description Language 1.0: RDF Schema

[RDF-PRIMER]

RDF Primer

[RDF/XML]

RDF/XML Syntax Specification

[RDF-XML-DIFFS]

Why RDF model is different from the XML model

[RFC 2119]

Key words for use in RFCs to Indicate Requirement Levels

[UAAG]

User Agent Accessibility Guidelines

[WCAG]

Web Content Accessibility Guidelines

[XMLS]

XML Schema Part 0: Primer

Appendix C: Contributors (Non-Normative)

EARL is the result of the work of many people over thepast. The editors would particularly

like to thank Wendy Chisholm, Sean B Palmer, and DanielDardailler, whose contributions have

included editing the first versions of the EARLspecifications, and Leonard Kasday who set the

work in motion to develop EARL. The editors apologise forany names left out of this list, and

will endeavour to rectify any errors noted in comments.

Contributors to this and/or previous Working Drafts

Shadi Abou-Zahra, Philip Ackermann, ChrisoulaAlexandraki, Shane Anderson, Myriam Arrue,

Gabriele Bartolini, Giorgio Brajnik, Dan Brickley, DanConnolly, Karl Dubost, Nick Gibbins, Al

Gilman, Emmanuelle Gutiérrez y Restrepo, DominiqueHazaël-Massieux, NadiaHeninger, Sandor

Herramhof, Ian Hickson, Björn Höhrmann, CarlosIglesias, Nick Kew, Johannes Koch, Jim Ley,

William Loughborough, Rui Lopes, John Lutts, CharlesMcCathieNevile, Libby Miller, Tom Martin,

Yehya Mohamed, Daniela Ortner, Dave Pawson, EricPrud'hommeaux, Pierre Queinnec, Chris Ridpath,

Romain Roure, Christophe Strobbe, Michael Squillace,Aaron Swartz, Olivier Thoreaux, Carlos

Velasco, Konstantinos Votis, and Rob Yonaitis.

Appendix D: Document Changes

Evaluation and ReportLanguage (EARL) 1.0 Schema

www.w3.org/TR/EARL10-Schema/16/16

Besides several minor editorial changes, the mostsignificant changes from the 29 October, 2009

Working Draft include:

Added examples to section 2.7OutcomeValue Class, to clarify the use of the terms;

Made earl:Software a subclass of doap:Project, and reusedseveral terms from DOAP

Moved entire conformance section into the DeveloperGuide for EARL 1.0 document

A detailed listing of the comments, resolutions, andchanges made is provided in the Open

Issues for EARL 1.0 Schema listing.


1楼 发布于:2016-6-22   |   查看数:0   |   回复数:0
初出江湖