OLAC Metadata Set

This document specifies the metadata set used by the Open Language Archives Community [OLAC] for the interchange of metadata within the framework of the Open Archives Initiative [OAI].

Fixes broken URLs in references.

There are no refinements for this element.

There are no encoding schemes for this element.

Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity. [DCMES1.1]

The name should be given in a form that is ready for sorting within an index. For the names of persons, this means that the name should be given in inverted order with the surname first. For the names of organizations, this means that any initial article should be omitted. When a resource has more than one contributor, use a separate Contributor element for each one.

Contributor is closely related to Creator. The Contributor designation is used for those entities whose role in the creation of the resource is not great enough to merit recognition as a primary source of the intellectual content.

A generic contributor:

<contributor>Smith, John L.</contributor>

A funding agency:

<contributor refine="funder">National Science
            Foundation</contributor>

There are no refinements for this element.

There are no encoding schemes for this element.

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. [DCMES1.1]

There are no refinements for this element.

There are no encoding schemes for this element.

Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. [DCMES1.1]

The name should be given in a form that is ready for sorting within an index. For the names of persons, this means that the name should be given in inverted order with the surname first. For the names of organizations, this means that any initial article should be omitted. When a resource has more than one creator, use a separate Creator element for each one.

Creator is closely related to Contributor. In determining whether an entity is a Creator (as opposed to a Contributor), use the same criteria that are followed for deciding that an entity should be listed in the "author" slot of a bibliographic reference as a primary source of the intellectual content. Entities that do not merit that level of recognition should be treated as Contributors.

A personal author:

<creator>Bloomfield, Leonard</creator>

An institutional author:

<creator>Linguistic Society of America</creator>

An editor:

<creator refine="editor">Sapir, Edward</creator>

There are no refinements for this element.

There are no encoding schemes for this element.

Following [DCMES1.1], we recommend that the date be encoded in YYYY-MM-DD format as defined in [W3CDTF]. Use two digits for month and day, even when the value is less than ten. This guarantees that a service provider can always do a straight alphanumeric sort to put values into correct chronological order.

A typical year of publication:

<date>1992</date>

A resource modified on October 16, 1996:

<date refine="modified">1996-10-16</date>

There are no refinements for this element.

There are no encoding schemes for this element.

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. [DCMES1.1]

No formatting conventions are defined within the text of Description. Service providers may format the entire Description as a single paragraph, collapsing adjacent white space characters into a single space.

When there is a URL for a document that describes the resource, use a separate Description element to encode just that URL. A Description that begins with "http:" will be interpreted by service providers as consisting solely of a URL and will be presented as a link in user interfaces. Service providers are not obliged to search other Description text for the occurrence of URLs.

A prose description of a resource:

<description>The CALLHOME Japanese corpus of telephone
            speech consists of 120 unscripted telephone conversations between native
            speakers of Japanese. All calls, which lasted up to 30 minutes, originated in
            North America and were placed to locations overseas (typically Japan). Most
            participants called family members or close friends. This corpus contains
            speech data files ONLY, along with the minimal amount of documentation needed
            to describe the contents and format of the speech files and the software
            packages needed to uncompress the speech data. </description>

A reference to an existing on-line description:

<description>http://www.ldc.upenn.edu/Catalog/LDC96S37.html
</description>

There are no refinements for this element.

There are no encoding schemes for this element.

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. [DCMES1.1]

For a digitally encoded dictionary:

<format code="text/xml">5,237 entries in a 1.2M XML
            file.</format>

For a digitally recorded text:

<format code="audio/wav">Duration: 153 seconds. Size: 3.3M.
            Sampling: 1 channel, 22 KHz, 8 bits.</format>

There are no refinements for this element.

There are no encoding schemes for this element.

This element is used in the description of executable programs to identify the kind of CPU that is needed to run them.

Software that runs on a Power PC:

<format.cpu code="ppc"/>

Software that runs on the Intel family of processors but needs at least 64 megabytes of memory:

