Page 140 - Building Digital Libraries
P. 140
Metadata Formats
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
<meta name="DC.title" lang="en" content="Dublin Core Meta tags – Test Document">
<meta name="DC.creator" content="Terry Reese">
<meta name="DC.subject" lang="en" content="DCMI; Dublin Core Metadata Initiative; DC META Tags">
<meta name="DC.description" lang="en" content="Examples of Dublin Core META Tags.">
<meta name="DC.publisher" content="Terry Reese">
<meta name="DC.contributor" content="DCMI Dublin Core Metadata Initiative">
<meta name="DC.date" scheme="W3CDTF" content="2004-01-01">
<meta name="DC.type" scheme="DCMIType" content="Text">
<meta name="DC.format" scheme="IMT" content="text/html">
<meta name="DC.identifier" content="http://library.osu.edu/meta-tags/dublin/">
<meta name="DC.language" scheme="RFC1766" content="en">
<meta name="DC.coverage" content="World">
<meta name="DC.rights" content="https://library.osu.edu/about/policies-procedures/
copyright-information/">
FIGURE 6.4
Dublin Core Meta Tag Example
fifteen agreed-upon core descriptive elements shared by all published docu-
ments. These core elements provide document publishers with a known set
of metadata values that can be applied to create minimal-level metadata
records that can then be utilized by any system that is Dublin Core-aware.
However, this comes at a cost, because Unqualified Dublin Core metadata
suffers from a low level of granularity—that is, much of the contextual infor-
mation about the data within a record is retained only at the most basic level.
In figure 6.5, the Dublin Core equivalent of the MARC record found in
figure 6.1 has been provided. Initially, it should be easy to see how the record
has been flattened, since information relating to subjects and classification
FIGURE 6.5
Unqualified Dublin Core
125
