TITLE: | Draft Expressing Dublin Core Metadata Using Topic Maps |
SOURCE: | Mr. Steve Pepper; Mr. Motomu Naito; Mr. Patrick Durusau |
PROJECT: | WD 29111: Information Technology - Topic Maps - Expressing Dublin Core Metadata using Topic Maps |
PROJECT EDITOR: | Dr. Sam Gyun Oh; Mr. Steve Pepper |
STATUS: | Draft |
ACTION: | Review in preparation for WG3 meeting |
DATE: | 2007-07-04 |
DISTRIBUTION: | SC34 and Liaisons |
REPLY TO: |
Dr. James David Mason (ISO/IEC JTC 1/SC 34 Secretariat - Standards Council of Canada) Crane Softwrights Ltd. Box 266, Kars, ON K0A-2E0 CANADA Telephone: +1 613 489-0999 Facsimile: +1 613 489-0995 Network: jtc1sc34@scc.ca http://www.jtc1sc34.org |
The Dublin Core Metadata Initiative (DCMI) has produced one of the most successful vocabularies for expressing document metadata and is in widespread use on the World Wide Web, in libraries, and in many other areas. DCMI vocabularies are defined as sets of abstract elements and terms; the syntactic expression of these elements and terms is technology dependent.
This Technical Report defines a standard way of expressing Dublin Core metadata using ISO/IEC 13250 Topic Maps. Its purpose is to ensure a uniform approach to the application of Dublin Core among users of Topic Maps and thus enable seamless integration and improved knowledge aggregation. It covers both the general case of expressing Dublin Core metadata sets and the specific case of assigning Dublin Core metadata to topic maps, i.e., to topic maps viewed as what Dublin Core calls “described resources”.
All four term sets described in [DCMT] are covered, i.e., the Dublin Core Metadata Element Set, Other Elements and Element Refinements, Encoding Schemes, and the DCMI Type Vocabulary.
For the purposes of this Technical Report the definitions given in ISO/IEC 13250-2 apply.
The following terms defined in [DCAM] are reproduced here for convenience:
This Clause describes basic equivalences between the Dublin Core Abstract Model and the Topic Maps Data Model and how concepts are mapped from the one to the other.
For the purpose of this Technical Report, a resource in Dublin Core is deemed to be equivalent to a subject in Topic Maps.
The assignment of metadata in the form of property-value pairs to Dublin Core resources is deemed to be the equivalent of making statements about a subject in Topic Maps.
Associations are used to represent property-value pairs whenever possible, which is to say in all cases except those case of:
elements that are naming properties (which are represented as topic names);
elements whose values consist of descriptive text or structured data types (which are represented as occurrences).
All such associations are binary and use the following pair of role types:
Role played by the described resource: http://psi.topicmaps.org/iso29111/resource
Role played by the resource that is the value of the property-value pair: http://psi.topicmaps.org/iso29111/value
When assigning Dublin Core metadata to a topic map, the topic map must first be reified. Statements are then made about the resulting topic.
[DCAM] describes models for resources described by descriptions and for metadata description sets. The concepts of these models are mapped to concepts of the Topic Maps Data Model as follows:
A DC described resource is represented by a topic item.
A DC property-value pair is represented by a Topic Maps statement (i.e., a name item, occurrence item or association item, as specified in Clause 4).
The property of a DC property-value pair is represented by the [type] property of the statement to which it gives rise.
The value of a DC property-value pair is represented either by a topic item or by the [value] property of a name or occurrence item, as specified in Clause 4.
A DC vocabulary encoding scheme or syntax encoding scheme is represented by the [datatype] property of an occurrence item.
A DC value string language is represented by a [scope] property that consists of a single topic representing the language in question.
This Clause specifies the Topic Maps representation of every element and term in [DCMT].
The following table shows the kind of Topic Maps construct to which each term in the Dublin Core Metadata Element Set should be mapped. The prefix dc is used to represent the URI http://purl.org/dc/elements/1.1/.
DC Term Name |
TM representation |
---|---|
contributor |
association of type dc:contributor |
coverage |
association of type dc:coverage |
creator |
association of type dc:creator |
date |
occurrence of type dc:date |
description |
occurrence of type dc:description |
format |
association of type dc:format |
identifier |
occurrence of type dc:identifier |
language |
association of type dc:language |
publisher |
association of type dc:publisher |
relation |
association of type dc:relation |
rights |
occurrence of type dc:rights |
source |
association of type dc:source |
subject |
association of type dc:subject |
title |
name of type dc:title |
type |
association of type dc:type |
The following table shows the kind of Topic Maps construct to which each term in the metadata set Other Elements and Element Refinements should be mapped. The prefix dct is used to represent the URI http://purl.org/dc/terms/.
DC Term Name |
TM representation |
---|---|
abstract |
occurrence of type dct:abstract |
accessRights |
occurrence of type dct:accessRights |
accrualMethod |
association of type dct:accrualMethod |
accrualPeriodicity |
association of type dct:accrualPeriodicity |
accrualPolicy |
association of type dct:accrualPolicy |
alternative |
name of type dct:alternative |
audience |
association of type dct:audience |
available |
occurrence of type dct:available |
bibliographicCitation |
occurrence of type dct:bibliographicCitation |
conformsTo |
association of type dct:conformsTo |
created |
occurrence of type dct:created |
dateAccepted |
occurrence of type dct:dateAccepted |
dateCopyrighted |
occurrence of type dct:dateCopyrighted |
dateSubmitted |
occurrence of type dct:dateSubmitted |
educationLevel |
occurrence of type dct:educationLevel |
extent |
occurrence of type dct:extent |
hasFormat |
association of type dct:hasFormat |
hasPart |
association of type dct:hasPart |
hasVersion |
association of type dct:hasVersion |
instructionalMethod |
occurrence of type dct:instructionalMethod |
isFormatOf |
association of type dct:isFormatOf |
isPartOf |
association of type dct:isPartOf |
isReferencedBy |
association of type dct:isReferencedBy |
isReplacedBy |
association of type dct:isReplacedBy |
isRequiredBy |
association of type dct:isRequiredBy |
issued |
occurrence of type dct:issued |
isVersionOf |
association of type dct:isVersionOf |
license |
occurrence of type dct:license |
mediator |
association of type dct:mediator |
medium |
occurrence of type dct:medium |
modified |
occurrence of type dct:modified |
provenance |
occurrence of type dct:provenance |
references |
association of type dct:references |
replaces |
association of type dct:replaces |
requires |
association of type dct:requires |
rightsHolder |
association of type dct:rightsHolder |
spatial |
association of type dct:spatial |
tableOfContents |
occurrence of type dct:tableOfContents |
temporal |
association of type dct:temporal |
valid |
occurrence of type dct:valid |
Each term in the metadata set Encoding Schemes is represented by a topic whose subject identifier is the same as the URI of the term in question.
Each term in the metadata set DCMI Type Vocabulary is represented by a topic whose subject identifier is the same as the URI of the term in question.