<format.cpu code="x86">At least 64M
            memory</format.cpu>

There are no refinements for this element.

There are no encoding schemes for this element.

For a resource that is a digitally encoded text, Format.encoding names the encoded character set it uses. For a resource that is a font, Format.encoding names an encoded character set that it is able to render. For a resource that is a software application, Format.encoding names an encoded character set that it can read as input or write as output. Service providers will use this information to match data files with the software tools that can be applied to them.

There are no refinements for this element.

There are no encoding schemes for this element.

For a resource that is a text file including markup, Format.markup identifies the markup system it uses, such as the SGML DTD, the XML Schema, the set of Standard Format markers, and the like. For a resource that is a stylesheet or a software application, Format.markup names a markup scheme that it can read as input or write as output. Service providers will use this information to match data files with the software tools that can be applied to them.

The content of the element should be a URI giving an OAI identifier for the markup scheme itself as a resource in an OLAC archive. Thus, if the DTD, Schema, or markup documentation is not already archived in an OLAC repository, the depositer of a marked-up resource must also deposit the documentation for the markup scheme. A resource identified in Format.markup should not also be listed with the requires refinement of Relation.

There are no refinements for this element.

There are no encoding schemes for this element.

This element is used in the description of executable programs to identify the operating system environment that is needed to run them.

Software that runs under OS/2:

<format.os code="OS/2"/>

Software that runs only under Windows NT 4.0 or higher:

<format.os code="MSWindows">NT 4.0 or
            higher</format.os>

There are no refinements for this element.

There are no encoding schemes for this element.

Identifies a programming language used by software that is distributed in source code form.

Source code that is written in C++:

<format.sourcecode code="C++"/>

Source code that is written in Java using the version 1.2 library:

<format.sourcecode code="Java">Version 1.2
            library</format.sourcecode>

There are no refinements for this element.

There are no encoding schemes for this element.

Recommended best practice is to identify the resource by means of a string or number conforming to a globally-known 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). [DCMES1.1]

In the case of a resource that is not electronically encoded, but is housed in a conventional archive, Identifier may be used to give a local shelf or box number, or whatever scheme is used to locate a resource within the collection.

Identifiers that begin with "http:" will be interpreted by service providers as URLs and be presented as links in user interfaces. Note that Identifier is to be used only for a URL that retrieves the actual resource; use Description for a URL that retrieves just a description of the resource.

Do not specify the "oai:" identifier for the resource as a value of Identifier, since it is already given in the header of the metadata record.

A Uniform Resource Locator for retrieval of an electronically encoded resource:

<identifier>http://arxiv.org/abs/cs.CL/0010033</identifier>

A local identifier for retrieval within a physical collection:

<identifier>Shelf 12, Box 7</identifier>

There are no refinements for this element.

There are no encoding schemes for this element.

Language is used for a language the resource is in, as opposed to the language it describes (see Subject.language). It is related to the audience for the work in that it identifies a language that the creator of the resource assumes that its eventual user will understand. When a resource is in more than one language, use a separate Language element for each language.

For a work of literature or other monolingual document aimed at the speakers of a particular language, use Language to identify that language. For a sound recording, use Language for the language being spoken in the recording. For a grammatical description, for instance, use Language for the language the grammar is written in; use Subject.language for the language whose grammar is being described. For an annotated text, use Language for the language in which the annotations are made; use Subject.language for the language of the base text that is being annotated. For a bilingual dictionary, use Language for the language in which the definitions are written; use Subject.language for the language whose words are being defined.

A resource in English about the Sikaiana language:

<language code="en"/>
<subject.language
            code="x-sil-sky"/>

A Yemba-French dictionary, where the alternate name Dschang is preferred.

<language code="fr"/>
<subject.language
            code="x-sil-ban">Dschang</subject.language>

The American Heritage Dictionary, which is both in and about American English:

<language code="en-us"/>
<subject.language
            code="en-us"/>

A resource about a language for which the controlled vocabulary does not yet provide a code:

