Examples of Dublin Core records for LC/Ameritech applicants

Contents:

The thirteen Dublin Core metadata elements

In general, all Dublin Core elements are optional and repeatable. For integration with American Memory, the elements with names in bold are required, as described in the competition Guidelines and Applications Instructions. Other elements, such as author and subject, are strongly recommended to faciltate access. Form should be used to hold an Internet Media Type (formerly known as MIME-type) when appropriate.

title
The name of the object, if it has one.
author
Name of the persons and organizations primarily responsible for the intellectual content of the resource. Encode one name per element.
otherAgent
Other person(s) and/or organization(s) who have made a significant contribution to the resource. The value of this element should follow the guidelines for the <author> element. The author and publisher elements are semantically equivalent to instances of this element with the values "author" and "publisher" for their type attributes respectively.
publisher
The agent or agency responsible for making the resource available. The value of this element should follow the guidelines for the <author> element.
date
The date of publication in any format (as indicated by the scheme attribute).
subject
The field of knowledge to which the resource belongs, typically indicated as a series of keywords, possibly taken from a controlled vocabulary as indicated by the scheme attribute.
objectType
The abstract category of the resource, such as article, image, dictionary, etc.
form
The particular data representation of the resource. Typically this will be an Internet Media Type (formerly known as MIME content type).
identifier
String or number used to uniquely identify this resource, for example a URN, or identification number used by some other scheme.
relation
Relationship of this resource to another resource. This element should specify what the relationship is (using the type attribute)
source
Objects, either electronic or printed, from which this resource was derived. This is a special case of the <relation> element.
language
The natural language(s) of the resource. When more than one <language> element is specified, it indicates that more than one language is used to a significant degree in the work. No inference should be made about the relative proportions of language content based on the order of appearence of such elements.
coverage
The spatial extent and/or temporal duration characteristic of the resource, e.g. "19th Century France".

These elements all share the following attributes:

type
optionally identifies a subcategorization of the metadata
scheme
identifies the domain or naming scheme from which categorizations are taken

MARBI Discussion Paper No. 86 (May, 1995) presents a suggested mapping from the Dublin Core elements to USMARC.

A sample record for Dublin Core metadata elements in SGML format

The syntax working group at the Warwick Metadata Workshop recommended the preparation of an SGML DTD for Dublin-Core metadata records

The proposed Dublin DTD defines specific elements for the 13 core elements, each of which bears attributes for type and scheme.

Using this syntax, a simple, minimal example might like look this:

 
<!DOCTYPE dublinCore PUBLIC '-//OCLC//DTD Dublin core v.1//EN'>
<dublinCore>
  <title>[Portrait of Zora Neale Hurston]</title>
  <author type='photographer'>Van Vechten, Carl</author>
  <otherAgent type='digitizer'>Any Library</otherAgent>
  <subject scheme='gmgpc'>Portrait Photographs</subject>
  <objectType>image</objectType>
  <form scheme='IMT'>image/jpeg</form>
  <relation type='ammemParent'>vanv</relation>
  <identifier type='URN'>hdl:loc.pp.vanv/5a52142</identifier>
</dublinCore>
 

The workshop also developed the concept of the Warwick Framework, a "container architecture" that would permit the extension of the Dublin Core set of elements through the addition of discrete packages of application-specific elements. For example, the Library might define an ammemNotes package, and use the container architecture roughly as follows:

 
<!DOCTYPE container PUBLIC '-//OCLC//DTD Warwick Framework Demo v.1//EN'>
<container>
 
<dublinCore>
  <!-- etc. as in preceding example -->
</dublinCore>
 
<package name='ammemNotes'>
  <metadata name='notes'>A note of arbitrary length</metadata>
</package>
 
</container>

These sample records should not be seen to define exact specifications, but rather to illustrate the emerging Dublin Core proposal. After awards are announced, and in the light of developments between now and then, the Library will work with awardees wishing to take this approach for providing intellectual access to develop detailed specifications.


Back to:

Go to:

(8/16/96)