Ontology for EUROVOC based on: The ontology is an extension of: SKOS Simple Knowledge Organization System Reference W3C Candidate Recommendation 17 March 2009 Including: Appendix A. SKOS eXtension for Labels (XL) UF 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 --- The non preferred term of an equivalence relationship. When ?equivrel rdfType ev:EquivalenceRelationship . ?equivrel ev:UF ?uf . ?equivrel ev:USE ?use . ?c xl:prefLabel ?use Then ?c xl:altLabel ?uf Notation <?use xl:literalForm> UF <?uf xl:literalForm> <?uf xl:literalForm> USE <?use xl:literalForm> USE 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 --- The preferred term of an equivalence relationship. When ?equivrel rdfType ev:EquivalenceRelationship . ?equivrel ev:UF ?uf . ?equivrel ev:USE ?use . ?c xl:prefLabel ?use Then ?c xl:altLabel ?uf Notation <?use xl:literalForm> UF <?uf xl:literalForm> <?uf xl:literalForm> USE <?use xl:literalForm> acronym 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 02 --- The related labels must have the may have a different language The object of the predicate is the acronym of the predicate subject. If an acronym is given for a subject in a diffferent language and the acronym and the subject label are bothe labels (xl:altLabel or xl:prefLabel) of the same concept, the the acronym must be used to index that concept in the language of the acronym and in the language of the subject label. An acronym may be the acronym of a full name, of a short name or of an unqualified name. UF+ 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 03 ---- The compound non preferred term of a compound equivalence relationship. When ?equivrel rdfType ev:CompoundEquivalence . ?equivrel ev:compoundNonPreferredTerm ?uf . ?equivrel ev:preferredTermComponent ?use . ?c xl:prefLabel ?use Then ?c xl:altLabel ?uf Notation <?use xl:literalForm> UF+ <?uf xl:literalForm> <?uf xl:literalForm> USE+ <?use xl:literalForm> (multiple) domain 4.2.4.4 Relations; a) Reciprocal Relationship - Hierarchical relationship BT/NT between two descriptors 01 [(domain/microthesauri),] The domain of a micro-thesaurus. A micro-thesaurus can be in only one domain (functional property). published thesaurus identifies the thesaurs being published. full name 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 02, 04 --- The relation between labels representing a short name (the subject) and a full name (the object). The relation holds between names of the same language. The following SPARQL query should have an empty result list SELECT ?lang(?a) WHERE { ?l ev:fullName ?a . FILTER ( lang(?l) != lang(?a) ) } domain CONSTRUCT { ?resource ev:inDomain ?domain } WHERE { ?resource skos:inScheme ?mt . ?mt ev:domain ?domain } Declares a resource to participate into a domain If an ev:Domain would be modelled as a skos:Colection, then the skos:member property restriction to the domain ev:Domain would be the inverse of ev:inDomain. micro thesaurus 4.2.4.4 Relations; a) Reciprocal Relationship - Hierarchical relationship BT/NT between two descriptors 01 [(domain/microthesauri),] -- The microthesaurus of a domain. Each micro thesaurus can be in only one domain. If ev:Domain would be modelled as a collection, the restriction of skos:member to the range ev:MicroThesaurus would be equivalent to ev:microThesaurus. ID relationship between subject (ev:Domain) and object (ev:microthesaurus) 4.2.4.3 Attributes Microthesaurus (CATEGORY) Microthesaurus ID [4 digit number, with leading zero, two leading digits = ev:Domain identifier] USE+ 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 03 ---- A preferred term of a compound equivalence relationship. When ?equivrel rdfType ev:CompoundEquivalence . ?equivrel ev:compoundNonPreferredTerm ?uf . ?equivrel ev:preferredTermComponent ?use . ?c xl:prefLabel ?use Then ?c xl:altLabel ?uf Notation <?use xl:literalForm> UF+ <?uf xl:literalForm> <?uf xl:literalForm> USE+ <?use xl:literalForm> (multiple) reference 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 06 --- Reference made from a note to a concept. The attribute typically may be used in a definition or scope note about a concept or a label. Not explicitly exported by the eurovoc portal. May be embedded in notes using RDFa compliant mark-up (e.g. the rel attribute). Usage of links in notes (Scope note, History note, definition) - all these notes can have XMLLiteral values with mark-up that appears in the xhtml mark up the namespace of this mark-up is http://www.w3.org/1999/xhtml and must be declared and used. XHTML must be compliant to version="XHTML+RDFa 1.0" the content will NOT include the xhtml:body element, only its content (plain text, <xhtml:div>, ...) - in all notes, href references may refer to: op: ev:reference (to a eurovoc concept) example: <xhtml:a rel="ev:reference" href="http://eurovoc.....">xyz</xhtml:a> short name 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 02, 04 --- The relation between labels representing a full name (the subject) and a short name (the object). The relation holds between names of the same language. The following SPARQL query should have an empty result list SELECT ?lang(?a) WHERE { ?l ev:shortName ?a . FILTER ( lang(?l) != lang(?a) ) } supported language 4.1.1 Purpose of Eurovoc --- supported language (in the thesaurus) Which languages are supported in the thesaurus. It allows to groww or reduce the required languages as needed. translation of 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 01 --- The related labels must have the different languages. The following SPARQL query should have an empty result list SELECT ?lang(?l2) WHERE { ?l1 ev:acronym ?l2 . FILTER ( lang(?l1) = lang(?l2) ) } ui 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 05 --- The concept in the domain is obsolete as from a date mentioned in the scope note. (should be present in each language) The object values identifies the concept that must be used instead. source A related resource from which the described resource is derived. The attribute typically may be used in a definition (note) about a concept or a label. The source then typically references the resource from which the definition subject (concept or label) is derived from. Not explicitly exported by the eurovoc portal. May be embedded in notes using RDFa compliant mark-up (e.g. the rel attribute). broader match S37 skos:mappingRelation, skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each instances of owl:ObjectProperty. S40 skos:closeMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each sub-properties of skos:mappingRelation. S41 skos:broadMatch is a sub-property of skos:broader, skos:narrowMatch is a sub-property of skos:narrower, and skos:relatedMatch is a sub-property of skos:related. broader 4.2.4.4 Relations; a) Reciprocal Relationship - Hierarchical relationship BT/NT between two descriptors 01 [descriptor,] --- S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S22 skos:broader is a sub-property of skos:broaderTransitive, and skos:narrower is a sub-property of skos:narrowerTransitive. S25 skos:narrower is the owl:inverseOf the property skos:broader. Must be given on import - agreement with TMS. The property skos:broader is not irreflexsive while this would be appropriate in most thesauri. broader transitive Calculated on import from - broader - tansitivity characteristic (could be inferred) S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S19 The rdfs:domain of skos:semanticRelation is the class skos:Concept. S21 skos:broaderTransitive, skos:narrowerTransitive and skos:related are each sub-properties of skos:semanticRelation. S24 skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:TransitiveProperty. S26 skos:narrowerTransitive is the owl:inverseOf the property skos:broaderTransitive. The property skos:broaderTrsansitive is not irreflexsive while this would be appropriate in mostapplications. change note Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral must not be indexed S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. close match S37 skos:mappingRelation, skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each instances of owl:ObjectProperty. S40 skos:closeMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each sub-properties of skos:mappingRelation. S45 skos:closeMatch and skos:exactMatch are each instances of owl:SymmetricProperty. definition Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral Must be indexed if subject is - ThesaurusTerm S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. editorial note Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral must not be indexed S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. exact match S42 skos:exactMatch is a sub-property of skos:closeMatch. S45 skos:closeMatch and skos:exactMatch are each instances of owl:SymmetricProperty. S46 skos:exactMatch is an instance of owl:TransitiveProperty. S47 skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch. The exact match is different from owl:samAs Mapping properties are between sckos:Concepts of different schema. The statement of transitivty therefore are not evident. For entailement, it may need to be considered taking this condition into account for defining transitive closure. example Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral must be indexed if subject is - ThesaurusTerm - ThesaurusConcept S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. has top concept 4.2.7.5 Search engine a) Advanced search engine 02 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Hierarchical relationship BT/NT between two descriptors; 01 [microthesaurus/descriptors] In the EUROVOC specification, a facet is - a topterm of the eurovoc thesaurus - a topterm of a microthesaurus --- Indicates whether this concept is a top concept S3 skos:inScheme, skos:hasTopConcept and skos:topConceptOf are each instances of owl:ObjectProperty. S5 The rdfs:domain of skos:hasTopConcept is the class skos:ConceptScheme. S6 The rdfs:range of skos:hasTopConcept is the class skos:Concept. S8 skos:topConceptOf is the owl:inverseOf the property skos:hasTopConcept. The following query provides the instances that are considered to be facets of a microthesaurus, per microthesaurus SELECT ?mt ?facet WHERE ?mt rdf:type ev:MicroThesaurus ?mt skos:hasTopConcept ?facet Usage convention is that top concepts of a scheme do not have broader concepts in that scheme. However, this is not a constraint. A top concept may have broader concepts in one scheme. history note Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral must be indexed if subject is - ThesaurusTerm S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. in scheme A skos:Concept may take part in more than one concept scheme. SKOS can not state that only certain concepts belong to the scheme (open, not closed) A skos relationship (like narrower, broader or related) does not entail concept scheme memberschip. So if one of these concepts is in a concept scheme it may not be the case that the other concept is part of the scheme. skos:inScheme does not only apply to skos:Concepts. Must be calculated on import for each concept and each microthesaurus, based on 1) ?mt ev:facet ?tt or ?mt skos:hasTopConcept ?tt 2) ?c skos:broaderTransitive ?tt Depends on construction of skos:broader:transitive S3 skos:inScheme, skos:hasTopConcept and skos:topConceptOf are each instances of owl:ObjectProperty. S4 The rdfs:range of skos:inScheme is the class skos:ConceptScheme. mapping relation Not all semantics are captured ant the provenance of properties is supposed to be evident. Mapping properties are between sckos:Concepts of different schema. S37 skos:mappingRelation, skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each instances of owl:ObjectProperty. S38 The rdfs:domain of skos:mappingRelation is the class skos:Concept. S39 The rdfs:range of skos:mappingRelation is the class skos:Concept member S30 skos:member and skos:memberList are each instances of owl:ObjectProperty. S31 The rdfs:domain of skos:member is the class skos:Collection. member list S30 skos:member and skos:memberList are each instances of owl:ObjectProperty. S32 The rdfs:domain of skos:memberList is the class skos:OrderedCollection. S33 The rdfs:range of skos:memberList is the class rdf:List. S34 skos:memberList is an instance of owl:FunctionalProperty. S35 For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property. Identifies the ordered list of members of an ordered collection. SKOS Statement S34 states the logical relationship between the skos:memberList and skos:member properties. This relationship means that a collection can be inferred from an ordered collection. This is illustrated in the example below. Example 45 (entailment) <MyOrderedCollection> rdf:type skos:OrderedCollection ; skos:memberList ( <X> <Y> <Z> ) . entails <MyOrderedCollection> rdf:type skos:Collection ; skos:member <X> , <Y> , <Z> . narrow match S37 skos:mappingRelation, skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each instances of owl:ObjectProperty. S40 skos:closeMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each sub-properties of skos:mappingRelation. S41 skos:broadMatch is a sub-property of skos:broader, skos:narrowMatch is a sub-property of skos:narrower, and skos:relatedMatch is a sub-property of skos:related. S43 skos:narrowMatch is the owl:inverseOf the property skos:broadMatch. narrower 4.2.4.4 Relations; a) Reciprocal Relationship - Hierarchical relationship BT/NT between two descriptors 01 [descriptor,] --- S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S22 skos:broader is a sub-property of skos:broaderTransitive, and skos:narrower is a sub-property of skos:narrowerTransitive. S25 skos:narrower is the owl:inverseOf the property skos:broader. May be calculated on import based on inverse property The property skos:narrower is not irreflexsive while this would be appropriate in most thesauri. narrower transitive May be calculated on import based on inverse property. Depends on construction of skos:broaderTransitive S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S19 The rdfs:domain of skos:semanticRelation is the class skos:Concept. S21 skos:broaderTransitive, skos:narrowerTransitive and skos:related are each sub-properties of skos:semanticRelation. S21 skos:broaderTransitive, skos:narrowerTransitive and skos:related are each sub-properties of skos:semanticRelation. S24 skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:TransitiveProperty. S26 skos:narrowerTransitive is the owl:inverseOf the property skos:broaderTransitive. The property skos:narrowerTrsansitive is not irreflexsive while this would be appropriate in mostapplications. note 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 06 --- Usage of links in notes (Scope note, History note, definition) - all these notes can have XMLLiteral values with mark-up that appears in the xhtml mark up the namespace of this mark-up is http://www.w3.org/1999/xhtml and must be declared and used. XHTML must be compliant to version="XHTML+RDFa 1.0" the content will NOT include the xhtml:body element, only its content (plain text, <xhtml:div>, ...) - in all notes, href references may refer to the following properties using the rel attribute (op = object property, dp = data property) dp: ev:relevantURL (ref to any website) example: <xhtml:a rel="ev:relevantURL" href="http://.........">xyz</xhtml:a> dp: ev:eurLexReference (ref to eurLex web site) example: <xhtml:a rel="ev:eurLexReference" href="http://.....">xyz</xhtml:a> op: ev:reference (to a eurovoc concept) example: <xhtml:a rel="ev:reference" href="http://eurovoc.....">xyz</xhtml:a> Domain and range of a note are note restricted note should ONLY be defined as annotation property. However, this gives problems in the protege 4 editor. Hence it is also an object property. Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. related 4.2.4.4 Relations; a) Reciprocal Relationship − Associative relationship RT/RT between two descriptors. 01 --- added irreflexive for eurovoc S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S19 The rdfs:domain of skos:semanticRelation is the class skos:Concept. S21 skos:broaderTransitive, skos:narrowerTransitive and skos:related are each sub-properties of skos:semanticRelation. S23 skos:related is an instance of owl:SymmetricProperty. S27 skos:related is disjoint with the property skos:broaderTransitive. May need to be inferred on import based on symmetric property. related match S37 skos:mappingRelation, skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each instances of owl:ObjectProperty. S40 skos:closeMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch are each sub-properties of skos:mappingRelation. S41 skos:broadMatch is a sub-property of skos:broader, skos:narrowMatch is a sub-property of skos:narrower, and skos:relatedMatch is a sub-property of skos:related. S44 skos:relatedMatch is an instance of owl:SymmetricProperty. scope note Needs to refer to a blank rdf note that must hold - ev:language - ev:noteLiteral must be indexed if subject is - ThesaurusTerm - ThesaurusConcept S16 skos:note, skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each instances of owl:AnnotationProperty. S17 skos:changeNote, skos:definition, skos:editorialNote, skos:example, skos:historyNote and skos:scopeNote are each sub-properties of skos:note. semantic relation May be calculated and stored for indexing, based on - skos:broader - skos:narrower - skos:related S18 skos:semanticRelation, skos:broader, skos:narrower, skos:related, skos:broaderTransitive and skos:narrowerTransitive are each instances of owl:ObjectProperty. S19 The rdfs:domain of skos:semanticRelation is the class skos:Concept. S20 The rdfs:range of skos:semanticRelation is the class skos:Concept. top concept of S3 skos:inScheme, skos:hasTopConcept and skos:topConceptOf are each instances of owl:ObjectProperty. S7 skos:topConceptOf is a sub-property of skos:inScheme. S8 skos:topConceptOf is the owl:inverseOf the property skos:hasTopConcept. alternative label resource CONSTRUCT ?subject skos:altLabel ?label WHERE { ?subject skosxl:altLabel ?xlLabel . ?xlLabel skosxl:literalForm ?label } May be entailed from - ev:EquivalenceRelationship - ev:CompoundEquivalence CONSTRUCT ?c xl:altLabel ?label WHERE ?eqr rdf:type ev:EquivalenceRelationship . ?eqr ev:UF ?label ?eqr ev:USE ?pt ?c xl:prefLabel ?pt CONSTRUCT ?c xl:altLabel ?label WHERE ?eqr rdf:type ev:CompoundEquivalence . ?eqr ev:compoundNonPreferredTerm ?label ?eqr ev:preferredTermComponent ?pt ?c xl:prefLabel ?pt S54 skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel are each instances of owl:ObjectProperty. S55 The rdfs:range of each of skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel is the class skosxl:Label. S57 The property chain (skosxl:altLabel, skosxl:literalForm) is a sub-property of skos:altLabel. hidden label resource CONSTRUCT { ?subject skos:hiddenLabel ?label } WHERE { ?subject skosxl:hiddenLabel ?xlLabel . ?xlLabel skosxl:literalForm ?label } S54 skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel are each instances of owl:ObjectProperty. S55 The rdfs:range of each of skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel is the class skosxl:Label. S58 The property chain (skosxl:hiddenLabel, skosxl:literalForm) is a sub-property of skos:hiddenLabel. CONSTRUCT { ?subject skos:hiddenLabel ?label } WHERE { ?subject xl:hiddenLabel ?xlLabel . ?xlLabel xl:literalForm ?label } label relation S59 skosxl:labelRelation is an instance of owl:ObjectProperty. S60 The rdfs:domain of skosxl:labelRelation is the class skosxl:Label. S61 The rdfs:range of skosxl:labelRelation is the class skosxl:Label. S62 skosxl:labelRelation is an instance of owl:SymmetricProperty. preferred label resource A preferred term may not be available for each thesaurus languages. - No PT are generated automatically by TMS - The portal import procedure must detect missing PT based on the value set generated by ev:supportsLanguage The import will generate a label as a blank node - the xl:literalForm is the empty string - the ev:toBeTranslated wil be set to <English PT> + ' (to be translated)' - Some terms may have a PT label and the property ev:toBeTranslated these will be shown as ev:literalForm + ' (' + ev:toBeTranslated + ')' S54 skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel are each instances of owl:ObjectProperty. S55 The rdfs:range of each of skosxl:prefLabel, skosxl:altLabel and skosxl:hiddenLabel is the class skosxl:Label. S56 The property chain (skosxl:prefLabel, skosxl:literalForm) is a sub-property of skos:prefLabel. CONSTRUCT { ?resource skos:prefLabel ?label } WHERE { ?resource skosxl:prefLabel ?xlLabel . ?xlLabel skosxl:literalForm ?label } The managed label of the subject resource. A managed label entails a simple skos"prefLabel. The property is implicitly constrained by skos:prefLabel. approved for release 4.2.7.12 List of approved descriptors 01 --- The value provides the expected release in which the concept will be released.. The value is a release typically is just the release number. No other text shall be provided. From the maintenance environement. EUR-Lex reference 4.2.4.3 Attributes b) EDITORIAL ATTRIBUTES EUR-Lex --- Direct link to Official Journal documents in the EUR-Lex database (See http://eur-lex.europa.eu/ ). Typically such links are embedded in scope notes or in definition (using the rel attribute according the RDFa standard). Usage of links in notes (Scope note, History note, definition) - all these notes can have XMLLiteral values with mark-up that appears in the xhtml mark up the namespace of this mark-up is http://www.w3.org/1999/xhtml and must be declared and used. XHTML must be compliant to version="XHTML+RDFa 1.0" the content will NOT include the xhtml:body element, only its content (plain text, <xhtml:div>, ...) - in all notes, href references may refer to: dp: ev:eurLexReference (ref to eurLex web site) example: <xhtml:a rel="ev:eurLexReference" href="http://.....">xyz</xhtml:a> export date 4.2.7.5 Search engine b) Additional search features 01 --- Date and time at which the thesaurus is published. Allows to check proper sequencing of loading. export version 4.2.7.4 Term display 04 --- the version identification of the published thesaurus (allows to recognize terms released with current version) has poly hierarchy 4.2.4.5 Polyhierarchy 01, 02 Indicates that a concept scheme supports poly-hierarchy. By default 'false' true indicates this is a realease including the terms and concepts that were approved in the maintenace workspoce. Not present or false means this is a full release of the "stable" version only of the TMS. ISO country code 4.2.4.4 Relations b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 04 --- 1) A country code is by default a UF of all PT of its concepts The country code has no language language 4.2.4.6 Language equivalence b) ATTRIBUTES − Text attributes such as scope notes, editorial notes or history notes are language specific. May be used to identify a language on a resource. Typically used to provide the language on a note which may be an object, or an XML literal note text xhtml:xhtml.body.type Embedded hyperlinks need to be parsed and validated on import. Content needs to be XHTML validated on import. An xml literal taking a plain text or an xhtml data type permuted literal form 4.2.6.18 Publishing b) GENERATION OF PERMUTATED ENTRIES 01 c) PDF FILES 01 4.2.7.9 Download section 01 --- CONVENTION Is different from the literal form of the label. Provides a permuted search string for the label Must be in the same language as the literal form of the label. The following SPARQL query should have an empty result list SELECT lang(?nPT) WHERE { ?label rdf:type xl:Label . ?label xl:literalForm ?lit . ?label xl:permutedLiteralForm ?permLit . FILTER ( lang(?lit) != lang(?permLit) ) } qualifier Label qualifier discriminating the xl:Label from other homographs in a specific language. The language of the qualifier is implied by the language of the xl:literalForm on the xl:Label in the domain. CONVENTION For eurovoc, the qualifier is part of the literal form of the label (appended between parenthesis. relevant URL 4.2.4.3 Attributes b) EDITORIAL ATTRIBUTES URL --- Traversable reference to relevant web sites relating to the concept or term. Usage of links in notes (Scope note, History note, definition) - all these notes can have XMLLiteral values with mark-up that appears in the xhtml mark up the namespace of this mark-up is http://www.w3.org/1999/xhtml and must be declared and used. XHTML must be compliant to version="XHTML+RDFa 1.0" the content will NOT include the xhtml:body element, only its content (plain text, <xhtml:div>, ...) - in all notes, href references may refer to: dp: ev:relevantURL (ref to any website) example: <xhtml:a rel="ev:relevantURL" href="http://xyz.com/xyz.html">xyz</xhtml:a> status 4.2.4.3 Attributes c) WORKFLOW ATTRIBUTES Translation --- The position or state of the resource with respect to the EUROVOC workflow. Three states are relevant for EUROVOC - valid: for released terms and concepts - to be translated: A term requiring further translation look at ev:toBeTranslated to find the outstanding translations - in maintenance: a concept or term in maintenance. look at ev:approvedForRelease to know for which version the approval holds. valid is the default status. (rejected and pending is not relevant for display on the portal) May need to be added on note also in maintenance to be translated valid term release version 4.2.7.4 Term display 04 4.2.7.5 Search engine b) Additional search features 01 --- The eurovoc release number in which the term was added. a fixed string 'n/a' if the historic release number is not available. to be translated 4.2.4.3 Attributes c) WORKFLOW ATTRIBUTES Translation 4.2.7.4 Term display 05 --- The range value must have - language (the language for which translatioin is required) - for a term this must be the language of the term - for a microthesaurus or domain this may be a comma seperated list of languages. The format is: <lang> [ ,'<lamg> ]* Identifier 4.2.4.6 Language equivalence a) Classes, − Each domain, microthesaurus or descriptor has a unique equivalent (same ID number) in each language. An unambiguous reference to the resource within a given context established by an identifying authority.. Date Created 4.2.4.3 Attributes b) EDITORIAL ATTRIBUTES Creation Date Date of creation of the resource. Date Modified 4.2.4.3 Attributes b) EDITORIAL ATTRIBUTES Updated Date Date on which the resource was changed. alternative label May entail (not required) CONSTRUCT { ?subject skos:altLabel ?label } WHERE { ?subject xl:altLabel ?xlLabel . ?xlLabel xl:literalForm ?label } Depends on construction of xl:altLabel S10 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each instances of owl:AnnotationProperty. S11 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each subproperties of rdfs:label. S12 The rdfs:range of each of skos:prefLabel, skos:altLabel and skos:hiddenLabel is the class of RDF plain literals. S13 skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. any type of resource may be labelled Constraints: - range must be a plain literal hidden label May be entailed based on property chain described in xl:hiddenLabel. The "hidden" labels are useful when a user is interacting with a knowledge organization system via a text-based search function. The user may, for example, enter mis-spelled words when trying to find a relevant concept. If the mis-spelled query can be matched against a "hidden" label, the user will be able to find the relevant concept, but the "hidden" label won't otherwise be visible to the user (so further mistakes aren't encouraged). S10 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each instances of owl:AnnotationProperty. S11 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each subproperties of rdfs:label. S12 The rdfs:range of each of skos:prefLabel, skos:altLabel and skos:hiddenLabel is the class of RDF plain literals. S13 skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. any type of resource may be labelled Constraints: - range must be a plain literal notation A notaion is a typed literal i.e. either of: - rdf:datatype - rdf:XMLLiteral In 1 concept scheme, no 2 concepts should have the same natation S15 skos:notation is an instance of owl:DatatypeProperty. --- not used in eurovoc preferred label May be entailed for concepts based on property chain of xl:prefLabel S10 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each instances of owl:AnnotationProperty. S11 skos:prefLabel, skos:altLabel and skos:hiddenLabel are each subproperties of rdfs:label. S12 The rdfs:range of each of skos:prefLabel, skos:altLabel and skos:hiddenLabel is the class of RDF plain literals. S13 skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties. S14 A resource has no more than one value of skos:prefLabel per language. Should be constrained to allow at most one value per language for each labeled resource. The following SPARQL query should have an empty result list SELECT ?resource ?label1 ?label2 WHERE { ?resource skos:prefLabel ?label1 , ?label2 . FILTER ( ?label1 != ?label2 && lang(?label1) = lang(?label2) ) } any type of resource may be labelled Constraints: - range must be a plain literal - A resource has no more than one value of skos:prefLabel per language tag literal form CONVENTION - typically uses xml:lang S50 skosxl:literalForm is an instance of owl:DatatypeProperty. S51 The rdfs:domain of skosxl:literalForm is the class skosxl:Label. S52 The rdfs:range of skosxl:literalForm is the class of RDF plain literals. models ev lexicalValue The range must be a plain literal. compound equivalence 2 1 1) Check that the related terms have the same langues 2) Make the compound-non-PT a UF+ of all of the PT concepts 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 b) CUSTOMIZED RECIPROCAL RELATIONSHIPS 03 ---- An association establishing the relationship between one compound non preferred term and its component terms. The component terms must be preferred terms. All terms in the relationship must have the same language. The following SPARQL query should have an empty result list SELECT lang(?nPT) WHERE { ?rel rdf:type ev:CompoundEquivalence . ?rel ev:preferredTermComponent ?PT . ?rel ev:compoundNonPreferredTerm ?nPT . FILTER ( lang(?PT) != lang(?nPT) ) } When the compound non preferred term is an xl:altLabel of an ev:ThesaurusConcept, then exactly one of the preffered terms must be an xl:prefLabel of that concept. When a preferred term (of the relationship) is the xl:prefLabel of an ev:ThesaurusConcept, then the compound non preferred term must be an xl:altLabel of that concept. compound non preferred term A compound non preferred term that is composed of two or more preferred terms. The relationship between the compound term and its components must be established by an ev:CompoundEquivalence relationship. country 1 A eurovoc (thesaurus) concept representing a country. A country is a thesaurus concept having one ISO country code Occasionally the code may not be known yet domain 1 Specification - 4.2.4.2, 4.2.4.3.Domain May be modelled as - a dedicated class (not chosen because a collection is supposed to contain concepts) - a Collection (not chosen because the collection only contains microthesauri, not concepts) The name of a domain is an skos prefLabel. There must be one label per supported language The (heading) label is implicitly constrained by skos:prefLabel. The identifier is in property dc:identifier equivalence relationship 1 1 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 --- The language rule of an equivalence relationship is not always followed. In particular if - there is an acronym (say "a") is defined as the xl:Label instance - and there is an xl:Label instance (say "s") such that "a" is an acronym of s (i.e.: s ev:acronym a). - and there is oa concept (say "C") sucht that C xl:prefLabel s or C xl:altLabel "s" then - a is a synonym (xl:altLabel) of C for lang(s), irespective of the value of lang(a). An association establishing the relationship between a preferred term and a simple non preferred term. All terms in the relationship must have the same language (see import rule for acronyms). The following SPARQL query should have an empty result list SELECT lang(?nPT) WHERE { ?rel rdf:type ev:EquivalenceRelationship . ?rel ev:USE ?PT . ?rel ev:UF ?nPT . FILTER ( lang(?PT) != lang(?nPT) ) } When the preferred term in this relationship is the xl:prefLabel of an ev:ThesaurusConcept, then the simple none preferred term must be an xl:altLabel of that concept. When the non preferred term is the xl:altLabel of an ev:ThesaurusConcept then the preferred term must be an xl:prefLabel of that concept last thesaurus export 1 1 1 A utility class capturing the publication characteristics of the ev:exportedThesaurus. language 1 System description of language. Each language is - labeled using skos:prefLabel (and skos:altLabel) in all of the other languages and - identified using a ev:language to identify iso 2-char language code. The class provides the set of languages that maybe in use in the thesaurus. The ev:Thesaurus identifies the languages actually used via its property ev:supportedLanguage. The label is implicitly constrained by skos:prefLabel microthesaurus 1 --- May be modelled - either as a concept scheme, giving all the thesaurus semantics (= the chosen approach) - or as a Collection (giving less thesaurus semantics) A group of concepts of a thesaurus. This group of concept complies to a thesaurus structure on itself. The name of a micro thesaurus is a skos prefLabel. There must be one label per language The label is implicitly constrained by skos:prefLabel. preferred term A preferred term. Such a term shall be the object of an xl:prefLabel property of an ev:ThesaurusConcept. simple non preferred term A non preferred term that is the equivalent of (one or more) preferred term/s. The relationship between the non preferred term and a preferred term must be established by an ev:EquivalenceRelationship. thesaurus 1 A published EUROVOC thesaurus. The publication characteristics are given by the property ev:exportedThesaurus (ev:Export -> ev:Thesaurus). An exported thesaurus is always the consolidated version of the thesaurus. The concepts in that thesaurus represent the consolidated version of that concept. Hence, plain rdf merge of 2 versions will give ambiguous results. Merginging is in any case a non sensical operation. Two exports may be compared to make a thesaurus update report. thesaurus concept 1 4.2.4.2 Classes − Descriptor The concept represented by a EUROVOC descriptor. It is a sub-class of a skos:Concept. thesaurus term 4.2.4.3 Attributes a) SPECIFIC ATTRIBUTES − Descriptor/non-descriptor (TERM) 4.2.4.4 Relations a) RECIPROCAL RELATIONSHIPS − Equivalence relationship USE/UF between a descriptor and a non-descriptor; 01 --- A EUROVOC term or label. All eurovoc relations are expressed between thesaurus terms. Terms may be preferred or non preferred Non preferred terms may be simple or compound. collection A labeled collection of concepts. S28 skos:Collection and skos:OrderedCollection are each instances of owl:Class. S29 skos:OrderedCollection is a sub-class of skos:Collection. S36 skos:Collection is disjoint with each of skos:Concept and skos:ConceptScheme. SKOS concept collections are labeled groups of SKOS concepts. Collections are useful where a group of concepts shares something in common, and it is convenient to group them under a common label. Concept An instance of skos:Concept may also be an instance of - owl:Class - owl:Property S1 skos:Concept is an instance of owl:Class. concept scheme An ontology may be a SKOS concept scheme S2 skos:ConceptScheme is an instance of owl:Class. S9 skos:ConceptScheme is disjoint with skos:Concept. ordered collection A labelled collection of ordered concepts. Ordered SKOS concept collections are labeled and ordered groups of SKOS concepts. Ordered collections are useful where a group of concepts shares something in common, and it is convenient to group them under a common label and place them in a meaningful order. The entailment between an ordered collection and a collection is detailed under skos:memberList. label resource 1 S48 skosxl:Label is an instance of owl:Class. S49 skosxl:Label is disjoint with each of skos:Concept, skos:ConceptScheme and skos:Collection. S53 skosxl:Label is a sub-class of a restriction on skosxl:literalForm cardinality exactly 1. memberschip of a label <L> in a concspt scheme <CS> may be asserted: - <S> skos:inScheme <CS>