| |
The 7th Dublin Core Metadata Workshop
October 25-27, 1999
Die Deutsche Bibliothek Frankfurt am Main, Germany
DC Date WG Agenda - DC7
This is a status report on DC-Date working group issues as of October 1999.
De-Duping Submitted Qualifiers
I've taken the liberty of conferring with the kind people who submitted lists of Date qualifiers for consideration as DCMI recommended Date qualifiers. They've helped me clarify which of their proposed qualifiers had equivalent qualifiers that had already been approved. The process of removing these duplicate (or at least equivalent) submissions has resulted in the enclosed, smaller set of qualifiers for consideration. This process is necessarily imperfect, so please let me know how it can be improved. This list is a departure point for discussion, and should be considered neither definitive nor final.
Proposed New Qualifiers -- De-Duped List
Qualifier Submitted by
Expiry (sunset clause) Business Entry Point, Australia
(for describing metadata/events)
RecordCreated GEM & RKM
Cataloging-Date Amico
Creation-Date-Qualifier Amico
Validated Amico
Transaction recorded RKM
Registration RKM
Transmission RKM
(for describing agent entities)
Active Amico & RKM
Birth Amico & RKM
Death Amico & RKM
Establishment RKM
Disestablishment RKM
(for business entities)
Execution RKM
Implementation RKM
Current DCMI Qualifiers
Note that these are subject to overall qualifier review guidelines to be discussed at the DC-7 meeting.
Date.Created Date.Issued Date.Accepted
Date.DataGathered Date.Available Date.Acquired
Date.Modified Date.Valid
Problems with Ranges
There are currently two problems with ranges:
- Ranges are not (yet) part of the W3C Profile of ISO 8601; we have
not heard from Misha what the status is of his attempts to add
ranges (normal ranges and open-ended ranges) to the W3C Profile.
- A few months ago we discovered that open-ended ranges (in which
either just a start date or just an end date appears, but not both)
are not allowed in ISO 8601, with the consequence that problem 1
becomes harder: to continue to be a Profile of 8601, the W3C
Technical Note must specify a subset of the 8601 standard.
Mitigating this problem a bit is that 8601 does not explicitly
disallow open-ended ranges, and the usage we envisioned does not
conflict with any existing usage.
Possible Solutions to Ranges
- Don't express ranges (open or closed) in one qualifier value, but
instead consider each qualifier to come as a trio of qualifiers;
e.g., Date.Valid, Date.ValidFrom, Date.ValidTo.
- Express ranges in one qualifier value, modifying the Dublin Core
Date syntax recommendation document along the lines the Date WG was
pursuing early this year. A document that defines such a syntax
might be
- consistent with ISO 8601, but not technically a Profile,
- divergent from ISO 8601, going in another direction entirely.
This document could be conceived in various contexts:
- a revised W3C Technical Note,
- a new and different W3C Technical Note, or
- a new Dublin Core (non-W3C) Recommendation.
Harmonization of Date Range Syntax with Coverage Date Ranges
Whatever solution is found for the syntax of dates, it seems desirable for that syntax to work with Coverage. Where this becomes controversial is with date ranges. The Coverage approach is akin to Solution A above, where each end of a range carries its own label.
Granularity/Precision
Granularity of dates refers to the various kinds of ambiguity that can arise around dates and ranges. For example, since any day in 1999 can be grossly identified with the date "1999", is the value "1999" a point in time, or a range of days? For that matter, could it be a range of months, weeks, or minutes? Similarly, can an actual range of years (with explicit starting and ending points) also imply a range of days, weeks, or minutes?
Point of contact: John A. Kunze

© Die Deutsche Bibliothek
Hannelore Effelsberg / 21.10.1999
|