On Thu, Dec 06, 2007 at 09:56:03AM -0500, Clay Redding wrote:
> If you use the string "PT0S" as the end date, that indicates an open
or infinite duration.
> TEMPER didn't help with this either. I think it also recommends
just leaving the unknown end date blank. No spec that I've seen has
a way of indicating "a future date that /will/ end at some point,
but we don't know when".
this raises an interesting question: what is the intended value after
the "-" (if 1970-) or the intended value of "PT0S" (if 1970-PT0S)?
another way of saying this is, why is the date range open ended?
the quoted material above raises two possibilities: "for all practical
purposes, it's ongoing and will never end"; "it will end at some
point, but we don't quite know when yet." these are two distinct kinds
of values, but neither leaving the end date blank nor the "PT0S"
solutions distinguish between them. is that important?
> >>> "Riley, Jenn" <[log in to unmask]> 12/06/07 9:04 AM >>> Any
> other suggestions for how to encode an open-ended date range? Even
> if DACS says not to do this, not all EAD implementers will be using
> DACS. I know it's convenient to make @normal conform to the ISO8601
> data type, but we're really excluding a significant use case here...
Charles Blair Co-Director, Digital Library Development Center
773-702-8459 University of Chicago Library
[log in to unmask] http://www.lib.uchicago.edu/~chas/