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

Expressing Dublin Core™ metadata using HTML/XHTML meta and link elements

Creator: Pete Johnston
Eduserv Foundation, UK
Creator: Andy Powell
Eduserv Foundation, UK
Date Issued: 2007-11-05
Identifier: //www.voudr.com/specifications/dublin-core/dc-html/2007-11-05/
Replaces: Not applicable
Is Replaced By: //www.voudr.com/specifications/dublin-core/dc-html/2008-08-04/
Latest Version: //www.voudr.com/specifications/dublin-core/dc-html/
Status of Document: This is a DCMIProposed Recommendation
Description of Document: This document describes how a Dublin Core™ metadata description set can be encoded in HTML/XHTML and elements. It is an HTML meta data profile, as defined by the HTML specification.

Table of contents

  1. Introduction
  2. The DCMI Abstract Model and DC-HTML
  3. Features of the DC-HTML Syntax
  4. The DC-HTML Meta Data Profile
  5. Appendix A. DC-TEXT Representation of Examples
  6. References
  7. Acknowledgements

1. Introduction

This document specifies a set of conventions by which a DC metadata描述setcan be can be represented within an HTML/XHTML Web page using HTML/XHTML elements and attributes. Formally, it defines ameta data profilefor HTML and XHTML.

The "Description Set Model" of the DCMI Abstract Model [DCAM] describes the constructs that make up a DC metadata描述set. In order to represent a DC metadata description set in an X/HTML document those constructs have to be represented as components in that HTML/XHTML document, i.e. as HTML/XHTML elements and attributes and as element content and attribute values.

This profile makes use only of the HTML/XHTMLandelements and their attributes.

2. The DCMI Abstract Model and DC-HTML

According to the "Description Set Model" of the DCMI Abstract Model [DCAM], a DC描述sethas the following structure:

  • a描述setis made up of one or more描述s

  • a描述is 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 another描述

The conventions described in this document implement the following subset of the DCAM "description set model".

  • a描述setis made up of one描述

  • a描述is made up of

    • 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

      • exactly onevalue URI

      • zero or oneplain value 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

i.e. the conventions here support a描述setcontaining a single描述, and a maximum of onevalue stringpervalue surrogate. In anon-literal value surrogate,avalue URImust be providedand avalue stringmust be aplain value string.The provision of avocabulary encoding scheme URIis not supported.

3. Features of the DC-HTML Meta Data Profile

3.1 URIs in DC-HTML

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

在DC-HTML职业file, those URIs are encoded as X/HTML attribute values. Later sections of this document describe the use of those different X/HTML attributes in detail. The purpose of this section is to make some general points about the representation of these URIs in DC-HTML.

3.1.1 URI references

在DC-HTML职业file,value URIsare encoded as URI references, used as X/HTML attribute values. A URI reference is either a URI or a relative reference [RFC3896].

