Expressing Dublin Core™ metadata using the Resource Description Framework (RDF)

Table of contents

1. Introduction
2. Summary of the RDF conceptual model
3. Namespace abbreviations
4. Representing DCAM constructs using the RDF Model
5. Some notes on semantics

References> Acknowledgements> Appendix A: Examples

1. Introduction

This document provides recommendations for expressing DC metadata using RDF, the Resource Description Framework. It does this by describing how the features of the DCMI Abstract Model[ABSTRACT-MODEL] are represented using the RDF model (or abstract syntax), as defined by the RDF Concepts and Abstract Syntax specification [RDF-CONCEPTS]. It does not rely on any specific RDF syntax encoding, though examples using the RDF/XML Syntax Specification [RDF-SYNTAX-GRAMMAR] are provided in Appendix A. This allows Dublin Core™ metadata to be encoded using this specification in any RDF encoding syntax or other RDF representation system, such as RDF databases.

This Recommendation replaces the following DCMI document:

• Expressing Qualified Dublin Core™ in RDF / XML [DCQ-RDF-XML], a DCMI Proposed Recommendation from May 2002. This Recommendation makes the following DCMI document obsolete (while not contradicting it):

• Expressing Simple Dublin Core™ in RDF/XML [DCMES-XML], a DCMI Recommendation from July 2002.

The document "Notes on DCMI specifications for Dublin Core™ metadata in RDF" [DC-RDF-NOTES] describes in more detail how this draft relates to the earlier specifications.

Many of the examples in this document make use of DCMI metadata terms [DCMI-TERMS]. See also the DCMI RDF Schemas for the DCMI terms [DCMI-SCHEMAS].

2. Summary of the RDF conceptual model

The RDF conceptual model is specified in the RDF Concepts and Abstract Syntax specification [RDF-CONCEPTS]. It is a relatively simple model, consisting of the following fundamentals:

• An RDF graph is a set of RDF triples

• An RDF triple has three components:

  • an RDF subject, which is an RDF URI reference or a blank RDF node

  • an RDF predicate, which is an RDF URI reference

  • an RDF object, which is an RDF URI reference, a blank RDF node or an RDF literal

• An RDF literal can be of two kinds:

  • an RDF plain literal is a character string with an optional associated language tag describing the language of the character string

  • an RDF typed literal is a character string with an associated RDF datatype URI. An RDF datatype defines the syntax and semantics of a set of character strings that represent data such as booleans, integers, dates, etc. These RDF triples are connected into RDF graphs, so that a non-literal RDF object of one RDF triple may be the RDF subject of another triple.

We will use diagrams to illustrate RDF graphs (for namespace abbreviations, see Section 3). A simple triple may look like in the following figure:

The structure of an RDF triple. In this figure, the RDF object is an RDF typed literal

While a graph consisting of three triples may look like the following:

An RDF graph consisting of three triples, connected via a blank RDF node.

For further information on RDF, see the RDF Concepts and Abstract Syntax specification [RDF-CONCEPTS], the RDF Vocabulary Description Language [RDF-SCHEMA], andhttp://www.w3.org/RDF/.

3. Namespace abbreviations

The following namespace abbreviations will be used in this document:

See also the DCMI RDF Schemas for the DCMI terms [DCMI-SCHEMAS].

4. Representing DCAM constructs using the RDF Model

This section describes how each of the constructs in the DCAM are represented in RDF. The RDF notions used here are defined in the RDF Concepts and Abstract Syntax specification [RDF-CONCEPTS] and the RDF Vocabulary Description Language [RDF-SCHEMA].

4.1 Descriptions and resources

DCAM descriptions and resources are represented in the following way:

• A DCAMdescriptionis represented using an RDF graph originating from a single RDF subject.
• A DCAM described resourceis represented by the RDF subject at the root of this RDF graph.
• If a DCAMdescribed resource URIis available in the description, it should be used as the RDF URI reference of the RDF subject at the root of the RDF graph. Otherwise, the RDF subject should be a blank RDF node. Syntaxes may choose to use anonymous identifiers (such as the rdf:nodeID construct) to implement this.

4.2 Statements, properties and values

A DCAMstatementis represented using an RDF triple comprising:

• an RDF subject that represents the DCAM resource
• an RDF predicate that is the DCAMproperty URI
• an RDF object that corresponds to the DCAM value surrogate. This RDF node will be referred to below as thevalue RDF node.

4.3 Non-literal值代理人

When the DCAM value surrogate is a non-literal value surrogate, the value RDF node is an RDF URI refence or a blank RDF node, with the characteristics given below.

下图展示了主要特征s of the RDF representation of non-literal value surrogates.

