An Overview of Dublin Core Metadata Schema Registry Shigeo Sugimoto Research Center for Knowledge Communities Grad. School of Library, Information and Media Studies University of Tsukuba Tsukuba, Ibaraki, Japan sugimoto @ slis. tsukuba. ac. jp
Agenda/Outline Introduction to Dublin Core Registry Demo by Snapshots History Functions Multi-linguality Issues Demo by Snapshots Some New Features of Dublin Core DC 15 elements in two namespaces Dublin Core Abstract Model Application Profiles Summary
History Project started at Asian Institute of Technology (AIT), Thailand under supervision of Thomas Baker in 1998 DCMI Registry WG since 1999 WG home: http://dublincore.org/groups/registry/ The DCMI registry provides definitions of DCMI Terms Registry was moved from OCLC to U.Tsukuba in February 2008 http://dcmi.kc.tsukuba.ac.jp/dcregistry/
Basic Functions Search and Browse Dublin Core Terms User Interface on the Web Application Interfaces Dublin Core Terms expressed in RDF Application Interfaces that return RDF descriptions Vocabulary Maintenance Tool Used by Usage Board Multilingual Feature 25 languages
Application Interface Provides Registry application interface - a collection of Web services SOAP and REST. Return results in RDF/XML format See Help page from DCMI Registry
Application Interface Services listItemSummary listSupportedLanguage listItemDetail getUpdates listElements listElementRefinements listVocabularyTerms listEncodingSchemes
Multi-lingual Issues Translation of the DCMI terms was recognized as an important issue for DCMI from very early stage of the development of DCMI terms. Translations of DCMI terms have been done by volunteers A few national standards A few official local affiliates Multi-lingual functions Browse Search Translation Support
Demo by Snapshots
Link to DCMI Registry
Browse | Search
Pull Down Menu
Summary of All Terms Properties Classes Vocabulary Encoding Schemes Syntax Encoding Schemes
Click on “Browse” button to browse “Summary of All Terms”
Click on “dc:contributor”
Scroll Down
Language Preference
Language Preference 25 languages Select Japanese
A Note on Translations Not all of translations are up to date.
Display in Japanese
Click on dc:contributor
Display in Japanese
Snap shots of multilingual output
Snap shots of multilingual output
Display in RDF/XML
RDF/XML output
Display in N-TRIPLE
N triple
Display in N3
N3
Contents of DCMI Registry
Contents of DCMI Registry
Contents of DCMI Registry
Contents of DCMI Registry
Contents of DCMI Registry
Contents of DCMI Registry 71 properties 15 properties in “dc” namespace 56 properties in “dcterms” namespace 35 classes 9 vocabulary encoding schemes 11 syntax encoding schemes 4 collections
A New Feature of Dublin Core Why two namespaces? Each of the Dublin Core 15 elements appears two times in the list “dc” namespace as a legacy namespace “dcterms” namespace for all terms Re-definition of Dublin Core 15 elements Visible through the registry
Go back to All Terms Page
Two “Date” Elements
“Date” element in different namespaces
Two “Contrubutor” Elements
Only one “Audience” element
dc: contributor and dcterms:contributor
Contributor in “dc” namespace dc: contributor and dcterms:contributor Contributor in “dc” namespace
dc: contributor and dcterms:contributor
dc: contributor and dcterms:contributor Contributor in “dcterms” namespace
Examples of a Contributor Note A second property with the ----- “dc” “dcterms” URI http://purl.org/dc/elements/1.1/contributor http://purl.org/dc/terms/contributor Label Contributor Definition An entity responsible Comment Examples of a Contributor Note A second property with the ----- Namespace http://purl.org/dc/elements/1.1/ http://purl.org/dc/terms/ Type of Term Property Has Range dcterms:Agent Version contributor-006 contributorT-001 Date Issued 1999-07-02 2008-01-14 Date Modified Refines ------ dc:contributor Is Refined By dcterms:contributor dcterms:creator
Comparison of dc:contributer and dcterms:contributor URI http://purl.org/dc/elements/1.1/contributor http://purl.org/dc/terms/contributor Label Contributor Definition An entity responsible Comment Examples of a Contributor Examples of a Contributor i Note A second property with the ----- Namespace http://purl.org/dc/elements/1.1/ http://purl.org/dc/terms/ Type of Term Property Has Range dcterms:Agent Version contributor-006 contributorT-001 Date Issued 1999-07-02 2008-01-14 Date Modified Refines ------ dc:contributor Is Refined By dcterms:contributor dcterms:creator
Comparison of dc:contributer and dcterms:contributor URI http://purl.org/dc/elements/1.1/contributor http://purl.org/dc/terms/contributor Name space http://purl.org/dc/elements/1.1/ http://purl.org/dc/terms/ Has Range ----- dcterms:Agent Refines ------ dc:contributor Is Refined By dcterms:contributor dcterms:creator
Relationships among terms No relationship defined dc:contributor dc:creator Is refined by/Refines dcterms:creator dcterms:contributor Is refined by/Refines
Relationships among terms Re-definition of the 15 elements and other elements allows to use legacy definition of Simple Dublin Core elements (ISO 15836) allows to define relationships among the re-defined 15 elements as well as all other elements allows to include domain/range definition of elements (i.e. properties)
Some other new features DCMI Abstract Model (DCAM) DCAM defines basic concepts and constructs of Dublin Core and relationships among them The DCAM document [3] is provided to Specify the components and constructs used in Dublin Core metadata Define the nature of the components used and describes how those components are combined to create information structures Provide an information model which is independent of any particular encoding syntax
Some other new features Singapore Framework [4] (Re-)Definition of Application Profiles http://www.dublincore.org/documents/singapore-framework/ Five components of an Application Profile Functional requirements (mandatory) describe the functions that the application profile is designed to support Domain model (mandatory) defines the basic entities described by the application profile and their fundamental relationships
Some other new features Singapore Framework Description Set Profile (DSP) (mandatory) define a set of metadata records that are valid instances of an application profile. Usage guidelines (optional) describe how to apply the application profile, how the used properties are intended to be used in the application context etc. Encoding syntax guidelines (optional) describe any application profile-specific syntaxes and/or syntax guidelines, if any.
Description Set Profile [5] Description Set Profile is defined as a set of Description Template A Description Template is a set of properties specified with structural and value constraints Structural constraints: mandatory levels, cardinality, etc. Value constraints: classes or types of values associated with the property
A Simplified Structural View of a an Application Profile Functional requirements Usage guidelines Domain model Encoding syntax guidelines Description Set Profile Description Template Description Template Description Template Terms
A Simplified Structural View of a an Application Profile A Description Set termA: Mandatory termC: Optional Repeatable termX: Mandatory Repeatable termZ: Mandatory if applicable termA termB termC termX termY termZ Metadata Vocabulary 2 (Metadata Element Set) Metadata Vocabulary 1 (Metadata Element Set)
A Simplified Structural View of an Application Profile A Description Set termA: Mandatory termC: Optional Repeatable termX: Mandatory Repeatable termZ: Mandatory if applicable A Description Set is defined using metadata terms defined in one or more metadata vocabularies (element sets). termA termB termC termX termY termZ Metadata Vocabulary 2 (Metadata Element Set) Metadata Vocabulary 1 (Metadata Element Set)
Summary DCMI Registry stores/provides DCMI terms Properties, Classes, etc. Dublin Core recommends to define metadata schemas reusing existing metadata terms, i.e. Mixing and Matching Metadata Schemas Metadata Schema Registry is a crucial service to enhance Mixing and Matching
Summary DCMI Registry provides only terms defined by DCMI and many links to external resources and terms User-friendly function to connect registries and information resources would be required to enhance usability for human users DCMI Registry provides only canonical information, i.e. information encoded in RDF Schema Users would want to get another type of information, e.g., good practices and explanations of terms with good examples.
References Dublin Core Metadta Initiative http://www.dublincore.org/ DCMI Registry http://dcmi.kc.tsukuba.ac.jp/dcregistry/ Dublin Core Abstract Model http://www.dublincore.org/documents/abstract-model/ Singapore Framework http://www.dublincore.org/documents/singapore-framework/ Description Set Profile, http://dublincore.org/documents/2008/03/31/dc-dsp/
appendix A Grahic Viewer of NDLSH (National Diet Library Subject Heading) http://raus.slis.tsukuba.ac.jp/ Example graph Example XML
A Graphic View of term “Tosyokan” (library in Japanese) A node represents a term Coloured arrows mean BT, NT, RT relatiponships.
<?xml version="1.0" encoding="UTF-8" ?> - <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:slis="http://juror.slis.tsukuba.ac.jp/ns/tsukubaterms#" xmlns:dc="http://purl.org/dc/elements/1.1/"> - <skos:Concept rdf:ID="http://raus.slis.tsukuba.ac.jp/ndlsh/00573385"> <dc:identifier>00573385</dc:identifier> <skos:prefLabel xml:lang="ja">図書館〈地理区分〉</skos:prefLabel> - <slis:annotation> - <slis:JapaneseTransliteration> <slis:label xml:lang="ja">図書館〈地理区分〉</slis:label> <slis:transcription xml:lang="ja">トショカン</slis:transcription> </slis:JapaneseTransliteration> </slis:annotation> <skos:altLabel xml:lang="ja">公共図書館</skos:altLabel> <slis:label xml:lang="ja">公共図書館</slis:label> <slis:transcription xml:lang="ja">コウキョウトショカン</slis:transcription> <skos:altLabel>Libraries</skos:altLabel>
<skos:narrower rdf:resource="http://raus. slis. tsukuba. ac <<<snip>>> <skos:related rdf:resource="http://raus.slis.tsukuba.ac.jp/ndlsh/00573392" /> <skos:related rdf:resource="http://raus.slis.tsukuba.ac.jp/ndlsh/00573399" /> <skos:related rdf:resource="http://raus.slis.tsukuba.ac.jp/ndlsh/00573408" /> <skos:related rdf:resource="http://raus.slis.tsukuba.ac.jp/ndlsh/00573391" /> <skos:related rdf:resource="http://raus.slis.tsukuba.ac.jp/ndlsh/00573397" /> <dc:relation rdf:datatype= "http://juror.slis.tsukuba.ac.jp/ns/tsukubaterms#NDC">010</dc:relation> <dc:relation rdf:datatype= "http://juror.slis.tsukuba.ac.jp/ns/tsukubaterms#NDLC">UL11</dc:relation> </skos:Concept> </rdf:RDF>