The URI may be represented in full. The following example shows avalue URIas the value of thehrefattribute:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 1: URI as attribute value (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 2: URI as attribute value (XHTML)

For all of the attributes in DC-HTML 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 thehrefattribute of thebaseelement or from the URI of the document itself. In the following example, the value of thehrefattribute is a relative reference. It is resolved relative to the base URI provided by thehrefattribute of thebaseelement to obtain a target URI ofhttp://example.org/docs/doc123:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 3: Relative reference as attribute value (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 4: Relative reference as attribute value (XHTML)

3.1.2 URIs,

DC-HTML Prefixed Names and Namespace Declarations

In DC-HTML,property URIsandsyntax encoding scheme URIsare represented as DC-HTML Prefixed Names.

A DC-HTML Prefixed Name is an abbreviation for a URI used in the DC-HTML format. A DC-HTML Prefixed Name consists of a "prefix" followed by a period (".") and a "local name".

The "prefix" in a DC-HTML Prefixed Name is associated with a "namespace URI" using a namespace declaration, made using a Namespace Declaration Element (see the section on Namespace Declarationsbelow). The URI represented by the DC-HTML Prefixed Name is determined by concatenating the "namespace URI" with which the prefix is associated and the "local name".

For a software application that is "encoding" a描述setby generating a DC-HTML instance, a DC-HTML Prefixed Name to represent a URI is determined by

  • dividing the URI into a pair consisting of a local name (the trailing characters of the URI, subject to the lexical constraints described above) and a namespace URI (the preceding part of the URI), and

  • providing a Namespace Declaration element for this namespace URI (using a prefix in the namespace declaration and in the DC-HTML Prefixed Name).

Note that this means for a single URI there is more than one possible DC-HTML Prefixed Name representation. For example, the URIhttp://purl.org/dc/terms/titlemight be represented using any of the following (namespace URI, local name) pairs:

  • {http://purl.org/dc/terms/}, title

  • {http://purl.org/dc/terms/t}, itle

  • {http://purl.org/dc/terms/ti}, tle

  • {http://purl.org/dc/terms/tit}, le

  • {http://purl.org/dc/terms/titl}, e

Communities typically decide on a convention for the DC-HTML Prefixed Name to be used for a URI, particularly for the URIs of terms (properties,classes,vocabulary encoding schemesandsyntax encoding schemes),但在理论上任何这四种形式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). Also, the characters used for the prefix in a DC-HTML Prefixed Name are not significant, but communities often adopt a convention on the common use of a prefix to facilitate human readability.

The following examples shows a namespace declaration and the use of a DC-HTML Prefixed Name for the value of thenameattribute of themetaelement:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 5: DC-HTML Prefixed Name as attribute value (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 6: DC-HTML Prefixed Name as attribute value (XHTML)

If the prefix used in a DC-HTML Prefixed Name has not been associated with a URI in a namespace declaration, no URI can be generated for that DC-HTML Prefixed Name. If the prefix has been associated with multiple URIs (though multiple namespace declarations) then the prefix is associated with the namespace URI specified in the latest declaration in the DC-HTML instance.

In the following examples the prefix "XX" is used in a a DC-HTML Prefixed Name, but there is no namespace declaration for that prefix so no URI is generated for that value of thenameattribute of themetaelement:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 7: DC-HTML Prefixed Name as attribute value, missing namespace declaration (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 8: DC-HTML Prefixed Name as attribute value, missing namespace declaration (XHTML)

In the following examples the prefix "XX" is used in a a DC-HTML Prefixed Name, and there are two namespace declaration for that prefix. The second namespace declaration is used to generate the URIhttp://your.example.org/terms/approvedfrom the value of thenameattribute of themetaelement:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 9: DC-HTML Prefixed Name as attribute value, multiple namespace declarations (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 10: DC-HTML Prefixed Name as attribute value, multiple namespace declarations (XHTML)

4. The DC-HTML Meta Data Profile

4.1 The

Profile Attribute Value

Where these conventions are used to represent a DC metadata_description set_ in an X/HTML document, the value of theprofileattribute of the X/HTMLheadelement must include the URI of this X/HTML metadata profile//www.voudr.com/specifications/dublin-core/dc-html/2007-11-05/

4.2 DC-HTML

Namespace Declarations

A DC-HTML namespace declaration associates a URI with a prefix, so that when that prefix is used in a DC-HTML Prefixed Name, that URI is used as a "namespace URI". A namespace declaration is made using the X/HTMLlinkelement and a specific convention for the value of therelattribute. In the DC-HTML profile, an X/HTMLlinkelement of which therelattribute has a value beginning with the charactersschema.represents a namespace declaration.

The DC-HTML namespace declaration must include:

  • a prefix, represented by part of the value of therelattribute of the X/HTMLlinkelement following the charactersschema.

  • a namespace URI, represented by the value of thehrefattribute of the X/HTMLlinkelement

In the following example, declarations are provided for two prefixes, each of which is used subsequently in a DC-HTML Prefixed Name.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 11: The Namespace Declaration (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 12: The Namespace Declaration (XHTML)

4.3 Encoding

a Description Set

A描述set由one_description_。

在DC-HTML职业file, the描述setis not explicitly represented, but thestatementsrepresented constitute a single描述within a描述set.

4.4 Encoding

a Description

A描述is a set of one or more_statements_ about a resource.

在DC-HTML职业file, the描述is not explicitly represented, but thestatementsrepresented constitute a single描述.

4.4.1 The

Described Resource URI

A描述has an associateddescribed resource URI.

在DC-HTML职业file-Full, the _described resource URI_is the URI of the X/HTML document

4.5 Encoding

a Statement

A描述is made up of one or more_statements_.

在DC-HTML职业file, eachstatementis represented as either an X/HTMLmetaelement or an X/HTMLlink元素。X / HTML元素的选择取决于whether thestatementcontains aliteral value surrogateor anon-literal value surrogate.

The examples below show a描述consisting of two_statements_.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 13: Statements as meta and link elements (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 14: Statements as meta and link elements (XHTML)

4.5.1 Encoding a Statement containing a Literal Value Surrogate

在DC-HTML职业file, eachstatementcontaining a_literal values surrogate_ is represented as an X/HTMLmeta元素。

4.5.1.1 The

Property URI

Astatementmust contain exactly oneproperty URI.

在DC-HTML职业file, aproperty URIin a_statement_ containing a _literal values surrogate_is represented as a DC-HTML Prefixed Name which is the value of thenameattribute of an X/HTMLmeta元素。

The examples below shows a描述consisting of a singlestatementwhere theproperty URIishttp://purl.org/dc/terms/title.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 15: The Property URI as the value of the name Attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 16: The Property URI as the value of the name Attribute (XHTML)

4.5.1.2 Encoding a Literal Value Surrogate

Aliteral value surrogateis made up of exactly one_value string_.

在DC-HTML职业file, avalue stringwithin a_literal values surrogate_ is represented by the combination of the values of several attributes of an X/HTMLmeta元素。

Avalue stringis either a _plain value string_or atyped value string.

Aplain value stringmay be associated with avalue string language.

在DC-HTML职业file, the string itself is represented as the value of thecontentattribute of an X/HTMLmetaelement, and avalue string languageis represented by the value of thelang(HTML) orxml:lang(XHTML) attribute of themeta元素。

The examples below shows a描述consisting of a singlestatementwith a _literal value surrogate_made up of aplain value stringwith novalue string language.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 17: Literal Value Surrogate Plain Value String as value of content Attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 18: Literal Value Surrogate Plain Value String as value of content Attribute (XHTML)

The examples below shows a描述consisting of a singlestatementwith a _literal value surrogate_made up of aplain value stringwhich includes avalue string language.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 19: Literal Value Surrogate Plain Value String with Value String Language (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 20: Literal Value Surrogate Plain Value String with Value String Language (XHTML)

Atyped value stringis associated with asyntax encoding scheme URI.

在DC-HTML职业file, the string itself is represented as the value of thecontentattribute of an X/HTMLmetaelement, and asyntax encoding scheme URIis represented as a DC-HTML Prefixed Name which is the value of theschemeattribute of the X/HTMLmeta元素。

The examples below show a描述组成的two_statements_non-literal value surrogates. In the secondstatementthenon-literal value surrogatecontains atyped value stringwith the_syntax encoding scheme URI_http://www.w3.org/2001/XMLSchema#date:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 21: Literal Value Surrogate with Typed Value String (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 22: Literal Value Surrogate with Typed Value String (XHTML)

4.5.2 Encoding a Statement containing a Non-Literal Value Surrogate

在DC-HTML职业file, eachstatementcontaining a_non-literal values surrogate_ is represented as an X/HTMLlink元素。

4.5.2.1. The

Property URI

Astatementmust contain exactly oneproperty URI.

在DC-HTML职业file, aproperty URIin a_statement_ containing anon-literal values surrogateis represented as a DC-HTML Prefixed Name which is the value of therelattribute of an X/HTMLlink元素。

The examples below shows a描述consisting of a singlestatementwhere theproperty URIishttp://purl.org/dc/terms/subject.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 23: The Property URI as the value of the rel attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 24: The Property URI as the value of the rel attribute (XHTML)

The HTML/XHTML rel attribute supports a list of linktypes, so where a描述contains multiplestatements_referring to differentpropertiesbut the same_value, they may be represented using a singlelink元素。

The examples below shows a描述consisting of twostatementswhere theproperty URIsarehttp://purl.org/dc/terms/creatorandhttp://purl.org/dc/terms/publisher.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 25: Multiple Property URIs as the value of the rel attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 26: Multiple Property URIs as the value of the rel attribute (XHTML)

The same描述could be represented using repeatedlinkelements:

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 27: The Property URI as the value of the rel attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 28: The Property URI as the value of the rel attribute (XHTML)

4.5.2.2. Encoding a Non-Literal Value Surrogate

In the subset of the DCAM description model supported by the DC-HTML profile, anon-literal value surrogateis made up of exactly onevalue URIand zero or oneplain value strings.

在DC-HTML职业file, thevalue URIis represented as the value of thehrefattribute of the X/HTMLlinkelement

The examples below shows a描述consisting of a singlestatementwith anon-literal value surrogatemade up of avalue URI.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 29: Non-Literal Value Surrogate with Value URI as value of href attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 30: Non-Literal Value Surrogate with Value URI as value of href attribute (XHTML)

Aplain value stringmay be associated with avalue string language.

在DC-HTML职业file, the string itself is represented as the value of thetitleattribute of the X/HTMLlinkelement, and avalue string languageis represented by the value of thelang(HTML) orxml:lang(XHTML) attribute of thelink元素。

The examples below shows a描述consisting of a singlestatementwith anon-literal value surrogatemade up of avalue URIand aplain value stringwith novalue string language.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 31: Non-Literal Value Surrogate with Plain Value String as value of title attribute (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 32: Non-Literal Value Surrogate Plain Value String as value of title attribute (XHTML)

The examples below shows a描述consisting of a singlestatementwith anon-literal value surrogatemade up of avalue URIand aplain value stringwhich includes avalue string language.

<！DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">   Services to Government

Example 33: Non-Literal Value Surrogate with Plain Value String with Value String Language (HTML)

< ?xml version = " 1.0 " ?> < !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   Services to Government

Example 34: Non-Literal Value Surrogate Plain Value String with Value String Language (XHTML)

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].

A.1 Examples

1 & 2

The X/HTML instances in Examples 1 & 2 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ) ) )

A.2 Example

3 & 4

The X/HTML instances in Examples 3 & 4 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:isReferencedBy ) ValueURI (  ) ) ) )

A.3 Example

5 & 6

The X/HTML instances in Examples 5 & 6 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) ) )

