Dublin Core
Dublin Core
About DCMI Themes Members Governing Board Usage Board Directorate
Bluesky Twitter 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: 2008-08-04
Identifier: http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/
Replaces: http://dublincore.org/specifications/dublin-core/dcq-html/2003-11-30/
Replaces: http://dublincore.org/specifications/dublin-core/dc-html/2007-11-05/
Is Replaced By: Not applicable
Latest Version: http://dublincore.org/specifications/dublin-core/dc-html/
Status of Document: This is a DCMI Recommendation
Description of Document: This document describes how a Dublin Core™ metadata description set can be encoded in HTML/XHTML <meta> and <link> 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. Addendum
  6. Appendix A. DC-TEXT Representation of Examples
  7. Appendix B. RDF/XML Representation of Examples
  8. References
  9. Acknowledgements

1. Introduction

This document specifies a set of conventions by which a DC metadata description set can be can be represented within an X/HTML Web page using X/HTML elements and attributes. Formally, it defines a meta data profile for HTML and XHTML; the profile is identified by the URI http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/ and is referred to in this document as the "DC-HTML" meta data profile.

The "Description Set Model" of the DCMI 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 X/HTML document those constructs have to be represented as components in that X/HTML document, i.e. as X/HTML elements and attributes and as element content and attribute values.

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

1.1 DC-HTML and GRDDL

The W3C Recommendation Gleaning Resource Descriptions from Dialects of Languages [GRDDL] describes a set of conventions for associating an XML document with an algorithm for the extraction of a set of RDF triples from that document. One of the mechanisms defined by GRDDL is the association of a Profile Transformation with an XHTML meta data profile.

The GRDDL Profile Transformation for the DC-HTML meta data profile is http://purl.org/dc/transform/dc-html-20080804-grddl/dc-html2rdfxml.xsl.

1.2 GRDDL, XML and Entity References [added 17 May 2010]

The GRDDL specification notes that a GRDDL XML processor might not process DTDs and schemas referenced by a document, and recommends:

Document authors, particularly XHTML document authors, who wish their documents to be unambiguous when used with GRDDL should avoid dependencies on an external DTD subset; specifically:

  • Explicitly include the XHTML namespace declaration in an XHTML document, or an appropriate namespace in an XML document.
  • Avoid use of entity references, except those listed in section 4.6 of the XML specification.
  • And, more generally, follow the rules listed for the standalone document validity constraint.

