W3C home > Mailing lists > Public > www-annotation@w3.org > January to June 2001

making checklink produce annotations

From: Charles McCathieNevile <charles@w3.org>
Date: Wed, 11 Apr 2001 13:42:26 -0400 (EDT)
To: <www-annotation@w3.org>
Message-ID: <Pine.LNX.4.30.0104111332190.16907-100000@tux.w3.org>
I have an idea that I am trying to get tools that can find problems in pages
and make annotations about them. (I am really trying to sneak up on the EARL
project - Evaluation and Repair Language, a vocabulary for exchanging
machine-comprehensible data about conformance to requirements such as WAi
guideline checkpoints, validity, etc.)

It seems that a possible easy implementation demo is checklink - the link
checker that is available from W3C - http://validator.w3.org/checklink

The idea is that the checker could be asked to make annotations of its
results.

It would then need to know to check for existing annotations, and should be
able to replace an old annotation with a new one, but I haven't thought my
way that far into it yet.

However, below is a sample bit of RDF that I am pretty sure I can generate
easily via XSLT from the existing checklink output. Does it seem to make
sense?

I am postulating a namespace for the possible checklink results, which are
really just HTTP return codes so there may be one already.

And I think I have got the xpointers "almost right" - I am sure they are not
actually correct yet, but near enough for the argument.

Note that these annotations do not carry a body, but use an existing piece of
the checklink report. Maybe I should just pour that into a body instead...

All thoughts welcome

Charles McCN

<r:RDF xmlns:r="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
       xmlns:a="http://www.w3.org/2000/10/annotation-ns#"
       xmlns:d="http://purl.org/dc/elements/1.1/">

 <r:Description>
  <r:type resource="http://www.w3.org/2000/10/annotation-ns#Annotation"/>
  <r:type resource="http://www.w3.org/2001/04/checklink#broken"/>
  <a:annotates r:resource="http://example.com/some/page.html"/>
  <a:context r:resource='http://example.com/some/page.html#xpointer(a[2])'/>
  <d:creator r:resource="http://validator.w3.org/checklink"/>
  <a:created>1999-10-14T12:10Z</a:created>
  <d:date>1999-10-14T12:10Z</d:date>
  <a:body
r:resource="http://validator.w3.org/checklink?uri=http://example.com/some/page.html#xpointer(id('d1code_404')/dt[1])"/>
 </r:Description>

 <r:Description>
  <r:type resource="http://www.w3.org/2000/10/annotation-ns#Annotation"/>
  <r:type resource="http://www.w3.org/2001/04/checklink#unauthorised"/>
  <a:annotates r:resource="http://example.com/some/page.html"/>
  <a:context r:resource='http://example.com/some/page.html#xpointer(a[24])'/>
  <d:creator r:resource="http://validator.w3.org/checklink"/>
  <a:created>1999-10-14T12:10Z</a:created>
  <d:date>1999-10-14T12:10Z</d:date>
  <a:body
r:resource="http://validator.w3.org/checklink?uri=http://example.com/some/page.html#xpointer(@class('unauthorized')/dt[3])"/>
 </r:Description>

</r:RDF>



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Wednesday, 11 April 2001 13:42:27 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Friday, 25 March 2005 11:19:17 GMT