A name given to the resource. This element is taken from the Dublin Core metadata standard v1.1.
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, such as a URI. This element is taken from the Dublin Core metadata standard v1.1.
A date of an event in the lifecycle of the resource. Will typically 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. This element is taken from the Dublin Core metadata standard v1.1.
An entity primarily responsible for making the content of the resource. Examples include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. This element is taken from the Dublin Core metadata standard v1.1.
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 [MIME] defining computer media formats). This element is taken from the Dublin Core metadata standard v1.1.
An account of the content of the resource. Examples include: An abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. This element is taken from the Dublin Core metadata standard v1.1.
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. This element is taken from the Dublin Core metadata standard v1.1.
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. This element is taken from the Dublin Core metadata standard v1.1.
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. This element is taken from the Dublin Core metadata standard v1.1.
An entity responsible 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.
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.
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.
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.
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.
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.