W3C home > Mailing lists > Public > public-wai-ert@w3.org > April 2005

Re: Adding more information about TestSubject

From: Charles McCathieNevile <charles@sidar.org>
Date: Wed, 06 Apr 2005 19:20:11 +1000
To: "Johannes Koch" <johannes.koch@fit.fraunhofer.de>, public-wai-ert@w3.org
Message-ID: <op.sosz7xfaw5l938@researchsft>

On Wed, 06 Apr 2005 18:26:17 +1000, Johannes Koch  
<johannes.koch@fit.fraunhofer.de> wrote:

>
>  From current EARL WD:
>
>    TestSubject
>
>    The class of things that have been evaluated. It needs to be qualified
>    with some type of information in order to make it unambiguous. You may
>    use an unambiguous property, or unambiguous constellation of
>    properties.
>
>
> 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?

Yes, and yes.

With the reprOf for Webcontent it should be reasonably easy to add sme  
HTTP properties to cover the headers that are sent or received. I think  
that these properties are already used in Annotea, so we don't even have  
to define them for ourselves.

Including the content itself is another question. Particularly if we are  
looking at Web pages that incorporate media objects, scripts and styles,  
it becomes quite complex.

On the other hand I can't think of a reason not to be able do this, and  
again Annotea might provide an interesting model. (What they actually do  
in the annotea server is store a page, and some metadata that happens to  
be based on HTTP).

cheers

Chaals

-- 
Charles McCathieNevile                      Fundacion Sidar
charles@sidar.org   +61 409 134 136    http://www.sidar.org
Received on Wednesday, 6 April 2005 09:20:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:52:49 UTC