Dublin Core
Dublin Core
About DCMI Themes Members Governing Board Usage Board Directorate
Twitter YouTube GitHub RSS Feed

Expressing Dublin Core™ Description Sets using XML (DS-DS-XML)

Expressing Dublin Core™ Description Sets using XML (DC-DS-XML)

Creator: Pete Johnston
Eduserv Foundation, UK
Creator: Andy Powell
Eduserv Foundation, UK
Date Issued: 2008-09-01
Identifier: //www.voudr.com/specifications/dublin-core/dc-ds-xml/2008-09-01/
Replaces: //www.voudr.com/specifications/dublin-core/dc-xml/2006-05-29/
Is Replaced By: Not applicable
Latest Version: //www.voudr.com/specifications/dublin-core/dc-ds-xml/
Status of Document: This is a DCMIProposed Recommendation
Description of Document: This document specifies an XML format for representing a Dublin Core™ metadata description set. It supports all the features of the description set described by the DCMI Abstract Model. The XML format is known as "DC-DS-XML".

Table of contents

  1. Introduction
  2. The DCMI Abstract Model and DC-DS-XML
  3. Features of the DC-DS-XML Syntax
  4. The DC-DS-XML Syntax
  5. Appendix A. DC-TEXT Representation of Examples
  6. Appendix B. RDF/XML Representation of Examples
  7. Notes
  8. References
  9. Acknowledgements

1. Introduction

This document specifies an XML format for representing a DC metadatadescription set. The XML format is known as "DC-DS-XML". (The "DS" is intended as an abbreviation fordescription set.)

The "Description Set Model" of the DCMI Abstract Model [ABSTRACT-MODEL] describes the constructs that make up a DC metadatadescription set. In order to represent a DC metadata description set in an XML document those constructs have to be represented as components in that XML document, i.e. as XML elements and XML attributes, XML element names and XML attribute names, and as XML element content and XML attribute values.

1.1 Design Considerations

The DC-DS-XML format described in this document was developed using the following design considerations:

  • The format should provide a serialisation of all the features of the "Description Set Model" of the Abstract Model, i.e. it should be possible to represent all the constructs that make up a DC metadatadescription set. (See Note 1).

  • The format is not required to address the features of the "Vocabulary Model" of the Abstract Model. For example, it is not required to express subproperty relationships between properties, subclass relationships between classes, etc.

  • The format should be easily usable with XML-based specifications such as XPath, XPointer and XQuery, i.e. for each construct in the Abstract Model there should be a mapping to exactly one construct in the XML syntax.

  • The format should not be dependent on features of a single XML Schema language.

  • It should be possible to describe the format using W3C XML Schema [XMLSCHEMA], but it is not a requirement that when the format is used to serialise _description sets_conforming to a DC Application Profile [DCAP], all the structural constraints expressed in the corresponding Description Set Profile [DSP] are captured using W3C XML Schema.

1.2 DC-DS-XML and GRDDL

The W3C RecommendationGleaning Resource Descriptions from Dialects of Languages[GRDDL] describes a set of conventions for associating an XML document with an algorithm for the extraction of a set of RDF triples from that document. One of the mechanisms defined by GRDDL is the association of a Namespace Transformation with an XML namespace.

A GRDDL Namespace Transformation is provided for the XML Namespace associated with the DC-DS-XML format. That transformation generates RDF graphs compatible with the recommendations of the DCMI RecommendationExpressing Dublin Core™ metadata using the Resource Description Framework (RDF)[DC-RDF].

2. The DCMI Abstract Model and DC-DS-XML

According to the "Description Set Model" of the DCMI Abstract Model [ABSTRACT-MODEL], a DCdescription sethas the following structure:

  • adescription setis made up of one or moredescriptions

  • adescriptionis made up of

    • zero or onedescribed resource URIand

    • one or morestatements

  • astatementis made up of

    • exactly oneproperty URIand

    • exactly onevalue surrogate

  • avalue surrogateis either aliteral value surrogateor anon-literal value surrogate

    • aliteral value surrogateis made up of

      • exactly onevalue string

    • anon-literal value surrogateis made up of

      • zero or onevalue URIs

      • zero or onevocabulary encoding scheme URIs

      • zero or morevalue strings

  • avalue stringis either aplain value stringor atyped value string

    • aplain value stringmay be associated with avalue string language

    • atyped value stringis associated with asyntax encoding scheme URI

  • anon-literal valuemay be described by anotherdescription

