recording the DOM?

Hi,

This is somewhat a random idea for your thoughts, I would be very 
interested in feedback and discussion.

Working with the DOM rather than the source code seems to be a trend, 
probably initiated by all the AJAX and such dynamic stuff. For example, 
the FireVox voice browser or the RAVEn evaluation tool work directly on 
the DOM of the page (I think both use FireFox as an engine) to do their 
work rather than the source code. This makes them capable to work well 
with dynamic Web applications.

In EARL we have asked ourselves what is a "Test Subject" and have the 
HTTP-in-RDF stuff to help describe "Content". In addition to describing 
the content by means of HTTP response and request pairs, would the DOM 
representation also be a useful way of describing the content tested? So 
basically the EARL report could say "I've tested the content received 
after exchanging these HTTP messages with the server, and with the such 
a DOM representation".

Of course this would be an additional and optional vocabulary extension 
like the HTTP-in-RDF. It is another way of describing what the content 
is that the tool tested. It would go into its own WG Note and would be a 
separate development (in other words, will not hold up EARL in any way). 
Still, someone needs to do the work. Anyone thinks this idea has merit 
and is interested in working on it?

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 Thursday, 22 March 2007 23:07:29 UTC