Alex Saltrapa wrote:
> Perhaps we can add the scheme "AUTHORITY" to the Contributor role:
>
> DC.Contributor = { scheme="AUTHORITY", content="University of Western
> Kazoo" }
>
> To indicate that the given entity has checked the resource and is
> willing to claim the resource as "accurate"/"correct"/whatever as makes
> sense in the situation.
I don't think that the element set should deal directly with the content of
documents. The original intent was to identify categories of metadata to
assist in locating (and classifying) documents. The validity of the
subject matter is a matter for the creator, and more particularly the
publisher, which leads on to...
> DC.Publisher = "Eastern Kazoo Web Hosting Service"
I think this is too literal or physical an interpretation of publisher. A
hosting service provides an area where a published document can be
distributed or displayed, like a bookshop. The publisher of a document is
responsible for making it available, or rather the decision to make it
available. In an intranet situation, the person or section responsible for
deciding the content of the site is the publisher. If this is the same as
the creator, then publisher can be dropped, but there is no advantage in
doing this. The person who puts the document onto the site, if they have no
input into its' intellectual content or the decision to include it on the
site, (e.g. site administrator) is neither the publisher nor a contributor.
There is no DC element to equate to their role.
Incidentally, we looked at using URLs as identifiers, and decided that they
were too unstable. The URL is an address. The document at that address
cannot be identified from a URL, nor can any change to the document. A
combination of other elements is usually sufficient to locate any document.
The Identifier can be used for internal record management, or left blank.
Dave Hardiman
I.S. Architectures Section
Dept. Social, Community & Family Affairs
Ireland
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|