David Bearman wrote:
> It is possible for events to be in coverage. If so the resource is "about"
> the event.
> But if the resource is "of" the event, the event is the DC.Type I think,
> David
>
> At 03:54 PM 9/11/98 +0200, Frank A. Roos wrote:
> >Jul,Erik wrote:
> >
> >> Simon:
> >>
> >> You wrote:
> >>
> >>
> >> > event -
> >> > non-persistent, time-based resources.
> >> [Jul,Erik]
> >>
> >> Are not events "time-and-space-based" resources?
> >
> >Could this imply that an event fits in the DC.Coverage slot? Maybe a
> >peculiar thought, but it keeps coming back in my mind following this Event
> >discussion.
> >
> >An event may then consist of a "slice" of the time base (temporal aspect)
> >and a "slice" of the geographical location (spatial aspect).
> >
> >
> >
> >
> >Attachment Converted: "c:\eudora\attach\vcard2.vcf"
> >
> David Bearman
> President
> Archives & Museum Informatics
> 5501 Walnut St., Suite 203
> Pittsburgh, PA 15232
> tel. +1-412-683-9775; fax +1-412-683-7366
> http://www.archimuse.com
It seems to me that DC.Type will always be present in a DC "record" (I can't
think of a situation where this is not the case). Consequently, if we want to
describe an "event" through our DC language, we may need both DC.Type and
DC.Coverage (if the latter is applicable; which it is in a lot of cases IMHO).
To generalize this thought, but maybe a bit off topic, although worthwhile I
think: it seems to me that each different type, is accompanied by a different
combination of the other DC fields. Maybe some fields are even mandatory to
make a type belong to a certain type (see for instance the "refer" and
"BiBTeX" bibliographic tools, where you have first to define type before
adding the (mandatory) fields to a record). So, type triggers a couple of
mandatory DC fields to be added to the DC record, that can be identified
beforehand as typical for that type. "Event" may at least need DC.coverage (in
most cases; does anybody know an example where an "event" does not have a
temporal or spatial aspect?), but undoubtedly also other fields.
One may even want to categorize the needed fields for each type.
|