W3C home > Mailing lists > Public > public-wai-ert@w3.org > March 2007

Re: recording the DOM?

From: Nick Kew <nick@webthing.com>
Date: Sat, 24 Mar 2007 14:50:55 +0000
To: public-wai-ert@w3.org
Message-ID: <20070324145055.757aa7a6@grimnir>

On Fri, 23 Mar 2007 00:07:27 +0100
Shadi Abou-Zahra <shadi@w3.org> wrote:

> 
> 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, 

FWIW, Valet already has the capability to record a DOM.  It uses
a dom: namespace to do so, with
dom:document
dom:element
dom:attribute
dom:text

This is used to display warning messages in their context, and to
distinguish significant changes/differences from ignorable ones.

That of course is only a partial DOM (it's just what this particular
tool needs).  But it seems fairly trivial to extend as necessary.

> 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?

AFAICS This is actually straightforward, and doesn't need us to address
the kind of ambiguity we had with "fuzzy pointers" (that issue arises
at the next level of structure up).  If noone picks this up, I might 
write up something.  But that's unlikely to be anytime soon.

-- 
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Received on Saturday, 24 March 2007 14:51:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:28 GMT