W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > April 2004

RE: EARL Testcase

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Thu, 15 Apr 2004 20:46:26 +0200
To: "'Chris Ridpath'" <chris.ridpath@utoronto.ca>, "'WAI ER IG List'" <w3c-wai-er-ig@w3.org>
Message-ID: <007001c42319$f54f3560$6466a8c0@K2>


i've also been playing around with this type of code:

  <earl:subject rdf:resource="#subject"/>
  <earl:result rdf:parseType="Resource">
    <earl:message>ALT Tags Exist</earl:message>
  <earl:assertedBy rdf:resource="#assertor"/>

...which makes aggregation very comfortable but kind of turns EARL
inside out (as i understand the current spec).

to me it makes sense as an assertion is really about the specific test
which the tool conducts, the earl:testcase should be optional if this
test really maps to a test suite. comments welcome...

-----Original Message-----
From: Chris Ridpath [mailto:chris.ridpath@utoronto.ca] 
Sent: Thursday, April 15, 2004 20:36
To: Shadi Abou-Zahra; 'WAI ER IG List'
Subject: Re: EARL Testcase

Works for me.

Although I'm not sure about the use of the "rdf:about" and
attributes. Should these both be "rdf:resource" attributes?

Charles - Any comments?


----- Original Message ----- 
From: "Shadi Abou-Zahra" <shadi@w3.org>
To: "'Chris Ridpath'" <chris.ridpath@utoronto.ca>; "'WAI ER IG List'"
Sent: Thursday, April 15, 2004 2:15 PM
Subject: RE: EARL Testcase

> hi,
> currently i'm just using this hack for my prototype:
> <earl:testcase
> rdf:about="http://www.w3.org/TR/WCAG10/#tech-text-equivalent">
>   <earl:testId
> rdf:resource="http://vendor-a.org/tool/tests/#check-for-alt" />
> </earl:testcase>
> regards,
>   shadi
Received on Thursday, 15 April 2004 14:46:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:35 UTC