So, XHTML documents using the DC-HTML profile should not include entity references other than the five predefined by the XML specification itself (&, <, >, ', "). Numeric character references (like © or © for the copyright sign) are supported.

2. The DCMI Abstract Model and DC-HTML

According to the "Description Set Model" of the DCMI 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 conventions described in this document implement the following subset of the DCAM "description set model".

  • a description set is made up of one description

  • a description is made up of

    • 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

      • exactly one value URI

      • zero or one plain 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

The differences between the full set of components of the description set and the subset supported by the DC-HTML meta data profile are summarised in the following table:

Component DCAM Description Model DC-HTML
description set One One
description One-to-many descriptions One description
described resource URI One per description; any URI One per description; document URI/Base URI
statement One-to-many statements per description One-to-many statements per description
property URI One per statement; any URI One per statement; any URI
literal value surrogate One per statement One per statement; partial support
literal value surrogate / value string One per literal value surrogate One per literal value surrogate; partial support
literal value surrogate / value string language Zero-to-one per value string Zero-to-one per value string
literal value surrogate / SES URI Zero-to-one per value string Zero-to-one per value string; XML Literal datatype not supported
non-literal value surrogate One per statement One per statement; partial support
non-literal value surrogate / value string Zero-to-many per non-literal value surrogate Zero-to-one per non-literal value surrogate; partial support
non-literal value surrogate / value string language Zero-to-one per value string Zero-to-one per value string
non-literal value surrogate / SES URI Zero-to-one per value string Not supported
non-literal value surrogate / value URI Zero-to-one per non-literal value surrogate One per non-literal value surrogate
non-literal value surrogate / VES URI Zero to one per non-literal value surrogate Not supported

i.e. the conventions here support a description set containing a single description, and a maximum of one value string per value surrogate. In a non-literal value surrogate, a value URI must be provided and a value string must be a plain value string. The provision of a vocabulary encoding scheme URI is not supported.

3. Features of the DC-HTML Meta Data Profile

3.1 URIs in DC-HTML

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

In the DC-HTML profile, 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

In the DC-HTML profile, value URIs are encoded as URI references, used as X/HTML attribute values. A URI reference is either a URI or a relative reference [RFC3986].

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

Example 1: URI as attribute value (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" >
  </head>
  <body>
  </body>
</html>

Example 2: URI as attribute value (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" />
  </head>
  <body>
  </body>
</html>

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 the href attribute of the base element or from the URI of the document itself. In the following example, the value of the hrefattribute is a relative reference. It is resolved relative to the base URI provided by the href attribute of thebase element to obtain a target URI ofhttp://example.org/docs/doc123:

Example 3: Relative reference as attribute value (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <base href="http://example.org/docs/" >
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.isReferencedBy" href="doc123" >
  </head>
  <body>
  </body>
</html>

Example 4: Relative reference as attribute value (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <base href="http://example.org/docs/" >
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.isReferencedBy" href="doc123" />
  </head>
  <body>
  </body>
</html>

3.1.2 URIs,

DC-HTML Prefixed Names and Namespace Declarations

In DC-HTML, property URIs and syntax encoding scheme URIs are 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 description set by 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) 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/title might 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 schemes and syntax encoding schemes), 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 in 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 the nameattribute of the meta element:

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" content="Services to Government" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" content="Services to Government" />
  </head>
  <body>
  </body>
</html>

In a DC-HTML Prefixed Name, the prefix is the part of the name preceding the first period character; the remainder of the string following the period is treated as the "local name" and appended to the "namespace URI". If a DC-HTML Prefixed Name contains more than one period character, the prefix is the part preceding the first period, and the local name is the remainder of the name following the first period, and any subsequent period characters simply form part of the local name.

In the following example the DC-HTML Prefixed Name "XX.date.removed" corresponds to the URI http://example.org/terms/date.removed

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.XX" href="http://example.org/terms/" >
    <meta name="XX.date.removed" content="2007-05-05" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.XX" href="http://example.org/terms/" />
    <meta name="XX.date.removed" content="2007-05-05" />
  </head>
  <body>
  </body>
</html>

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 for that prefix 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 the nameattribute of the meta element:

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" content="Services to Government" >
    <meta name="XX.approved" content="2007-01-05" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" content="Services to Government" />
    <meta name="XX.approved" content="2007-01-05" />
  </head>
  <body>
  </body>
</html>

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 URI http://your.example.org/terms/approved from the value of the name attribute of the meta element:

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.XX" href="http://my.example.org/terms/" >
    <link rel="schema.XX" href="http://your.example.org/terms/" >
    <meta name="DC.title" content="Services to Government" >
    <meta name="XX.approved" content="2007-01-05" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.XX" href="http://my.example.org/terms/" />
    <link rel="schema.XX" href="http://your.example.org/terms/" />
    <meta name="DC.title" content="Services to Government" />
    <meta name="XX.approved" content="2007-01-05" />
  </head>
  <body>
  </body>
</html>

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 theprofile attribute of the X/HTML head element must include the URI of this X/HTML metadata profile http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/

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/HTML link element and a specific convention for the value of the rel attribute. In the DC-HTML profile, an X/HTML link element of which the relattribute 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 the relattribute of the X/HTML link element following the characters schema.

  • a namespace URI, represented by the value of the hrefattribute of the X/HTML link element

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

Example 13: The Namespace Declaration (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.MARCREL" href="http://www.loc.gov/loc.terms/relators/" >
    <meta name="DC.title" content="Services to Government" >
    <link rel="MARCREL.EDT" href="http://example.org/agents/DeptOfObfuscation" >
  </head>
  <body>
  </body>
</html>

Example 14: The Namespace Declaration (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.MARCREL" href="http://www.loc.gov/loc.terms/relators/" />
    <meta name="DC.title" content="Services to Government" />
    <link rel="MARCREL.EDT" href="http://example.org/agents/DeptOfObfuscation" />
  </head>
  <body>
  </body>
</html>

4.3 Encoding

a Description Set

A description set is made up of one_description_.

In the DC-HTML profile, the description set is not explicitly represented, but the statements represented constitute a single description within a description set.

4.4 Encoding

a Description

A description is a set of one or more_statements_ about a resource.

In the DC-HTML profile, the description is not explicitly represented, but the statements represented constitute a single description.

4.4.1 The

Described Resource URI

A description has an associated described resource URI.

In the DC-HTML profile, the _described resource URI_is the URI of the X/HTML document

4.5 Encoding

a Statement

A description is made up of one or more_statements_.

In the DC-HTML profile, each statement is represented as either an X/HTML meta element or an X/HTMLlink element. The choice of X/HTML element depends on whether the statement contains a literal value surrogate or a non-literal value surrogate.

The examples below show a description consisting of two_statements_.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <meta name="DC.title" content="Services to Government" >
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <meta name="DC.title" content="Services to Government" />
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" />
  </head>
  <body>
  </body>
</html>

4.5.1 Encoding a Statement containing a Literal Value Surrogate

In the DC-HTML profile, each statement containing a_literal values surrogate_ is represented as an X/HTMLmeta element.

4.5.1.1 The

Property URI

A statement must contain exactly one property URI.

In the DC-HTML profile, a property URI in a_statement_ containing a _literal values surrogate_is represented as a DC-HTML Prefixed Name which is the value of thename attribute of an X/HTML meta element.

The examples below shows a description consisting of a single statement where the property URI ishttp://purl.org/dc/terms/title.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" content="Services to Government" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" content="Services to Government" />
  </head>
  <body>
  </body>
</html>
4.5.1.2 Encoding a Literal Value Surrogate

A literal value surrogate is made up of exactly one_value string_.

In the DC-HTML profile, a value string within a_literal values surrogate_ is represented by the combination of the values of several attributes of an X/HTML metaelement.

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.

In the DC-HTML profile, the string itself is represented as the value of the content attribute of an X/HTML metaelement, and a value string language is represented by the value of the lang (HTML) or xml:lang (XHTML) attribute of the meta element.

The examples below shows a description consisting of a single statement with a _literal value surrogate_made up of a plain value string with no value string language.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" content="Services to Government" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" content="Services to Government" />
  </head>
  <body>
  </body>
</html>

The examples below shows a description consisting of a single statement with a _literal value surrogate_made up of a plain value string which includes a value string language.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" lang="en" content="Services to Government" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" xml:lang="en" content="Services to Government" />
  </head>
  <body>
  </body>
</html>

A typed value string is associated with a syntax encoding scheme URI.

In the DC-HTML profile, the string itself is represented as the value of the content attribute of an X/HTML metaelement, and a syntax encoding scheme URI is represented as a DC-HTML Prefixed Name which is the value of thescheme attribute of the X/HTML meta element.

The examples below show a description consisting of two_statements_ with literal value surrogates. In the second statement the literal value surrogate contains a typed value string with the_syntax encoding scheme URI_http://www.w3.org/2001/XMLSchema#date:

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="schema.XSD" href="http://www.w3.org/2001/XMLSchema#" >
    <meta name="DC.title" lang="en" content="Services to Government" >
    <meta name="DCTERMS.modified" scheme="XSD.date" content="2007-07-22" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="schema.XSD" href="http://www.w3.org/2001/XMLSchema#" />
    <meta name="DC.title" xml:lang="en" content="Services to Government" />
    <meta name="DCTERMS.modified" scheme="XSD.date" content="2007-07-22" />
  </head>
  <body>
  </body>
</html>

4.5.2 Encoding a Statement containing a Non-Literal Value Surrogate

In the DC-HTML profile, each statement containing a_non-literal values surrogate_ is represented as an X/HTMLlink element.

4.5.2.1. The

Property URI

A statement must contain exactly one property URI.

In the DC-HTML profile, a property URI in a_statement_ containing a non-literal values surrogate is represented as a DC-HTML Prefixed Name which is the value of the rel attribute of an X/HTML linkelement.

The examples below shows a description consisting of a single statement where the property URI ishttp://purl.org/dc/terms/subject.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" />
  </head>
  <body>
  </body>
</html>

The X/HTML rel attribute supports a list of linktypes, so where a description contains multiple statements_referring to different properties but the same_value, they may be represented using a single linkelement.

The examples below shows a description consisting of two statements where the property URIs arehttp://purl.org/dc/terms/creator andhttp://purl.org/dc/terms/publisher.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.creator DCTERMS.publisher" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.creator DCTERMS.publisher" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" />
  </head>
  <body>
  </body>
</html>

The same description could be represented using repeated link elements:

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.creator" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" >
    <link rel="DCTERMS.publisher" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.creator" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" />
    <link rel="DCTERMS.publisher" href="http://example.org/agents/DCMI" title="Dublin Core™ Metadata Initiative" />
  </head>
  <body>
  </body>
</html>
4.5.2.2. Encoding a Non-Literal Value Surrogate

In the subset of the DCAM description model supported by the DC-HTML profile, a non-literal value surrogate is made up of exactly one value URI and zero or one plain value strings.

In the DC-HTML profile, the value URI is represented as the value of the href attribute of the X/HTMLlink element

The examples below shows a description consisting of a single statement with a non-literal value surrogate made up of a value URI.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" />
  </head>
  <body>
  </body>
</html>

A plain value string may be associated with a value string language.

In the DC-HTML profile, the string itself is represented as the value of the title attribute of the X/HTML linkelement, and a value string language is represented by the value of the lang (HTML) or xml:lang (XHTML) attribute of the link element.

The examples below shows a description consisting of a single statement with a non-literal value surrogate made up of a value URI and a plain value string with no value string language.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.subject" href="http://example.org/topics/archives" title="Archives" />
  </head>
  <body>
  </body>
</html>

The examples below shows a description consisting of a single statement with a non-literal value surrogate made up of a value URI and a plain value string which includes a value string language.

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" >
    <link rel="DCTERMS.subject" lang="en" href="http://example.org/topics/archives" title="Archives" >
  </head>
  <body>
  </body>
</html>

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

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />
    <link rel="DCTERMS.subject" xml:lang="en" href="http://example.org/topics/archives" title="Archives" />
  </head>
  <body>
  </body>
</html>

Addendum

1. Additional Notes on Namespace Declarations

1.1 Case in Prefix Matching

The case of the characters in the string schema. is not significant. If the value of the relattribute of the X/HTML link element begins with the strings SCHEMA. or sChEmA., then the element is interpreted as a namespace declaration.

Note also that the matching of the prefix in a DC-HTML Prefixed Name to the prefix in the namespace declaration is not case-sensitive, e.g. a prefix of "dc" in the value of the nameattribute of the meta element will match a prefix of "DC" in the value of the rel attribute of the link element.

In the following example the namespace declaration associates the prefix "DC" with the namespace URI http://purl.org/dc/elements/1.1/, and the DC-HTML Prefixed Name "dc.title" corresponds to the URI http://purl.org/dc/elements/1.1/title

Example Add 01: The Namespace Declaration: Case in Prefix Matching (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="SCHEMA.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="dc.title" content="Services to Government" >
  </head>
  <body>
  </body>
</html>

Example Add 02: The Namespace Declaration: Case in Prefix Matching (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="SCHEMA.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="dc.title" content="Services to Government" />
  </head>
  <body>
  </body>
</html>

Note, however, that case is significant in the interpretation of the URIs generated from DC-HTML prefixed names by a DCAM/RDF application: e.g. the two URIs http://example.org//terms/title and http://example.org//terms/Title are not considered equal.

1.2 Prefix Conventions

It is important to note that the use of prefixes such as "DC" or "DCTERMS" is simply a community convention. There is no requirement that these prefixes are associated with the namespace URIs http://purl.org/dc/elements/1.1/ and http://purl.org/dc/terms/

In the following example the namespace declaration associates the prefix "DC" with the namespace URI http://example.org/terms/, and the DC-HTML Prefixed Name "DC.date" corresponds to the URI http://example.org/terms/date

Example Add 03: The Namespace Declaration: Prefix Conventions (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://example.org/terms/" >
    <meta name="DC.date" content="2007-05-05" >
  </head>
  <body>
  </body>
</html>

Example Add 04: The Namespace Declaration: Prefix Conventions (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://example.org/terms/" />
    <meta name="DC.date" content="2007-05-05" />
  </head>
  <body>
  </body>
</html>

Similarly, the namespace URIs http://purl.org/dc/elements/1.1/ and http://purl.org/dc/terms/ may be associated with any prefixes.

In the following example the namespace declaration associates the prefix "XX" with the namespace URI http://purl.org/dc/elements/1.1/, and the DC-HTML Prefixed Name "XX.date" corresponds to the URI http://purl.org/dc/elements/1.1/date

Example Add 05: The Namespace Declaration: Prefix Conventions (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.XX" href="http://purl.org/dc/elements/1.1/" >
    <meta name="XX.date" content="2007-05-05" >
  </head>
  <body>
  </body>
</html>

Example Add 06: The Namespace Declaration: Prefix Conventions (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.XX" href="http://purl.org/dc/elements/1.1/" />
    <meta name="XX.date" content="2007-05-05" />
  </head>
  <body>
  </body>
</html>

1.3 Omitted Declarations

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.

In the following examples the prefixes "XX" and "DCTERMS" are used in DC-HTML Prefixed Names, but there are no namespace declarations for those prefixes so no URI is generated for those values of the nameattribute of the meta element. Note that this applies to the "DCTERMS" prefix, as well as to the "XX" prefix: the "DC" and "DCTERMS" prefixes are not subject to any special treatment; there are no "built-in" namespace declarations.

Example Add 07: The Namespace Declaration: Omitted Declarations (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <meta name="DC.title" content="Services to Government" >
    <meta name="XX.approved" content="2007-01-05" >
    <meta name="DCTERMS.issued" content="2007-01-04" >
  </head>
  <body>
  </body>
</html>

Example Add 08: The Namespace Declaration: Omitted Declarations (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <meta name="DC.title" content="Services to Government" />
    <meta name="XX.approved" content="2007-01-05" />
    <meta name="DCTERMS.issued" content="2007-01-04" />
  </head>
  <body>
  </body>
</html>

1.4 Multiple Declarations

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 for that prefix in the DC-HTML instance.

In the following examples the prefix "XX" is used in a DC-HTML Prefixed Name, and there are two namespace declaration for that prefix. The second namespace declaration is used to generate the URI http://your.example.org/terms/approved from the value of the name attribute of the meta element:

Example Add 09: The Namespace Declaration: Multiple Declarations (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.XX" href="http://my.example.org/terms/" >
    <link rel="schema.XX" href="http://your.example.org/terms/" >
    <meta name="DC.title" content="Services to Government" >
    <meta name="XX.approved" content="2007-01-05" >
  </head>
  <body>
  </body>
</html>

Example Add 10: The Namespace Declaration: Multiple Declarations (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.XX" href="http://my.example.org/terms/" />
    <link rel="schema.XX" href="http://your.example.org/terms/" />
    <meta name="DC.title" content="Services to Government" />
    <meta name="XX.approved" content="2007-01-05" />
  </head>
  <body>
  </body>
</html>

1.5 Prefixed Names Preceding Declarations

The meta or link elements containing the DC-HTML prefixed names in name and rel attribute values may occur before the link elements representing namespace declarations for the prefixes used. As above, in the case of multiple declarations for a single prefix, the latest declaration for the prefix is used.

In the following examples, the second namespace declaration is used to generate the URI http://your.example.org/terms/approved from the value of the name attribute of the meta element:

Example Add 11: The Namespace Declaration: Prefixed Names Preceding Declarations (HTML)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
   "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <meta name="DC.title" content="Services to Government" >
    <meta name="XX.approved" content="2007-01-05" >
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" >
    <link rel="schema.XX" href="http://my.example.org/terms/" >
    <link rel="schema.XX" href="http://your.example.org/terms/" >
  </head>
  <body>
  </body>
</html>

Example Add 12: The Namespace Declaration: Prefixed Names Preceding Declarations (XHTML)

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head profile="http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/">
    <title>Services to Government</title>
    <meta name="DC.title" content="Services to Government" />
    <meta name="XX.approved" content="2007-01-05" />
    <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
    <link rel="schema.XX" href="http://my.example.org/terms/" />
    <link rel="schema.XX" href="http://your.example.org/terms/" />
  </head>
  <body>
  </body>
</html>

Appendix A.

DC-TEXT Representation of Example Description Sets

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

A.1 Examples

1 & 2

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
    )
  )
)

A.2 Example

3 & 4

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    ResourceURI ( <http://example.org/docs/> )
    Statement (
      PropertyURI ( dcterms:isReferencedBy )
      ValueURI ( <http://example.org/docs/doc123> )
    )
  )
)

A.3 Example

5 & 6

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.4 Example

7 & 8

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

@prefix xx: <http://example.org/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( xx:date.removed )
      LiteralValueString ( "2007-05-05" )
    )
  )
)

A.5 Example

9 & 10

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.6 Example

11 & 12

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix your: <http://your.example.org/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
    Statement (
      PropertyURI ( your:approved )
      LiteralValueString ( "2007-01-05" )
    )
  )
)

A.7 Example

13 & 14

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix marcrel: <http://www.loc.gov/loc.terms/relators/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
    Statement (
      PropertyURI ( marcrel:EDT )
      ValueURI ( <http://example.org/agents/DeptOfObfuscation> )
    )
  )
)

A.8 Examples

15 & 16

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
      ValueString ( "Archives" )
    )
  )
)

A.9 Examples

17 & 18

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.10 Examples

19 & 20

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.11 Examples

21 & 22

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government"
        Language ( en )
      )
    )
  )
)

