- From: Gabriele Bartolini <me@gabrielebartolini.it>
- Date: Thu, 07 Apr 2005 21:34:40 +0200
- To: Johannes Koch <johannes.koch@fit.fraunhofer.de>,public-wai-ert@w3.org
At 10.26 06/04/2005, Johannes Koch wrote: >With HTTP, the content of a resource is not defined with a URL but may >vary not only over time, but also with Accept* headers, cookies or POST >parameters. Would it be better to include this information as properties >of TestSubject? Should there be a way to include the content that was >actually tested in the EARL report? Agree. I guess we should give developers a chance to include details regarding the negotiation of the resource in EARL. In particular content negotiation mechanisms (e.g. at least HTTP header information) and, why not, the content as well. In some cases it may be useful, especially for historical purposes. There would need to think a way of extending this process to other media types, but I guess starting with (X)HTML and XML would be a wise choice (keeping in mind maybe some kind of text files like - for instance - CSS or programming languages). I also believe these pieces of information would be extremely useful for persistency issues as well. I would consider not only the Accept headers, but even the ones that an HTTP server would return (e.g. Content-Language). Ciao, -Gabriele -- Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check and ht://Miner maintainer Current Location: Prato, Toscana, Italia me@gabrielebartolini.it | www.gabrielebartolini.it | ICQ#129221447 > "Lasciate ogne speranza, voi ch'intrate", Dante Alighieri, Divina Commedia, Inferno
Received on Thursday, 7 April 2005 19:52:57 UTC