<subject.language>Ancient
            Sumerian</subject.language>

There are no refinements for this element.

There are no encoding schemes for this element.

Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. [DCMES1.1]

The name should be given in a form that is ready for sorting within an index. For the names of persons, this means that the name should be given in inverted order with the surname first. For the names of organizations, this means that any initial article should be omitted. When a resource has more than one publisher, use a separate Publisher element for each one.

A typical publisher:

<publisher>Oxford University Press</publisher>

There are no refinements for this element.

There are no encoding schemes for this element.

This element is used to document relationships between resources. Recommended best practice is to reference the related resource by means of an "oai:" identifier; this means that a metadata record for it should be placed in an archive. In cases where the metadata for the related resource is not in an archive, check if Source is the right element. Otherwise, enter a free text description of the related resource.

For a required markup definition (like a DTD or Schema) use Format.markup rather than Relation.

A Relation that begins with "oai:" should be presented by service providers as an active link that retrieves the metadata for that resource.

A link to a required font:

<relation
            refine="requires">oai:sil:software/ipafont</relation>

Links to the component pieces of a collected work:

<relation
            refine="hasPart">oai:somearchive:holding126</relation>
<relation
            refine="hasPart">oai:somearchive:holding127</relation>
<relation
            refine="hasPart">oai:somearchive:holding128</relation>
<relation
            refine="hasPart">oai:somearchive:holding129</relation>
<relation
            refine="hasPart">oai:somearchive:holding130</relation>

There are no refinements for this element.

There are no encoding schemes for this element.

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. [DCMES1.1]

There are no refinements for this element.

There are no encoding schemes for this element.

This element describes where the resource came from. For instance, it may be the bibliographic information about a printed book of which this is the electronic encoding or from which the information was extracted. It may be a journal, volume, and page reference if the resource represents a published article. It may be the name and dates of a conference at which a paper was originally presented.

An encoded edition of a book:

<source>An encoded edition of Lau Dictionary, by Charles E.
            Fox. Pacific Linguistcs C-24, 1974.</source>

A conference paper:

<source>A paper presented at Workshop on Web-based Language
            Documentation and Description, Philadelphia, PA, 12-15 December
            2000.</source>

Data extracted from a published source:

<source>Kwara'ae flora vocabulary extracted from Guide to
            the Forests of the British Solomon Islands, by T. C. Whitmore. Oxofrd
            University Press, 1966.

There are no refinements for this element.

There are no encoding schemes for this element.

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. [DCMES1.1]

There are no refinements for this element.

There are no encoding schemes for this element.

See Language for a complete discussion (with examples) of using the Language and Subject.language elements.

There are no refinements for this element.

There are no encoding schemes for this element.

Typically, a Title will be a name by which the resource is formally known. [DCMES1.1]

A translation of the title can be supplied in a second Title element. Use the lang attribute to identify the language of these elements.

A typical title:

<title>A Dictionary of the Nggela
            Language</title>

A vernacular title with translation:

<title lang="x-sil-llu">Na tala 'uria na idulaa
            diana</language>
<title lang="en">The road to good
            reading</language>

There are no refinements for this element.

There are no encoding schemes for this element.

Type includes terms describing general categories, functions, genres, or aggregation levels for content. To describe the physical or digital manifestation of the resource, use the Format element. [DCMES1.1]

The resource is a video recording:

<type code="image"/>

There are no refinements for this element.

There are no encoding schemes for this element.

For a resource that is information in or about a language, Type.data identifies what kind of informaton it is from a linguistic standpoint. For a resource that is a software tool, Type.data identifies what kind of information it processes. Service providers may use this information to match data files with software tools that might be applied to them.

The resource describes the grammar of a language:

<Type.data code="description/grammar"/>

The resouce includes the orthographic transcription of text:

<Type.data code="transcription/orthographic"/>

There are no refinements for this element.

There are no encoding schemes for this element.

This element is used with resources that are software applications to classify what they are used for.