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

RE: [HTTP-in-RDF] date properties for timestamping

From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
Date: Sat, 9 Jun 2007 00:26:48 +0200
Message-ID: <09700B613C4DD84FA9F2FEA521882819020C6A1C@ayalga.fundacionctic.org>
To: "Johannes Koch" <johannes.koch@fit.fraunhofer.de>, <public-wai-ert@w3.org>


> possible candidates for timetamping properties are:
> * dc:date (for both http:Request and http:Response); here we 
> have to clarify that the times are to be measured at the 
> client and not to be confused with the Date HTTP header.
> * dc:dateSubmitted (for http:Request) and dc:dateAccepted (for
> http:Response)

I more in favour of dc:date because I think it's definition, "A point or period of time associated with an event in the lifecycle of the resource.", covers perfectly our use cases.

Don't like dc:dateSubmitted and dc:dateAccepted too much because I think their current definitions "Date of submission of the resource (e.g. thesis, articles, etc.)" and "Date of acceptance of the resource (e.g. of thesis by university department, of article by journal, etc.)" respectively, manage slightly different concepts:

 - Request sth vs. submit sth, which are more or less the opposite.
 - Respond to sth vs. acceptance of sth, a kind of respond.


Carlos Iglesias

CTIC Foundation
Science and Technology Park of Gijón
33203 - Gijón, Asturias, Spain 

phone: +34 984291212
fax: +34 984390612
email: carlos.iglesias@fundacionctic.org
URL: http://www.fundacionctic.org
Received on Friday, 8 June 2007 22:27:17 UTC

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