SWAD-Europe Thesaurus Activity: Deliverable 8.1 RDF Schema for ISO Standard Thesauri

N.B. This document series is now deprecated. Please see http://www.w3.org/2004/02/skos/core/guide/ for the latest version of the SKOS Core Guide.

Abstract:: This document describes an RDF schema for encoding both monolingual and multilingual thesauri that complies with ISO 2788:1986 and ISO 5964:1985 standards. The schema is concept-based, and features an extensible framework of properties, allowing the schema to be extended and/or customised.
Project name:: Semantic Web Advanced Development for Europe (SWAD-Europe)
Project Number:: IST-2001-34732
Workpackage name:: 8. Thesaurus Research Prototype
Workpackage description:: http://www.w3.org/2001/sw/Europe/plan/workpackages/live/esw-wp-8.html
Deliverable title:: 8.1: thesaurus_schema_draft
This version:: http://www.w3.org/2001/sw/Europe/reports/thes/8.1/draft02.html
Latest version:: http://www.w3.org/2001/sw/Europe/reports/thes/8.1/
Previous version:: http://www.w3.org/2001/sw/Europe/reports/thes/8.1/draft01.html
Status:: Draft
Authors:: Alistair Miles, CCLRC, UK
Brian Matthews, CCLRC, UK

Status of this document

This section describes the status of this document at the time of its publication. This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. The latest status of this document series is maintained at the W3C.

This document is a public DRAFT for discussion. This document is an output of the research work of the Semantic Web Advanced Development for Europe Project, which is associated with the W3C Semantic Web Activity. This document is made available by W3C for discussion only. Publication of this document by W3C does not imply endorsement by W3C, including the Team and Membership.

Comments on this document are welcome and should be sent to the authors or to the public-esw-thes@w3.org list. An archive of this list is available at http://lists.w3.org/Archives/Public/public-esw-thes/.

1. Introduction
2. Schema description

2.1. Schema classes
2.2. Schema properties

3. Discussion of design features

3.1. RDF schema
3.2. Concept-based
3.3. Relationships as arcs
3.4. Extensible/customisable
3.5. Multilingual
3.6. Inter-thesaurus mapping
3.7. Scope notes

References
Appendices

A1. The RDF Schema
A2. Example data
A3. Language identifiers for use with multilingual data

1. Introduction [back to contents]

This document describes an RDF schema for representing both monolingual and multilingual thesauri. The specifications agree with ISO 2788:1986 (monolingual) and ISO 5964:1985 (multilingual) standards. This work builds on a review of previous RDF thesaurus work, presented in SWAD deliverable 8.2.

The schema implements the following features:

Concept-based
Extensible/customisable
Monolingual or multilingual
Concepts as language-embedded or language-independent
Non-exact multilingual equivalence relationships
Inter-thesaurus mapping
Scope notes

2. Schema description [back to contents]

The base XML namespace for classes and properties in the schema is

http://www.w3c.rl.ac.uk/2003/07/31-tif#

The Language class and identifiers for all languages defined by ISO639-1 are supplied in a separate schema (see Appendix 3). These resources are referenced with the base namespace

http://www.w3c.rl.ac.uk/2003/07/31-lang#

This schema adopts the convention of using slightly shorter names for the rdf:ID of each property or class, for a file format that is still human-readable but is also compact and convenient to author, and adding an rdfs:label to each property/class which can be used as the full descriptive name.

The classes and properties of the schema are described below.

2.1. Schema classes [back to contents]

Thesaurus (rdf:ID="Thesaurus")
An instance of this class may be used to define meta-properties of the thesaurus itself, such as title, description, authors and so on.: Thesaurus-Object (rdf:ID="ThesaurusObject")
The super-class of all classes of objects that are part of a thesaurus.: Concept (rdf:ID="Concept")
An instance of this class defines a unique concept in a thesaurus: Term (rdf:ID="Term")
Used to define a textual representation of a concept, such as a word or phrase.: Scope-Note (rdf:ID="ScopeNote")
Defines a comment on a concept, prescribing the bounds of appropriate usage of the concept. Sub-classes of this class are used to describe specific types of comment. A General-Note refers to [???]. A History-Note refers to [???]. A Hierarchy-Note refers to [???]. A Translation-Note refers to [???]. An Editor-Note refers to [???].

2.2. Schema properties [back to contents]

Table 1. Summary of TIF properties
Domain	Property	Range
Concept	is-defined-by	Thesaurus
	has-classification-code	Literal
	is-indicated-by	Term
	has-preferred-term
	has-non-preferred-term
	concept-relation	Concept
	has-broader-concept
	has-narrower-concept
	has-related-concept
	concept-equivalence	Concept
	has-exact-equivalent
	has-inexact-equivalent
	has-partial-equivalent
	has-one-to-many-equivalent
Term	has-value	Literal
Thesaurus-Object	in-language-of	Language

has-classification-code (rdf:ID="code")
Defines a unique identifier for a Concept.: is-defined-by (rdf:ID="isDefinedBy")
Relates a Concept to the Thesaurus it is a part of. [Use rdfs:isDefinedBy ???]: has-value (rdf:ID="value")
Defines the literal value of a Term.: in-language-of (rdf:ID="language")
Defines the relationship between a Thesaurus-Object such as a Concept or Scope-Note and its Language.: has-scope-note (rdf:ID="note")
Defines the relationship from a Concept to a Scope-Note.: is-indicated-by (rdf:ID="indicatedBy")
The super-property of all properties defining relationships from Concepts to Terms.

is-indicated-by property hierarchy