A.4 Example

7 & 8

The X/HTML instances in Examples 7 & 8 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) ) )

A.5 Example

9 & 10

The X/HTML instances in Examples 9 & 10 represent the following description set:

@prefix dcterms:  . @prefix your:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) ) Statement ( PropertyURI ( your:approved ) LiteralValueString ( "2007-01-05" ) ) ) )

A.6 Example

11 & 12

The X/HTML instances in Examples 11 & 12 represent the following description set:

@prefix dcterms:  . @prefix marcrel:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) Statement ( PropertyURI ( marcrel:EDT ) ValueURI (  ) ) ) )

A.7 Examples

13 & 14

The X/HTML instances in Examples 13 & 14 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ValueString ( "Archives" ) ) ) )

A.8 Examples

15 & 16

The X/HTML instances in Examples 15 & 16 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) ) )

A.9 Examples

17 & 18

The X/HTML instances in Examples 17 & 18 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" ) ) ) )

A.10 Examples

19 & 20

The X/HTML instances in Examples 19 & 20 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" Language ( en ) ) ) ) )

A.11 Examples

21 & 22

The X/HTML instances in Examples 21 & 22 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:title ) LiteralValueString ( "Services to Government" Language ( en ) ) ) Statement ( PropertyURI ( dcterms:modified ) LiteralValueString ( "2007-07-22" SyntaxEncodingSchemeURI (  ) ) ) ) )