The DC-DS-XML format described in this document implements all the features of the DCAM "description set model".

3. Features of the DC-DS-XML Syntax

3.1 URIs in DC-DS-XML

The Abstract Model uses Uniform Resource Identifiers (URIs) [RFC3986] to refer both to the resources described and to metadata terms (properties,classes,vocabulary encoding schemesandsyntax encoding schemes).

In DC-DS-XML, URIs are encoded as URI references, used as XML attribute values. A URI reference is either a URI or a relative reference [RFC3986]. Later sections of this document describe the use of those different XML attributes in detail. The purpose of this section is to make some general points about the representation of these URIs in DC-DS-XML.

The URI may be represented in full. The following example shows a URI as the value of thedcds:propertyURIattribute:

XML Example 1: URI as attribute value

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   以便决定:propertyURI = " http://purl.org/dc/terms/title "> DCMI Home Page

The representation of the URI may be abbreviated through the use of an XML entity reference as follows, for example:

XML Example 2: URI作为属性值(与XML实体参考性用途e)

< ?xml version="1.0" encoding="UTF-8" ?>  ]>    dcds:propertyURI="&dcterms;title"> DCMI Home Page

For all of the attributes in DC-DS-XML which have URIs as values, the value may also be a relative reference. The relative reference is resolved relative to a base URI, obtained either from the value of anxml:baseattribute or from the URI of the document itself. In the following example, the value of thedcds:propertyURIattribute is a relative reference. It is resolved relative to the base URI provided by thexml:baseattribute to obtain a target URI ofhttp://purl.org/dc/terms/title:

XML Example 3: Relative reference as attribute value

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSetxml:base="http://purl.org/dc/terms/"xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   dcds:propertyURI="title"> DCMI Home Page

4. The DC-DS-XML Syntax

4.1 Encoding a Description Set: The Description Set Element

Adescription setis a set of one or moredescriptions.

In DC-DS-XML, adescription setis represented by an XML element known as a Description Set Element (See Note 2). A DC-DS-XML instance represents a single DCdescription set, so has exactly one Description Set Element.

A Description Set Element has an expanded name (XML Namespace Name/local name pair) with the XML Namespace Namehttp://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/and local namedescriptionSet.

In the examples presented in this document, the XML Namespace Namehttp://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/is always associated with the prefix "dcds". For convenience, after this point, the names of XML elements and XML attributes are presented in the text as XML QNames (e.g.dcds:descriptionSet,dcds:resourceURI), rather than as expanded names, but the prefix used is not significant.

XML Example 4: the Description Set Element

< ?xml version="1.0" encoding="UTF-8" ?> xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page

The Description Set Element must contain one or more Description Elements.

4.2 Encoding a Description: The Description Element

Adescriptionis a set of one or morestatementsabout a resource.

In DC-DS-XML, adescriptionis represented by an XML element known as a Description Element. A Description Element is a child element of a Description Set Element and has the namedcds:description.

The following example shows adescription setconsisting of a singledescription:

XML Example 5: the Description Element

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">  DCMI Home Page

Adescription setmay contain multipledescriptions.

In DC-DS-XML, eachdescriptionis represented by a separate Description Element. The order of the Description Elements within a Description Set Element is not significant.

The following example shows adescription setconsisting of twodescriptions:

XML Example 6: Multiple Description Elements

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">  DCMI Home Page  UKOLN Home Page

The encoding ofdescription setswith multipledescriptionsis described further in Section 4.6.

A Description Element may have a Described Resource URI attribute and must contain one or more Statement Elements.

4.2.1 The

Described Resource URI

Adescriptionmay have an associateddescribed resource URI.

