#acl AndyPowell:read,write,delete,admin PeteJohnston:read,write,delete,admin All:read = Expressing Dublin Core metadata using XML (DC-XML-Full) = This document is part of the [wiki:Self:. DC Architecture Wiki]. '''IMPORTANT:''' Do '''not''' cite materials in this Wiki other than for the purposes of collaborating on document creation. This Wiki is intended to be used to work on draft copies of documents. Finished documents will be published, in a persistent and citable form, on the dublincore.org Web site (or elsewhere in some cases). || '''Title:''' || '''Expressing Dublin Core metadata using XML (DC-XML-Full)''' || || '''Creator:''' || Pete Johnston, Eduserv Foundation || || '''Creator:''' || Andy Powell, Eduserv Foundation || || '''Date Issued:''' || 2008-07-23 || || '''Identifier:''' || http://dublincore.org/architecturewiki/DCXMLRevision/DCXMLFGuidelines/2008-07-23 || || '''Replaces:''' || http://dublincore.org/architecturewiki/DCXMLRevision/DCXMLFGuidelines/2007-06-19 || || '''Is Replaced By:''' || Not applicable || || '''Latest Version:''' || http://dublincore.org/architecturewiki/DCXMLRevision/DCXMLFGuidelines || || '''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-XML-Full".|| [[TableOfContents([3])]] == Contents == 1. Introduction 1. The DCMI Abstract Model and DC-XML-Full 1. Some Features of the DC-XML-Full Syntax 1. The DC-XML-Full Syntax 1. Encoding a Description Set: The Description Set Element 1. Encoding Descriptions: Description Elements 1. Encoding Statements: Statement Elements 1. Encoding Value Surrogates 1. Encoding Literal Value Surrogates 1. Encoding Non-Literal Value Surrogates 1. Encoding Value Strings: Value String Elements 1. Encoding Descriptions of Values 1. Appendix A: Text Representation of Examples 1. Notes 1. References [[Anchor(Introduction)]] == 1. Introduction == This document specifies an XML format for representing a DC metadata ''description set''. The XML format is known as "DC-XML-Full". The "Description Set Model" of the DCMI Abstract Model [[#ABSTRACT-MODEL ABSTRACT-MODEL]] describes the constructs that make up a DC metadata ''description 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. [[Anchor(Design-Considerations)]] === 1.1 Design Considerations === The DC-XML-Full 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 metadata ''description set''. (See [#Note1 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 XMLSCHEMA]], but it is not a requirement that when the format is used to serialise ''description sets'' conforming to a DC Application Profile [[#DCAP DCAP]], all the constraints expressed in the corresponding Description Set Profile [[#DC-DSP DC-DSP]] are captured using W3C XML Schema. [[Anchor(DC-XML-Full-and-GRDDL)]] === 1.2 DC-XML-Full and GRDDL === The W3C Recommendation ''Gleaning Resource Descriptions from Dialects of Languages'' [[#GRDDL 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-XML-Full format. That transformation generates RDF graphs compatible with the recommendations of the DCMI Recommendation Expressing Dublin Core metadata using the Resource Description Framework (RDF) [[#DC-RDF DC-RDF]]. [[Anchor(The-DCMI-Abstract-Model-and-DC-XML-Full)]] == 2. The DCMI Abstract Model and DC-XML-Full == According to the "Description Set Model" of the DCMI Abstract Model [[#ABSTRACT-MODEL ABSTRACT-MODEL]], a DC ''description set'' has the following structure: * a ''description set'' is made up of one or more ''descriptions'' * a ''description'' is made up of * zero or one ''described resource URI'' and * one or more ''statements'' * a ''statement'' is made up of * exactly one ''property URI'' and * exactly one ''value surrogate'' * a ''value surrogate'' is either a ''literal value surrogate'' or a ''non-literal value surrogate'' * a ''literal value surrogate'' is made up of exactly one ''value string'' * a ''non-literal value surrogate'' is made up of * zero or one ''value URIs'' * zero or one ''vocabulary encoding scheme URIs'' * zero or more ''value strings'' * a ''value string'' is either a ''plain value string'' or a ''typed value string'' * a ''plain value string'' may be associated with a ''value string language'' * a ''typed value string'' is associated with a ''syntax encoding scheme URI'' * a ''non-literal value'' may be described by another ''description'' The DC-XML-Full format described in this document implements all the features of the DCAM "description set model". [[Anchor(Features-of-the-DC-XML-Full-Syntax)]] == 3. Features of the DC-XML-Full Syntax == [[Anchor(URIs-in-DC-XML-Full)]] === 3.1 URIs in DC-XML-Full === The Abstract Model uses Uniform Resource Identifiers (URIs) [[#RFC3896 RFC3896]] to refer both to the resources described within DC metadata ''description sets'' and to metadata terms (''properties'', ''classes'', ''vocabulary encoding schemes'' and ''syntax encoding schemes'') used in those ''description sets''. In DC-XML-Full, URIs are encoded as URI references, used as XML attribute values. A URI reference is either a URI or a relative reference [[#RFC3896 RFC3896]]. 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-XML-Full. The URI may be represented in full. The following example shows a URI as the value of the `dcxf:propertyURI` attribute: {{{ DCMI Home Page }}} '''XML Example 1: URI as attribute value''' The representation of the URI may be abbreviated through the use of an XML entity reference as follows, for example: {{{ ]> DCMI Home Page }}} '''XML Example 2: URI as attribute value (with XML entity reference)''' For all of the attributes in DC-XML-Full 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 an `xml:base` attribute or from the URI of the document itself. In the following example, the value of the `dcxf:propertyURI` attribute is a relative reference. It is resolved relative to the base URI provided by the `xml:base` attribute to obtain a target URI of `http://purl.org/dc/terms/title`: {{{ DCMI Home Page }}} '''XML Example 3: Relative reference as attribute value''' [[Anchor(The-DC-XML-Full-Syntax)]] == 4. The DC-XML-Full Syntax == [[Anchor(Encoding-a-Description-Set-The-Description-Set-Element)]] === 4.1 Encoding a Description Set: The Description Set Element === A ''description set'' is a set of one or more ''descriptions''. In DC-XML-Full, a ''description set'' is represented by an XML element known as a Description Set Element (See [#Note2 Note 2]). A DC-XML-Full instance represents a single DC ''description 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 Name `http://dublincore.org/xmlns/2008/07/23/dc-xml-full/` and local name `descriptionSet`. In the examples presented in this document, the XML Namespace Name `http://dublincore.org/xmlns/2008/07/23/dc-xml-full/` is always associated with the prefix "dcxf". For convenience, after this point, the names of XML elements and XML attributes are presented in the text as XML QNames (e.g. `dcxf:descriptionSet`, `dcxf:resourceURI`), rather than as expanded names, but the prefix used is not significant. {{{ DCMI Home Page }}} '''XML Example 4: the Description Set Element''' The Description Set Element must contain one or more [#Encoding-a-Description-The-Description-Element Description Elements]. [[Anchor(Encoding-a-Description-The-Description-Element)]] === 4.2 Encoding a Description: The Description Element === A ''description'' is a set of one or more ''statements'' about a resource. In DC-XML-Full, a ''description'' is 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 name `dcxf:description`. The following example shows a ''description set'' consisting of a single ''description'': {{{ DCMI Home Page }}} '''XML Example 5: the Description Element''' A ''description set'' may contain multiple ''descriptions''. In DC-XML-Full, each ''description'' is represented by a separate Description Element. The order of the Description Elements within a Description Set Element is not significant. The following example shows a ''description set'' consisting of two ''descriptions'': {{{ DCMI Home Page UKOLN Home Page }}} '''XML Example 6: Multiple Description Elements''' The encoding of ''description sets'' with multiple ''descriptions'' is described further in [#Encoding-Descriptions-of-Values the section on Encoding Descriptions of Values]. A Description Element may have a [#The-Described-Resource-URI Described Resource URI] attribute and must contain one or more [#Encoding-a-Statement-The-Statement-Element Statement Elements]. [[Anchor(The-Described-Resource-URI)]] ==== 4.2.1 The Described Resource URI Attribute ==== A ''description'' may have an associated ''described resource URI''. In DC-XML-Full, a ''described resource URI'' is represented as the value of an XML attribute of the Statement Element. The attribute has the name `dcxf:resourceURI`. The examples below show a ''description'' with the ''described resource URI'' `http://dublincore.org/pages/home`. {{{ DCMI Home Page }}} '''XML Example 7: the Described Resource URI Attribute''' Note that the representation of the ''described resource URI'' may be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on [#URI-references URI references]). [[Anchor(Encoding-a-Statement-The-Statement-Element)]] === 4.4 Encoding a Statement: The Statement Element === A ''description'' is made up of one or more ''statements''. In DC-XML-Full, each child XML element of a Description Element represents a single ''statement'' and is known as a Statement Element. A Statement Element always has the name `dcxf:statement`. The following example shows a ''description set'' with a single ''description'' consisting of a single ''statement'': {{{ DCMI Home Page }}} '''XML Example 8: A Statement Element''' A ''description'' may be made up of multiple ''statements''. In DC-XML-Full, each ''statement'' is represented by a separate Statement Element. The order of the Statement Elements within a Description Element is not significant. The following example shows a ''description'' consisting of two ''statements'': {{{ DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 9: Multiple Statement Elements''' A Statement Element must have a [#The-Property-URI Property URI] attribute, it may have various other attributes and it may contain zero or more [#Encoding-a-Value-String-The-Value-String-Element Value String Elements]. [[Anchor(The-Property-URI)]] ==== 4.4.1 The Property URI ==== A ''statement'' must contain exactly one ''property URI''. In DC-XML-Full, a ''property URI'' is represented as the value of an XML attribute of the Statement Element. The attribute has the name `dcxf:propertyURI`. The examples below show a ''description'' consisting of two ''statements'' where the ''property URIs'' are `http://purl.org/dc/terms/title` and `http://purl.org/dc/terms/publisher`. {{{ DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 10: The Property URI Attribute''' Note that the representation of the ''property URI'' may be abbreviated through the use of an XML entity reference or a URI relative reference (see the section on [#URI-references URI references]). [[Anchor(Encoding-a-Value-Surrogate)]] === 4.4 Encoding a Value Surrogate === A ''statement'' contains exactly one ''value surrogate''. A ''value surrogate'' is either a ''literal value surrogate'' or a ''non-literal value surrogate''. [[Anchor(Encoding-a-Literal-Value-Surrogate)]] ==== 4.4.1 Encoding a Literal Value Surrogate ==== A ''literal value surrogate'' is made up of exactly one ''value string''. Note that a ''literal value surrogate'' can not contain a ''value URI'' or a ''vocabulary encoding scheme URI''. [[Anchor(The-Literal-Surrogate-Value-String)]] ===== 4.4.1.1 The Literal Surrogate Value String ===== In DC-XML-Full, a ''value string'' within a ''literal value surrogate'' is 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 the ''literal value surrogate'', the Value String Element has the name `dcxf:literalValueString`. For the case of the ''literal value surrogate'', a Statement Element must contain exactly one Value String Element with the name `dcxf:literalValueString`. It is an error for a Statement Element to contain multiple Value String Elements with the name `dcxf:literalValueString`. The example below shows a ''description'' consisting of a single ''statement'' which includes a ''literal value surrogate'' (with a ''value string''). {{{ Dublin Core Metadata Initiative }}} '''XML Example 11: The Value String Element (Literal Value Surrogate)''' For more details on representing ''value strings'', see the section on [#Encoding-a-Value-String-The-Value-String-Element Value String Elements]. [[Anchor(Encoding-a-Non-Literal-Value-Surrogate)]] ==== 4.4.2 Encoding a Non-Literal Value Surrogate ==== A ''non-literal value surrogate'' is made up of * zero or one ''value URIs'' * zero or one ''vocabulary encoding scheme URIs'' * zero or more ''value strings'' [[Anchor(The-Value-URI)]] ===== 4.4.2.1 The Value URI Attribute ===== A ''non-literal value surrogate'' may contain a ''value URI''. In DC-XML-Full, a ''value URI'' is represented as the value of an XML attribute of the Statement Element. The attribute has the name `dcxf:valueURI`. The examples below show a ''description'' consisting of two ''statements'' where the second ''statement'' includes a ''non-literal value surrogate'' with the ''value URI'' `http://example.org/agents/DCMI`. {{{ DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 12: The Value URI Attribute''' Note that the representation of the ''value URI'' may be abbreviated through the use of an XML entity reference or a URI relative reference (see [#URI-references the section on URI references]). [[Anchor(The-Vocabulary-Encoding-Scheme-URI)]] ===== 4.4.2.2 The Vocabulary Encoding Scheme URI Attribute ===== A ''non-literal value surrogate'' may include a ''vocabulary encoding scheme URI''. In DC-XML-Full, a ''vocabulary encoding scheme URI'' is represented as the value of an XML attribute of the Statement Element. The attribute has the name `dcxf:vocabEncSchemeURI`. The examples below show a ''description'' consisting of three ''statements'' where the third ''statement'' includes a ''non-literal value surrogate'' with the ''vocabulary encoding scheme URI'' `http://purl.org/dc/terms/LCSH`. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 13: The Vocabulary Encoding Scheme URI Attribute''' Note that the representation of the ''vocabulary encoding scheme URI'' may be abbreviated through the use of an XML entity reference or a URI relative reference (see [#URI-references the section on URI references]). [[Anchor(The-Non-Literal-Surrogate-Value-String)]] ===== 4.4.2.3 The Non-Literal Surrogate Value String ===== A ''non-literal value surrogate'' may contain multiple ''value strings''. In DC-XML-Full, a ''value string'' within a '''non-literal value surrogate''' is 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 the ''non-literal value surrogate'', the Value String Element has the name `dcxf:valueString`. The presence of a ''value string'' in a ''non-literal value surrogate'' within a ''statement'' is optional. If no ''value string'' is present, in DC-XML-Full, the Statement Element is empty. The example below shows a ''description'' consisting of four ''statements'' where the fourth ''statement'' includes a ''non-literal value surrogate'' with a ''value URI'' but no ''value string''. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 14: Empty Statement Element''' The example below shows a ''description'' consisting of four ''statements'' where the second and third ''statements'' each include a ''non-literal value surrogate'' containing a ''value string''. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 15: The Value String Element (Non-Literal Value Surrogate)''' A ''non-literal value surrogate'' may contain multiple ''value strings''. So in DC-XML, a Statement Element representing a ''statement'' with a ''non-literal value surrogate'' may contain multiple Value String Elements. The order of the Value String Elements within a Statement Element is not significant. The following example shows a ''description'' in which the third ''statement'' includes a ''non-literal value surrogate'' containing two ''value strings'': {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata Métadonnées }}} '''XML Example 16: Multiple Value String Elements (Non-Literal Value Surrogate)''' For more details on representing ''value strings'', see the section on [#Encoding-a-Value-String-The-Value-String-Element Value String Elements]. [[Anchor(Encoding-a-Value-String-The-Value-String-Element)]] === 4.5 Encoding a Value String: The Value String Element === A ''value string'' may occur within either a ''literal value surrogate'' or a ''non-literal value surrogate''. A ''literal value surrogate'' must contain exactly one ''value string''. A ''non-literal value surrogate'' may contain multiple ''value strings''. In DC-XML-Full, a ''value string'' within a ''value surrogate'' is 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 the ''literal value surrogate'', the Value String Element has the name `dcxf:literalValueString` (see the section [#The-Literal-Surrogate-Value-String The Literal Surrogate Value String]. For the case of the ''non-literal value surrogate'', the Value String Element has the name `dcxf:valueString` (see the section [#The-Non-Literal-Surrogate-Value-String The Non-Literal Surrogate Value String]). A ''value string'' is either a ''plain value string'' or a ''typed value string''. [[Anchor(Encoding-a-Plain-Value-String)]] ==== 4.5.1 Encoding a Plain Value String ==== [[Anchor(The-Value-String-Language)]] ===== 4.5.1.1 The Value String Language ===== A ''plain value string'' may be associated with a ''value string language'' In DC-XML-Full, a ''value string language'' is represented by an `xml:lang` attribute of the Value String Element. The values of the attribute are language identifiers as defined by IETF RFC 4646 [#RFC4646 RFC 4646] (or its successor). The example below shows a ''description'' consisting of three ''statements'' where the first ''statement'' has a ''non-literal value surrogate'' containing a ''plain value string'' "DCMI Home Page" associated with the ''value string language'' "en-GB" : {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} '''XML Example 17: The Value String Language''' [[Anchor(Encoding-a-Typed-Value-String)]] ==== 4.5.2 Encoding a Typed Value String ==== [[Anchor(The-Syntax-Encoding-Scheme-URI)]] ===== 4.5.2.1 The Syntax Encoding Scheme URI ===== A ''typed value string'' is associated with a ''syntax encoding scheme URI''. In DC-XML-Full, a ''syntax encoding scheme URI'' is represented as the value of an XML attribute of the Value String Element. The attribute has the name `dcxf:syntaxEncSchemeURI`. The examples below show a ''description'' consisting of three ''statements'' where the third ''statement'' has a ''non-literal value surrogate'' containing a ''typed value string'' with the ''syntax encoding scheme URI'' `http://www.w3.org/2001/XMLSchema#date`: {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} '''XML Example 18: The Syntax Encoding Scheme URI Attribute''' Note that the representation of the ''syntax encoding scheme URI'' may be abbreviated through the use of an XML entity reference or a URI relative reference (see [#URI-references the section on URI references]). [[Anchor(XML-data-as-a-Typed-Value-String)]] ===== 4.5.2.2 XML data as a Typed Value String ===== A ''typed value string'' may be an XML fragment, in which case it must be associated with the ''syntax encoding scheme URI'' '''http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral''' The example below shows a ''description'' consisting of two ''statements'' where the second ''statement'' contains a ''literal value surrogate'' which includes a ''typed value string'' in the form of an XML fragment: {{{ DCMI Home Page

