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

Re: correct RDF Re: Locating In EARL Example

From: Chris Ridpath <chris.ridpath@utoronto.ca>
Date: Mon, 11 Apr 2005 04:32:03 -0400
Message-ID: <010801c53e70$f0518220$957ba8c0@traveler>
To: <shadi@w3.org>, "'Charles McCathieNevile'" <charles@sidar.org>, <public-wai-ert@w3.org>

>> http://checker.atrc.utoronto.ca/test1-earl2.html
> Looking really good! Except that we still need to
> finalize what exactly we put into the <rdf:li>...
Yes! This is just example code and should not be taken as final. I'm making 
suggestions so we have something to work with. This is very much open to 

>> <!-- this describes the anchor -->
>> <rdf:li rdf:parseType="Resource">
>> <earl:line>9</earl:line>
>> <earl:href>spending.html</earl:href>
>> <earl:xpath>/html/body/p/a</earl:xpath>
>> <earl:name>anchor</earl:name>
>> </rdf:li>
> First of all, I think earl:name would only repeat what
> is already written in the HTML spec.
> What is it actually used for?
I'm suggesting that the earl:name property is used to describe the thing 
identified by the rdf:li items. In this example it's an image. I'm not sure 
that using the earl:name property is the correct element to use but there 
needs to be something. In my other example there were 2 things that need to 
be identified:

The anchor around the image needs to be identified so that's in the 
earl:name element:
<rdf:li rdf:parseType="Resource">

The image contained by the anchor is named using the earl:name element:
<rdf:li rdf:parseType="Resource">

We need to include several chunks of information that describe the 
accessibility error and each of the chunks needs to be named. Does that make 

> Secondly, I think that *if* we can use XPath
> to reference the error, then we can just use
> something like this to describe all of the
> above in one go:
>  "//a[@href='dogs.html' and value()='click here']"
We need something other than xpath for when the document changes. I think 
the xpath used in the examples identifies the error as long as the document 
doesn't change. Your suggestion could also be used but I think it may break 
down on many of the more complex accessibility errors.

Received on Monday, 11 April 2005 08:32:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:52:49 UTC