METALING

Génération de XML OLAC

A name given to the resource. Typically, Title will be a name by which the resource is formally known.
An entity primarily responsible for making the content of the resource. 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.
💡 Recommended best practice is to use the Contributor element instead of Creator, except in cases where there is significant creative involvement by the person or organization and there is no suitable refinement term from the olac:role scheme to use with Contributor.
The topic of the content of the resource. Typically, Subject will be expressed as keywords, key phrases, or classification codes that describe the topic of the resource.
💡 Recommended best practice is that a metadata record should contain at least one Subject or Coverage (or one of its refinements) or Description element (or one of its refinements) in order to give the prospective user some idea of the content of the resource that goes beyond the informative potential of just a title alone. Using all of these elements is encouraged.
💡 When the subject is a human language, recommended best practice is to use a value from the olac:language scheme with the Subject element to identify an individual language precisely.
💡 When the subject matter falls within the field of linguistics, recommended best practice is to use a value from the olac:linguistic-field scheme to identify the subfield.
This document specifies the codes, or suggested vocabulary, for the 'linguistic' value of the xsi:type attribute of the OLAC Subject element. These codes describe the content of a resource as about a particular subfield of linguistic science, or about the level of linguistic structure which is the primary concern of a given subfield.
This document specifies the codes, or controlled vocabulary, for the Discourse Type extension of the Type metadata element. These codes describe the content of a resource as structured in such a way as to represent a particular type of discourse.
Codes ISO 639-3 pour les langues
An account of the content of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the content.
💡 Recommended best practice is that a metadata record should contain at least one Description (or one of its refinements) or Coverage (or one of its refinements) or Subject element in order to give the prospective user some idea of the content of the resource that goes beyond the informative potential of just a title alone. Using all of these elements is encouraged.
An entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service.
💡 Recommended best practice is to identify a Publisher by means of a name in a form that is ready for sorting within an index.

An entity responsible for making contributions to the content of the resource. Examples of a Contributor include a person, an organization, or a service.
💡 Recommended best practice is to identify a Contributor by means of a name in a form that is ready for sorting within an alphabetical index.
💡 Recommended best practice is to use a value from the olac:role scheme to indicate the role of the Contributor.
Role is an attribute of both the Creator and Contributor elements. (Please note that Dublin Core now discourages the use of the Creator element, recommending that all Role information be associated with Contributor elements.) This document specifies the controlled vocabulary of the Role attribute used by OLAC. This attribute specifies the functional role of the entity named in the creation of a given resource.
A point or period of time associated with an event in the lifecycle of the resource. Date may be used to express temporal information at any level of granularity.
💡 Recommended best practice is that a record have at least one instance of Date (or one of its refinements).
💡 Recommended best practice is that every instance of Date (or one of its refinements) use a value matching the dcterms:W3CDTF scheme, or enclose the element value in square brackets if the value does not conform to the encoding scheme (e.g., if it is supplied by the cataloger, is approximate, or is in some doubt).
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 that every record should contain at least one Type element that uses a value from the dcterms:DCMIType scheme to identify the nature or genre of the content of the resource.
💡 Recommended best practice is that every record for which it is applicable should contain at least one Type element that uses a value from the olac:linguistic-type scheme to identify its linguistic data type.
This document specifies the codes, or controlled vocabulary, for the Discourse Type extension of the Type metadata element. These codes describe the content of a resource as structured in such a way as to represent a particular type of discourse.
This document specifies the codes, or controlled vocabulary, for the Linguistic Data Type extension of the DCMI Type element. These codes describe the content of a resource from the standpoint of recognized structural types of linguistic information.
The physical or digital manifestation of the resource. Typically, Format may include the media-type or dimensions of the resource.
💡 In the case of a digital resource, recommended best practice is to express the Format using a MIME type value from the dcterms:IMT scheme.
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.
💡 When the value of Identifier is a Uniform Resource Locator (URL), recommended best practice is to specify the dcterms:URI scheme.
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 as for the Relation element above.
A language of the intellectual content of the resource.
💡 Recommended best practice is that every record contain at least one Language element.
💡 For a resource that does not include language content, include a Language element containing the code zxx for 'No linguistic content.'
💡 Recommended best practice is to use a value from the olac:language scheme with the Language element to identify an individual language precisely.
Codes ISO 639-3 pour les langues
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.
💡 When the related resource is also held in a participating archive, recommended best practice is to identify the related resource by means of its OAI identifier. A Relation that begins with 'oai:' will typically be presented by service providers as an active link that retrieves the metadata for that resource.
💡 If the related resource is not cataloged in the system of a participating archive, recommended best practice is to identify the related resource through a standard unique identifier.
💡 If the related resource is available online, specify the dcterms:URI scheme and give a stable Uniform Resource Locator (URL).
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 that a metadata record should contain at least one Coverage (or one of its refinements) or Description (or one of its refinements) or Subject element in order to give the prospective user some idea of the content of the resource that goes beyond the informative potential of just a title alone. Using all of these elements is encouraged.
💡 In the case of spatial coverage, recommended best practice is to use a value from an encoding scheme to give precise geocoding of the resource.
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 can be made about the status of these and other rights with respect to the resource.