W3C home > Mailing lists > Public > public-wai-ert@w3.org > March 2005

Requirement? An "evidence" property

From: Charles McCathieNevile <charles@sidar.org>
Date: Sun, 20 Mar 2005 18:57:02 -0500
To: "public-wai-ert@w3.org" <public-wai-ert@w3.org>
Message-ID: <op.snynhce5w5l938@researchsft>

Particularly in dealing with results that are inferred from other results,  
one of the things I have wanted is some way of saying how those results  
were derived.

This may be a particular extension to earl:message (i.e. modelled as an RD  
subProperty). That would require the range of a Message to be pretty  

The simple use case I have is as follows:

I use MUTAT to generate assertions that the EARL spec meets each of the  
required tests in SpecGL. I also write an OWL rule that says that anything  
that meets each test meets the test "conforms to SpecGL".

I want to generate an assertion that says the EARL spec conforms to  
SpecGL, and provide linkage to why I think this is so. That way, I can  
ship around the single assertion, but people can follow it back and verify.

The design I have in mind looks like this:

   <assertedBy r:resource="#chaals" />
   <testCase r:resource="../../SpecGL#required" />
   <result r:type="&earl;pass" />
   <mode r:resource="&earl;heuristic" />

<!-- the foregoing is already there. The following is what I suggest as a  
strawman -->

   <evidence r:parseType="Collection">
     <evRule r:resource="../../SpecGL#requiredRule" />
     <Assertion r:resource="#point1A" />
     <Assertion r:resource="#point1B" />
     <Assertion r:resource="#point2A" />
     <Assertion r:resource="#point3A" />
     <Assertion r:resource="#point3B" />
     <Assertion r:resource="#point3C" />
     <Assertion r:resource="#point4A" />
     <Assertion r:resource="#point5A" />
     <Assertion r:resource="#point5B" />
     <Assertion r:resource="#point6A" />

Things that come up immediately:

Querying a collection is a pain at the moment. EricP promised, in the  
meeting in Boston, that there was a way around it, but suggested that a  
standardised way around it won't get into SPARQL until version 2, which  
they expect to be 18 months - 2 years away. (Their predictions, on the  
other hand, seem relatively well-grounded so far, so I am not afraid that  
it will really be 6 years away although that possibility should not be  

It is important to have a collection, IMHO. As I understand it this is  
about the only RDF mechanism to say "these things an nothing else", which  
avoids problems when people start merging data, or modelling complex data.

This covers providing evidence for a simple deduction. We should try to  
anticipate this being used to provide evidence relied on by other tests,  
too. Which I suspect means in particular that we should not rush to  
restrict the scope, even if we do not want to get into designing a test  
description language yet...

I also have a more complex use case, which I will send seperately.



Charles McCathieNevile                      Fundacion Sidar
charles@sidar.org   +61 409 134 136    http://www.sidar.org
Received on Sunday, 20 March 2005 08:57:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:52 UTC