These qualifiers identify schemes that aid in the interpretation of an element value. These schemes include controlled vocabularies and formal notations or parsing rules. A value expressed using an encoding scheme will thus be a token selected from a controlled vocabulary (e.g., a term from a classification system or set of subject headings) or a string formatted in accordance with a formal notation (e.g., "2000-01-01" as the standard expression of a date). If an encoding scheme is not understood by a client or agent, the value may still be useful to a human reader.

In some cases, encoding schemes not yet registered that are needed for DC-Lib are indicated. These will be registered and/or approved by the DCMI Usage Board as DC Encoding Schemes in the future.

Either a Title or an Identifier is mandatory. If no title is available, best practice is to give a constructed title, derive a title from the resource or supply [no title]. If using qualified Dublin Core, an element refinement for titles other than the main title(s) should be included.

Retain initial articles and use local sorting algorithms based on language. A language qualifier may be used to indicate language of title if appropriate. (For example, see: Initial Definite and Indefinite Articles for a list of articles in various languages)

Best practice is to use this element refinement for titles other than the main title.

Retain initial articles and use local sorting algorithms based on language. A language qualifier may be used to indicate language of title if appropriate. (For example, see: Initial Definite and Indefinite Articles for a list of articles in various languages)

Note: This table is used for encoding schemes currently defined by DCMI. As additional schemes are registered, they will be included.

Additional encoding schemes will be registered for those used in the library domain based on the MARC list of subject and classification schemes. Including an identifier to link to a registry where all encoding schemes are defined (e.g. based on RSLP schema) needs to be explored.

Recommend use of an element refinement for type of Date. Recommend that dates be encoded 1) using W3C-DTF (structured with hyphens) or ISO 8601 (structured without hyphens) or 2) supplied as free text that does not take the form of a string of numerals (with or without hyphens).

It is acceptable to use widely-recognized practice such as day-month-year where the day and year are represented with numerals and month with a name or standard abbreviation (e.g., "1 January 2002" or "1 Jan 2002"). Avoid the use of potentially ambiguous date representations such as DD/MM/YY or MM/DD/YY (e.g., "04/05/05")

This includes the date that a snapshot of the resource was taken (particularly for dynamic resources) if different from Date.Created.

Use existing element <dateCaptured> under <publicationInfo> in the Metadata Object Description Schema.

Standard identifier: Provide at least one standard identifier from a standard scheme (e.g., URL, ISBN, etc.) if one or more standard identifiers have been assigned to the resource and are known to the metadata agency.

Unique-resource identifier: Provide applicable identifiers assigned to one-of-a-kind resources (such as accession numbers assigned to items in a museum collection) if one or more of this class of identifiers have been assigned to the resource and are known to the metadata agency. If the structure of the identifier (e.g., all numerals) is potentially ambiguous it is recommended that the associated agencies' name be included as part of the identifier element.

Citation: Provide a citation if no standard identifier is assigned and a formal citation is a common means of identifying the resource being described (e.g., a journal article).

Use the element Identifier on a more abstract level; identifier for local library holdings like call number could be put into the DC-Lib element Holding Location.

A constructed or derived ID of a local nature may be supplied, including a specification of the supplying organisation, in the absence of a globally unique one.

In the absence of a globally unique Identifier, a constructed or derived one of a local nature can be supplied, including a specification of the supplying organisation.

Consider registering OpenURL as an encoding scheme after completion of the standard.

If using qualifiers, use the most specific one that is applicable.

When no Identifier is available, a bibliographic description may be constructed. Future work will involve developing guidelines.

DCMI Point, ISO 3166, DCMI Box, TGN

MARC Geographic Area Codes, MARC Country Codes

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

Use this element for geographic coverage. The value of this element may also be included in Subject if desired.

There is a need to evaluate DCMI Box and DCMI Point as for their usefulness for libraries and how they relate to current library practices for recording cartographic data.

Need to evaluate whether any refinements or encoding scheme(s) are appropriate for DC-Lib use. MARC target audience codes may be considered.

Being able to specify the version or edition of a given work is often critical to successful resource discovery and identification to determine whether a resource is the same as another one. This is particularly important for resources that change frequently. This is not to be used for versions in the sense of different physical formats (e.g. the PDF version of a textual resource).
Use existing element <edition> under <publicationInfo> in the Metadata Object Description Schema

Decision by DCMI Usage Board in May 2002.

Use for a physical location that allows the user to retrieve the item when a URI is not appropriate (e.g. for physical items not available electronically). This also facilitates access if the URI doesn't retrieve anything or only a poor substitute. When there is further identification within a location (e.g. call number, accession number), consider using Identifier.

Use existing element <location> in the Metadata Object Description Schema

Decision by DCMI Usage Board in May 2002.