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

Re: Last Call Review: EARL 1.0 Schema Last Call Working Draft

From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
Date: Tue, 24 Apr 2007 09:03:43 +0200
Message-ID: <462DABCF.9080405@fit.fraunhofer.de>
To: shuaib <skarim@ifs.tuwien.ac.at>
Cc: public-wai-ert@w3.org

Hi Shuaib, or is Karim your first name?

shuaib schrieb:
> Hi Johannes,
> For example, there can be inline graphics and multimedia in the contents for
> which separate http:Requests are generated. The existing schema is depicting
> the multiple requests.

Subsequent request to inline graphics etc. can be modeled by using RDF 
collections like in example 2.2 of 

<http:Connection rdf:ID="conn2">
   <http:request rdf:parseType="Collection">
     <http:Request rdf:about="#req0"/>
     <http:Request rdf:about="#req1"/>

> It would also be interesting to capture and depict
> the "actual" time durations to fulfill these requests (difference between
> timestamps of corresponding requests-responses) by the respective servers.

I think we already thought about adding time properties. The HTTP spec 
talks about time in the section on caching. You could add e.g. 
http://purl.org/dc/terms/created or refinements like 
http://purl.org/dc/terms/dateSubmitted to the Request resources. Usually 
the server already sends a Date header. But you could additionally add 
your local date/time to the Response resource.

Johannes Koch
BIKA Web Compliance Center - Fraunhofer FIT
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142628    Fax: +49-2241-142065
Received on Tuesday, 24 April 2007 07:04:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:55 UTC