Dublin Core
From HLWIKI Canada
| Are you interested in contributing to HLWIKI Canada - hlwiki.ca? contact: dean.giustini@ubc.ca
To browse other articles on a range of HSL topics, see the wiki index.
IntroductionSee also Digital Libraries Glossary, Resource Description and Access (RDA) & CVHL / BVCS Dublin Core Records
Simple and Qualified DCThe Dublin Core standard includes two levels: Simple and Qualified. Simple Dublin Core comprises fifteen elements; Qualified Dublin Core includes three additional elements (Audience, Provenance and RightsHolder), as well as a group of element refinements (also called qualifiers) that refine the semantics of the elements in ways that may be useful in resource discovery. The Simple Dublin Core Metadata Element Set (DCMES) consists of 15 metadata elements:
Each Dublin Core element is optional and may be repeated. The DCMI has established standard ways to refine elements and encourage the use of encoding and vocabulary schemes. There is no prescribed order in Dublin Core for presenting or using the elements. Full information on element definitions and term relationships can be found in the Dublin Core Metadata Registry Dublin Core Metadata Registry. Qualified Dublin CoreAfter the original 15 elements were specified, an ongoing process extended the Metadata Element Set (DCMES). Additional terms were identified in working groups and judged by the Usage Board to conform with principles of good practice for Dublin Core metadata elements. The goal is to make an element narrower or more specific; a refined element shares meaning of the unqualified element but in a more restricted way. The guiding principle for qualification of elements - known as the Dumb-Down Principle - is that an application that does not understand a specific refinement should ignore it and treat it as an unqualified element. While this results in loss of specificity, the remaining element (without qualifier) is adequate for discovery. In addition to refinements, Qualified Dublin Core includes a set of recommended encoding schemes designed to aid in interpretation. A value expressed using an encoding scheme may be a token selected from a controlled vocabulary (e.g., term from a classification system or set of subject headings) or a string formatted in accordance with a formal notation (e.g., "2000-12-31" as standard expression of a date). If encoding is not understood by computers, it may be useful to use human readers. DCMI maintains a small vocabulary recommended for use within element Type; this currently consists of 12 terms. SyntaxesSyntax choices for DC metadata depend on a number of variables, and "one size fits all" prescriptions rarely apply. When considering an appropriate syntax, it is important to note that Dublin Core concepts and semantics are designed to be syntax independent, are equally applicable in a variety of contexts, as long as the metadata is in a form suitable for interpretation both by machines and by human beings. The Dublin Core Abstract Model provides a reference model against which particular DC encoding guidelines can be compared, independent of any particular encoding syntax. Such a reference model allows implementors to gain a better understanding of the kinds of descriptions they are trying to encode and facilitates the development of better mappings and translations between different syntaxes. References
|