A.12 Examples

23 & 24

The X/HTML instances in Examples 23 & 24 represent the following description set:

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government"
        Language ( en )
      )
    )
    Statement (
      PropertyURI ( dcterms:modified )
      LiteralValueString ( "2007-07-22"
        SyntaxEncodingSchemeURI ( <http://www.w3.org/2001/XMLSchema#date> )
      )
    )
  )
)

A.13

Examples 25 & 26

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
      ValueString ( "Archives" )
    )
  )
)

A.14

Examples 27 & 28

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:creator )
      ValueURI ( <http://example.org/agents/DCMI> )
      ValueString ( "Dublin Core™ Metadata Initiative" )
    )
    Statement (
      PropertyURI ( dcterms:publisher )
      ValueURI ( <http://example.org/agents/DCMI> )
      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: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:publisher )
      ValueURI ( <http://example.org/agents/DCMI> )
      ValueString ( "Dublin Core™ Metadata Initiative" )
    )
    Statement (
      PropertyURI ( dcterms:publisher )
      ValueURI ( <http://example.org/agents/DCMI> )
      ValueString ( "Dublin Core™ Metadata Initiative" )
    )
  )
)

A.16

Examples 31 & 32

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
    )
  )
)

A.17

Examples 33 & 34

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

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
      ValueString ( "Archives" )
    )
  )
)

