On Wed, 24 Sep 1997, Ricky Erway wrote:
>
> 7.Date [less specific]
> Label: DATE
> The date the resource was ---made available in its present
> form---+++issued+++. Recommended best practice is an 8-digit number
> in the form YYYY-MM-DD as defined in
> http://purl.org/metadata/dc/8601-date-profile, a profile of ISO 8601.
> In this scheme, the date element +++value+++, 1994-11-05, corresponds
> to November 5, 1994. Many other schema are possible, but if used,
> they should be identified in an unambiguous manner.
>
> to read:
> The date the resource was issued. Recommended best practice is an
> 8-digit number in the form YYYY-MM-DD as defined in
> http://purl.org/metadata/dc/8601-date-profile, a profile of ISO 8601.
> In this scheme, the date element value, 1994-11-05, corresponds to
> November 5, 1994. Many other schema are possible, but if used, they
> should be identified in an unambiguous manner.
Does the Date Subgroup have any comment on this? I thought we were looking
at a much more general definition like "a date associated with the
resource" to allow for many different types of dates (date created; date
last verified; date valid to, etc.) using the type qualifier. However, I
have no objection to the above definition being the default type of date
(i.e. the assumed definition when no qualifier is used).
Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior MARC Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4020 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ [log in to unmask] ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|