It would seem to be useful to be able to attach a property of "role" or
"kind" to Coverage, as Debbie suggests. This may have a value of
Spatial, Temporal, Cultural or some other form. Then if it were
possible to have multiple roles for a coverage instance, one could have
Coverage.Spatial = Bath
Coverage.Temporal = 19th Century
--Tom
Thomas D. Wason, Ph.D.
IMS Project: Defining the Internet Architecture for Education
(http://www.imsproject.org)
GEM: Gateway to Educational Materials (http://gem.syr.edu/)
[log in to unmask]
919.839.8187
-----Original Message-----
From: Debbie Campbell <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Friday, July 30, 1999 1:53 AM
Subject: use of DC for describing events.
>The National Library of Australia is in the process of defining the
metadata
>schema for a new subject gateway called PADI (Preserving Access to
Digital
>Information). We have already set up a site containing the information
in
>static pages, but want to migrate to a dynamic service (see
>http://www.nla.gov.au/padi/ ). A substantial number of resources on the
site
>describe conferences.
>
>The schema we have chosen is the Dublin Core with some local
extensions. For
>conferences, we would like to use the DC.Type of EVENT. However, we
think
>that Dublin Core may not be granular enough to contain all of the
required
>information. The particular elements of concern are DC.Date and
DC.Coverage.
>
>
>Date:
>the date of the conference could be held in the temporal component of
the
>Coverage element as a range. However, presumably the date of the
conference
>could also be stored in the Date element because the metadata set being
>created is a surrogate for the event itself. This is complicated when
the
>content of the conference itself addresses a particular timeframe.
>
>Place:
>the location of the conference could be held in the spatial component
of the
>Coverage element. But we have assumed that if the conference is about
(say)
>'art in 19th Century Bath', then that is really the content of the
Coverage
>element. In the CIMI guide, location information is placed at the head
of
>the Description element. A similar solution is applied in MARC.
However,
>this is less effective for retrieval where we want to group all
conferences
>occurring at a particular location. So, for the moment we have decided
to
>have a separate element called PADI.Place.
>
>With regard to the conference papers associated with a conference, we
have
>decided that they can be described as a separate metadata set including
the
>Relation element with IsBasisOf.
>
>Is there an implemented schema which addresses this situation for a
>significant set of conferences ? (The DC workshop series has no
metadata
>:-))
>
>Thanks
>Debbie
>
>--
>Debbie Campbell, Metadata Coordinator, Coordination Support Branch
>National Library of Australia, Canberra, ACT 2601
>ph: +61 2 6262 1673; fax: +61 2 6273 2545
>mailto:[log in to unmask] http://www.nla.gov.au/meta
>
>
>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|