In DC-DS-XML, adescribed resource URIis represented as the value of an XML attribute of the Statement Element. The attribute has the namedcds:resourceURI.

The examples below show adescriptionwith thedescribed resource URI//www.voudr.com/pages/home.

XML Example 7: The Resource URI Attribute

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">  dcds:resourceURI="//www.voudr.com/www/pages/home">  DCMI Home Page

Note that the representation of thedescribed resource URImay be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on URIs in DC-DS-XML).

4.3 Encoding a Statement: The Statement Element

Adescriptionis made up of one or morestatements.

In DC-DS-XML, each child XML element of a Description Element represents a singlestatementand is known as a Statement Element. A Statement Element always has the namedcds:statement.

The following example shows adescription setwith a singledescriptionconsisting of a singlestatement:

XML Example 8: A Statement Element

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">  以便决定:propertyURI = " http://purl.org/dc/terms/title "> DCMI Home Page

Adescriptionmay be made up of multiplestatements.

In DC-DS-XML, eachstatementis represented by a separate Statement Element. The order of the Statement Elements within a Description Element is not significant.

The following example shows adescriptionconsisting of twostatements:

XML Example 9: Multiple Statement Elements

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">  以便决定:propertyURI = " http://purl.org/dc/terms/title "> DCMI Home Pagedcds:propertyURI="http://purl.org/dc/terms/publisher"> Dublin Core™ Metadata Initiative

A Statement Element must have a Property URI attribute, it may have various other attributes and it may contain zero or more Value String Elements.

4.3.1 The Property URI Attribute

Astatementmust contain exactly oneproperty URI.

In DC-DS-XML, aproperty URIis represented as the value of an XML attribute of the Statement Element. The attribute has the namedcds:propertyURI.

The examples below show adescriptionconsisting of twostatementswhere theproperty URIsarehttp://purl.org/dc/terms/titleandhttp://purl.org/dc/terms/publisher.

XML Example 10: The Property URI Attribute

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   以便决定:propertyURI = " http://purl.org/dc/terms/title "> DCMI Home Page   dcds:propertyURI="http://purl.org/dc/terms/publisher"> Dublin Core™ Metadata Initiative

Note that the representation of theproperty URImay be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on URIs in DC-DS-XML).

4.4 Encoding a Value Surrogate

Astatementcontains exactly onevalue surrogate.

Avalue surrogateis either aliteral value surrogateor anon-literal value surrogate.

4.4.1 Encoding a Literal Value Surrogate

Aliteral value surrogateis made up of exactly onevalue string.

Note that aliteral value surrogatecan not contain avalue URIor avocabulary encoding scheme URI.

4.4.1.1 The Literal Surrogate Value String Element

In DC-DS-XML, avalue stringwithin aliteral value surrogateis represented by an XML element known as a Value String Element. A Value String Element is a child element of a Statement Element and, for the case of theliteral value surrogate, the Value String Element has the namedcds:literalValueString. For the case of theliteral value surrogate, a Statement Element must contain exactly one Value String Element with the namedcds:literalValueString. It is an error for a Statement Element to contain multiple Value String Elements with the namedcds:literalValueString.

The example below shows adescriptionconsisting of a singlestatementwhich includes aliteral value surrogate(with avalue string).

XML Example 11:The Value String Element (Literal Value Surrogate)

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   Dublin Core™ Metadata Initiative

For more details on representingvalue strings, see the section on Value String Elements.

4.4.2 Encoding a Non-Literal Value Surrogate

Anon-literal value surrogateis made up of

  • zero or onevalue URIs

  • zero or onevocabulary encoding scheme URIs

  • zero or morevalue strings

4.4.2.1 The Value URI Attribute

Anon-literal value surrogatemay contain avalue URI.

In DC-DS-XML, avalue URIis represented as the value of an XML attribute of the Statement Element. The attribute has the namedcds:valueURI.

The examples below show adescriptionconsisting of twostatementswhere the secondstatementincludes anon-literal value surrogatewith thevalue URIhttp://example.org/agents/DCMI.

