Sorry to come late to this discussion .... We have been working on a
date/time definition, it is based on ISO 8601 (although not on W3CDTF, for
reasons described in the second reference below), supports ranges and
several other features, is part of the PREMIS 2.0 schema, and we are
considering developing it further for use in other schemas.
The schema is at:
http://www.loc.gov/standards/premis/datetime/extendedDateTime.xsd
See also:
http://www.loc.gov/standards/premis/datetime/
--Ray Denenberg
----- Original Message -----
From: "Dunn, Kathryn M." <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, November 19, 2008 5:33 PM
Subject: best practice for date ranges
Hello!
Forgive me if this isn't the right listserv for implementation questions
- suggestions for more appropriate places to go are welcome.
I am wondering if there is any prevailing thought on how to represent a
date range, when using the W3CDTF profile of ISO 8601.
http://dublincore.org/documents/dcmi-terms/#terms-date uses the
definition "A point or period of time associated with an event in the
lifecycle of the resource.", and recommends
http://www.w3.org/TR/NOTE-datetime, but there is no guidance there on
how we might handle a period of time.
I feel like I have seen something like this within a DC date element,
but can't come up with any references:
start=2008-11-08; end=2008-11-09
Thanks in advance for any help!
Katie Dunn
Technology & Metadata Librarian
Rensselaer Polytechnic Institute
518-276-8353
[log in to unmask]
|