On Friday, I was reminded of my action to look thru the current DCMES
definitions and suggest possible revisions to make them more in line with
the DCMI Abstract Model (DCAM).
Here are the ones that I find problematic:
---
Element Name: Format
Label: Format
Definition: The physical or digital manifestation of the resource.
Comment: Typically, Format may include the media-type or dimensions of
the resource. Format may be used to identify the software, hardware, or
other equipment needed to display or operate the resource. Examples of
dimensions include size and duration. Recommended best practice is to
select a value from a controlled vocabulary (for example, the list of
Internet Media Types [MIME] defining computer media formats).
Problem: The current definition implies that the value is a "manifestation
of the resource", which is not the intention. This issue has previously
been raised on one of the the DCMI lists (I forget when and where) which
suggests that at least one real end-user has mis-interpretted this wording
in this way.
Proposed definition: The media-type or dimensions of the resource.
Proposed comment: Format may be used to identify the software, hardware,
or other equipment needed to display or operate the resource. Examples of
dimensions include size and duration. Recommended best practice is to
select a value from a controlled vocabulary (for example, the list of
Internet Media Types [MIME] defining computer media formats).
---
Element Name: Source
Label: Source
Definition: A Reference to a resource from which the present resource is
derived.
Comment: The present resource may be derived from the Source resource in
whole or in part. Recommended best practice is to identify the referenced
resource by means of a string or number conforming to a formal
identification system.
Problem: As per the DCAM, the value is the related resource, not a
reference to the resource.
Proposed definition: A resource from which the present resource is
derived.
---
Element Name: Relation
Label: Relation
Definition: A reference to a related resource.
Comment: Recommended best practice is to identify the referenced resource
by means of a string or number conforming to a formal identification
system.
Problem: same as with Source.
Proposed definition: A related resource.
Proposed comment: unchanged
---
Element Name: Rights
Label: Rights Management
Definition: Information about rights held in and over the resource.
Comment: Typically, Rights will contain a rights management statement for
the resource, or reference a service providing such information. Rights
information often encompasses Intellectual Property Rights (IPR),
Copyright, and various Property Rights. If the Rights element is absent,
no assumptions may be made about any rights held in or over the resource.
Problem: the comment refers both to a 'statement' and a reference to a
service that provides a statement' This is an implementation issue anbd
shouldn't be in the comment.
Proposed definition: unchanged
Proposed comment: Typically, Rights will contain a rights management
statement for the resource. Rights information often encompasses
Intellectual Property Rights (IPR), Copyright, and various Property
Rights. If the Rights element is absent, no assumptions may be made about
any rights held in or over the resource.
Andy
--
Distributed Systems, UKOLN, University of Bath, Bath, BA2 7AY, UK
http://www.ukoln.ac.uk/ukoln/staff/a.powell
tel: +44 1225 383933 msn: [log in to unmask]
Resource Discovery Network http://www.rdn.ac.uk/
|