A.12

Examples 23 & 24

The X/HTML instances in Examples 19 & 20 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ValueString ( "Archives" ) ) ) )

A.13

Examples 25 & 26

The X/HTML instances in Examples 25 & 26 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.14

Examples 27 & 28

The X/HTML instances in Examples 27 & 28 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) Statement ( PropertyURI ( dcterms:publisher ) ValueURI (  ) ValueString ( "Dublin Core™ Metadata Initiative" ) ) ) )

A.15

Examples 29 & 30

The X/HTML instances in Examples 29 & 30 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ) ) )

A.16

例子31日& 32

The X/HTML instances in Examples 31 & 32 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ValueString ( "Archives" ) ) ) )

A.17

Examples 33 & 34

The X/HTML instances in Examples 33 & 34 represent the following description set:

@prefix dcterms:  . DescriptionSet ( Description ( Statement ( PropertyURI ( dcterms:subject ) ValueURI (  ) ValueString ( "Archives" Language ( en ) ) ) ) )

References

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

[DC-TEXT]
DC-Text: A Text Syntax for Dublin Core™ MetadataDCMI Working Draft. 2007-04-02
//www.voudr.com/architecturewiki/DCText/2007-04-02

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

[IRI]
Duerst, M., M. Suignard. RFC 3987: Internationalized Resource Identifiers (IRIs). Internet Engineering Task Force (IETF). January 2005.
<http://www.ietf.org/rfc/rfc3987.txt>

[URI]
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>

Errata

2008-01-14. Removed premature "Replaces:" link to//www.voudr.com/specifications/dublin-core/dcq-html/2003-11-30/.

2008-03-31. Removed note: " As of 2007-11-05, aproposalto "replicate" the fifteen properties of thehttp://purl.org/dc/elements/1.1/("dc:") namespace in thehttp://purl.org/dc/terms/("dcterms:") namespace has not been approved or implemented. Until this DCMI Proposed Recommendation is approved as a DCMI Recommendation, references herein to names such as dcterms:subject and dcterms:title should be understood as having the status of "proposed" as well.

2008-08-04. Changed GRDDL profile transform URI from tohttp://www.incognitum.net/petej/projects/dc-html/xslt/2007/11/05/dc-html2rdfxml.xsltohttp://purl.org/dc/transform/dc-html-20071105-grddl/dc-html2rdfxml.xsl.