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

brief scenarios for DOMContent or DOM-in-RDF

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Tue, 11 Dec 2007 19:59:49 +0100
Message-ID: <475EDE25.9000900@w3.org>
To: public-wai-ert@w3.org

Hi,

Ref: <http://www.w3.org/2007/11/28-er-minutes.html#item03>

During the last meeting, we identified that DOM is a potential form of 
content representation that could be included in the "content-in-RDF" 
work. It is however unclear what the scope of this new concept would be, 
and so we decided to work out some brief scenarios to outline the use 
cases for this. Here are some off the top of my head:

- An evaluation tool sends an HTTP GET request to a server and records 
the message body received in the HTTP response. It records the message 
body as a byte sequence by default. If it can build a DOM from this 
message then it records that too.

- An evaluation tool uses a browser engine internally. It allows the 
user to interact with the page, for example to fill out different form 
fields or to activate controls. The evaluation tool uses the DOM that is 
generated by the browser to carry out the tests. It records the DOM at 
the time the tests were executed.

- A quality assurance tool processes the EARL reports generated by 
different evaluation tools, for example to generate different reports or 
to provide summaries and statistics. The user can browse through the 
test reports to explore the results, for example to analyze specific 
issues on the Web site. The tool allows the user to browser through the 
DOM representation of the HTTP content to identify the problem.


Regards,
   Shadi


-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Tuesday, 11 December 2007 18:59:58 GMT

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