DC-TEXT representation	RDF graph
@prefix dcterms: . @prefix ex: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:subject ) ValueURI ( ) VocabularyEncodingSchemeURI ( ex:ExampleSubjects ) ValueString ( "Biology" language ( "en" ) ) ValueString ( "EA32" syntaxEncodingSchemeURI ( ex:SubjectEncoding ) ) ) ) )
The representation of the DCAM constructs in the case of a non-literal value surrogate. The notation "@en" represents an RDF language tag, while "^^ex:SubjectEncoding" represents an RDF Datatype.

4.4 Value URIs

A DCAMvalue URIis represented using the RDF URI Reference of thevalue RDF node. If no value URI is given, the value RDF node is a blank node.

4.5 Vocabulary Encoding Scheme URIs

A DCAMvocabulary encoding scheme URIis represented using an RDF triple comprising:

• an RDF subject that is thevalue RDF node.

• an RDF predicate that isthe RDF URI referencedcam:memberOf

• an RDF object with a corresponding RDF URI Reference being the DCAM vocabulary encoding scheme URI

4.6 Value Strings, Value String Languages and Syntax Encoding Scheme URIs

A DCAMvalue stringis represented using an RDF triplecomprising:

• an RDF subject that is thevalue RDF node

• an RDF predicate that is the RDF URI reference``rdf:value

• an RDF object that is an RDF Literal node``(either an RDF plain literal or RDF typed literal), containing the DCAM value string.

A DCAM _value string language_is represented using a language tag associated with a RDF plain literal occurring as the RDF object of this RDF triple. The language tag is constructed as defined by RFC-3066, normalized to lowercase.

A DCAMsyntax encoding scheme URIis represented using the RDF datatype URI associated with a RDF typed literal occurring as the RDF object of this RDF triple.

4.7 Literal value surrogates

When the DCAM value surrogate is a literal value surrogate, the value RDF node is an RDF literal node, with exactly the same chararacteristics as in the case of DCAM value strings above.

The following diagrams illustrate the main features of the RDF representation of literal value surrogates.

DC-TEXT representation	RDF graph
@prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) literalValueString ( "Learning Biology" language ( "en" ) ) ) ) )
The representation of the DCAM constructs in the case of a literal value surrogate with a language tag. The notation "@en" represents an RDF language tag.

The following diagram illustrates the second case, using RDF typed literals:

DC-TEXT representation	RDF graph
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix ex: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( ex:age ) literalValueString ( "43" SyntaxEncodingSchemeURI ( xsd:int ) ) ) ) )
The representation of the DCAM constructs in the case of a literal value surrogate with a Syntax Encoding Scheme URI. The notation"^^xsd:int" represents an RDF Datatype.

4.8 Description sets

A DCAMdescription setis represented as an RDF graphthat includes one or more DCAM descriptions as described above.

4.9 Describing values

A DCAM value can be further described in a separate DCAM description within the same DCAM description set. This is represented in RDF by letting the value RDF node be the root of an RDF graph representing any DCAM statements in the DCAM description of the value. Thus, the value RDF nodewill be the RDF subject of a set of triples representing the DCAM description of the value.

5. Some notes on semantics

5.1 RDF semantics and the DCMI Abstract Model

The RDF expression of the DCMI Abstract Model has a special status among the DCMI encoding specifications. As the semantics of the notions DCMI Abstract Model is based on the semantics of the corresponding notions in RDF (as defined by [RDF-SEMANTICS]), it is of fundamental importance that the RDF expression preserves any semantics of the DCAM. Also, any valid inferences that can be made using RDF semantics need to be valid when interpreted in terms of the DCMI Abstract Model. These requirements have not yet been formalized, but are thought to be reasonable and relatively straightforward. Among other things, formulating them would require defining a reverse mapping from RDF to the DCMI Abstract Model.

5.2 Value Classes

The class or type of a value can be inferred in several ways:

• Using the range of the corresponding property. For example, if the range of the propertyex:ownerisex:Person, it can be inferred that all values of theex:ownerproperty are of typeex:Person.

• Using an explicitrdf:typestatement on the value. For example, if a resource has the propertyrdf:typewith the valueex:Person, the value can be inferred to be of the typeex:Person.

• Using knowledge from the application context. For example, an application might know that it only manages reources of typeex:Book, even though this is not part of the metadata itself.

It is recommended that RDF applications use explicitrdf:typetriples, even if that means creating a separate DCAM description of the value.

The propertydcterms:type语义相似吗rdf:type. At the time of writing, the precise relationship between those properties remains undecided.
It is recommended that RDF applications implementing this specification primarily use and understandrdf:typein place ofdcterms:type当表达Dublin Core™ metadata in RDF, as most RDF processors come with built-in knowledge ofrdf:type.

References

ABSTRACT-MODEL

DCMI Abstract Model
<//www.voudr.com/specifications/dublin-core/abstract-model/>

DC-RDF-NOTES

