| The Dublin Core Metadata Initiative has established a common set of 15 metadata properties which apply to resources of all types across many areas of interest. The "Dublin Core", as the DCMI Metadata Terms are often referred to, encapsulates all of the metadata that many applications require. DCMI also has a standard binding to RDF, so using Dublin Core in HyperContent provides a way to store metadata that is completely standards based and widely understood by people and machines alike.
HyperContent has a built in editor for Dublin Core metadata; here is a description of the fifteen elements taken from the original publication, with some clarifications made in descriptions of version 1.1, and annotations with usage information specific to HyperContent.
Dublin Core 1.0 Namespace:
The name given to the resource, usually by the Creator or Publisher.
HyperContent displays the Title of a file in the Content Manager when the file is selected, or appears in a list such as search results. It is recommended to use Title as the text of links to a file, and in the title tag of HTML output.
Author or Creator
The person or organization primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources.
HyperContent automatically sets the active users name as Creator when a new file is created
Subject and Keywords
The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemas is encouraged.
A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources.
The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity.
A person or organization not specified in a Creator element who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organization specified in a Creator element (for example, editor, transcriber, and illustrator).
A date associated with the creation or availability of the resource. Recommended best practice is defined in a profile of ISO 8601 ( http://www.w3.org/TR/NOTE-datetime ) that includes (among others) dates of the forms YYYY and YYYY-MM-DD. In this scheme, the date 1994-11-05 corresponds to November 5, 1994.
HyperContent sets Date to current the date when a file is first created.
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.
HyperContent will set the Type of a file when it is created to DCMI Image, Text, or Audio according to the file's MIME type. If none of those is appropriate, it is left blank. The user can select the type from a dropdown list of all the DCMI types. This list can be controlled in the properties file dcmi-types.xml.
The data format and, optionally, dimensions (e.g., size, duration) of the resource. The format is used to identify the software and possibly hardware that might be needed to display or operate the resource. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types defining computer media formats).
HyperContent sets the Format of a file to it's MIME type when it is created.
A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as International Standard Book Numbers (ISBN) or other formal names would also be candidates for this element.
HyperContent sets the Identifier of a file to its path in the repository at the time it is created.
Information about a second resource from which the present resource is derived. While it is generally recommended that elements contain information about the present resource only, this element may contain metadata for the second resource when it is considered important for discovery of the present resource.
Recommended best practice is to use RFC 3066 which, in conjunction with 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.
HyperContent's built-in Dublin Core editor allows the user to select from a list of all languages represented by two letter language codes; this list can be edited in the properties file language-codes.xml. The Language, if set, will be used to find the best corresponding dictionary for use in the spell checker.
An identifier of a second resource and its relationship to the present resource. This element is used to express linkages among related resources. Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system
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) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.
A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource.