#acl AndyPowell:read,write,delete,admin PeteJohnston:read,write,delete,admin All:read = Expressing Dublin Core Metadata in XML = 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). This is a draft document, made available for public comment. Comments should be sent to the DC-ARCHITECTURE@jiscmail.ac.uk mailing list (for detailed technical comments) or to the DC-GENERAL@jiscmail.ac.uk mailing list (for comments of a more general nature). || '''Title:''' || '''Expressing Dublin Core Metadata in XML''' || || '''Creator:''' || Pete Johnston, Eduserv Foundation || || '''Creator:''' || Andy Powell, Eduserv Foundation || || '''Date Issued:''' || 2006-05-16 || || '''Identifier:''' || http://dublincore.org/architecturewiki/DCXMLRevision/DCXMLGuidelines/2006-05-16 || || '''Replaces:''' || Not applicable || || '''Is Replaced By:''' || Not applicable || || '''Latest Version:''' || http://dublincore.org/architecturewiki/DCXMLRevision/DCXMLGuidelines || || '''Description of Document:''' || This document specifies an XML format for representing a Dublin Core metadata description set. The XML format is known as "DC-XML".|| == Contents == 1. Introduction 1. The DCMI Abstract Model and DC-XML 1. The DC-XML Syntax 1. GRDDL 1. Appendix A: Text Representation of Examples 1. Notes 1. References == 1. Introduction == This document specifies an XML format for representing a DC metadata description set. The XML format is known as "DC-XML". The DCMI Abstract Model [[#DCAM DCAM]] describes the entities that make up a DC metadata description set and the relationships between those entities. In order to represent a DC metadata description set in an XML document the entities it comprises 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-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 Model" of the DCAM, i.e. it should be possible to represent all the entities that make up a DC metadata description set and the relationships between them. (See [#Note1 Note 1]). * The format is not required to address the features of the "Schema Model" of the DCAM. 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 DCAM 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, all the constraints expressed in a DC Application Profile are captured using W3C XML Schema. == 2. The DCMI Abstract Model and DC-XML == According to the DCAM: * a ''description set'' is made up of one or more ''descriptions'' * a ''description'' is made up of * zero or one ''resource URI'' and * one or more ''statements'' * a ''statement'' is made up of * exactly one ''property URI'' and * zero or one ''reference to'' a value in the form of a ''value URI'' * zero or more ''representations of'' a value, each in the form of a ''value representation'' * zero or one ''vocabulary encoding scheme URI'' * a ''value representation'' is either * a ''value string'' or * a ''rich representation'' * a ''value string'' may have an associated ''value string language'' * a ''value string'' may have an associated ''syntax encoding scheme URI'' * a ''value'' may be the subject of a ''related description'' The DC-XML format described in this document implements all the features of the DCAM. == 3. The DC-XML Syntax == [[Anchor(sec3.1)]] === 3.1 URIs and XML Qualified Names === The DCAM uses URIs to refer both to resources and to metadata terms (properties, vocabulary encoding schemes and syntax encoding schemes). In DC-XML, URIs are sometimes represented as XML Qualified Names (QNames). An XML QName is an abbreviation for an "expanded name", a pair consisting of an XML Namespace Name (a URI, which is associated with the QName prefix in an XML Namespace declaration) and a local name. For a software application that is parsing a DC-XML instance, the URI is determined from the XML QName by appending the local name part of the QName to the XML Namespace Name. Note that only some XML QNames in a DC-XML instance are mapped to URIs in this way: this specification indicates when that mapping is applied. For a software application that is "encoding" a ''description set'' by generating a DC-XML instance, the QName is determined by using the trailing characters of the URI as the local name of the QName, and the preceding part of the URI as the XML Namespace Name. Note that this means for a single URI there is more than one possible QName representation. For example, the URI `http://purl.org/dc/elements/1.1/date` might be represented using any of the following expanded names (XML Namespace Name, local name pairs): * `{http://purl.org/dc/elements/1.1/}, date` * `{http://purl.org/dc/elements/1.1/d}, ate` * `{http://purl.org/dc/elements/1.1/da}, te` * `{http://purl.org/dc/elements/1.1/dat}, e` Communities typically decide on a convention for the QName to be used, but in theory any of these four forms could be deployed without changing the interpretation of the instance. For all DCMI terms, the convention used by the DCMI community is to split the term URI into an expanded name at the right-most '/' (forward slash) character (as per the first example above). In DC-XML, only some URIs are represented as XML QNames; other URIs are represented in full. The table below summarises the options available: || '''URI''' ||<:> '''May be represented as URI''' ||<:> '''May be represented as QName''' || || Resource URI ||<:> Yes ||<:> No || || Value URI ||<:> Yes ||<:> No || || Property URI ||<:> No ||<:> Yes || || Vocabulary Encoding Scheme URI ||<:> Yes ||<:> Yes || || Syntax Encoding Scheme URI ||<:> Yes ||<:> Yes || === 3.2 Encoding a Description Set: The Description Set Element === A ''description set'' is a set of one or more ''descriptions''. In DC-XML, a ''description set'' is represented by an XML element known as a Description Set Element (See [#Note2 Note 2]). A DC-XML instance has exactly one Description Set Element. A Description Set Element always has an expanded name with the XML Namespace Name `http://purl.org/dc/xml/` and local name `descriptionSet`. In the examples presented in this document, the XML Namespace Name `http://purl.org/dc/xml/` is always associated with the prefix "dcx". {{{ DCMI Home Page }}} '''XML Example 1: the Description Set Element''' === 3.3 Encoding a Description: The Description Element === A ''description'' is a set of one or more ''statements'' about a resource. In DC-XML, a ''description'' is represented by an XML element known as a Description Element. Any XML element which is a child element of a Description Set Element is a Description Element. The following example shows a ''description set'' consisting of a single ''description'': {{{ DCMI Home Page }}} '''XML Example 2: the Description Element''' In the remainder of this document, Description Elements are shown using an XML element with an expanded name with the XML Namespace Name `http://purl.org/dc/xml/` and local name `description` (represented by the XML QName `dcx:description`). However, it is important to remember that a Description Element may have a different element name if such a name is useful or neceesary for the particular application. A ''description set'' may contain multiple ''descriptions''. In DC-XML, 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 3: Multiple Description Elements''' The encoding of ''description sets'' with multiple ''descriptions'' is described further in [#sec3.6 section 3.6]. ==== 3.3.1 The Resource URI ==== A ''description'' may have an associated ''resource URI''. In DC-XML, a ''resource URI'' must be encoded in full. The ''resource URI'' is represented as the value of an XML attribute of the Description Element. The attribute has the name `dcx:resourceURI`. {{{ DCMI Home Page }}} '''XML Example 4: the Resource URI Attribute''' Note that the representation of the ''resource URI'' may be abbreviated through the use of an XML entity reference, as follows: {{{ ]> DCMI Home Page }}} '''XML Example 5: the Resource URI Attribute (with XML entity reference)''' === 3.4 Encoding Statements: Statement Elements === A ''description'' is made up of one or more ''statements''. In DC-XML, each child XML element of a Description Element represents a single ''statement'' and is known as a Statement Element. The following example shows a ''description'' consisting of a single ''statement'': {{{ DCMI Home Page }}} '''XML Example 6: A Statement Element''' A ''description'' may be made up of multiple ''statements'', each 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 7: Multiple Statement Elements''' ==== 3.4.1 The Property URI ==== A ''statement'' must contain exactly one ''property URI''. In DC-XML, the ''property URI'' is represented by the element name of the Statement Element (an XML QName). The ''property URI'' is determined from the QName by applying the QName-URI mapping described in [#sec3.1 section 3.1] The example below shows a ''description'' consisting of two ''statements'' where the ''property URIs'' are `http://purl.org/dc/elements/1.1/title` and `http://purl.org/dc/elements/1.1/publisher`. {{{ DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 8: The Property URI''' ==== 3.4.2 The Value URI ==== A ''statement'' may contain a ''value URI''. In DC-XML, the ''value URI'' must be encoded in full. The ''value URI'' is represented as the value of an XML attribute of the Statement Element. The attribute has the name `dcx:valueURI`. The example below shows a ''description'' consisting of two ''statements'' where the second ''statement'' includes the ''value URI'' `http://example.org/agents/DCMI`. {{{ DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 9: The Value URI Attribute''' The representation of the ''value URI'' may be abbreviated through the use of an XML entity reference, as follows: {{{ ]> DCMI Home Page Dublin Core Metadata Initiative }}} '''XML Example 10: the Value URI Attribute (using an XML entity reference)''' ==== 3.4.3 The Vocabulary Encoding Scheme URI Attribute ==== A ''statement'' may include a ''vocabulary encoding scheme URI''. In DC-XML, a ''vocabulary encoding scheme URI'' may either be encoded in full or as an XML QName. In both cases it is represented as the value of an XML attribute of the Statement Element. If the ''value URI'' appears in full, the attribute has the name `dcx:vocabEncSchemeURI`. If the ''value URI'' is represented using an XML QName, the attribute has the name `dcx:vocabEncSchemeQName`. The example below shows a ''description'' consisting of three ''statements'' where the third ''statement'' includes the ''vocabulary encoding scheme URI'' `http://purl.org/dc/terms/LCSH`. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 11: The Vocabulary Encoding Scheme URI Attribute''' Where an XML QName is used, the ''vocabulary encoding scheme URI'' is determined from the QName by applying the QName-URI mapping described in [#sec3.1 section 3.1]. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 12: the Vocabulary Encoding Scheme QName Attribute''' Note that the two examples above illustrate two alternate ways of representing the same information. A single Statement Element should not have both a `dcx:vocabEncSchemeURI` and a `dcx:vocabEncSchemeQName` attribute. ==== 3.4.4 Empty Statement Elements ==== The presence of a ''value representation'' in a ''statement'' is optional. In DC-XML, the Statement Element may therefore be empty. The example below shows a ''description'' consisting of four ''statements'' where the fourth ''statement'' provides a ''value URI'' but no ''value representation''. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 13: Empty Statement Element''' === 3.5 Encoding Value Strings and Rich Representations: Value Representation Elements === A ''statement'' may contain multiple ''value representations''. In DC-XML, the ''value representations'' are represented by child elements of the Statement Element known as Value Representation Elements. The order of the Value Representation Elements within a Statement Element is not significant. A value representation may take the form of a ''value string'' or a ''rich representation'' ==== 3.5.1 The Value String ==== A ''value string'' is represented by an XML element with the element name `dcx:valueString`. The example below shows a ''description'' consisting of four ''statements'' where the first three ''statements'' each include a ''value string''. {{{ DCMI Home Page Dublin Core Metadata Initiative Metadata }}} '''XML Example 14: The Value String''' A ''statement'' may contain multiple ''value strings'', each represented by a separate `dcx:valueString` child XML element. The following example shows a ''description'' in which the first ''statement'' provides three ''value strings'': {{{ Site Map Plan du site Plan del sitio Dublin Core Metadata Initiative }}} '''XML Example 15: Multiple Value Strings''' ===== 3.5.1.1 The Value String Language ===== A ''value string'' may have an associated ''value string language''. In DC-XML, a ''value string language'' is represented by an `xml:lang` attribute of the `dcx:valueString` XML element representing the ''value string''. The example below shows a ''description'' consisting of three ''statements'' where the first ''statement'' has an associated ''value string language'' "en-GB" with the ''value string'' "DCMI Home Page": {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} '''XML Example 16: The Value String Language''' ===== 3.5.1.2 The Syntax Encoding Scheme URI ===== A ''value string'' may have an associated ''syntax encoding scheme URI''. In DC-XML, a ''syntax encoding scheme URI'' may be encoded in full or it may be represented as an XML QName. In both cases, the ''syntax encoding scheme URI'' is represented as the value of an XML attribute of the `dcx:valueString` element. If the ''syntax encoding scheme URI'' is encoded in full, the attribute has the name `dcx:syntaxEncSchemeURI`. If it is represented using an XML QName, the attribute has the name `dcx:syntaxEncSchemeQName`. The example below shows a ''description'' consisting of three ''statements'' where the third ''statement'' associates the ''syntax encoding scheme URI'' `http://www.w3.org/2001/XMLSchema#date` with the ''value string'' "2005-05-05": {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} '''XML Example 17: The Syntax Encoding Scheme URI Attribute''' Where an XML QName is used, the ''syntax encoding scheme URI'' is determined from the QName by applying the QName-URI mapping described in [#sec3.1 section 3.1]. {{{ DCMI Home Page Dublin Core Metadata Initiative 2005-05-05 }}} '''XML Example 18: the Syntax Encoding Scheme QName Attribute''' Note that these two examples illustrate two alternate ways of representing the same information. A single `dcx:valueString` XML element should not have both a `dcx:syntaxEncSchemeURI` and a `dcx:syntaxEncSchemeQName` attribute. ==== 3.5.2 Rich Representations ==== A ''value'' may also be represented by a ''rich representation'' - i.e. by some XML data or by a binary data object. ===== 3.5.2.1 XML Data ===== An XML data ''rich representation'' may be provided in two ways. It may be provided "inline" within the DC-XML document or it may be provided as a separate XML document, the URI of which is provided as an attribute value. Inline XML data is represented by the content of a Value Representation Element with the element name `dcx:XMLRepresentation`. The example below shows a ''description'' consisting of two ''statements'' where the second ''statement'' includes a ''rich representation'' of the ''value'' 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: Rich Representation - XML Data''' The URI of external XML data is encoded as the value of the `dcx:representationURI` attribute of the `dcx:XMLRepresentation` element, as follows: {{{ DCMI Home Page dcx:representationURI="http://example.org/docs/doc.xml" /> }}} '''XML Example 20: Rich Representation - XML Data''' ===== 3.5.2.2 Binary Data ===== A binary data ''rich representation'' may be provided in two ways. It may be provided "inline" within the DC-XML document or it may be provided as a separate XML document, the URI of which is provided as an attribute value. Inline binary data is represented by the content of a Value Representation Element with the element name `dcx:binaryRepresentation`. The XML element content is a Base64 encoding of the binary object. The value of the attribute `dcx:mimeType` provides the MIME type for the binary data object; the attribute must be present and the value must be a valid MIME type. The example below shows a ''description'' consisting of two ''statements'' where the second ''statement'' includes a ''rich representation'' of the ''value'' in the form of a binary data object: {{{ DCMI Home Page dcx:mimeType="image/png">AABBCCDDEEFF }}} '''XML Example 21: Rich Representation - Binary Data''' The URI of external binary data is encoded as the value of the `dcx:representationURI` attribute of the `dcx:binaryRepresentation` element: {{{ DCMI Home Page dcx:representationURI="http://example.org/imgs/img.png" /> }}} '''XML Example 22: Rich Representation - Binary Data''' A ''statement'' may contain multiple ''rich representations'' in the form of separate `dcx:XMLRepresentation` or `dcx:binaryRepresentation` XML elements. Furthermore, a single ''statement'' may provide both ''value strings'' and ''rich representations''. The following example shows a ''description'' in which the second ''statement'' provides two ''value strings'' and two ''rich representations'': {{{ DCMI Home Page The home page provides an overview of the content of the DCMI Web site. It also displays current news items. El Home Page proporciona una descripción del contenido del sitio del Web de DCMI. Además presenta noticias actuales.

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