Notes on DCMI specifications for Dublin Core™ metadata in RDF
<//www.voudr.com/specifications/dublin-core/dc-rdf-notes/2008-01-14/>

DCMES-XML

Expressing Simple Dublin Core™ in RDF/XML
<//www.voudr.com/specifications/dublin-core/dcmes-xml/>

DCQ-RDF-XML

Expressing Qualified Dublin Core™ in RDF / XML
<//www.voudr.com/specifications/dublin-core/dcq-rdf-xml/>

DCMI-TERMS

DCMI Metadata Terms
<//www.voudr.com/specifications/dublin-core/dcmi-terms/>

DCMI-SCHEMAS

DCMI term declarations represented in RDF schema language
<//www.voudr.com/schemas/rdfs/>

DC-TEXT

DC-TEXT: A Text Syntax for Dublin Core™ Metadata
<//www.voudr.com/specifications/dublin-core/dc-text/>

RDF-CONCEPTS

Resource Description Framework (RDF): Concepts and Abstract Syntax
<http://www.w3.org/TR/rdf-concepts/>

RDF-SCHEMA

RDF Vocabulary Description Language 1.0: RDF Schema
<http://www.w3.org/TR/rdf-schema/>

RDF-VALIDATOR

W3C RDF Validation Service

<http://www.w3.org/RDF/Validator/>

RDF-SYNTAX-GRAMMAR

RDF/XML Syntax Specification (Revised)
<http://www.w3.org/TR/rdf-syntax-grammar/>

RDF-SEMANTICS

RDF Semantics
<http://www.w3.org/TR/rdf-mt/>

Acknowledgements

Thanks to Tom Baker, the members of the DC Usage Board and the members of the DC Architecture Working Group for their comments on previous versions of this document.

Appendix A: Examples

The following examples use the DC-TEXT syntax [DC-TEXT] for describing examples of Dublin Core™ metadata. The corresponding RDF graph is then presented, using the RDF/XML syntax [RDF-SYNTAX-GRAMMAR]. Familiarity with the "striped" RDF/XML syntax is assumed. The W3C RDF Validator [RDF-VALIDATOR] service may be used to convert these RDF/XML samples to triples and graphs.

@prefix dcterms:  .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( dcterms:subject )
ValueURI (  )
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/">

@prefix dcterms:  .
@prefix ex:  .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( dcterms:subject )
VocabularyEncodingSchemeURI ( ex:MyVocab )
ValueString ( "Ornitology" )
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:ex="http://example.org/taxonomy/"
xmlns:dcam="http://purl.org/dc/dcam/">





Ornitology

@prefix dcterms:  .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( dcterms:title )
literalValueString ( "Learning Biology"
language ( "en" )
)
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/">


Learning Biology

@prefix dcterms:  .
@prefix ex:  .
@prefix xsd: > .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( ex:age )
literalValueString ( "43"
SyntaxEncodingSchemeURI ( xsd:int )
)
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:ex="http://example.org/ns#">



43

@prefix dcterms:  .
@prefix ex:  .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( dcterms:subject )
ValueURI (  )
VocabularyEncodingSchemeURI ( ex:ExampleSubjects )
ValueString ( "Biology"
language ( "en" )
)
ValueString ( "Biologi"
language ( "sv" )
)
ValueString ( "EA32"
SyntaxEncodingSchemeURI ( ex:SubjectEncoding )
)
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:ex="http://example.org/taxonomy/"
xmlns:dcam="http://purl.org/dc/dcam/">




rdf:resource="http://example.org/taxonomy/ExampleSubjects"/>
Biology
Biologi
rdf:datatype="http://example.org/taxonomy/SubjectEncoding">
EA32

@prefix dcterms:  .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .

DescriptionSet (
Description (
ResourceURI (  )
Statement (
PropertyURI ( dcterms:creator )
ValueURI (  )
ValueString ( "John Smith" )
)
)

Description (
ResourceURI (  )
Statement (
PropertyURI ( foaf:phone )
ValueURI (  )
)
Statement (
PropertyURI ( dcterms:type )
ValueURI ( foaf:Person )
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:foaf="http://xmlns.com/foaf/0.1/">




John Smith

@prefix dcterms:  .

DescriptionSet (
Description (
Statement (
PropertyURI ( dcterms:subject )
ValueURI (  )
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/">

@prefix dcterms:  .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .

DescriptionSet (
Description (
Statement (
PropertyURI ( dcterms:creator )
ValueId ( "john" )
ValueString ( "John Smith" )
)
)

Description (
ResourceId ( "john" )
Statement (
PropertyURI ( foaf:phone )
ValueURI (  )
)
Statement (
PropertyURI ( dcterms:type )
ValueURI ( foaf:Person )
)
)
)

http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:foaf="http://xmlns.com/foaf/0.1/"




John Smith