Re: EARL Pointers

Hi John,

John Resig wrote:
> Here are a couple of my thoughts:
 > [SNIP]

Thank you for sharing these thoughts. Jim Ley is leading this work and 
will respond, he is currently working on the "stand-alone" version of 
the vocabulary (separated out from EARL).


> - A user clicks an error report button
> - The contents of the page is sent to a server for analysis
> - The server responds with an RDF EARL Report
> - The client analyzes the report
> - All error-producing elements are highlighted with contextual information
> 
> Is this the sort of thing that you'd be looking for?

This is indeed a realistic scenario and very relevant to evaluating Web 
accessibility. But there are also other scenarios outside the realm of 
Web accessibility. For example, the pointers sent back by the server 
could be bookmarks in a Web page and not necessarily error reports. I 
imagine interactive Web applications such as keyword highlighting, 
in-page searches, or other navigation functionality. This is why we are 
separating this vocabulary out of EARL and making it stand-alone.

However, I wasn't actually thinking as far as a specific application. I 
just thought that jQuery may be a good candidate implementation for the 
pointer vocabulary we are developing, and that it may in turn benefit 
from supporting such a vocabulary.


Regards,
   Shadi


-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C)           http://www.w3.org/ |
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ |
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ |
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 Wednesday, 31 January 2007 17:49:02 UTC