W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

DAV:checkin-date

From: <Tim_Ellison@uk.ibm.com>
Date: Tue, 5 Dec 2000 14:54:50 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <802569AC.0051EE83.00@d06mta07.portsmouth.uk.ibm.com>



> Section 5.1.5: DAV:checkin-date (protected)
> - -----------------------------------------
> I still vote for giving a rationale for the term
> "reasonable approximation".  What is the idea here?

The term was taken from RFC2616 regarding the requirements for an HTTP/1.1
server to provide a Date: header if the server can provide a "resonale
approximation of the current time"
(http://andrew2.andrew.cmu.edu/rfc/rfc2616.html#sec-14.18).

It seemed reasonable to only require the same level of time keeping
accuracy for the checkin date property.

Regards,

Tim Ellison
Java Technology Centre, MP146
IBM UK Laboratory, Hursley Park, Winchester, UK.
tel: +44 (0)1962 819872  internal: 249872  MOBx: 270452
Received on Tuesday, 5 December 2000 09:55:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:39 GMT