XML Example 12: The Value URI Attribute

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page  dcds:valueURI="http://example.org/agents/DCMI">  Dublin Core™ Metadata Initiative

Note that the representation of thevalue URImay be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on URIs in DC-DS-XML).

4.4.2.2 The Vocabulary Encoding Scheme URI Attribute

Anon-literal value surrogatemay contain avocabulary encoding scheme URI.

In DC-DS-XML, avocabulary encoding scheme URIis represented as the value of an XML attribute of the Statement Element. The attribute has the namedcds:vesURI.

The examples below show adescriptionconsisting of threestatementswhere the thirdstatementincludes anon-literal value surrogatewith thevocabulary encoding scheme URIhttp://purl.org/dc/terms/LCSH.

XML Example 13: The Vocabulary Encoding Scheme URI Attribute

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   Dublin Core™ Metadata Initiative   dcds:vesURI="http://purl.org/dc/terms/LCSH"> Metadata

Note that the representation of thevocabulary encoding scheme URImay be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on URIs in DC-DS-XML).

4.4.1.3 The Non-Literal Surrogate Value String Element

Anon-literal value surrogatemay contain multiplevalue strings.

In DC-DS-XML, avalue stringwithin anon-literal value surrogateis represented by an XML element known as a Value String Element. A Value String Element is a child element of a Statement Element and, for the case of thenon-literal value surrogate, the Value String Element has the namedcds:valueString.

The presence of avalue stringin anon-literal value surrogatewithin astatementis optional. If novalue stringis present, in DC-DS-XML, the Statement Element is empty.

The example below shows adescriptionconsisting of fourstatementswhere the fourthstatementincludes anon-literal value surrogatewith avalue URIbut novalue string.

XML Example 14: Empty Statement Element

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   Dublin Core™ Metadata Initiative   Metadata

The example below shows adescriptionconsisting of fourstatementswhere the second and thirdstatementseach include anon-literal value surrogatecontaining avalue string.

XML Example 15: The Value String Element (Non-Literal Value Surrogate)

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   Dublin Core™ Metadata Initiative  Metadata

Anon-literal value surrogatemay contain multiplevalue strings.

So in DC-XML, a Statement Element representing astatementwith anon-literal value surrogatemay contain multiple Value String Elements. The order of the Value String Elements within a Statement Element is not significant.

The following example shows adescriptionin which the thirdstatementincludes anon-literal value surrogatecontaining twovalue strings:

XML Example 16: Multiple Value String Elements (Non-Literal Value Surrogate)

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   Dublin Core™ Metadata Initiative   MetadataMétadonnées

For more details on representingvalue strings, see the section on Value String Elements.

4.5 Encoding a Value String: The Value String Element

Avalue stringmay occur within either aliteral value surrogateor anon-literal value surrogate. Aliteral value surrogatemust contain exactly onevalue string. Anon-literal value surrogatemay contain multiplevalue strings.

In DC-DS-XML, avalue stringwithin avalue surrogateis represented by an XML element known as a Value String Element. A Value String Element is a child element of a Statement Element.

For the case of theliteral value surrogate, the Value String Element has the namedcds:literalValueString(see the section The Literal Surrogate Value String.

For the case of thenon-literal value surrogate, the Value String Element has the namedcds:valueString(see the section The Non-Literal Surrogate Value String).

Avalue stringis either aplain value stringor atyped value string.

4.5.1 Encoding a Plain Value String

4.5.1.1 The Value String Language Attribute

Aplain value stringmay be associated with avalue string language.

In DC-DS-XML, avalue string languageis represented by anxml:langattribute of the Value String Element. The values of the attribute are language identifiers as defined by IETF RFC 4646 RFC 4646 (or its successor).

The example below shows adescriptionconsisting of threestatementswhere the firststatementhas aliteral value surrogatecontaining aplain value string"DCMI Home Page" associated with thevalue string language"en-GB" :

XML Example 17: The Value String Language

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">    xml:lang="en-GB">DCMI Home Page   Dublin Core™ Metadata Initiative   2005-05-05

4.5.2 Encoding a Typed Value String

4.5.2.1. The Syntax Encoding Scheme URI Attribute

Atyped value stringis associated with asyntax encoding scheme URI.

In DC-DS-XML, asyntax encoding scheme URIis represented as the value of an XML attribute of the Value String Element. The attribute has the namedcds:sesURI.

The examples below show adescriptionconsisting of threestatementswhere the thirdstatementhas aliteral value surrogatecontaining atyped value stringwith thesyntax encoding scheme URIhttp://www.w3.org/2001/XMLSchema#date:

XML Example 18: The Syntax Encoding Scheme URI Attribute

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   Dublin Core™ Metadata Initiative    dcds:sesURI="http://www.w3.org/2001/XMLSchema#date">2005-05-05

Note that the representation of thesyntax encoding scheme URImay be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on URIs in DC-DS-XML).