El Home Page proporciona una descripción del contenido del sitio del Web de DCMI. Además se presentan noticias actuales.

 }}} '''XML Example 23: Multiple Value Strings and Multiple Rich Representations''' [[Anchor(sec3.6)]] === 3.6 Encoding Related Descriptions === As noted in [#sec3.3 section 3.3], ''description sets'' may contain multiple ''descriptions''. Each ''description'' is represented by a separate Description Element. The order of the Description Elements has no significance. In cases where a ''description'' is about a resource which is the ''value'' of a ''statement'' in another ''description'' within the ''description set'', the ''description'' is known as a ''related description''. 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 ''resource URI'' in the ''description'' of that resource, as shown below: {{{ DCMI Home Page DCMI Alternative Home Page dcx:resourceURI="http://example.org/agents/DCMI"> Dublin Core Metadata Initiative }}} '''XML Example 24: Related Description''' 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'' and the subject of another ''description'' in the same ''description set'' (a ''related description''). In such cases, the association between the ''statement'' and the ''related description'' is made by labelling the ''related description'' using an XML attribute of the Description Element. The attribute has the name `dcx:descriptionId`. The attribute value may then be cited in the the value of a `dcx:descriptionRef` XML attribute of one or more Statement Elements elsewhere in the same ''description set''. Each value of a `dcx:descriptionRef` XML attribute must match the value of a `dcx:descriptionId` attribute in the same DC-XML instance. Note that this is a syntactic mechanism for linking references to ''values'' to the ''related descriptions'' of those ''values'': the label itself does not appear in the DCAM. {{{ DCMI Home Page DCMI Alternative Home Page Dublin Core Metadata Initiative }}} '''XML Example 25: Related Description''' == 4. GRDDL == An XSLT transformation from DC-XML to RDF/XML [[#RDFXML RDFXML]] is available. The GRDDL specification [[#GRDDL GRDDL]] defines a set of conventions for associating an XML instance document with a transformation. One approach is to reference the transformation using an attribute of the root element, as follows: {{{ ... }}} '''XML Example 26: GRDDL''' The transformation can also be associated with a set of XML documents through information provided by the "namespace document". == 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 document in Example 1 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) ) }}} === A.2 Example 2 === The DC-XML document in Example 2 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) ) }}} === A.3 Example 3 === The DC-XML document in Example 3 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) Description ( Statement ( PropertyURI ( dc:title ) ValueString ( "UKOLN Home Page" ) ) ) ) }}} === A.4 Example 4 === The DC-XML document in Example 4 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) ) }}} === A.5 Example 5 === The DC-XML document in Example 5 represents the following description set: {{{ @prefix dc: . @prefix dcmi: . DescriptionSet ( Description ( ResourceURI ( dcmi:home ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) ) }}} === A.6 Example 6 === The DC-XML document in Example 6 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) ) ) }}} === A.7 Example 7 === The DC-XML document in Example 7 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.8 Example 8 === The DC-XML document in Example 8 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.9 Example 9 === The DC-XML document in Example 9 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.10 Example 10 === The DC-XML document in Example 10 represents the following description set: {{{ @prefix dc: . @prefix agent: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( agent:DCMI ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.11 Example 11 === The DC-XML document in Example 11 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:subject ) VocabularyEncodingSchemeURI ( ) ValueString ( "Metadata" ) ) ) ) }}} === A.12 Example 12 === The DC-XML document in Example 12 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . @prefix dcmi: . DescriptionSet ( Description ( ResourceURI ( dcmi:home ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:subject ) VocabularyEncodingSchemeURI ( dcterms:LCSH ) ValueString ( "Metadata" ) ) ) ) }}} === A.13 Example 13 === The DC-XML document in Example 13 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:subject ) VocabularyEncodingSchemeURI ( ) ValueString ( "Metadata" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI ( ) ) ) ) }}} === A.14 Example 14 === The DC-XML document in Example 14 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:subject ) VocabularyEncodingSchemeURI ( ) ValueString ( "Metadata" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI ( ) ) ) ) }}} === A.15 Example 15 === The DC-XML document in Example 15 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "Site Map" ) ValueString ( "Plan du site" ) ValueString ( "Plan del sitio" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:isPartOf ) ValueURI ( ) ) ) ) }}} === A.16 Example 16 === The DC-XML document in Example 16 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" Language ( en-GB ) ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:date ) ValueString ( "2005-05-05" ) ) ) ) }}} === A.17 Example 17 === The DC-XML document in Example 17 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:date ) ValueString ( "2005-05-05" SyntaxEncodingSchemeURI ( ) ) ) ) ) }}} === A.18 Example 18 === The DC-XML document in Example 18 represents the following description set: {{{ @prefix dc: . @prefix dcmi: . @prefix agent: . @prefix xsd: . DescriptionSet ( Description ( ResourceURI ( dcmi:home ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( agent:DCMI ) ValueString ( "Dublin Core Metadata Initiative" ) ) Statement ( PropertyURI ( dc:date ) ValueString ( "2005-05-05" SyntaxEncodingSchemeURI ( xsd:date ) ) ) ) ) }}} === A.19 Example 19 === The DC-XML document in Example 19 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" Language ( en-GB ) ) ) Statement ( PropertyURI ( dc:description ) RichRepresentation ( "

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

" ) ) ) ) }}} === A.20 Example 20 === The DC-XML document in Example 20 represents the following description set: {{{ to follow }}} === A.21 Example 21 === The DC-XML document in Example 21 represents the following description set: {{{ @prefix dc: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" Language ( en-GB ) ) ) Statement ( PropertyURI ( dc:description ) RichRepresentation ( Base64 ( "AABBCCDDEEFF" MIME ( "image/png" ) ) ) ) ) ) }}} === A.22 Example 22 === The DC-XML document in Example 22 represents the following description set: {{{ to follow }}} === A.23 Example 23 === The DC-XML document in Example 23 represents the following description set: {{{ @prefix dc: . @prefix dcterms: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" Language ( en-GB ) ) ) Statement ( PropertyURI ( dc:description ) ValueString ( "The home page provides an overview of the content of the DCMI Web site. It also displays current news items." Language: ( en-GB ) ) ValueString ( "El Home Page proporciona una descripción del contenido del sitio del Web de DCMI. Además presenta noticias actuales." Language: ( es-ES ) ) RichRepresentation ( "

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

" ) RichRepresentation ( "

El Home Page proporciona una descripción del contenido del sitio del Web de DCMI. Además se presentan noticias actuales.

" ) ) ) ) }}} === A.24 Example 24 === The DC-XML document in Example 24 represents the following description set: {{{ @prefix dc: . @prefix my: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ) ) Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Alternative Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) ValueURI ( ) ) ) Description ( ResourceURI ( ) Statement ( PropertyURI ( my:name ) ValueString ( "Dublin Core Metadata Initiative" ) ) ) ) }}} === A.25 Example 25 === The DC-XML document in Example 25 represents the following description set: {{{ @prefix dc: . @prefix my: . DescriptionSet ( Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) DescriptionRef ( descDCMI ) ) ) Description ( ResourceURI ( ) Statement ( PropertyURI ( dc:title ) ValueString ( "DCMI Alternative Home Page" ) ) Statement ( PropertyURI ( dc:publisher ) DescriptionRef ( descDCMI ) ) ) Description ( DescriptionId ( descDCMI ) Statement ( PropertyURI ( my:name ) ValueString ( "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 value strings only. oai_dc is a different XML format from DC-XML, 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(DCAM)]]'''[DCAM]'''[[BR]]DCMI Abstract Model[[BR]]http://dublincore.org/documents/abstract-model/ [[Anchor(XML)]]'''[XML]'''[[BR]]''Extensible Markup Language (XML) 1.0 (Third Edition)''. W3C Recommendation 04 February 2004.[[BR]]http://www.w3.org/TR/REC-xml [[Anchor(XMLSCHEMA)]]'''[XMLSCHEMA]'''[[BR]]''XML Schema Part 0: Primer Second Edition''. W3C Recommendation 28 October 2004.[[BR]]http://www.w3.org/TR/xmlschema-0/ [[Anchor(XMLNS)]]'''[XMLNS]'''[[BR]]''Namespaces in XML''. W3C Recommendation 14 January 1999.[[BR]]http://www.w3.org/TR/REC-xml-names [[Anchor(RDFXML)]]'''[RDFXML]'''[[BR]]''RDF/XML Syntax Specification (Revised)'' W3C Recommendation 10 February 2004.[[BR]]http://www.w3.org/TR/rdf-syntax-grammar/ [[Anchor(GRDDL)]]'''[GRDDL]'''[[BR]]''Gleaning Resource Descriptions from Dialects of Languages (GRDDL)'' W3C Coordination Group Note 13 April 2004[[BR]]http://www.w3.org/TR/rdf-schema/ [[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(DC-TEXT)]]'''[DC-TEXT]'''[[BR]]''DC-Text: A Text Syntax for Dublin Core Metadata'' Draft of 2006-05-22.[[BR]]http://dublincore.org/architecturewiki/DCText/2006-05-22