Re: Conformance tool specification

Good approach... at least for fixed web pages, or for reporting on the 
status of a page at a particular time

Problem comes in if page has changed.  You do spot that via the hash (or do 
you mean checksum?).

But if a page does change, it would be useful to retain as much information 
as possible, not just say that the RDF no longer applies.  One way to do 
this is to make sure all elements have unique id's that do not get 
changed.   Or, if a checkpoint refers to a regions of a page, with many 
elements, that section should be wrapped in a <span> with a unique id.

Still have a problem if regions overlap instead of being nested.... hmmm... 
can  xpointer specify regions between two elements?

Len


At 11:19 AM 9/18/00 -0400, Charles McCathieNevile wrote:
>I wrote some very rough notes on how one could work.
>
>I am sending this mostly at this stage so the page doesn't get lost <grin/>
>
>http://www.w3.org/2000/09/conf-tool
>
>charles
>
>--
>Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
>W3C Web Accessibility Initiative                      http://www.w3.org/WAI
>Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
>September - November 2000:
>W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, 
>France

--
Leonard R. Kasday, Ph.D.
Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple 
University
(215) 204-2247 (voice)                 (800) 750-7428 (TTY)
http://astro.temple.edu/~kasday         mailto:kasday@acm.org

Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group
http://www.w3.org/WAI/ER/IG/

The WAVE web page accessibility evaluation assistant: 
http://www.temple.edu/inst_disabilities/piat/wave/

Received on Monday, 18 September 2000 11:49:05 UTC