- From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
- Date: Tue, 24 Apr 2007 10:39:28 +0200
- To: shuaib <skarim@ifs.tuwien.ac.at>
- Cc: public-wai-ert@w3.org
shuaib schrieb: >> 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. > > Here are you referring to HTTP Specs. RFC2616, or the HTTP RDF vocabulary > under review? The HTTP 1.1 spec (RFC 2616). > I saw in RFC 2616 the caching mechanism but not the comparable > details in HTTP RDF. Maybe I overlooked something. No you didn't :-) > In any case, shouldn't these properties be made part of HTTP RDF schema, or > you are leaving it to the users to extend if they are in need of? Group: This could be a topic for further discussion. -- 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 08:40:38 UTC