I've gathered together very useful suggestions from
David, Erik, Stu, and the CIMI group for the following
resultant shortened description for "event" which is now
de-italicised in the DC.Type position paper
non-persistent, time-based occurence. Metadata for an event
provides descriptive information that is the basis for discovery
of the purpose, location, duration, responsible agents, and
links to related events and resources. Event metadata may not
identify a retrievable resource if the described instantiation
has expired or is yet to occur. Examples - exhibition, web-cast,
conference, workshop, open-day, performance, battle, trial,
wedding, tea-party, conflagration.
In particular, the earlier explanations in terms of
"transformation" turned out to be too difficult to
use unambiguously in the definition, so I've moved
these ideas to a little "gloss" which I think should be
incorporated into the USER GUIDE - for safe-keeping
meanwhile it's in a small font after the description:
Additional explanation for users:
The occurrence of an event may involve the transformation of
source resources (such as scripts, scores, artefacts, etc)
and may lead to the creation of
derived resources (such as a film, tape, transcript, image,
pile of ash, etc) but the event has a fundamental identity
separate from these other resources.
Another function of a record for an event is as an anchor to tie
back to from related items where there is a large number of them.
For example, rather than listing the
entire contents of an exhibition in the record for the
exhibition, the records for the individual items could point
to the exhibition record through Relation=IsPartOf.
I propose that this position paper for DC.Type is now stable
and should be considered for ratification as part of DC.
Any final comments??
Dr Simon Cox - Australian Geodynamics Cooperative Research Centre
CSIRO Exploration & Mining, PO Box 437, Nedlands, WA 6009 Australia
T: +61 8 9389 8421 F: +61 8 9389 1906 [log in to unmask]