4.5.2.2. XML data as a Typed Value String

Atyped value stringmay be an XML fragment, in which case it must be associated with thesyntax encoding scheme URIhttp://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral

The example below shows adescriptionconsisting of twostatementswhere the secondstatementcontains aliteral value surrogatewhich includes atyped value stringin the form of an XML fragment:

XML Example 19: XML Data as Typed Value String

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page    dcds:sesURI="http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral"> 
 
The DCMI home page provides an overview of the content of the DCMI Web site. It also displays current news items.

4.6 Encoding Descriptions of Values

As noted in the section on Encoding a Description,description setsmay contain multipledescriptions. Eachdescriptionis represented by a separate Description Element. The order of the Description Elements has no significance.

It may be that thedescribed resourceof adescriptionis referred to as thevalueof astatementin anotherdescriptionwithin thedescription set. If that resource has been assigned a URI, then that URI appears as thevalue URIin thestatementwhere the resource is thevalueand as adescribed resource URIin thedescriptionof that resource, as shown below:

XML Example 20: Non-Literal Value as Described Resource

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   dcds:valueURI="http://example.org/agents/DCMI"/>    DCMI Alternative Home Page   dcds:valueURI="http://example.org/agents/DCMI"/>   dcds:resourceURI="http://example.org/agents/DCMI">  Dublin Core™ Metadata Initiative

In some cases the resource will not have a URI assigned, or the URI will not be known. Such a resource may still be avaluein astatementin onedescriptionand thedescribed resourceof anotherdescriptionin the samedescription set.

In such cases, the association between thestatementin the firstdescriptionand the seconddescriptionis made by using an identifier for the resource which is local to a DC-DS-XML instance. This local identifier is used as the value of adcds:valueRefXML attribute of one or more Statement Elements and as the value of adcds:resourceIdXML attribute of a Description Element. Each value of adcds:valueRefXML attribute must match the value of adcds:resourceIdattribute in the same DC-DS-XML instance.

Note that this is a syntactic mechanism for linking references tovaluesinstatementsto thedescriptionsof thosevalues: the local identifier itself does not appear in thedescription set.

XML Example 21: Non-Literal Value as Described Resource

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > <民国:descriptionSet xmlns:dcds="http://purl.org/dc/xmlns/2008/09/01/dc-ds-xml/">   DCMI Home Page   dcds:valueRef="DCMI"/>    DCMI Alternative Home Page   dcds:valueRef="DCMI"/>   dcds:resourceId="DCMI">  Dublin Core™ Metadata Initiative

Appendix A. DC-TEXT Representation of Example Description Sets

This appendix provides representations of all the examples provided in the main body of the document using the DC-Text syntax [DC-TEXT].

A.1 Example 1

The DC-DS-XML instance in Example 1 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.2 Example 2

The DC-DS-XML instance in Example 2 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.3 Example 3

The DC-DS-XML instance in Example 3 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.4 Example 4

The DC-DS-XML instance in Example 4 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.5 Example 5

The DC-DS-XML instance in Example 5 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.6 Example 6

The DC-DS-XML instance in Example 6 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "UKOLN Home Page" ) ) ) )

A.7 Example 7