The DCMI home page provides an overview of the content of the DCMI Web site. It also displays current news items.

 }}} '''XML Example 19: XML Data as Typed Value String''' [[Anchor(Encoding-Descriptions-of-Values)]] === 4.7 Encoding Descriptions of Values === As noted in the section on [#Encoding-a-Description:-The-Description-Element Encoding a Description], ''description sets'' may contain multiple ''descriptions''. Each ''description'' is represented by a separate Description Element. The order of the Description Elements has no significance. It may be that the ''described resource'' of a ''description'' is referred to as the ''value'' of a ''statement'' in another ''description'' within the ''description set''. If that resource has been assigned a URI, then that URI appears as the ''value URI'' in the ''statement'' where the resource is the ''value'' and as a ''described resource URI'' in the ''description'' of that resource, as shown below: {{{ DCMI Home Page DCMI Alternative Home Page Dublin Core Metadata Initiative }}} '''XML Example 20: Value as Described Resource''' In some cases the resource will not have a URI assigned, or the URI will not be known. Such a resource may still be a ''value'' in a ''statement'' in one ''description'' and the ''described resource'' of another ''description'' in the same ''description set''. In such cases, the association between the ''statement'' in the first ''description'' and the second ''description'' is made by using an identifier for the resource which is local to a DC-XML-Full instance. This local identifier is used as the value of a `dcxf:valueRef` XML attribute of one or more Statement Elements and as the value of a `dcxf:resourceId` XML attribute of a Description Element. Each value of a `dcxf:valueRef` XML attribute must match the value of a `dcxf:resourceId` attribute in the same DC-XML-Full instance. Note that this is a syntactic mechanism for linking references to ''values'' in ''statements'' to the ''descriptions'' of those ''values'': the local identifier itself does not appear in the ''description set''. {{{ DCMI Home Page DCMI Alternative Home Page Dublin Core Metadata Initiative }}} '''XML Example 21: Value as Described Resource''' == Appendix A. DC-TEXT Representation of Examples == This appendix provides representations of all the examples provided in the main body of the document using the DC-Text syntax [[#DC-TEXT DC-TEXT]]. === A.1 Example 1 === The DC-XML-Full instance in Example 1 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.2 Example 2 === The DC-XML-Full instance in Example 2 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.3 Example 3 === The DC-XML-Full instance in Example 3 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.4 Example 4 === The DC-XML-Full instance in Example 4 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.5 Example 5 === The DC-XML-Full instance in Example 5 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.6 Example 6 === The DC-XML-Full instance in Example 6 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 7 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.8 Example 8 === The DC-XML-Full instance in Example 8 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) ) ) }}} === A.9 Example 9 === The DC-XML-Full instance in Example 9 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 10 represents the following description set: {{{ @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.11 Example 11 === The DC-XML-Full 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-XML-Full instance in Example 12 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 13 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 14 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 15 represents the following description set: {{{ @prefix dcterms: . 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 Example 16 === The DC-XML-Full instance in Example 16 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 17 represents the following description set: {{{ @prefix dcterms: . 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 === The DC-XML-Full instance in Example 18 represents the following description set: {{{ @prefix dcterms: . 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 === The DC-XML-Full instance in Example 19 represents the following description set: {{{ @prefix dcterms: . 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-XML-Full instance in Example 20 represents the following description set: {{{ @prefix dcterms: . @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-XML-Full instance in Example 21 represents the following description set: {{{ @prefix dcterms: . @prefix my: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueRef ( 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 == === B.1 Example 1 === The DC-XML-Full instance in Example 1 represents the following RDF graph: {{{ DCMI Home Page }}} === B.2 Example 2 === The DC-XML-Full instance in Example 2 represents the following RDF graph: {{{ DCMI Home Page }}} === B.3 Example 3 === The DC-XML-Full instance in Example 3 represents the following RDF graph: {{{ DCMI Home Page }}} === B.4 Example 4 === The DC-XML-Full instance in Example 4 represents the following RDF graph: {{{ DCMI Home Page }}} === B.5 Example 5 === The DC-XML-Full instance in Example 5 represents the following RDF graph: {{{ DCMI Home Page }}} === B.6 Example 6 === The DC-XML-Full instance in Example 6 represents the following RDF graph: {{{ DCMI Home Page UKOLN Home Page }}} === B.7 Example 7 === The DC-XML-Full instance in Example 7 represents the following RDF graph: {{{ DCMI Home Page }}} === B.8 Example 8 === The DC-XML-Full instance in Example 8 represents the following RDF graph: {{{ DCMI Home Page }}} === B.9 Example 9 === The DC-XML-Full instance in Example 9 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative }}} === B.10 Example 10 === The DC-XML-Full instance in Example 10 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative }}} === B.11 Example 11 === The DC-XML-Full instance in Example 11 represents the following RDF graph: {{{ Dublin Core Metadata Initiative }}} === B.12 Example 12 === The DC-XML-Full instance in Example 12 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative }}} === B.13 Example 13 === The DC-XML-Full instance in Example 13 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} === B.14 Example 14 === The DC-XML-Full instance in Example 14 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} === B.15 Example 15 === The DC-XML-Full instance in Example 15 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} === B.16 Example 16 === The DC-XML-Full instance in Example 16 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata Métadonnées }}} === B.17 Example 17 === The DC-XML-Full instance in Example 17 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} === B.18 Example 18 === The DC-XML-Full instance in Example 18 represents the following RDF graph: {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} === B.19 Example 19 === The DC-XML-Full instance in Example 19 represents the following RDF graph: {{{ 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-XML-Full instance in Example 20 represents the following RDF graph: {{{ DCMI Home Page DCMI Alternative Home Page Dublin Core Metadata Initiative }}} === B.21 Example 21 === The DC-XML-Full instance in Example 21 represents the following RDF graph: {{{ DCMI Home Page DCMI Alternative Home Page Dublin Core Metadata Initiative }}} == Notes == [[Anchor(Note1)]]'''[1]''' This document defines one XML format for representing DC metadata description sets in XML. Other formats may exist supporting other subsets of the DCMI Abstract Model. For example, the Open Archives Initiative Protocol for Metadata Harvesting [[#OAIPMH OAIPMH]] defines a format, commonly known as oai_dc, which supports the serialisation only of description sets containing a single description, with statements referencing only the fifteen properties of the DCMES, and using literal value surrogates only. oai_dc is a different XML format from DC-XML-Full, but that does not change the value and usefulness of oai_dc as a format for serialising that particular subset of DC metadata description sets. [[Anchor(Note2)]]'''[2]''' In this document the term "element" is used to refer only to XML elements, and it should always be interpreted in that sense wherever it occurs. It is not used to refer to the properties of the DCMES. == References == [[Anchor(ABSTRACT-MODEL)]]'''[ABSTRACT-MODEL]'''[[BR]]''DCMI Abstract Model'' DCMI Recommendation. 2007-06-04[[BR]]http://dublincore.org/2007/06/04/documents/abstract-model/ [[Anchor(DC-DSP)]]'''[DC-DSP]'''[[BR]]''Description Set Profiles: A constraint language for Dublin Core Application Profiles'' DCMI Working Draft. 2008-03-31[[BR]]http://dublincore.org/documents/2008/03/31/dc-dsp/ [[Anchor(DC-RDF)]]'''[DC-RDF]'''[[BR]]''Expressing Dublin Core metadata using the Resource Description Framework (RDF)'' DCMI Recommendation. 2008-01-14[[BR]]http://dublincore.org/documents/2008/01/14/dc-rdf/ [[Anchor(DC-TEXT)]]'''[DC-TEXT]'''[[BR]]''Expressing Dublin Core metadata using the DC-Text format'' DCMI Recommended Resource. 2007-12-03[[BR]]http://dublincore.org/documents/2007/12/03/dc-text/ [[Anchor(DCAP)]]'''[DCAP]'''[[BR]]''The Singapore Framework for Dublin Core Application Profiles'' 2008-01-14[[BR]]http://dublincore.org/documents/2008/01/14/singapore-framework/ [[Anchor(GRDDL)]]'''[GRDDL]'''[[BR]]''Gleaning Resource Descriptions from Dialects of Languages (GRDDL)'' W3C Recommendation 11 September 2007[[BR]]http://www.w3.org/TR/2007/REC-grddl-20070911/ [[Anchor(OAIPMH)]]'''[OAIPMH]'''[[BR]]''The Open Archives Initiative Protocol for Metadata Harvesting'' Protocol Version 2.0 of 2002-06-14.[[BR]]http://www.openarchives.org/OAI/openarchivesprotocol.html [[Anchor(RDFXML)]]'''[RDFXML]'''[[BR]]''RDF/XML Syntax Specification (Revised)'' W3C Recommendation 10 February 2004[[BR]]http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210 [[Anchor(RFC3986)]]'''[RFC3986]'''[[BR]]''RFC 3986: Uniform Resource Identifier (URI): Generic Syntax''. Internet Engineering Task Force (IETF). January 2005[[BR]]http://www.ietf.org/rfc/rfc3986.txt [[Anchor(RFC4646)]]'''[RFC4646]'''[[BR]]''RFC 4646: Tags for Identifying Languages''. Internet Engineering Task Force (IETF). September 2006.[[BR]]http://www.ietf.org/rfc/rfc4646.txt [[Anchor(XML)]]'''[XML]'''[[BR]]''Extensible Markup Language (XML) 1.0 (Fourth Edition)''. W3C Recommendation 16 August 2006, edited in place 29 September 2006.[[BR]]http://www.w3.org/TR/2006/REC-xml-20060816/ [[Anchor(XMLSCHEMA)]]'''[XMLSCHEMA]'''[[BR]]''XML Schema Part 0: Primer Second Edition''. W3C Recommendation 28 October 2004.[[BR]]http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/ == Changes in this version == * Remove use of DC-XML-Full Prefixed Names.