A.18

Examples 35 & 36

The X/HTML instances in Examples 35 & 36 represent the following description set:

@prefix dcterms: <http://purl.org/dc/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dcterms:subject )
      ValueURI ( <http://example.org/topics/archives> )
      ValueString ( "Archives"
        Language ( en )
      )
    )
  )
)

A.19 Examples Add 01 & Add 02

The X/HTML instances in Examples Add 01 & Add 02 represent the following description set:

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.20 Examples Add 03 & Add 04

The X/HTML instances in Examples Add 03 & Add 04 represent the following description set:

@prefix dc: <http://example.org/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:date )
      LiteralValueString ( "2007-05-05" )
    )
  )
)

A.21 Examples Add 05 & Add 06

The X/HTML instances in Examples Add 05 & Add 06 represent the following description set:

@prefix xx: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( xx:date )
      LiteralValueString ( "2007-05-05" )
    )
  )
)

A.22 Examples Add 07 & Add 08

The X/HTML instances in Examples Add 07 & Add 08 represent the following description set:

@prefix dc: <http://purl.org/dc/elements/1.1/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
  )
)

A.23 Examples Add 09 & Add 10

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix your: <http://your.example.org/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
    Statement (
      PropertyURI ( your:approved )
      LiteralValueString ( "2007-01-05" )
    )
  )
)

