HOME > メモ > DublinCore

Dublin Core

Dublin Core Metadeta Initiative（http://dublincore.org/）が制定している、「Title」「Creator」「Subject」など15の属性（メタデータ）のセット。

文書などの標準的な属性セットとしてXMLなどでよく用いられ、しばしば「DC」と略される。

Dublin Coreのキャッチフレーズは「Making it easier to find information」。

---

以下の説明は、

http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/DublicCoreMetaDataForContent

より引用

Brief dublin core overview

See http://dublincore.org for more detailed description.

The Dublin Core defines the 15 elements:

• Title

  A name given to the resource.

  Typically, a Title will be a name by which the resource is formally known.

• Creator

  An entity primarily responsible for making the content of the resource.

  Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.

• Subject

  The topic of the content of the resource.

  Typically, a 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.

• Description

  An account of the content of the resource.

  Description may 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.

• Publisher

  An entity responsible for making the resource available

  Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.

• Contributor

  An entity responsible for making contributions to the content of the resource.

  Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity.

• Date

  A date associated with an event in the life cycle 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 W3CDTFx and follows the YYYY-MM-DD format.

• Type

  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 working draft list of Dublin Core Types DCT1x). To describe the physical or digital manifestation of the resource, use the FORMAT element.

• Format

  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 determine 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 MIMEx defining computer media formats).

• Identifier

  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. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).

• Source

  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 reference the resource by means of a string or number conforming to a formal identification system.

• Language

  A language of the intellectual content of the resource.

  Recommended best practice for the values of the Language element is defined by RFC 1766 RFC1766x which includes a two-letter Language Code (taken from the ISO 639 standard ISO639x), followed optionally, by a two-letter Country Code (taken from the ISO 3166 standard ISO3166x). For example, en for English, fr for French, or en-uk for English used in the United Kingdom.

• Relation

  A reference to a related resource.

  Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.

• Coverage

  The extent or scope of the content of the resource.

  Coverage will typically 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 TGNx) and that, where appropriate, named places or time periods be used in preference to numeric identifiers such as sets of coordinates or date ranges.

• Rights

  Definition: Information about rights held in and over the resource.

  Typically, a Rights element 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 can be made about the status of these and other rights with respect to the resource.

The Dublin Core allows all elements to be repeated. A content objects may often have multiple dates associated with it and could even have multiple descriptions.

The elements may be qualified. For example, you can have both creation and modification dates.

See Also : XML SemanticWeb