
|
INTRO |
Spam Indexing |
Mark Up |
MetaTags |
SGML/XML |
Dublin Core |
PICS |
Metametatags |
![]() |
|
|
|
|
|
|
|
|
How Dublin Core is used.
How to create Dublin Core metadata Where to place DC metadata Positive and negative aspects of author applied metadata What is Dublin Core
|
Dublin
CoreThe development of a uniform standard set of authored applied indexing terms is the result of on-going work by a network working group to develop a standard set of "metadata elements." Dublin Core does not now represent a standard in the sense promolgated by, for example, the American National Standards Institute (ANSI) or the International Organization for Standards (ISO). It is, however, becoming recognized as an important proto-standard and has been applied by a diverse group. That diversity is both geographic and by subject.
Dublin Core tags can be read by a range of indexing and cataloging software packages, including SWISH-E, freeWAIS-sf2.0, GLIMPSE, HARVEST, or ISEARCH. In addition, perl script can be written to capture Dublin Core tags.
The Dublin Core set of fifteen elements includes:
Element: Title: formal resource name
Element: Creator: resource author - may be person, corporate author,
or service
Element: Subject: key words or phrases
Element: Description: abstracts, tables of contents, graphics, etc
Element: Publisher: Responsible party offering resource - person, organization,
etc
Element: Contributor: entity making content contribution - less than
creator
Element: Date: YYYY-MM-DD format
Element: Type: General categories - see DCT1 - Dublin Core Types |
http://dublincore.org/documents/1999/03/12/resource-typelist/|
Element: Format: "physical or digital manifestation of the resource"
Element: Identifier: e.g. URx, DOI. ISBN
Element: Source: Derivative source - formal indexing method prefered
Element: Language - language code (ISO639) and option country code
(ISO3166) -- e.g. en-us = American English
Element: Relation: reference to resource - prefer formal indexing
Element: Coverage: spatial, temoral, or jurisdiction extent or scope
of resource - prefer use of controlled vocabulary
Element: Rights: rights management statement
Source: Using Dublin Core |http://dublincore.org/documents/2001/04/12/usageguide/|
There are, of course, many sources in many places
in many languages for controlled vocabulary. Perhaps we are most familiar
with the Library of Congress Subject Headings (LCHS) and Classification.
Dublin Core recognizes and supports a wide range of thesauri. A good source
can be found at Traugott Koch, Controlled vocabularies, thesauri and classification
systems available in the WWW. DC Subject, available:
http://www.lub.lu.se/metadata/subject-help.html
Fortunately, the Dublin Core metatag "Schemes" indicate
which of the supported controlled vocabularies are used in any given document.
Consider the positive and negative implications of (a) the requirement or recommendation that a controlled vocabulary be used (b) without controlling which controlled vocabulary is to be used.
The Dublin Core metadata provided below were generated from the template provided by the Nordic Metadata Project at http://www.lub.lu.se/cgi-bin/nmdc.pl
Examine that metadata closely. It contains references to definitions of Dublic Core , definitions for each of the elements (eg Title), and encoding standards (eg Date).
<html>
<head>
<title> Web Management: Dublin Core </title>
<META NAME="DC.Title" CONTENT="Web Document Management">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#title"><META NAME="DC.Title.Alternative" CONTENT="LIS 5990 Summer 2000">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#title"><META NAME="DC.Creator.PersonalName" CONTENT="Koehler, Wallace">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#creator"><META NAME="DC.Creator.PersonalName.Address" CONTENT="wkoehler@ou.edu">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#creator"><META NAME="DC.Subject" CONTENT="metadata">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="bibliographic control">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="Web sites">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="WWW">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCSH) Dublin Core, metadata, resource discovery">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCSH) Internet">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCSH) Library Catalogs and Bulletins">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCSH) Indexing, Abstracting">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCSH) Classification and Notation">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCCS) ZA">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Subject" CONTENT="(SCHEME=LCCS) Z">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject"><META NAME="DC.Description" CONTENT="A library school web-based graduate course on bibliographic management of the WWW">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#description"><META NAME="DC.Publisher" CONTENT="MLIS Program, Valdosta State University">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#publisher"><META NAME="DC.Date" CONTENT="(SCHEME=ISO8601) 2000-05-01">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#date"><META NAME="DC.Type" CONTENT="Text.Index">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#type"><META NAME="DC.Format" CONTENT="(SCHEME=IMT) text/html">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#format">
<LINK REL=SCHEMA.imt HREF="http://sunsite.auc.dk/RFC/rfc/rfc2046.html"><META NAME="DC.Identifier" CONTENT="http://www.valdosta.edu/">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#identifier"><META NAME="DC.Language" CONTENT="(SCHEME=ISO639-1) en">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#language"><META NAME="DC.Coverage" CONTENT="metadata">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#coverage"><META NAME="DC.Rights" CONTENT="Copyright Wallace Koehler 2000 All Rights Reserved">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#rights"><META NAME="DC.Date.X-MetadataLastModified" CONTENT="(SCHEME=ISO8601) 2000-02-05">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#date">
</head>