EARL (Evaluation And Report Language) 0.975 RDF Schema Assertion An assertion consists of parts Assertor, TestSubject, ResultProperty, and TestCase. Assertor The class of entities making an assertion in EARL (e.g. running the test). assertedBy For earl:assertedBy(x,y), the assertion (x) is asserted by (y). TestSubject The class of things which are being evaluated in an EARL evaluation - the things that are the subject of every assertion This needs to be qualified with some type of information in order to make it unambiguous. You may use an unambiguous property, or unambiguous constellation of properties. regarding ResultProperty The set of result properties in EARL; they are the range of earl:result for all EARL Assertions. result The property with range ResultProperty. TestCase The class of all TestCases. Conceptually, a Test Case is some resource to which another resource can be validated against - something for which it can be demonstrated that it passes or fails against (or otherwise). This may in fact include many things - validation classes, code test cases, or more subjective guidelines such as WCAG. tested The property with range TestCase. operator for operator(x, y), y is the operator of x This is the operator of a machine (range undefined) contactInfo for contactInfo(x, y), y is some some kind of generic contact information for y. This is a sub classable property. A strict domain is used rather than a restriction so that one may infer that the subject is an Assertor. Not that that information would actually help. email Generally, for earl:email(x, y) x has an email address of y. The URI of the object will normally start with "mailto:", and will not be a literal. This is not a sub property of foaf:mbox! That property can only be applied to people. name The common proper name for some earl:Assertor. This is related to foaf:name. platform For platform(x, y), y is the platform on which x ran/runs e.g. the platform on which the test(s) were run, or the general platform on which something runs os The Operating System on which an assertion was run, or of which an Assertor uses. testMode The test mode of some EARL assertion Manual Auto Heuristic WebContent WebContent is synonymous with "Document Source" in UAAG, and "Representation" in RFC 2616. Anything which is an instance of WebContent must have exactly one reprOf predicate hanging from it. Tool This is a tool; a bit of software, perhaps with a desc. UserAgent A user agent date This whole earl:datatype thing seems odd. Why don't we specify a particular literal form and use that? YYYY-MM-DD (HH:MM:SS) version For earl:version(x, y), read: x is of version y reprOf For reprOf(x, y), read that x is a representation of y, possibly derived from an HTTP GET transaction. a daml:UniqueProperty? format The MIME type of the WebContent subject, as a literal. snapshot Points to a snapshot of a serialization of the resource when it was evaluated validity The validity state for an EARL ResultProperty. Validity The class of all EARL validity states. passes 1 fails 1 notApplicableTo 1 confidence for confidence(x, y), x has the confidence y, where y is a number between 0 and 1 (or 0% and 100%, the idea is to have a range). severity same idea as confidence, only this is a measure of the severity of the test failure. id Since we decided that earl shouldn't be a test point definition language, id is now the only property that we can have for a TestCase. A single guideline, checkpoint, etc. - this should be the unique identifier for the TestCase EARL (Evaluation And Report Language) 0.975