has-preferred-Term (rdf:ID="preferred")
A subproperty of is-indicated-by, defining that Term which is the preferred term (also known as reference or indexing term) for the Concept.: has-non-preferred-Term (rdf:ID="nonPreferred")
A subproperty of the is-indicated-by property, defining a Term which is a non-preferred term for the Concept.: concept-relation (rdf:ID="conceptRelation")
A generalisation of all the relationships between Concepts in the same language. The has-broader|narrower|related-concept relationships are its subproperties.: has-broader-concept (rdf:ID="broader")
Defines the relationship between a Concept and another that is in some way broader in scope.: has-narrower-concept (rdf:ID="narrower")
Defines the relationship between a Concept and another that is in some way narrower in scope.: has-related-concept (rdf:ID="related")
Defines the relationship between a Concept and another that is in some way usefully related.: concept-equivalence (rdf:ID="conceptEquivalence")
A generalisation of all the relationships between Concepts of different languages. The has- exact, inexact, partial, one-to-many -equivalent relationships are its subproperties. The exact nature of the relationship for non-exact equivalences should be explained in translator's scope notes.: has-exact-equivalent (rdf:ID="exact")
Defines the relationship between two concepts in different languages which are exactly equivalent.: has-inexact-equivalent (rdf:ID="inexact")
Defines the relationship between two concepts in different languages which are not exact, but are in some way overlapping in their meaning.: has-partial-equivalent (rdf:ID="partial")
Defines the relationship between two concepts in different languages which are not exact, but one is broader in scope and encompasses the other.: has-one-to-many-equivalent (rdf:ID="oneToMany")
Defines the relationship between a Concept which may only be adequately translated by using a combination of more than one Concept from the target language.

3. Discussion of design features [back to contents]

3.1. RDF Schema [back to contents]

At this stage, RDF schema has been chosen as the underlying system for defining the RDF thesaurus vocabulary. The document Deliverable 8.6: OWL Ontologies for Thesaurus Data will explore the use of OWL for the same purpose.

3.2. Concept-based [back to contents]

The schema described here defines a concept-based model for thesaurus data (see ref 8.2). The concept-based design has been preferred to the term-based design for the following reasons. First, it allows a clear distinction to be made between information about meaning and conceptual relationships, and information about terms, word variants, and other purely lexical relationships. Such a distinction encourages clarity and consistency in thesaurus design, maintenaince and interoperation (ref ???). The concept-based model also reveals how a thesaurus may be related to, and hence engineered to interoperate with, other knowledge modelling structures such as ontologies, dictionaries, concept maps, topic maps etc. Finally, the concept-oriented model is easier to maintain and update without threatening integrity. This is due to the separation of concepts and the generalisation hierarchy from the terms of the thesaurus, making it possible to change terms, move or shuffle them about, and change which is chosen as the preferred alternative, without disturbing the generalisation hierarchy itself.

3.3. Relationships as arcs [back to contents]

This schema models concept-to-concept and concept-to-term relationships as arcs in the RDF graph. This choice was made to produce a more compact and intuitive representation format.

3.4. Extensible/customisable [back to contents]

This schema has been designed to allow it to be extended and/or customised to accomodate variations in thesauru implementation. The mechanism choisen to support this feature was to define top level properties 'concept-relation' 'concept-equivalence' and 'indicated-by'. Any extension or customisation of the schema must implement its properties as subproperties of the above.

3.5. Multilingual [back to contents]

