Re: proposed changes to the EARL schema


> I was thinking of a slightly different use case. I was 
> considering the case of using a persistent triplestore, like 
> 3store, Jena or Kowari for storing testsuites or test runs 
> that keeps a run number and several EARL test reports 
> contained within the test suite/test run. Each test 
> suite/test run would have to be unique and versioned. I was 
> not thinking about storing files, but an RDF tree or grove 
> of tests and tests...
> I do not see how the EARL report can identify itself in this 
> scenario?

OK, got it now. But what is an EARL *report* exactly? For example:

* tool A can execute 11 tests
* tool B can execute 62 tests
* policy C consists of 89 tests
* policy D consists of 17 tests

Maybe it is more flexible to use test/assertion pairs (rather than whole


---                                                    --- 
Shadi Abou-Zahra,    Chair and Team Contact for the ERT WG 
World Wide Web Consortium (W3C), 
Web Accessibility Initiative (WAI), 
Evaluation and Repair Tools WG, 
2004, Route des Lucioles - 06560 Sophia-Antipolis - France 
Voice: +33(0)4 92 38 50 64        Fax: +33(0)4 92 38 78 22 

Received on Thursday, 21 April 2005 22:40:55 UTC