A.24 Examples Add 11 & Add 12

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

@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix your: <http://your.example.org/terms/> .
DescriptionSet (
  Description (
    Statement (
      PropertyURI ( dc:title )
      LiteralValueString ( "Services to Government" )
    )
    Statement (
      PropertyURI ( your:approved )
      LiteralValueString ( "2007-01-05" )
    )
  )
)

Appendix B.

RDF/XML Representation of Examples

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

B.1 Examples

1 & 2

The X/HTML instances in Examples 1 & 2 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:subject rdf:resource="http://example.org/topics/archives" />
  </rdf:Description>
</rdf:RDF>

B.2 Example

3 & 4

The X/HTML instances in Examples 3 & 4 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="http://example.org/docs/">
    <dcterms:isReferencedBy rdf:resource="http://example.org/docs/doc123" />
  </rdf:Description>
</rdf:RDF>

B.3 Example

5 & 6

The X/HTML instances in Examples 5 & 6 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.4 Example

7 & 8

The X/HTML instances in Examples 7 & 8 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
        xmlns:xx="http://example.org/terms/" >
  <rdf:Description rdf:about="">
    <xx:date.removed>2007-05-05</xx:date.removed>
  </rdf:Description>
</rdf:RDF>

B.5 Example

9 & 10

The HTML/XHTML instances in Examples 9 & 10 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.6 Example