The DC-DS-XML instance in Example 7 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.8 Example 8

The DC-DS-XML instance in Example 8 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) )

A.9 Example 9

The DC-DS-XML instance in Example 9 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.10 Example 10

The DC-DS-XML instance in Example 10 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.11 Examples 11

The DC-DS-XML instance in Example 11 represents the following description set:

@prefix my:  . DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( my:name ) LiteralValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.12 Example 12

The DC-DS-XML instance in Example 11 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.13 Example 13

The DC-DS-XML instance in Example 13 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:subject ) VocabularyEncodingSchemeURI (  ) ValueString ( "Metadata" ) ) ) )

A.14 Example 14

The DC-DS-XML instance in Example 14 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:subject ) ValueClassURI (  ) VocabularyEncodingSchemeURI (  ) ValueString ( "Metadata" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI (  ) ) ) )

A.15 Example 15

The DC-DS-XML instance in Example 15 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:subject ) ValueClassURI (  ) VocabularyEncodingSchemeURI (  ) ValueString ( "Metadata" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI (  ) ) ) )

A.16 Examples 16

The DC-DS-XML instance in Example 16 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:subject ) ValueClassURI (  ) VocabularyEncodingSchemeURI (  ) ValueString ( "Metadata" ) ValueString ( "Métadonnées" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI (  ) ) ) )

A.17 Example 17

The DC-DS-XML instance in Example 17 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" Language ( en-GB ) ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:date ) ValueString ( "2005-05-05" ) ) ) )

A.18 Example 18

18 th代表DC-DS-XML实例的例子e following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:date ) ValueString ( "2005-05-05" SyntaxEncodingSchemeURI (  ) ) ) ) )

A.19 Example 19

