Template-Type: DUBLINCORE

This template type is now deprecated.

Please see the more recent work on integrating Dublin Core and ROADS, known as 'DC in a box', available from:

http://edward.ilrt.bris.ac.uk/dciab/

Attribute Notes

Template-Type DUBLINCORE

Handle Assigned automatically

Template-Version 0.2

Title The name given to the resource, usually by the Creator or Publisher.

Creator- (AGENT CLUSTER)
Creator-Name-v*
Creator-Type-v*
Creator-Email-v* The person or organization primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources.
See AGENT cluster.

Subject-v* The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemes is encouraged.

Description-v* A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources.

Publisher- (AGENT CLUSTER)
Publisher-Name-v*
Publisher-Type-v*
Publisher-Email-v* The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity.
See AGENT cluster.

Contributor- (AGENT CLUSTER)
Contributor-Name-v*
Contributor-Type-v*
Contributor-Email-v* A person or organization not specified in a Creator element who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organization specified in a Creator element (for example, editor, transcriber, and illustrator).
See AGENT cluster.

Date-v* A date associated with the creation or availability of the resource. Recommended best practice is defined in a profile of ISO 8601 that includes (among others) dates of the forms YYYY and YYYY-MM-DD. In this scheme, for example, the date 1994-11-05 corresponds to November 5, 1994.

Type-v* The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary. For the sake of interoperability, Type should be selected from an enumerated list that is currently under development in the workshop series.

Format-v* The data format and, optionally, dimensions (e.g., size, duration) of the resource. The format is used to identify the software and possibly hardware that might be needed to display or operate the resource. For the sake of interoperability, the format should be selected from an enumerated list that is currently under development in the workshop series.

Identifier-v* A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as International Standard Book Numbers (ISBN) or other formal names are also candidates for this element.

Source-v* Information about a second resource from which the present resource is derived. While it is generally recommended that elements contain information about the present resource only, this element may contain metadata for the second resource when it is considered important for discovery of the present resource.

Language-v* The language of the intellectual content of the resource. Recommended best practice is defined in RFC 1766.

Relation-v* An identifier of a second resource and its relationship to the present resource. This element is used to express linkages among related resources. For the sake of interoperability, relationships should be selected from an enumerated list that is currently under development in the workshop series.

Coverage-v* The spatial or temporal characteristics of the intellectual content of the resource. Spatial coverage refers to a physical region (e.g., celestial sector) using place names or coordinates (e.g., longitude and latitude). Temporal coverage refers to what the resource is about rather than when it was created or made available (the latter belonging in the Date element). Temporal coverage is typically specified using named time periods (e.g., neolithic) or the same date/time format as recommended for the Date element.

Rights-v* A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource.

To-Be-Reviewed-Date

Record-Last-Verified-Email

Record-Last-Verified-Date

Comments

Destination

Attribute	Notes
Template-Type	DUBLINCORE
Handle	Assigned automatically
Template-Version	0.2
Title	The name given to the resource, usually by the Creator or Publisher.
Creator- (AGENT CLUSTER) Creator-Name-v* Creator-Type-v* Creator-Email-v*	The person or organization primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources. See AGENT cluster.
Subject-v*	The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemes is encouraged.
Description-v*	A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources.
Publisher- (AGENT CLUSTER) Publisher-Name-v* Publisher-Type-v* Publisher-Email-v*	The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. See AGENT cluster.
Contributor- (AGENT CLUSTER) Contributor-Name-v* Contributor-Type-v* Contributor-Email-v*	A person or organization not specified in a Creator element who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organization specified in a Creator element (for example, editor, transcriber, and illustrator). See AGENT cluster.
Date-v*	A date associated with the creation or availability of the resource. Recommended best practice is defined in a profile of ISO 8601 that includes (among others) dates of the forms YYYY and YYYY-MM-DD. In this scheme, for example, the date 1994-11-05 corresponds to November 5, 1994.
Type-v*	The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary. For the sake of interoperability, Type should be selected from an enumerated list that is currently under development in the workshop series.
Format-v*	The data format and, optionally, dimensions (e.g., size, duration) of the resource. The format is used to identify the software and possibly hardware that might be needed to display or operate the resource. For the sake of interoperability, the format should be selected from an enumerated list that is currently under development in the workshop series.
Identifier-v*	A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as International Standard Book Numbers (ISBN) or other formal names are also candidates for this element.
Source-v*	Information about a second resource from which the present resource is derived. While it is generally recommended that elements contain information about the present resource only, this element may contain metadata for the second resource when it is considered important for discovery of the present resource.
Language-v*	The language of the intellectual content of the resource. Recommended best practice is defined in RFC 1766.
Relation-v*	An identifier of a second resource and its relationship to the present resource. This element is used to express linkages among related resources. For the sake of interoperability, relationships should be selected from an enumerated list that is currently under development in the workshop series.
Coverage-v*	The spatial or temporal characteristics of the intellectual content of the resource. Spatial coverage refers to a physical region (e.g., celestial sector) using place names or coordinates (e.g., longitude and latitude). Temporal coverage refers to what the resource is about rather than when it was created or made available (the latter belonging in the Date element). Temporal coverage is typically specified using named time periods (e.g., neolithic) or the same date/time format as recommended for the Date element.
Rights-v*	A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource.
To-Be-Reviewed-Date
Record-Last-Verified-Email
Record-Last-Verified-Date
Comments
Destination

ROADS tables

Notes

Type authority file based on http://sunsite.berkeley.edu/Metadata/structuralist.html

[Back to ROADS templates registry]

Maintained by: Andy Powell
Last updated: 3-Feb-1999