11 & 12

The X/HTML instances in Examples 11 & 12 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
        xmlns:your="http://your.example.org/terms/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
    <your:approved>2007-01-05</your:approved>
  </rdf:Description>
</rdf:RDF>

B.7 Example

13 & 14

The X/HTML instances in Examples 13 & 14 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
        xmlns:marcrel="http://www.loc.gov/loc.terms/relators/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
    <marcrel:EDT rdf:resource="http://example.org/agents/DeptOfObfuscation" />
  </rdf:Description>
</rdf:RDF>

B.8 Examples

15 & 16

The X/HTML instances in Examples 15 & 16 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
    <dcterms:subject rdf:resource="http://example.org/topics/archives" />
  </rdf:Description>
</rdf:RDF>

B.9 Examples

17 & 18

The X/HTML instances in Examples 17 & 18 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.10 Examples

19 & 20

The X/HTML instances in Examples 19 & 20 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.11 Examples

21 & 22

The X/HTML instances in Examples 21 & 22 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title xml:lang="en">Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.12 Examples

23 & 24

The X/HTML instances in Examples 23 & 24 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dc:title xml:lang="en">Services to Government</dc:title>
    <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2007-07-22</dcterms:modified>
  </rdf:Description>
</rdf:RDF>

B.13

Examples 25 & 26