The 'in-language-of' property may be used to define the language here of any thesaurus-object. Thus this schema does not restrict the user to modelling concepts as language embedded or language independent (see 8.2#scetion). We recommend that the user attaches in-language-of properties either to only concepts or to only terms. The concept-equivalence subproperties 'exact', 'inexact', 'partial' and 'one-to-many' allow the equivalence of concepts in different languages to be described. The document Deliverable 8.3: RDF Schema for Multilingual Thesauri will explore the issue of representing variations in multilingual thesauri further.

3.6. Inter-thesaurus mapping [back to contents]

The 'concept-equivalence' subproperties defined in this schema also allow concepts from different thesauri to be mapped to each other. Thus mapping and non-exact mapping is supported by this schema. However, there have been criticism of the ISO 5964:1985 property set, especially of the 'partial-equivalent' property. This property is used to specify that one concept may be mapped to another which is either broader or narrower in scope. Thus the partial-equivalent property does not specify which is the broader and which is the narrower. The issue of inter-thesaurus mapping will be explored further in the document Deliverable 8.4: RDF Schema Extension for Inter-thesaurus Mapping.

3.7. Scope notes [back to contents]

This schema supports the use of scope notes of several types, as is consistent with recommendations made by the ISO standards, and practise in development of thesauri.

References [back to contents]

ISO 2788

ISO 5964

Deliverable 8.2

ILRT schema

Limber schema

Appendix 1 - RDF Schema [back to contents]

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rdfs [
	<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
	<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
	<!ENTITY xsd "http://www.w3.org/2000/10/XMLSchema#" >
	<!ENTITY tif "http://www.w3c.rl.ac.uk/2003/07/31-tif#" >
	<!ENTITY dc "http://purl.org/dc/elements/1.1/" >
	<!ENTITY dct "http://purl.org/dc/terms/" > 
	<!ENTITY lang "http://www.w3c.rl.ac.uk/2003/07/31-lang#" >
	]>
	
<!-- This is the Thesaurus Interchange Format (TIF) for monolingual or multilingual thesauri.  
	Authors:					A J Miles, B M Matthews
	Date:						31/07/2003
	Version:					1.3
	Assume base namespace:	http://www.w3c.rl.ac.uk/2003/07/31-tif#
	-->
	
<rdf:RDF 
	xml:lang="en" 
	xmlns:rdf="&rdf;" 
	xmlns:rdfs="&rdfs;" 
	xmlns:dc="&dc;" 
	xmlns:dct="&dct;" 
	xmlns:tif="&tif;" 
	xmlns:lang="⟨" 
	xmlns="&tif;" 
	xml:base="&tif;"
	>
	
	<!-- Description of this schema. -->
	
	<rdf:Description rdf:about="">
		<rdfs:comment>This is the Thesaurus Interchange Format (TIF).</rdfs:comment>
		<rdfs:label xml:lang="en">Thesaurus Interchange Format (TIF)</rdfs:label>
		<dc:title xml:lang="en">Thesaurus Interchange Format (TIF)</dc:title>
		<dc:publisher xml:lang="en">Council for the Central Laboratory of the Research Councils (CCLRC)</dc:publisher>
		<dc:description xml:lang="en">This is the Thesaurus Interchange Format (TIF) for monolingual or multilingual thesauri.</dc:description>
		<dc:creator xml:lang="en">A J Miles</dc:creator>
		<dc:creator xml:lang="en">B M Matthews</dc:creator>
		<dc:subject xml:lang="en">Thesaurus</dc:subject>
		<dc:subject xml:lang="en">Semantic Web</dc:subject>
		<dct:modified>2003-07-31</dct:modified>
	</rdf:Description>
	
	<!-- Definition of the classes. -->
	
	<rdfs:Class rdf:ID="Thesaurus">
		<rdfs:comment>Properties may be added to an instance of the Thesaurus class to describe for example the name of the thesaurus, the subject, a textual description, the creators, the date of last modification etc.</rdfs:comment>
		<rdfs:label>Thesaurus</rdfs:label>
		<rdfs:subClassOf rdf:resource="&rdf;Resource"/>
	</rdfs:Class>
	
	<rdfs:Class rdf:ID="ThesaurusObject">
		<rdfs:comment>The superclass of all classes of object that are part of a thesaurus</rdfs:comment>
		<rdfs:label>Thesaurus-object</rdfs:label>
		<rdfs:subClassOf rdf:resource="&rdf;Resource"/>
	</rdfs:Class>
	
	<rdfs:Class rdf:ID="Concept">
		<rdfs:comment>A unique concept defined within a vocabulary scheme, such as a thesaurus or classification scheme. Instances can use the rdfs:isDefinedBy property with a vocabulary namespace as its value, to indicate the vocabulary to which the concept belongs.</rdfs:comment>
		<rdfs:label>Concept</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ThesaurusObject"/>
	</rdfs:Class>
	
	<rdfs:Class rdf:ID="Term">
		<rdfs:comment>Instances of this class represent the written forms of concepts, capturing a word or phrase that expresses the concept.</rdfs:comment>
		<rdfs:label>Term</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ThesaurusObject"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="ScopeNote">
		<rdfs:comment>Provides a comment on the concept, for disambiguation, explanation etc.  The string is given by the rdf:value of ScopeNote.</rdfs:comment>
		<rdfs:label>Scope-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ThesaurusObject"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="GeneralNote">
		<rdfs:comment><!-- TODO --></rdfs:comment>
		<rdfs:label>General-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ScopeNote"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="HierarchyNote">
		<rdfs:comment><!-- TODO --></rdfs:comment>
		<rdfs:label>Hierarchy-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ScopeNote"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="TranslationNote">
		<rdfs:comment><!-- TODO --></rdfs:comment>
		<rdfs:label>Translation-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ScopeNote"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="EditorNote">
		<rdfs:comment><!-- TODO --></rdfs:comment>
		<rdfs:label>Editor-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ScopeNote"/>
	</rdfs:Class>

	<rdfs:Class rdf:ID="HistoryNote">
		<rdfs:comment><!-- TODO --></rdfs:comment>
		<rdfs:label>History-note</rdfs:label>
		<rdfs:subClassOf rdf:resource="#ScopeNote"/>
	</rdfs:Class>

	<!-- Definition of the properties. -->
	
	<rdf:Property rdf:ID="code">
		<rdfs:comment>The unique identifier of a concept.</rdfs:comment>
		<rdfs:label>has-classification-code</rdfs:label>
		<rdfs:domain rdf:resource="#Concept"/>
		<rdfs:range rdf:resource="&rdfs;Literal"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="value">
		<rdfs:comment>The string value of a term</rdfs:comment>
		<rdfs:label>has-value</rdfs:label>
		<rdfs:domain rdf:resource="#Term"/>
		<rdfs:range rdf:resource="&rdfs;Literal"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="language">
		<rdfs:comment>The language of a concept or scope note.</rdfs:comment>
		<rdfs:label>in-language-of</rdfs:label>
		<rdfs:domain rdf:resource="#ThesaurusObject"/>
		<rdfs:range rdf:resource="⟨Language"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="note">
		<rdfs:comment>A scope note of a concept.</rdfs:comment>
		<rdfs:label>has-scope-note</rdfs:label>
		<rdfs:domain rdf:resource="#Concept"/>
		<rdfs:range rdf:resource="#ScopeNote"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="indicatedBy">
		<rdfs:comment>A defining term for a concept.</rdfs:comment>
		<rdfs:label>is-indicated-by</rdfs:label>
		<rdfs:domain rdf:resource="#Concept"/>
		<rdfs:range rdf:resource="#Term"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="preferred">
		<rdfs:comment>The preferred term for a concept.</rdfs:comment>
		<rdfs:label>has-preferred-term</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#indicatedBy"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="nonPreferred">
		<rdfs:comment>A non-preferred term for a concept.</rdfs:comment>
		<rdfs:label>has-non-preferred-term</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#indicatedBy"/>
	</rdf:Property>

	<rdf:Property rdf:ID="conceptRelation">
		<rdfs:comment>A generalisation of all possible relationships between two concepts from the same language.</rdfs:comment>
		<rdfs:label>concept-relation</rdfs:label>
		<rdfs:domain rdf:resource="#Concept"/>
		<rdfs:range rdf:resource="#Concept"/>
	</rdf:Property>

	<rdf:Property rdf:ID="broader">
		<rdfs:comment>The subject has a broader concept specified by the object.</rdfs:comment>
		<rdfs:label>has-broader-concept</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptRelation"/>
	</rdf:Property>

	<rdf:Property rdf:ID="narrower">
		<rdfs:comment>The subject has a narrower concept specified by the object.</rdfs:comment>
		<rdfs:label>has-narrower-concept</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptRelation"/>
	</rdf:Property>

	<rdf:Property rdf:ID="related">
		<rdfs:comment>The related concept relation.</rdfs:comment>
		<rdfs:label>has-related-concept</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptRelation"/>
	</rdf:Property>

	<rdf:Property rdf:ID="conceptEquivalence">
		<rdfs:comment>A generalisation of all possible relationships between concepts from different languages.</rdfs:comment>
		<rdfs:label>concept-equivalence</rdfs:label>
		<rdfs:domain rdf:resource="#Concept"/>
		<rdfs:range rdf:resource="#Concept"/>
	</rdf:Property>

	<rdf:Property rdf:ID="exact">
		<rdfs:comment>The object of this property is a concept which is identical in meaning and scope to the subject of this property.</rdfs:comment>
		<rdfs:label>has-exact-equivalent</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/>
	</rdf:Property>

	<rdf:Property rdf:ID="inexact">
		<rdfs:comment>The object of this property expresses the same general concept as the subject, although the meanings of these terms are not precisely identical.</rdfs:comment>
		<rdfs:label>has-inexact-equivalent</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/>
	</rdf:Property>

	<rdf:Property rdf:ID="partial">
		<rdfs:comment>The subject (a concept from the source language) cannot be matched to an exactly equivalent concept in the target language, but a near translation is achieved by the object of this property, which is a concept with a slightly narrower or broader meaning.</rdfs:comment>
		<rdfs:label>has-partial-equivalent</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/>
	</rdf:Property>

	<rdf:Property rdf:ID="oneToMany">
		<rdfs:comment>The subject (a concept from the source language) can only be expressed in the target language as a combination of two or more concepts from the target language.</rdfs:comment>
		<rdfs:label>has-one-to-many-equivalent</rdfs:label>
		<rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/>
	</rdf:Property>

</rdf:RDF>

Appendix 2 - Example data [back to contents]

Appendix 3 - RDF language Identifiers [back to contents]

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rdfs [
	<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
	<!ENTITY xsd "http://www.w3.org/2000/10/XMLSchema#">
	<!ENTITY dc "http://purl.org/dc/elements/1.1/">
	<!ENTITY dct "http://purl.org/dc/terms/">
	<!ENTITY lang "http://www.w3c.rl.ac.uk/2003/07/31-lang#">
]>

<!-- This file describes the language identifiers for use with the Thesaurus Interchange Format (TIF)
	Authors:					A J Miles, B M Matthews
	Date:						31/07/2003
	Version:					1.3
	Assume base namespace:	http://www.w3c.rl.ac.uk/2003/07/31-lang#
	-->
	
<rdf:RDF xml:lang="en" xmlns:rdf="&rdf;" xmlns:rdfs="&rdfs;" xmlns:dc="&dc;" xmlns:dct="&dct;" xmlns:lang="⟨" xmlns="⟨" xml:base="⟨">

	<!-- Description of this schema. -->
	
	<rdf:Description rdf:about="">
		<rdfs:comment>This file describes the language identifiers for use with the Thesaurus Interchange Format (TIF)</rdfs:comment>
		<rdfs:label xml:lang="en">Language Identifiers</rdfs:label>
		<dc:title xml:lang="en">Language Identifiers</dc:title>
		<dc:publisher xml:lang="en">Council for the Central Laboratory of the Research Councils (CCLRC)</dc:publisher>
		<dc:description xml:lang="en">This file describes the language identifiers for use with the Thesaurus Interchange Format (TIF).</dc:description>
		<dc:creator xml:lang="en">A J Miles</dc:creator>
		<dc:creator xml:lang="en">B M Matthews</dc:creator>
		<dc:subject xml:lang="en">Multilingual Thesaurus</dc:subject>
		<dc:subject xml:lang="en">Semantic Web</dc:subject>
		<dct:modified>2003-07-31</dct:modified>
	</rdf:Description>
	
	<!-- Definition of the classes. -->
	
	<rdfs:Class rdf:ID="Language">
		<rdfs:comment>Defines the class of resources that refer to natural languages.</rdfs:comment>
		<rdfs:label>Language</rdfs:label>
		<rdfs:subClassOf rdf:resource="&rdf;Resource"/>
	</rdfs:Class>
	
	<!-- Definition of the properties. -->
	
	<rdf:Property rdf:ID="ISO639-1">
		<rdfs:comment>The ISO639 two letter code.</rdfs:comment>
		<rdfs:label>two-char-code</rdfs:label>
		<rdfs:domain rdf:resource="#Language"/>
		<rdfs:range rdf:resource="&rdfs;Literal"/>
	</rdf:Property>
	
	<rdf:Property rdf:ID="ISO639-2">
		<rdfs:comment>The ISO639 three letter code.</rdfs:comment>
		<rdfs:label>three-char-code</rdfs:label>
		<rdfs:domain rdf:resource="#Language"/>
		<rdfs:range rdf:resource="&rdfs;Literal"/>
	</rdf:Property>
	
	<!-- Definition of the instances. -->
	
	<Language rdf:ID="AB">
		<rdfs:label>ABKHAZIAN</rdfs:label>
		<ISO639-1>AB</ISO639-1>
	</Language>
	<Language rdf:ID="OM">
		<rdfs:label>AFAN(OROMO)</rdfs:label>
		<ISO639-1>OM</ISO639-1>
	</Language>
	<Language rdf:ID="AA">
		<rdfs:label>AFAR</rdfs:label>
		<ISO639-1>AA</ISO639-1>
	</Language>
	<Language rdf:ID="AF">
		<rdfs:label>AFRIKAANS</rdfs:label>
		<ISO639-1>AF</ISO639-1>
	</Language>
	<Language rdf:ID="SQ">
		<rdfs:label>ALBANIAN</rdfs:label>
		<ISO639-1>SQ</ISO639-1>
	</Language>
	<Language rdf:ID="AM">
		<rdfs:label>AMHARIC</rdfs:label>
		<ISO639-1>AM</ISO639-1>
	</Language>
	<Language rdf:ID="AR">
		<rdfs:label>ARABIC</rdfs:label>
		<ISO639-1>AR</ISO639-1>
	</Language>
	<Language rdf:ID="HY">
		<rdfs:label>ARMENIAN</rdfs:label>
		<ISO639-1>HY</ISO639-1>
	</Language>
	<Language rdf:ID="AS">
		<rdfs:label>ASSAMESE</rdfs:label>
		<ISO639-1>AS</ISO639-1>
	</Language>
	<Language rdf:ID="AY">
		<rdfs:label>AYMARA</rdfs:label>
		<ISO639-1>AY</ISO639-1>
	</Language>
	<Language rdf:ID="AZ">
		<rdfs:label>AZERBAIJANI</rdfs:label>
		<ISO639-1>AZ</ISO639-1>
	</Language>
	<Language rdf:ID="BA">
		<rdfs:label>BASHKIR</rdfs:label>
		<ISO639-1>BA</ISO639-1>
	</Language>
	<Language rdf:ID="EU">
		<rdfs:label>BASQUE</rdfs:label>
		<ISO639-1>EU</ISO639-1>
	</Language>
	<Language rdf:ID="BN">
		<rdfs:label>BENGALI;BANGLA</rdfs:label>
		<ISO639-1>BN</ISO639-1>
	</Language>
	<Language rdf:ID="DZ">
		<rdfs:label>BHUTANI</rdfs:label>
		<ISO639-1>DZ</ISO639-1>
	</Language>
	<Language rdf:ID="BH">
		<rdfs:label>BIHARI</rdfs:label>
		<ISO639-1>BH</ISO639-1>
	</Language>
	<Language rdf:ID="BI">
		<rdfs:label>BISLAMA</rdfs:label>
		<ISO639-1>BI</ISO639-1>
	</Language>
	<Language rdf:ID="BR">
		<rdfs:label>BRETON</rdfs:label>
		<ISO639-1>BR</ISO639-1>
	</Language>
	<Language rdf:ID="BG">
		<rdfs:label>BULGARIAN</rdfs:label>
		<ISO639-1>BG</ISO639-1>
	</Language>
	<Language rdf:ID="MY">
		<rdfs:label>BURMESE</rdfs:label>
		<ISO639-1>MY</ISO639-1>
	</Language>
	<Language rdf:ID="BE">
		<rdfs:label>BYELORUSSIAN</rdfs:label>
		<ISO639-1>BE</ISO639-1>
	</Language>
	<Language rdf:ID="KM">
		<rdfs:label>CAMBODIAN</rdfs:label>
		<ISO639-1>KM</ISO639-1>
	</Language>
	<Language rdf:ID="CA">
		<rdfs:label>CATALAN</rdfs:label>
		<ISO639-1>CA</ISO639-1>
	</Language>
	<Language rdf:ID="ZH">
		<rdfs:label>CHINESE</rdfs:label>
		<ISO639-1>ZH</ISO639-1>
	</Language>
	<Language rdf:ID="CO">
		<rdfs:label>CORSICAN</rdfs:label>
		<ISO639-1>CO</ISO639-1>
	</Language>
	<Language rdf:ID="HR">
		<rdfs:label>CROATIAN</rdfs:label>
		<ISO639-1>HR</ISO639-1>
	</Language>
	<Language rdf:ID="CS">
		<rdfs:label>CZECH</rdfs:label>
		<ISO639-1>CS</ISO639-1>
	</Language>
	<Language rdf:ID="DA">
		<rdfs:label>DANISH</rdfs:label>
		<ISO639-1>DA</ISO639-1>
	</Language>
	<Language rdf:ID="NL">
		<rdfs:label>DUTCH</rdfs:label>
		<ISO639-1>NL</ISO639-1>
	</Language>
	<Language rdf:ID="EN">
		<rdfs:label>ENGLISH</rdfs:label>
		<ISO639-1>EN</ISO639-1>
	</Language>
	<Language rdf:ID="EO">
		<rdfs:label>ESPERANTO</rdfs:label>
		<ISO639-1>EO</ISO639-1>
	</Language>
	<Language rdf:ID="ET">
		<rdfs:label>ESTONIAN</rdfs:label>
		<ISO639-1>ET</ISO639-1>
	</Language>
	<Language rdf:ID="FO">
		<rdfs:label>FAROESE</rdfs:label>
		<ISO639-1>FO</ISO639-1>
	</Language>
	<Language rdf:ID="FJ">
		<rdfs:label>FIJI</rdfs:label>
		<ISO639-1>FJ</ISO639-1>
	</Language>
	<Language rdf:ID="FI">
		<rdfs:label>FINNISH</rdfs:label>
		<ISO639-1>FI</ISO639-1>
	</Language>
	<Language rdf:ID="FR">
		<rdfs:label>FRENCH</rdfs:label>
		<ISO639-1>FR</ISO639-1>
	</Language>
	<Language rdf:ID="FY">
		<rdfs:label>FRISIAN</rdfs:label>
		<ISO639-1>FY</ISO639-1>
	</Language>
	<Language rdf:ID="GL">
		<rdfs:label>GALICIAN</rdfs:label>
		<ISO639-1>GL</ISO639-1>
	</Language>
	<Language rdf:ID="KA">
		<rdfs:label>GEORGIAN</rdfs:label>
		<ISO639-1>KA</ISO639-1>
	</Language>
	<Language rdf:ID="DE">
		<rdfs:label>GERMAN</rdfs:label>
		<ISO639-1>DE</ISO639-1>
	</Language>
	<Language rdf:ID="EL">
		<rdfs:label>GREEK</rdfs:label>
		<ISO639-1>EL</ISO639-1>
	</Language>
	<Language rdf:ID="KL">
		<rdfs:label>GREENLANDIC</rdfs:label>
		<ISO639-1>KL</ISO639-1>
	</Language>
	<Language rdf:ID="GN">
		<rdfs:label>GUARANI</rdfs:label>
		<ISO639-1>GN</ISO639-1>
	</Language>
	<Language rdf:ID="GU">
		<rdfs:label>GUJARATI</rdfs:label>
		<ISO639-1>GU</ISO639-1>
	</Language>
	<Language rdf:ID="HA">
		<rdfs:label>HAUSA</rdfs:label>
		<ISO639-1>HA</ISO639-1>
	</Language>
	<Language rdf:ID="HE">
		<rdfs:label>HEBREW</rdfs:label>
		<ISO639-1>HE</ISO639-1>
	</Language>
	<Language rdf:ID="HI">
		<rdfs:label>HINDI</rdfs:label>
		<ISO639-1>HI</ISO639-1>
	</Language>
	<Language rdf:ID="HU">
		<rdfs:label>HUNGARIAN</rdfs:label>
		<ISO639-1>HU</ISO639-1>
	</Language>
	<Language rdf:ID="IS">
		<rdfs:label>ICELANDIC</rdfs:label>
		<ISO639-1>IS</ISO639-1>
	</Language>
	<Language rdf:ID="ID">
		<rdfs:label>INDONESIAN</rdfs:label>
		<ISO639-1>ID</ISO639-1>
	</Language>
	<Language rdf:ID="IA">
		<rdfs:label>INTERLINGUA</rdfs:label>
		<ISO639-1>IA</ISO639-1>
	</Language>
	<Language rdf:ID="IE">
		<rdfs:label>INTERLINGUE</rdfs:label>
		<ISO639-1>IE</ISO639-1>
	</Language>
	<Language rdf:ID="IU">
		<rdfs:label>INUKTITUT</rdfs:label>
		<ISO639-1>IU</ISO639-1>
	</Language>
	<Language rdf:ID="IK">
		<rdfs:label>INUPIAK</rdfs:label>
		<ISO639-1>IK</ISO639-1>
	</Language>
	<Language rdf:ID="GA">
		<rdfs:label>IRISH</rdfs:label>
		<ISO639-1>GA</ISO639-1>
	</Language>
	<Language rdf:ID="IT">
		<rdfs:label>ITALIAN</rdfs:label>
		<ISO639-1>IT</ISO639-1>
	</Language>
	<Language rdf:ID="JA">
		<rdfs:label>JAPANESE</rdfs:label>
		<ISO639-1>JA</ISO639-1>
	</Language>
	<Language rdf:ID="JV">
		<rdfs:label>JAVANESE</rdfs:label>
		<ISO639-1>JV</ISO639-1>
	</Language>
	<Language rdf:ID="KN">
		<rdfs:label>KANNADA</rdfs:label>
		<ISO639-1>KN</ISO639-1>
	</Language>
	<Language rdf:ID="KS">
		<rdfs:label>KASHMIRI</rdfs:label>
		<ISO639-1>KS</ISO639-1>
	</Language>
	<Language rdf:ID="KK">
		<rdfs:label>KAZAKH</rdfs:label>
		<ISO639-1>KK</ISO639-1>
	</Language>
	<Language rdf:ID="RW">
		<rdfs:label>KINYARWANDA</rdfs:label>
		<ISO639-1>RW</ISO639-1>
	</Language>
	<Language rdf:ID="KY">
		<rdfs:label>KIRGHIZ</rdfs:label>
		<ISO639-1>KY</ISO639-1>
	</Language>
	<Language rdf:ID="RN">
		<rdfs:label>KURUNDI</rdfs:label>
		<ISO639-1>RN</ISO639-1>
	</Language>
	<Language rdf:ID="KO">
		<rdfs:label>KOREAN</rdfs:label>
		<ISO639-1>KO</ISO639-1>
	</Language>
	<Language rdf:ID="KU">
		<rdfs:label>KURDISH</rdfs:label>
		<ISO639-1>KU</ISO639-1>
	</Language>
	<Language rdf:ID="LO">
		<rdfs:label>LAOTHIAN</rdfs:label>
		<ISO639-1>LO</ISO639-1>
	</Language>
	<Language rdf:ID="LA">
		<rdfs:label>LATIN</rdfs:label>
		<ISO639-1>LA</ISO639-1>
	</Language>
	<Language rdf:ID="LV">
		<rdfs:label>LATVIAN;LETTISH</rdfs:label>
		<ISO639-1>LV</ISO639-1>
	</Language>
	<Language rdf:ID="LN">
		<rdfs:label>LINGALA</rdfs:label>
		<ISO639-1>LN</ISO639-1>
	</Language>
	<Language rdf:ID="LT">
		<rdfs:label>LITHUANIAN</rdfs:label>
		<ISO639-1>LT</ISO639-1>
	</Language>
	<Language rdf:ID="MK">
		<rdfs:label>MACEDONIAN</rdfs:label>
		<ISO639-1>MK</ISO639-1>
	</Language>
	<Language rdf:ID="MG">
		<rdfs:label>MALAGASY</rdfs:label>
		<ISO639-1>MG</ISO639-1>
	</Language>
	<Language rdf:ID="MS">
		<rdfs:label>MALAY</rdfs:label>
		<ISO639-1>MS</ISO639-1>
	</Language>
	<Language rdf:ID="ML">
		<rdfs:label>MALAYALAM</rdfs:label>
		<ISO639-1>ML</ISO639-1>
	</Language>
	<Language rdf:ID="MT">
		<rdfs:label>MALTESE</rdfs:label>
		<ISO639-1>MT</ISO639-1>
	</Language>
	<Language rdf:ID="MI">
		<rdfs:label>MAORI</rdfs:label>
		<ISO639-1>MI</ISO639-1>
	</Language>
	<Language rdf:ID="MR">
		<rdfs:label>MARATHI</rdfs:label>
		<ISO639-1>MR</ISO639-1>
	</Language>
	<Language rdf:ID="MO">
		<rdfs:label>MOLDAVIAN</rdfs:label>
		<ISO639-1>MO</ISO639-1>
	</Language>
	<Language rdf:ID="MN">
		<rdfs:label>MONGOLIAN</rdfs:label>
		<ISO639-1>MN</ISO639-1>
	</Language>
	<Language rdf:ID="NA">
		<rdfs:label>NAURU</rdfs:label>
		<ISO639-1>NA</ISO639-1>
	</Language>
	<Language rdf:ID="NE">
		<rdfs:label>NEPALI</rdfs:label>
		<ISO639-1>NE</ISO639-1>
	</Language>
	<Language rdf:ID="NO">
		<rdfs:label>NORWEGIAN</rdfs:label>
		<ISO639-1>NO</ISO639-1>
	</Language>
	<Language rdf:ID="OC">
		<rdfs:label>OCCITAN</rdfs:label>
		<ISO639-1>OC</ISO639-1>
	</Language>
	<Language rdf:ID="OR">
		<rdfs:label>ORIYA</rdfs:label>
		<ISO639-1>OR</ISO639-1>
	</Language>
	<Language rdf:ID="PS">
		<rdfs:label>PASHTO;PUSHTO</rdfs:label>
		<ISO639-1>PS</ISO639-1>
	</Language>
	<Language rdf:ID="FA">
		<rdfs:label>PERSIAN(farsi)</rdfs:label>
		<ISO639-1>FA</ISO639-1>
	</Language>
	<Language rdf:ID="PL">
		<rdfs:label>POLISH</rdfs:label>
		<ISO639-1>PL</ISO639-1>
	</Language>
	<Language rdf:ID="PT">
		<rdfs:label>PORTUGUESE</rdfs:label>
		<ISO639-1>PT</ISO639-1>
	</Language>
	<Language rdf:ID="PA">
		<rdfs:label>PUNJABI</rdfs:label>
		<ISO639-1>PA</ISO639-1>
	</Language>
	<Language rdf:ID="QU">
		<rdfs:label>QUECHUA</rdfs:label>
		<ISO639-1>QU</ISO639-1>
	</Language>
	<Language rdf:ID="RM">
		<rdfs:label>RHAETO-ROMANCE</rdfs:label>
		<ISO639-1>RM</ISO639-1>
	</Language>
	<Language rdf:ID="RO">
		<rdfs:label>ROMANIAN</rdfs:label>
		<ISO639-1>RO</ISO639-1>
	</Language>
	<Language rdf:ID="RU">
		<rdfs:label>RUSSIAN</rdfs:label>
		<ISO639-1>RU</ISO639-1>
	</Language>
	<Language rdf:ID="SM">
		<rdfs:label>SAMOAN</rdfs:label>
		<ISO639-1>SM</ISO639-1>
	</Language>
	<Language rdf:ID="SG">
		<rdfs:label>SANGHO</rdfs:label>
		<ISO639-1>SG</ISO639-1>
	</Language>
	<Language rdf:ID="SA">
		<rdfs:label>SANSKRIT</rdfs:label>
		<ISO639-1>SA</ISO639-1>
	</Language>
	<Language rdf:ID="GD">
		<rdfs:label>SCOTSGAELIC</rdfs:label>
		<ISO639-1>GD</ISO639-1>
	</Language>
	<Language rdf:ID="SR">
		<rdfs:label>SERBIAN</rdfs:label>
		<ISO639-1>SR</ISO639-1>
	</Language>
	<Language rdf:ID="SH">
		<rdfs:label>SERBO-CROATIAN</rdfs:label>
		<ISO639-1>SH</ISO639-1>
	</Language>
	<Language rdf:ID="ST">
		<rdfs:label>SESOTHO</rdfs:label>
		<ISO639-1>ST</ISO639-1>
	</Language>
	<Language rdf:ID="TN">
		<rdfs:label>SETSWANA</rdfs:label>
		<ISO639-1>TN</ISO639-1>
	</Language>
	<Language rdf:ID="SN">
		<rdfs:label>SHONA</rdfs:label>
		<ISO639-1>SN</ISO639-1>
	</Language>
	<Language rdf:ID="SD">
		<rdfs:label>SINDHI</rdfs:label>
		<ISO639-1>SD</ISO639-1>
	</Language>
	<Language rdf:ID="SI">
		<rdfs:label>SINGHALESE</rdfs:label>
		<ISO639-1>SI</ISO639-1>
	</Language>
	<Language rdf:ID="SS">
		<rdfs:label>SISWATI</rdfs:label>
		<ISO639-1>SS</ISO639-1>
	</Language>
	<Language rdf:ID="SK">
		<rdfs:label>SLOVAK</rdfs:label>
		<ISO639-1>SK</ISO639-1>
	</Language>
	<Language rdf:ID="SL">
		<rdfs:label>SLOVENIAN</rdfs:label>
		<ISO639-1>SL</ISO639-1>
	</Language>
	<Language rdf:ID="SO">
		<rdfs:label>SOMALI</rdfs:label>
		<ISO639-1>SO</ISO639-1>
	</Language>
	<Language rdf:ID="ES">
		<rdfs:label>SPANISH</rdfs:label>
		<ISO639-1>ES</ISO639-1>
	</Language>
	<Language rdf:ID="SU">
		<rdfs:label>SUNDANESE</rdfs:label>
		<ISO639-1>SU</ISO639-1>
	</Language>
	<Language rdf:ID="SW">
		<rdfs:label>SWAHILI</rdfs:label>
		<ISO639-1>SW</ISO639-1>
	</Language>
	<Language rdf:ID="SV">
		<rdfs:label>SWEDISH</rdfs:label>
		<ISO639-1>SV</ISO639-1>
	</Language>
	<Language rdf:ID="TL">
		<rdfs:label>TAGALOG</rdfs:label>
		<ISO639-1>TL</ISO639-1>
	</Language>
	<Language rdf:ID="TG">
		<rdfs:label>TAJIK</rdfs:label>
		<ISO639-1>TG</ISO639-1>
	</Language>
	<Language rdf:ID="TA">
		<rdfs:label>TAMIL</rdfs:label>
		<ISO639-1>TA</ISO639-1>
	</Language>
	<Language rdf:ID="TT">
		<rdfs:label>TATAR</rdfs:label>
		<ISO639-1>TT</ISO639-1>
	</Language>
	<Language rdf:ID="TE">
		<rdfs:label>TELUGU</rdfs:label>
		<ISO639-1>TE</ISO639-1>
	</Language>
	<Language rdf:ID="TH">
		<rdfs:label>THAI</rdfs:label>
		<ISO639-1>TH</ISO639-1>
	</Language>
	<Language rdf:ID="BO">
		<rdfs:label>TIBETAN</rdfs:label>
		<ISO639-1>BO</ISO639-1>
	</Language>
	<Language rdf:ID="TI">
		<rdfs:label>TIGRINYA</rdfs:label>
		<ISO639-1>TI</ISO639-1>
	</Language>
	<Language rdf:ID="TO">
		<rdfs:label>TONGA</rdfs:label>
		<ISO639-1>TO</ISO639-1>
	</Language>
	<Language rdf:ID="TS">
		<rdfs:label>TSONGA</rdfs:label>
		<ISO639-1>TS</ISO639-1>
	</Language>
	<Language rdf:ID="TR">
		<rdfs:label>TURKISH</rdfs:label>
		<ISO639-1>TR</ISO639-1>
	</Language>
	<Language rdf:ID="TK">
		<rdfs:label>TURKMEN</rdfs:label>
		<ISO639-1>TK</ISO639-1>
	</Language>
	<Language rdf:ID="TW">
		<rdfs:label>TWI</rdfs:label>
		<ISO639-1>TW</ISO639-1>
	</Language>
	<Language rdf:ID="UG">
		<rdfs:label>UIGUR</rdfs:label>
		<ISO639-1>UG</ISO639-1>
	</Language>
	<Language rdf:ID="UK">
		<rdfs:label>UKRAINIAN</rdfs:label>
		<ISO639-1>UK</ISO639-1>
	</Language>
	<Language rdf:ID="UR">
		<rdfs:label>URDU</rdfs:label>
		<ISO639-1>UR</ISO639-1>
	</Language>
	<Language rdf:ID="UZ">
		<rdfs:label>UZBEK</rdfs:label>
		<ISO639-1>UZ</ISO639-1>
	</Language>
	<Language rdf:ID="VI">
		<rdfs:label>VIETNAMESE</rdfs:label>
		<ISO639-1>VI</ISO639-1>
	</Language>
	<Language rdf:ID="VO">
		<rdfs:label>VOLAPUK</rdfs:label>
		<ISO639-1>VO</ISO639-1>
	</Language>
	<Language rdf:ID="CY">
		<rdfs:label>WELSH</rdfs:label>
		<ISO639-1>CY</ISO639-1>
	</Language>
	<Language rdf:ID="WO">
		<rdfs:label>WOLOF</rdfs:label>
		<ISO639-1>WO</ISO639-1>
	</Language>
	<Language rdf:ID="XH">
		<rdfs:label>XHOSA</rdfs:label>
		<ISO639-1>XH</ISO639-1>
	</Language>
	<Language rdf:ID="YI">
		<rdfs:label>YIDDISH</rdfs:label>
		<ISO639-1>YI</ISO639-1>
	</Language>
	<Language rdf:ID="YO">
		<rdfs:label>YORUBA</rdfs:label>
		<ISO639-1>YO</ISO639-1>
	</Language>
	<Language rdf:ID="ZA">
		<rdfs:label>ZHUANG</rdfs:label>
		<ISO639-1>ZA</ISO639-1>
	</Language>
	<Language rdf:ID="ZU">
		<rdfs:label>ZULU</rdfs:label>
		<ISO639-1>ZU</ISO639-1>
	</Language>
</rdf:RDF>

RDF Schema for ISO Standard Thesauri

Description of the TIF RDF Schema for thesauri complying with ISO2788 and ISO5964 standards