Matrix defining the KEV Format to represent the Dublin Core Element Set


dc:title KEV Format: dc
dc:creator Committee NISO AX, OpenURL Standard Committee
dc:description This Matrix represents the Dublin Core Element Set.
dc:identifier info:ofi/fmt:kev:mtx:dc
dcterms:created 2004-01-01
dcterms:modified

A representation of a Key/Encoded-Value pair is generated by concatenating the contents of the first four columns of a row that begins with an ampersand in the Matrix below. The ordering of KEV pairs is not important. Rows which have '#' in the first column are comments and should not be included in the representation.

The following data types are provided for the values of the Keys, which must be URL-encoded:

<data> Character string
<id> Character string for an Identifier (Z39.88-2004, Part 1, Section 7)
<fmt-id> Character string for a Format Identifier (Z39.88-2004, Part 1, Sections 12 a nd 13)
<m-key> Character string for a Metadata Key (Z39.88-2004, Part 2, Section 7.1)
<url> Character string for a URL
<date> Character string representing a date to the complete date level of the W3CDTF profile of ISO 8601, of the form: [ YYYY-MM-DD | YYYY-MM | YYYY ]
<time> Character string representing a date and time to the seconds level of the W3CDTF profile of ISO 8601, of the form: [ YYYY-MM-DDThh:mm:ssTZD | YYYY-MM-DD ]

Abbreviations in column headings:

Delim Key Equals Value Min Max Description
& title = <data> 0 * A name given to the resource. Typically, Title will be a name by which the resource is formally known.
uri: http://purl.org/dc/elements/1.1/title
dc:title
& creator = <data> 0 *
An entity primarily responsible for making the content of the resource. Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
uri: http://purl.org/dc/elements/1.1/creator
dc:creator
& subject = <data> 0 * A topic of the content of the resource. Typically, Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
uri: http://purl.org/dc/elements/1.1/subject
dc:subject
& description = <data> 0 * An account of the content of the resource. Examples of Description include, but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.
uri: http://purl.org/dc/elements/1.1/description
dc:description
& publisher = <data> 0 * An entity responsbile for making the resource available. Examples of Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
uri: http://purl.org/dc/elements/1.1/publisher
dc:publisher
& contributor = <data> 0 * An entity responsible for making contributions to the content of the resource. Examples of Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
uri: http://purl.org/dc/elements/1.1/contributor
dc:contributor
& date = <data> 0 * A date of an event in the lifecycle of the resource. Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 and includes (among others) dates of the form YYYY-MM-DD.
uri: http://purl.org/dc/elements/1.1/date
dc:date
& type = <data> 0 * The nature or genre of the content of the resource. Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary. To describe the physical or digital manifestation of the resource, use the FORMAT element.
uri: http://purl.org/dc/elements/1.1/type
dc:type
& format = <data> 0 * The physical or digital manifestation of the resource. Typically, Format may include the media-type or dimensions of the resource. Format may be used to identify the software, hardware, or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types defining computer media formats).
uri: http://purl.org/dc/elements/1.1/format
dc:format
& identifier = <data> 0 * An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Formal identification systems include but are not limited to the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).
uri: http://purl.org/dc/elements/1.1/identifier
dc:identifier
& source = <data> 0 * A Reference to a resource from which the present resource is derived. The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.
uri: http://purl.org/dc/elements/1.1/source
dc:source
& language = <data> 0 * A language of the intellectual content of the resource.
Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian", and "en-GB" for English used in the United Kingdom.
uri: http://purl.org/dc/elements/1.1/language
dc:language
& relation = <data> 0 * A reference to a related resource.
Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.
uri: http://purl.org/dc/elements/1.1/relation
dc:relation
& coverage = <data> 0 * The extent or scope of the content of the resource. Typically, Coverage will include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.
uri: http://purl.org/dc/elements/1.1/coverage
dc:coverage
& rights = <data> 0 * Information about rights held in and over the resource. Typically, Rights will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions may be made about any rights held in or over the resource.
uri: http://purl.org/dc/elements/1.1/rights
dc:rights