Thank you Simon. For what it is worth, I would like to concur in all three
of Simon's further point's below and note also that it is likely that some
users of DC Lite will only use DC.Source, though this should probably be
discouraged in the user guide.
Rebecca asked for examples as well. I personally am a very poor
cataloger/documentalist and would ask that others provide examples, but to
clarify the specific issue about which Rebecca wrote, I would note that the
Version relation is an edition or state BY THE SAME CREATOR intended to be
creatively different but IN A SUFFICIENTLY MINOR DEGREE as to not be a
different work. Format transformations (whether by the original creator or
others) are intended to be REPLICATIONS, NOT CREATIVELY DIFFERENT from
their source, but as Simonm correctly points out, artifacts are intyroduced
by such processes and it is often important to know from what source the
format I have has been derived.
David
At 02:33 PM 12/21/97 +0000, Simon Cox wrote:
>Congratulations and thanks to David Bearman for a very
>effective and succinct summary of the deliberations of
>the Relation working group.
>
>A few comments:
>
>A. I would suggest that for the purposes of DC-Lite
>one additional piece of information probably needs to
>be stated explicitly so that people can see what
>"Relation" is all about. The _second_ (?) simplest
>versions of the Dublin Core Relation element will
>normally require two attributes:
>1. the relation type - as summarised by David;
>2. identification of the related resource.
>This has syntax implications.
>(The _simplest_ version might only have the
>identifier and dispense with the type ...)
>
>B. Now that the intended use of Relation has been completed (!!??)
>the role of DC-Source suggested originally I think by Doug Dodds
>at Helsinki, and discussed a little further on meta2, can be
>understood by comparison with (DC-Relation type=IsBasedOn).
>DC-Source will often refer to the same related resource as
>one identified through DC-Relation of this type,
>with the special characteristics that
>(i) the related resource may be several steps away
>through a chain of "derivations",
>(ii) the metadata for the related resource is judged to
>be very important for resource discovery of the present
>resource as well, and so can be embedded within the metadata
>for the present resource with the qualifier DC-Source.
>
>Thus, Kenneth Branagh's movie of Henry V
> DC.Creator="Kenneth Branagh"
> DC.Date="1994" (?)
>could have metadata for the Shakespeare script embedded
>within its metadata through use of DC-Source,
> DC.Source.Creator="William Shakespeare"
> DC.Source.Date="1605" (?)
>while the link through DC-Relation would just
>_identify_ the Shakespeare
> DC.Relation=(Type=IsBasedOn,Identifier=theShakespeareScript)
>
>(This illustrates the problems with the syntax for a Lite version.)
>
>C. The User Guide for DC-Relation would be well served
>through a bunch of examples for each of the types.
>--
>__________________________________________________
>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]
>http://www.ned.dem.csiro.au/SimonCox/
>
>
>
David Bearman, President
Archives & Museum Informatics
5501 Walnut St., Suite 203
Pittsburgh, PA 15232 USA
ph. + 1-412-683-9775
fax + 1-412-683-7366
email: [log in to unmask]
URL: www.archimuse.com
|