 |
 |
 |
| SWAD-Europe Thesaurus Activity |
| Deliverable 8.1 |
Modelling Thesauri for the Semantic WebDescription of a draft ISO-compatible RDF schema for theasuri |
|
|
|
| SWAD-Europe Thesaurus Activity |
| Deliverable 8.1 |
Modelling Thesauri for the Semantic WebDescription of a draft ISO-compatible RDF schema for theasuri |
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.
This document is contributing to Workpackage 8 Deliverable 8.1/8.2 (Public discussion document relating an RDF thesaurus schema to at least two more complex RDF ontologies). An initial draft "concept-based" standard is proposed which is compatible with ISO standards in the area.
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/.
Here we present the Thesaurus Interchange Format (TIF) for the semantic web. An interchange format must be based on a theoretically sound conceptual model of that which is being represented. If not, there is the possibility for ambiguity and loss of information. Therefore we first outline two options for modelling thesauri, the 'concept-oriented' and 'term-oriented' models, relating these to the ISO standards for thesaurus definition. We then give justification for basing the TIF on the concept-oriented model, with an extension to allow compact term-oriented representations. Our TIF is an RDF schema, and the intended use of the properties and classes of the schema are described. We then discuss possible benefits associated with defining TIF as an OWL ontology.
Here we describe two approaches to modelling thesauri.
The ISO 2788:1986 standard implies that the set of terms that is a preferred term (also known as indexing term or descriptor) and its non-preferred alternatives (also known as synonyms) constitute a set of possible labels for some abstract concept that exists in the domain of human thought. In other words, terms stand for concepts. In the concept-oriented model, the abstract concepts themselves are modelled explicitly, and are represented as a class of objects. The hierarchical and associative relationships (broader, narrower, related) of the thesaurus are then asserted between concepts. That is, the concepts are the nodes in the generalisation hierarchy. In a multilingual thesaurus, equivalence relationships are asserted between concepts.
In short, there are no term-term relationships, only concept-concept and concept-term relationships. This model is illustrated in figure 1.
The concept-relation relationship is defined as the generalisation of all relationships that may be defined between concepts of the same language. The familiar broader, narrower and related relationships are its members.
Notions of equivalence between concepts are used to define multilingual thesauri, or to map between two thesauri from difference sources describing overlapping domains. The concept-equivalence relationship is the generalisation of all such relationships. This approach allows for the representation of multilingual thesauri in which each language has its own concept hierarchy. It is also backwards-compatible with multilingual thesauri in which there is one hierarchy, with alternate preferred terms for different languages.
In a term-oriented model, although it may be tacitly implied that a set of terms stands for some abstract concept, the concept is not reified in the model. Terms which are preferred terms are used as the nodes in the generalisation hierarchy. In this model it is usual to distinbuish between the class of objects that are preferred terms and the class of objects that are non-preferred terms. This model is illustrated in figure [???].
We have chosen to base the TIF on the concept-oriented model, for the following reasons. First, the concept-oriented model more accurately reflects the human knowledge structure that is being modelled. This encourages people to focus on the concepts themselves, and acknowledge that different people may use different terms to stand for the same concept. Thus by adhering to a concept-oriented model in thesaurus development, there is increased scope for removing and avoiding ambiguity. This also simplifies the process of creating mappings between two similar thesauri in the same domain, a task which is particularly appropriate for the semantic web, where several different individuals my create their own indexing structures referring to the same domain. Second, 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. Third, it is strongly recommended by the ISO 5964:1985 standard that multilingual equivalence relations are made only between preferred terms. By allowing equivalence relations only between concepts, the concept-oriented model enforces this recommendation.
However, the term-oriented approach is the traditional approach for modelling thesauri, and will be more familiar to existing users. It is mmore compact and easier to interpret. Therefore we have created an extension to TIF, called TIFS (for TIF-simple), which consists of a set of term-term properties. This allows one to generate a term-oriented view onto a thesaurus. Although this schema does allow one to generate a term-oriented thesaurus from scratch, we strongly recommend that the concept-oriented approach is used to model the thesaurus, and is maintained by those who control, maintain and update the vocabulary, and term-oriented views may be generated and used as necessary. In this way the strengths of both models are retained, and may be exploited according to need. More detailed discussion of the term-oriented to concept-oriented mapping can be found below.
In this section we give the RDF schema for monolingual or multilingual thesauri, based on the concept-oriented model described above. The base XML namespace for classes and properties in the schema is
http://www.w3c.rl.ac.uk/2003/07/31-tif#
I have followed 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 class hierarchy is shown in figure 3. Here follows a short description of the intended usage of each class.
The domain/range values for the properties of the TIF schema are illustrated in figure [???] and also in table 1.
| 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 |
Here follows a short description of the properties defined in the schema.
The Language class and identifiers for all languages defined by ISO639-1 are supplied in a separate file (see Appendix [???]). These resources are referenced with the base namespace
http://www.w3c.rl.ac.uk/2003/07/31-lang#
The TIFS schema defines properties that describe the relationships of a term-oriented thesaurus. This schema will seem much more familiar to users of traditional thesauri, having properties such as BT (has-broader-term) NT (has-narrower-term) and UF (use-for). As described above, although these properties would allow one to define a term-oriented (traditional) thesaurus from scratch, we recommend that these properties are viewed as derived properties. That is, they are derived from the concept-oriented data. The intention in including this schema is to allow users to produce minimal compact representations of their thesauri, which are at the same time more familiar in structure to users of traditional thesauri.
No additional classes are defined here. The Term class from TIF is imported.
We chose here not to define additional classes to describing the disjoint classes of preferred-terms and their synonyms (we might have, for example, defined two further classes called Preferred-Term and Non-Preferred-Term, as sub-classes of the Term class). This choice was made to retain the simplicity of the schema. Adding these classes would provide extra validation power. However, we intend that the concept-oriented TIF is used as the main representation format, on which validation tests are performed. Therefore TIFS should be streamlined to retain a highly compact form. Whether or not a Term is a preferred term can be inferred from the absence or presence of the use property (non-preferred terms must have this property).
Here follows a short description of the properties.
Term-oriented properties (as defined by TIFS Schema) may be derived from concept-oriented properties (as defined by TIF schema) according to the following relationships:
BT = has-preferred-term-1; has-broader-concept; has-preferred-term
NT = has-preferred-term-1; has-narrower-concept; has-preferred-term
RT = has-preferred-term-1; has-related-concept; has-preferred-term
UF = has-preferred-term-1; has-non-preferred-term
USE = has-non-preferred-term-1; has-preferred-term
SN = is-indicated-by-1; has-scope-note; rdf:value
Where ; represents relational composition; (p ; q)(a,c) if and only if there exists some b such that: p(a,b) and q(b,c). We have also expressed these relationships as mapping rules, and used the Closed World Machine (CWM) to perform the derivation of TIFS from TIF. These rules are in Appendix VI.
The primary approach taken here is to use RDF Schema. This is to allow a simplicity of expression which can immediately be put to use before standardisation of OWL has been completed. However, using OWL would allow the expression of constraints on the model, such as the transitivity of and inverse relationships between has-broader-concept and has-narrower-concept properties, and the symmetricity of the has-related-concept property. The expression of these constraints, and the support of tools that maintain and enforce them would further enhance and support the maintenaince of thesaurus integrity and consistency. Therefore we also present the TIF and TIFS as an OWL ontology, as an alternative to the RDF schema representation, in appendices [???]. [should the ontology extend descriptions for the same resources as the schema, or use different ones???].
One entire thesaurus (ELSST) as well as fragments of others (e.g. AAT, 1994) have been represented in RDF compliant with the proposed TIF schema to test its coverage. ELSST is a multilingual thesaurus (English, French, Spanish, German) for the social science domain as a restricted vocabulary for indexing and accessing metadata entries. The ELSST thesaurus contains 49 main hierarchies with 1,107 preferred terms, 273 standalone preferred terms and 860 synonyms as non-preferred terms. All the preferred terms of the monolingual thesaurus have been translated into French, German and Spanish. There are 511 French, 1316 German and 638 Spanish synonyms. The thesaurus has been produced in an MS-Access database which writes out RDF or the thesaurus conventional alphabetic listing and has tools to examine the thesaurus and search using terms in one language to access metadata in another. Although produced, it is actively being used, and is therefore constantly under revision by UKDA. In particular, following the project further translations of terms into Finnish, Norwegian, Danish & Greek are planned, as are the inclusion of terms related through inexact translations in addition to the exact translations already included. Also the CESSDA group of European Data Archives have agreed to adopt ELSST as the European Controlled Vocabulary for Social Science, and will meet to define an adoption timetable in March 2002.
We present a candidate for the Thesaurus Interchange Format (TIF) for use in the semantic web. The TIF is an RDF schema, based on the concept-oriented thesaurus model. We also present an extension to the TIF to allow the derivation and representation of more compact term-oriented thesaurus data. We recommend that thesauri be modelled and maintained using the concept-oriented approach, and that the concept-oriented TIF is used wherever possible. In situations where a more compact format is desired, or where the familiarity of term-oriented relationships to traditional thesaurus users is desired, term-oriented TIFS representations may be generated and published.
We also present TIF and TIFS as OWL ontologies. In this format we can express constraints on the data model. We anticipate that when tool support for OWL ontologies becomes more mature, this functionality may be exploited for the purpose of maintaining and validating thesaurus data. We anticipate this to be a fruitful area for further work in the near future.
The TIF is built as an extensible framework of classes and properties. In this way it may be extended to express other kinds of semantic relationship between concepts or terms. For example, we could introduce ACK /AF relations between terms for abbreviations and acronyms, such as in the DAML+OIL ontology from DRC, or we could express the diagonal relationships related-broader-concept and related-narrower-concept, such as in the ETB thesaurus schema. We could also model categories, as are found in many thesaurus, as a sub-class of concepts or terms, and the semantically more precise relationships that go with them.
Another area for future research is in the domain of migration from thesauri to more richly structured ontologies. A solid framework for pinning down the exact semantic relationships that are implied between concepts in a thesaurus is required here.
This work has also revealed the strength of the RDF approach in exploiting its capability to represent different information structures in alternative modelling views, and to transform between such views. More work could proceed in the direction of exploring and standardising tools for RDF transformations.
<?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>
<?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 tifs "http://www.w3c.rl.ac.uk/2003/07/31-tif-simple#" > <!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 minimal representation format Thesaurus Interchange (TIF-simple or TIFS). Authors: A J Miles, B M Matthews Date: 31/07/2003 Version: 0.2 Assume base namespace: http://www.w3c.rl.ac.uk/2003/07/31-tif-simple# --> <rdf:RDF xml:lang="en" xmlns:rdf="&rdf;" xmlns:rdfs="&rdfs;" xmlns:dc="&dc;" xmlns:dct="&dct;" xmlns:tif="&tif;" xmlns:tifs="&tifs;" xmlns:lang="⟨" xmlns="&tifs;" xml:base="&tifs;" > <!-- Description of this schema. --> <rdf:Description rdf:about=""> <rdfs:comment>This is the minimal representation format Thesaurus Interchange (TIF-simple or TIFS). </rdfs:comment> <rdfs:label xml:lang="en">Thesaurus Interchange Format - Simple (TIFS)</rdfs:label> <dc:title xml:lang="en">Thesaurus Interchange Format - Simple (TIFS)</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 minimal representation format Thesaurus Interchange (TIF-simple or TIFS). </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 properties. --> <rdf:Property rdf:ID="SN"> <rdfs:comment>A scope note of a concept.</rdfs:comment> <rdfs:label>has-scope-note</rdfs:label> <rdfs:domain rdf:resource="&tif;Term"/> <rdfs:range rdf:resource="&rdfs;Literal"/> </rdf:Property> <rdf:Property rdf:ID="termRelation"> <rdfs:comment>A generalisation of all possible relationships between two terms from the same language.</rdfs:comment> <rdfs:label>term-relation</rdfs:label> <rdfs:domain rdf:resource="&tif;Term"/> <rdfs:range rdf:resource="&tif;Term"/> </rdf:Property> <rdf:Property rdf:ID="BT"> <rdfs:comment>The subject has a broader term specified by the object.</rdfs:comment> <rdfs:label>has-broader-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </rdf:Property> <rdf:Property rdf:ID="NT"> <rdfs:comment>The subject has a narrower term specified by the object.</rdfs:comment> <rdfs:label>has-narrower-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </rdf:Property> <rdf:Property rdf:ID="RT"> <rdfs:comment>The related term relation.</rdfs:comment> <rdfs:label>has-related-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </rdf:Property> <rdf:Property rdf:ID="UF"> <rdfs:comment>The mapping from a descriptor (indexing term, preferred term) to a synonym (non-preferred term)</rdfs:comment> <rdfs:label>use-for</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </rdf:Property> <rdf:Property rdf:ID="USE"> <rdfs:comment>The mapping from a synonym (non-preferred term) to its descriptor (indexing term, preferred term)</rdfs:comment> <rdfs:label>use</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </rdf:Property> <rdf:Property rdf:ID="termEquivalence"> <rdfs:comment>The super-property of all properties relating terms from different languages.</rdfs:comment> <rdfs:label>term-equivalence</rdfs:label> <rdfs:domain rdf:resource="&tif;Term"/> <rdfs:range rdf:resource="&tif;Term"/> </rdf:Property> <rdf:Property rdf:ID="EE"> <rdfs:comment><!-- TODO --></rdfs:comment> <rdfs:label>has-exact-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> </rdf:Property> <rdf:Property rdf:ID="IE"> <rdfs:comment><!-- TODO --></rdfs:comment> <rdfs:label>has-inexact-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> </rdf:Property> <rdf:Property rdf:ID="PE"> <rdfs:comment><!-- TODO --></rdfs:comment> <rdfs:label>has-partial-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> </rdf:Property> <rdf:Property rdf:ID="OE"> <rdfs:comment><!-- TODO --></rdfs:comment> <rdfs:label>has-one-to-many-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> </rdf:Property> </rdf:RDF>
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE owl [ <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" > <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" > <!ENTITY owl "http://www.w3.org/2002/07/owl#" > <!ENTITY xsd "http://www.w3.org/2000/10/XMLSchema#" > <!ENTITY tif "http://www.w3c.rl.ac.uk/2003/07/31-tif-owl#" > <!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) in OWL. Authors: A J Miles, B M Matthews Date: 31/07/2003 Version: 0.1 Assume base namespace: http://www.w3c.rl.ac.uk/2003/07/31-tif-owl# --> <rdf:RDF xmlns:rdf ="&rdf;" xmlns:rdfs ="&rdfs;" xmlns:owl ="&owl;" xmlns:xsd ="&#xsd;" xmlns:dc ="&dc;" xmlns:dct ="&dct;" xmlns:tif ="&tif;" xmlns:lang ="⟨" xmlns ="&tif;" xml:base ="&tif;" > <owl:Ontology rdf:about=""> <rdfs:comment>This is the specification of the Thesaurus Interchange Format (TIF) in OWL</rdfs:comment> <rdfs:label xml:lang="en">Thesaurus Interchange Format (TIF) in OWL</rdfs:label> <dc:title xml:lang="en">Thesaurus Interchange Format (TIF) in OWL</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 specification of the Thesaurus Interchange Format (TIF) in OWL</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> </owl:Ontology> <!-- Definition of the classes. --> <owl:Class rdf:ID="Thesaurus"> <rdfs:comment></rdfs:comment> <rdfs:label>Thesaurus</rdfs:label> </owl:Class> <owl:Class rdf:ID="ThesaurusObject"> <rdfs:comment>Thesaurus-object</rdfs:comment> <rdfs:label>Thesaurus-object</rdfs:label> </owl:Class> <owl:Class rdf:ID="Concept"> <rdfs:comment></rdfs:comment> <rdfs:label>Concept</rdfs:label> <rdfs:subClassOf rdf:resource="#ThesaurusObject"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#code"/> <owl:cardinality rdf:datatype="&#xsd;nonNegativeInteger">1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#preferred"/> <owl:cardinality rdf:datatype="&#xsd;nonNegativeInteger">1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> </owl:Class> <owl:Class rdf:ID="Term"> <rdfs:comment></rdfs:comment> <rdfs:label>Term</rdfs:label> <rdfs:subClassOf rdf:resource="#ThesaurusObject"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#value"/> <owl:cardinality rdf:datatype="&#xsd;nonNegativeInteger">1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> </owl:Class> <owl:Class rdf:ID="ScopeNote"> <rdfs:comment></rdfs:comment> <rdfs:label>Scope-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ThesaurusObject"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="&rdf;value"/> <owl:cardinality rdf:datatype="&#xsd;nonNegativeInteger">1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> </owl:Class> <owl:Class rdf:ID="GeneralNote"> <rdfs:comment></rdfs:comment> <rdfs:label>General-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ScopeNote"/> </owl:Class> <owl:Class rdf:ID="HierarchyNote"> <rdfs:comment></rdfs:comment> <rdfs:label>Hierarchy-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ScopeNote"/> </owl:Class> <owl:Class rdf:ID="TranslationNote"> <rdfs:comment></rdfs:comment> <rdfs:label>Translation-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ScopeNote"/> </owl:Class> <owl:Class rdf:ID="EditorNote"> <rdfs:comment></rdfs:comment> <rdfs:label>Editor-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ScopeNote"/> </owl:Class> <owl:Class rdf:ID="HistoryNote"> <rdfs:comment></rdfs:comment> <rdfs:label>History-note</rdfs:label> <rdfs:subClassOf rdf:resource="#ScopeNote"/> </owl:Class> <!-- Definition of the properties. --> <owl:ObjectProperty rdf:ID="language"> <rdfs:comment></rdfs:comment> <rdfs:label>in-language-of</rdfs:label> <rdfs:domain rdf:resource="#ThesaurusObject" /> <rdfs:range rdf:resource="⟨Language" /> </owl:ObjectProperty> <owl:DatatypeProperty rdf:ID="code"> <rdfs:comment></rdfs:comment> <rdfs:label>has-classification-code</rdfs:label> <rdfs:domain rdf:resource="#Concept" /> <rdfs:range rdf:resource="&rdfs;literal" /> </owl:DatatypeProperty> <owl:DatatypeProperty rdf:ID="value"> <rdfs:comment></rdfs:comment> <rdfs:label>has-value</rdfs:label> <rdfs:domain rdf:resource="#Term" /> <rdfs:range rdf:resource="&rdfs;literal" /> </owl:DatatypeProperty> <owl:ObjectProperty rdf:ID="note"> <rdfs:comment></rdfs:comment> <rdfs:label>has-scope-note</rdfs:label> <rdfs:domain rdf:resource="#Concept" /> <rdfs:range rdf:resource="#ScopeNote" /> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="indicatedBy"> <rdfs:comment></rdfs:comment> <rdfs:label>is-indicated-by</rdfs:label> <rdfs:domain rdf:resource="#Concept" /> <rdfs:range rdf:resource="#Term" /> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="indicates"> <rdfs:comment></rdfs:comment> <rdfs:label>indicates</rdfs:label> <rdfs:domain rdf:resource="#Term" /> <rdfs:range rdf:resource="#Concept" /> <owl:inverseOf rdf:resource="#indicatedBy"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="preferred"> <rdfs:comment></rdfs:comment> <rdfs:label>has-preferred-term</rdfs:label> <rdf:type rdf:resource="&owl;InverseFunctionalProperty"/> <rdfs:subPropertyOf rdf:resource="#indicatedBy"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="nonPreferred"> <rdfs:comment></rdfs:comment> <rdfs:label>has-non-preferred-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#indicatedBy"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="conceptRelation"> <rdfs:comment></rdfs:comment> <rdfs:label>concept-relation</rdfs:label> <rdfs:domain rdf:resource="#Concept" /> <rdfs:range rdf:resource="#Concept" /> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="broader"> <rdfs:comment></rdfs:comment> <rdfs:label>has-broader-concept</rdfs:label> <rdf:type rdf:resource="&owl;TransitiveProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptRelation"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="narrower"> <rdfs:comment></rdfs:comment> <rdfs:label>has-narrower-concept</rdfs:label> <rdf:type rdf:resource="&owl;TransitiveProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptRelation"/> <owl:inverseOf rdf:resource="#broader"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="related"> <rdfs:comment></rdfs:comment> <rdfs:label>has-related-concept</rdfs:label> <rdf:type rdf:resource="&owl;SymmetricProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptRelation"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="conceptEquivalence"> <rdfs:comment></rdfs:comment> <rdfs:label>concept-equivalence</rdfs:label> <rdfs:domain rdf:resource="#Concept" /> <rdfs:range rdf:resource="#Concept" /> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="exact"> <rdfs:comment></rdfs:comment> <rdfs:label>has-exact-equivalent</rdfs:label> <rdf:type rdf:resource="&owl;SymmetricProperty"/> <rdf:type rdf:resource="&owl;TransitiveProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="inexact"> <rdfs:comment></rdfs:comment> <rdfs:label>has-inexact-equivalent</rdfs:label> <rdf:type rdf:resource="&owl;SymmetricProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="partial"> <rdfs:comment></rdfs:comment> <rdfs:label>has-partial-equivalent</rdfs:label> <rdf:type rdf:resource="&owl;SymmetricProperty"/> <rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="oneToMany"> <rdfs:comment></rdfs:comment> <rdfs:label>has-one-to-many-equivalent</rdfs:label> <rdfs:subPropertyOf rdf:resource="#conceptEquivalence"/> </owl:ObjectProperty> </rdf:RDF>
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE owl [ <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" > <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" > <!ENTITY owl "http://www.w3.org/2002/07/owl#" > <!ENTITY xsd "http://www.w3.org/2000/10/XMLSchema#" > <!ENTITY tif "http://www.w3c.rl.ac.uk/2003/07/31-tif-owl#" > <!ENTITY tifs "http://www.w3c.rl.ac.uk/2003/07/31-tif-simple-owl#" > <!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 extension to the Thesaurus Interchange Format for term-based thesauri (TIF-simple or TIFS) in OWL. Authors: A J Miles, B M Matthews Date: 31/07/2003 Version: 0.1 Assume base namespace: http://www.w3c.rl.ac.uk/2003/07/31-tif-simple-owl# --> <rdf:RDF xmlns:rdf ="&rdf;" xmlns:rdfs ="&rdfs;" xmlns:owl ="&owl;" xmlns:xsd ="&#xsd;" xmlns:dc ="&dc;" xmlns:dct ="&dct;" xmlns:tif ="&tif;" xmlns:tifs ="&tifs;" xmlns:lang ="⟨" xmlns ="&tifs;" xml:base ="&tifs;" > <owl:Ontology rdf:about=""> <rdfs:comment>This is the extension of the Thesaurus Interchange Format for term-based thesauri (TIF-simple or TIFS) in OWL</rdfs:comment> <rdfs:label xml:lang="en">Thesaurus Interchange Format - Simple (TIFS) in OWL</rdfs:label> <dc:title xml:lang="en">Thesaurus Interchange Format - Simple (TIFS) in OWL</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 extension to the Thesaurus Interchange Format for term-based thesauri (TIF-simple or TIFS) in OWL.</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> </owl:Ontology> <!-- Definition of the classes. --> <owl:Class rdf:ID="PTerm"> <rdfs:comment>The class of preferred terms (also known as 'descriptors' or 'indexing terms').</rdfs:comment> <rdfs:label>Preferred-term</rdfs:label> <rdfs:subClassOf rdf:resource="&tif;Term"/> </owl:Class> <owl:Class rdf:ID="NTerm"> <rdfs:comment>The class of non-preferred terms (also known as 'synonyms').</rdfs:comment> <rdfs:label>Non-preferred-term</rdfs:label> <rdfs:subClassOf rdf:resource="&tif;Term"/> <!-- Every non-preferred term must have exactly one 'USE' property --> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#USE"/> <owl:cardinality rdf:datatype="&#xsd;nonNegativeInteger">1</owl:cardinality> </owl:Restriction> </rdfs:subClassOf> <!-- If support for OWL DL - can include following statement to specify that the class of non-preferred terms is disjoint with the class of preferred terms. --> <owl:disjointWith rdf:resource="#PTerm"/> </owl:Class> <!-- Definition of the properties. --> <owl:ObjectProperty rdf:ID="UF"> <rdfs:comment></rdfs:comment> <rdfs:label>use-for</rdfs:label> <rdfs:domain rdf:resource="#PTerm"/> <rdfs:range rdf:resource="#NTerm"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="USE"> <rdfs:comment></rdfs:comment> <rdfs:label>use</rdfs:label> <owl:inverseOf rdf:resource="#UF"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="termRelation"> <rdfs:comment>The super-property of all properties connecting the preferred terms from the same language.</rdfs:comment> <rdfs:label>term-relation</rdfs:label> <rdfs:domain rdf:resource="#PTerm"/> <rdfs:range rdf:resource="#PTerm"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="BT"> <rdfs:comment></rdfs:comment> <rdfs:label>has-broader-term</rdfs:label> <rdf:type rdf:resource="&owl;TransitiveProperty"/> <rdfs:subPropertyOf rdf:resource="#termRelation"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="NT"> <rdfs:comment></rdfs:comment> <rdfs:label>has-narrower-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> <rdf:type rdf:resource="&owl;TransitiveProperty"/> <owl:inverseOf rdf:resource="#BT"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="RT"> <rdfs:comment></rdfs:comment> <rdfs:label>has-related-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termRelation"/> <rdf:type rdf:resource="&owl;SymmetricProperty"/> </owl:ObjectProperty> <owl:DatatypeProperty rdf:ID="SN"> <rdfs:comment></rdfs:comment> <rdfs:label>has-scope-note</rdfs:label> <rdfs:domain rdf:resource="&tif;Term" /> <rdfs:range rdf:resource="&rdfs;literal" /> </owl:DatatypeProperty> <owl:ObjectProperty rdf:ID="termEquivalence"> <rdfs:comment>The super-property of all properties relating terms from different languages. The domain/range constraints of this property maintain that multilingual equivalence statements may be made only between the preferred or indexing terms of a thesaurus.</rdfs:comment> <rdfs:label>term-equivalence</rdfs:label> <rdfs:domain rdf:resource="#PTerm"/> <rdfs:range rdf:resource="#PTerm"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="EE"> <rdfs:comment></rdfs:comment> <rdfs:label>has-exact-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> <rdf:type rdf:resource="&owl;SymmetricProperty"/> <rdf:type rdf:resource="&owl;TransitiveProperty"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="IE"> <rdfs:comment></rdfs:comment> <rdfs:label>has-inexact-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> <rdf:type rdf:resource="&owl;SymmetricProperty"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="PE"> <rdfs:comment></rdfs:comment> <rdfs:label>has-partial-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> <rdf:type rdf:resource="&owl;SymmetricProperty"/> </owl:ObjectProperty> <owl:ObjectProperty rdf:ID="OE"> <rdfs:comment></rdfs:comment> <rdfs:label>has-one-to-many-equivalent-term</rdfs:label> <rdfs:subPropertyOf rdf:resource="#termEquivalence"/> </owl:ObjectProperty> </rdf:RDF>
<?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>
#CWM rules to create term-based statements from concept-based statements
@prefix tif: <http://www.w3c.rl.ac.uk/2003/07/22-tif#> .
@prefix tifs: <http://www.w3c.rl.ac.uk/2003/07/22-tif-simple#> .
@prefix log: <http://www.w3.org/2000/10/swap/log#> .
#RULE C - UF USE mappings
this log:forAll <#d>, <#e>, <#f> .
{
<#d>
tif:preferredTerm <#e>;
tif:nonPreferredTerm <#f> .
}
log:implies
{
<#e> tifs:UF <#f> .
<#f> tifs:USE <#e> .
}
.
#RULE D - BT mappings
this log:forAll <#g>, <#h>, <#i> .
{
<#g>
tif:broader [tif:preferredTerm <#i>];
tif:preferredTerm <#h> .
}
log:implies
{
<#h> tifs:BT <#i> .
}
.
#RULE E - NT mappings
this log:forAll <#j>, <#k>, <#l> .
{
<#j>
tif:narrower [tif:preferredTerm <#l>];
tif:preferredTerm <#k> .
}
log:implies
{
<#k> tifs:NT <#l> .
}
.
#RULE F - RT mappings
this log:forAll <#m>, <#n>, <#o> .
{
<#m>
tif:related [tif:preferredTerm <#o>];
tif:preferredTerm <#n> .
}
log:implies
{
<#n> tifs:RT <#o> ;
}
.
#RULE G - SN mapping
this log:forAll <#p>, <#q>, <#r> .
{
<#p> tif:scopeNote [rdf:value <#q>] ;
tif:preferredTerm <#r> .
}
log:implies
{
<#r> tifs:SN <#q> .
}
.