19 th代表DC-DS-XML实例的例子e following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:description ) LiteralValueString ( "
 
The DCMI home page provides an overview of the content of the DCMI Web site. It also displays current news items.
 
" SyntaxEncodingSchemeURI (  ) ) ) ) )

A.20 Example 20

The DC-DS-XML instance in Example 20 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。@prefix my:  . DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ) ) Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) ValueString ( "DCMI Alternative Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ) ) Description ( ResourceURI (  ) Statement ( PropertyURI ( my:name ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.21 Example 21

The DC-DS-XML instance in Example 21 represents the following description set:

@ prefix使用dc: < http://purl.org/dc/terms/ >。@prefix my:  . DescriptionSet ( Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueId ( DCMI ) ) ) Description ( ResourceURI (  ) Statement ( PropertyURI ( dcterms:title ) ValueString ( "DCMI Alternative Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueRef ( DCMI ) ) ) Description ( ResourceId ( DCMI ) Statement ( PropertyURI ( my:name ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

Appendix B.

RDF/XML Representation of Examples

This appendix provides representations of all the examples provided in the main body of the document using the RDF/XML syntax [RDFXML].

B.1 Example 1

The DC-DS-XML instance in Example 1 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.2 Example 2

The DC-DS-XML instance in Example 2 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.3 Example 3

The DC-DS-XML instance in Example 3 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.4 Example 4

The DC-DS-XML instance in Example 4 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.5 Example 5

The DC-DS-XML instance in Example 5 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.6 Example 6

The DC-DS-XML instance in Example 6 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page   UKOLN Home Page

B.7 Example 7

The DC-DS-XML instance in Example 7 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.8 Example 8

The DC-DS-XML instance in Example 8 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page

B.9 Example 9

The DC-DS-XML instance in Example 9 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page  Dublin Core™ Metadata Initiative

B.10 Example 10

The DC-DS-XML instance in Example 10 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page  Dublin Core™ Metadata Initiative

B.11 Example 11

The DC-DS-XML instance in Example 11 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:my="http://my.example.org/terms/" >  Dublin Core™ Metadata Initiative

B.12 Example 12

The DC-DS-XML instance in Example 12 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page   Dublin Core™ Metadata Initiative

B.13 Example 13

The DC-DS-XML instance in Example 13 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcam="http://purl.org/dc/dcam/" >  DCMI Home Page   Dublin Core™ Metadata Initiative     Metadata

B.14 Example 14

The DC-DS-XML instance in Example 14 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcam="http://purl.org/dc/dcam/" >  DCMI Home Page   Dublin Core™ Metadata Initiative     Metadata

B.15 Example 15

The DC-DS-XML instance in Example 15 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcam="http://purl.org/dc/dcam/" >  DCMI Home Page   Dublin Core™ Metadata Initiative     Metadata

B.16 Example 16

The DC-DS-XML instance in Example 16 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcam="http://purl.org/dc/dcam/" >  DCMI Home Page   Dublin Core™ Metadata Initiative     Metadata Métadonnées

B.17 Example 17

The DC-DS-XML instance in Example 17 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page   Dublin Core™ Metadata Initiative   2005-05-05

B.18 Example 18

18 th代表DC-DS-XML实例的例子e following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page   Dublin Core™ Metadata Initiative   2005-05-05

B.19 Example 19

19 th代表DC-DS-XML实例的例子e following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" >  DCMI Home Page  
 
The DCMI home page provides an overview of the content of the DCMI Web site. It also displays current news items.

B.20 Example 20

The DC-DS-XML instance in Example 20 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:my="http://my.example.org/terms/" >  DCMI Home Page    DCMI Alternative Home Page    Dublin Core™ Metadata Initiative

B.21 Example 21

The DC-DS-XML instance in Example 21 represents the following RDF graph:

< ?xml version = " 1.0 " encoding = " utf - 8 " ? > < rdf: rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:my="http://my.example.org/terms/" >  DCMI Home Page    DCMI Alternative Home Page    Dublin Core™ Metadata Initiative

References

[ABSTRACT-MODEL]
DCMI Abstract ModelDCMI Recommendation. 2007-06-04
//www.voudr.com/specifications/dublin-core/abstract-model/2007-06-04/

[DC-DSP]
Description Set Profiles: A constraint language for Dublin Core™ Application ProfilesDCMI Working Draft. 2008-03-31
//www.voudr.com/specifications/dublin-core/dc-dsp/2008-03-31/

[DC-RDF]
Expressing Dublin Core™ metadata using the Resource Description Framework (RDF)DCMI Recommendation. 2008-01-14
//www.voudr.com/specifications/dublin-core/dc-rdf/2008-01-14/

[DC-TEXT]
Expressing Dublin Core™ metadata using the DC-Text formatDCMI Recommended Resource. 2007-12-03
//www.voudr.com/specifications/dublin-core/dc-text/2007-12-03/

[DCAP]
The Singapore Framework for Dublin Core™ Application Profiles2008-01-14
//www.voudr.com/specifications/dublin-core/singapore-framework/2008-01-14//

[GRDDL]
Gleaning Resource Descriptions from Dialects of Languages (GRDDL)W3C Recommendation 11 September 2007
http://www.w3.org/TR/2007/REC-grddl-20070911/

[RDFXML]
RDF/XML Syntax Specification (Revised)W3C Recommendation 10 February 2004
http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/

[RFC3986]
Berners-Lee, T., R. Fielding, L. Masinter.RFC 3986: Uniform Resource Identifier (URI): Generic Syntax.Internet Engineering Task Force (IETF). January 2005.
<http://www.ietf.org/rfc/rfc3986.txt>

[RFC4646]
Phillips, A., M. Davis.RFC 4646: Tags for Identifying Languages.Internet Engineering Task Force (IETF). September 2006.
<http://www.ietf.org/rfc/rfc4646.txt>

[XML]
Extensible Markup Language (XML) 1.0 (Fourth Edition)W3C Recommendation 16 August 2006, edited in place 29 September 2006
http://www.w3.org/TR/2006/REC-xml-20060816/

[XMLSCHEMA]
XML Schema Part 0: Primer Second EditionW3C Recommendation 28 October 2004
http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/

Errata

2009-08-27。纠正不正确的“替换”链接(had pointed to "//www.voudr.com/specifications/dublin-core/dc-xml/2006-05-06/").