I'm made more than a little nervous by the doubt about which fields
should be recorded...
> Collapsing AUTHOR/PUBLISHER/OTHER-AGENT into one or two elements has been
> proposed
For my own part, I don't understand what happened to author's institution
(this is distinct from publisher) -- is tht part of OtherAgent?
> Addition of a simple rights management field would be useful to preclude
> downloading of large elements that
agreed.
> What to do about COVERAGE?
retain it. It's clearly important for GIS and geographical uses.
> Should there be an ABSTRACT element, separate from SUBJECT?
You're not going to get abstracts for most web page.
> Is it necessary to distinguish between SUBJECT and CONTENT for image
> description?
I don't understand this -- what's CONTENT? Subject is presumably as per
Dewey Decimal or YAHOO categorisation.
> How should RELATION be implemented?
I'm not sure -- the REL/REV draft that Murray and I wrote is a possibility.
> Element Names
>
> Current names for Dublin Core elements are alpha strings that
> perpetuate their anglo-centric (and text-centric) origin. [...]
> a means of
> element name indirection should be put in place soon to allow
> non-english language names as well as names that might be tailored
> better to specialized domains.
I don't agree. HTML has the same problem. We shouldn't try and solve
it here.
> Element Substructure
>
> The basic application of Dublin Core elements should be as simple
> descripters as we would expect them to applied by authors.
>
> More sophisticated Dublin Core applications (by publisher, libraries, and
> others) will require means for specifying sub-element structure as well as
> extensions. Such substructure needs to be developed and specified formally
> and registered.
Why would they not want to use a modified MARC record?
> Possible qualifiers:
>
> SCHEME
> TYPE
> ROLE
> Enumerated values of some elements
> FLAGS
>
> Requirements Document for the Dublin Core
>
> Do we need one and why?
I think a document explaining the intended goals of the DC would be
very helpful, but to some extent there already is one.
I'm not sure what else is needed.
Lee
|