The X/HTML instances in Examples 21 & 22 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:subject rdf:resource="http://example.org/topics/archives" rdf:value="Archives" />
  </rdf:Description>
</rdf:RDF>

B.14

Examples 27 & 28

The X/HTML instances in Examples 27 & 28 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:creator rdf:resource="http://example.org/agents/DCMI" rdf:value="Dublin Core™ Metadata Initiative" />
    <dcterms:publisher rdf:resource="http://example.org/agents/DCMI" rdf:value="Dublin Core™ Metadata Initiative" />
  </rdf:Description>
</rdf:RDF>

B.15

Examples 29 & 30

The X/HTML instances in Examples 29 & 30 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:creator rdf:resource="http://example.org/agents/DCMI" rdf:value="Dublin Core™ Metadata Initiative" />
    <dcterms:publisher rdf:resource="http://example.org/agents/DCMI" rdf:value="Dublin Core™ Metadata Initiative" />
  </rdf:Description>
</rdf:RDF>

B.16

Examples 31 & 32

The X/HTML instances in Examples 31 & 32 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:subject rdf:resource="http://example.org/topics/archives" />
  </rdf:Description>
</rdf:RDF>

B.17

Examples 33 & 34

The X/HTML instances in Examples 33 & 34 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:subject rdf:resource="http://example.org/topics/archives" rdf:value="Archives" />
  </rdf:Description>
</rdf:RDF>

B.18

Examples 35 & 36

The X/HTML instances in Examples 35 & 36 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dcterms="http://purl.org/dc/terms/" >
  <rdf:Description rdf:about="">
    <dcterms:subject xml:lang="en" rdf:resource="http://example.org/topics/archives" rdf:value="Archives" />
  </rdf:Description>
</rdf:RDF>

B.19 Examples Add 01 & Add 02

The HTML/XHTML instances in Examples Add 01 & Add 02 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.20 Examples Add 03 & Add 04

The HTML/XHTML instances in Examples Add 03 & Add 04 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://example.org/terms/" >
  <rdf:Description rdf:about="">
    <dc:date>2007-05-05</dc:date.>
  </rdf:Description>
</rdf:RDF>

B.21 Examples Add 05 & Add 06

The HTML/XHTML instances in Examples Add 05 & Add 06 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <xx:date>2007-05-05</xx:date.>
  </rdf:Description>
</rdf:RDF>

B.22 Examples Add 07 & Add 08

The HTML/XHTML instances in Examples Add 07 & Add 08 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
  </rdf:Description>
</rdf:RDF>

B.23 Examples Add 09 & Add 10

The HTML/XHTML instances in Examples Add 09 & Add 10 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
        xmlns:your="http://your.example.org/terms/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
    <your:approved>2007-01-05</your:approved>
  </rdf:Description>
</rdf:RDF>

B.20 Examples Add 11 & Add 12

The HTML/XHTML instances in Examples Add 11 & Add 12 represent the following RDF graph:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:dc="http://purl.org/dc/elements/1.1/" >
        xmlns:your="http://your.example.org/terms/" >
  <rdf:Description rdf:about="">
    <dc:title>Services to Government</dc:title>
    <your:approved>2007-01-05</your:approved>
  </rdf:Description>
</rdf:RDF>

References

[ABSTRACT-MODEL]
DCMI Abstract Model DCMI Recommendation. 2007-06-04
http://dublincore.org/specifications/dublin-core/abstract-model/2007-06-04/

[DC-TEXT]
Expressing Dublin Core™ metadata using the DC-Text format DCMI Recommended Resource. 2007-12-03
http://dublincore.org/specifications/dublin-core/dc-text/2007-12-03/

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

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

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

Acknowledgements

This document draws on the existing recommendations for encoding Dublin Core™ metadata in HTML, including documents by John Kunze, Simon Cox, Eric Miller and Andy Powell, and on comments made by Julian Reschke.

Errata

2010-05-17 : Addded section 1.2 on standalone validity and entity references.

2010-05-17 : Changed entity reference from   to  .

2010-02-15 : Corrected profile URI values in twelve examples in Addendum.

2010-02-15 : Corrected date of two of previous errata changes.

2009-09-21 : Changed value of profile attribute of this document to refer to both http://www.w3.org/2003/g/data-view and http://dublincore.org/specifications/dublin-core/dc-html/2008-08-04/ profiles

2009-09-21 : In section 3.1.2, changed "the latest declaration in the DC-HTML instance" to "the latest declaration for that prefix in the DC-HTML instance"

2009-09-21 : Added Addendum on namespace declarations to emphasise that case is not significant in matching prefix to namespace declaration; the prefixes "DC" and "DCTERMS" may be associated with any "namespace URI", and the "namespace URIs" http://purl.org/dc/elements/1.1/ and http://purl.org/dc/terms/ may be associated with any prefix; namespace declarations are required for all prefixes, including "DC" and "DCTERMS"; and that the use of a prefix in a may precede a namespace declaration.

2009-09-21 : Added new DC-Text and RDF/XML examples to Appendices A and B, corresponding to the new examples in the Addendum.