Based on ISO 25964 - mapping between the UML model in the ISO standard and the SKOS schema. Not modelled but requiring further extension: - CustomTermAttribute : Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType. - CustomConceptAttribute : Best practice would be to define custom RDF data-type properties taking plain literal values. The property name depends on the customAttributeType. - refersTo (reference from within a note to a concept or label/term: May be an embedded and tagged link in the note value (e.g., as done for EuroVoc). - CustomNote : depending noteType a new custom property should be defined as a sub-property of skos:note (consider applicability of: skos:changeNote and skos:example)
Contributor
A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
An entity responsible for making contributions to the resource.
Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
Coverage
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Creator
An entity primarily responsible for making the resource.
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
Date
A point or period of time associated with an event in the lifecycle of the resource.
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
Description
An account of the resource.
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Format
Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME].
The file format, physical medium, or dimensions of the resource.
Identifier
An unambiguous reference to the resource within a given context.
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
Language
A language of the resource.
Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].
Publisher
An entity responsible for making the resource available.
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Relation
A related resource.
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Source
A related resource from which the described resource is derived.
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Subject
The topic of the resource.
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element.
Title
A name given to the resource.
Type
Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
The nature or genre of the resource.
Conforms To
An established standard to which the described resource conforms.
Examples of a Contributor include a person, an organization, or a service.
Date Created
Date of creation of the resource.
Examples of a Creator include a person, an organization, or a service.
Extent
The size or duration of the resource.
Has Format
A related resource that is substantially the same as the pre-existing described resource, but in another format.
This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.
Has Part
A related resource that is included either physically or logically in the described resource.
Has Version
A related resource that is a version, edition, or adaptation of the described resource.
Is Format Of
A related resource that is substantially the same as the described resource, but in another format.
Is Part Of
A related resource in which the described resource is physically or logically included.
Is Referenced By
A related resource that references, cites, or otherwise points to the described resource.
Is Replaced By
A related resource that supplants, displaces, or supersedes the described resource.
Is Required By
A related resource that requires the described resource to support its function, delivery, or coherence.
Is Version Of
A related resource of which the described resource is a version, edition, or adaptation.
Changes in version imply substantive changes in content rather than differences in format.
Date Issued
Date of formal issuance (e.g., publication) of the resource.
Medium
The material or physical carrier of the resource.
Date Modified
Date on which the resource was changed.
Examples of a Publisher include a person, an organization, or a service.
References
A related resource that is referenced, cited, or otherwise pointed to by the described resource.
Replaces
A related resource that is supplanted, displaced, or superseded by the described resource.
Requires
A related resource that is required by the described resource to support its function, delivery, or coherence.
ISO hasConceptGroupLabel (of ConceptGroup) Other optional attributes or associations not detailed below typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified These can be attached (if needed) to the rdfs:label using owl:Axiom annotations
ISO hasNodeLabel (of Thesaurus Array) Other optional attributes or associations not detailed below typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified These can be attached (if needed) to the rdfs:label using owl:Axiom annotations
In ISO 25964, "hasDefinition" applies to a term rather than to a concept.
In ISO 25964, "hasEditorialNote" applies to a term rather than to a concept.
ISO refersTo is not mapped. Work is ongoing in the RDF group to type the content explicitly as HTML or XML In RDF1.1 (http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-html). This would allow embedding relevant hyperlinks in notes. May be an embedded and tagged link in the note value (e.g., as done for EuroVoc).
In ISO 25964, some types of Note are associated with concepts, others with terms. In SKOS, all documentation notes are associated with concepts. In basic SKOS, notes are represented using simple annotation properties, which type captures the note type. However the SKOS annotation properties can also be used with structured representation of notes as fully-fledged resources. See http://www.w3.org/TR/skos-primer/#secdocumentation and http://www.w3.org/TR/skos-primer/#secadvanceddocumentation for examples of both approaches. Within a thesaurus the application of notes to concept and term is more restrictive than in SKOS. A note may be a structure. In general, this can be modelled using rdf:value (to represent lexicalValue) The language should be held in rdf:value. If this is an XMLLiteral, the language shall also be made available using dc:language (or dct:language). Note: Work is ongoing in the RDF group to type the content explicitly as HTML or XML In RDF1.1 (http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-html). This would allow embedding relevant hyperlinks in notes. Additional attributes can be added to the note structure: - dct:created - dct:modified
In ISO 25964, "hasScopeNote" applies to a concept.
The inverse of this property is a sub-property of skos:member. The related skos:Concept (domain) and iso-thes:ConceptGroup (range) are in the same ConceptScheme.
ISO 25964-1: UF+ The non preferred term labeling a complex concept. The complex concept will be identified by splitting the non preferred term into 2 or more (component) preferred terms.
ISO 25964-1: UF+ The non-preferred term taging a compount concept that should be represented by a combination of preferred terms
ISO 25964-1: USE+ One of two or more (component) preferred terms used together to represent the (complex) concept labeled by a (split) non preferred term.
ISO 25964-1: USE+ The two or more (component) preferred terms following should be used together to represent the concept indicated by the (split) non preferred term.
iso-thes:plusUseTerm (and its inverse iso-thes:plusUFTerm) may be derived from iso-thes:CompoundEquivalence. For a iso-thes:CompoundEquivalence instance each derived iso thes:plusUseTerm has as: - subject: the iso thes:plusUF value - object: the iso thes:plusUse value In special cases where the iso thes:SplitNonPreferredTerm has more than one decomposition, the inverse inference may not be possible.
skos:altLabel is a super property of the chain iso-thes:splitAltLabel o skos-xl:literalForm If C iso-thes:splitAltLabel L and L skos-xl:literalForm V, then X skos:altLabel V.
All members of the (object) subGroup are members of the (subject) group.
Explicitly links a concept to one or more subordinate arrays. Each array may either be composed of narrower concepts (using a characteristic division) or by concepts that need not be narrower terms (facet organization). I.e. Though each array only contains sibling concepts, no hierarchical relation may be derived between a Concept and the the Concepts in any of its subordinte Arrays.
All members of the (subject) group are members of the (subject) superGroup.
ISO 35964: hasSuperOrdinateConcept The subject array organizes the a set of sibling concepts under the (object) concept.
Super property of ISO isPartOf Applies to any ISO 25964 "isPartOf" relation that targets the Thesaurus. Subjects of the skos:inScheme statements can be ISO 25964’s ThesaurusConcept, ConceptGroup, and ThesaurusArray. Only applies to ISO 25964 "contains" statements having a Thesaurus [ConceptScheme] as subject.
ISO status - on ThesaurusConcept - on ThesaurusTerm
Agent
A resource that acts or has the power to act.
Examples of Agent include person, organization, and software agent.
Agent Class
A group of agents.
Examples of Agent Class include groups seen as classes, such as students, women, charities, lecturers.
File Format
A digital resource format.
Examples include the formats defined by the list of Internet Media Types.
Linguistic System
A system of signs, symbols, sounds, gestures, or rules used in communication.
Examples include written, spoken, sign, and computer languages.
Location
A spatial region or named place.
Location, Period, or Jurisdiction
A location, period of time, or jurisdiction.
Media Type
A file format or physical medium.
Media Type or Extent
A media type or extent.
Period of Time
An interval of time that is named or defined by its start and end dates.
Physical Medium
A physical material or carrier.
Examples include paper, canvas, or DVD.
Size or Duration
A dimension or extent, or a time taken to play or execute.
Examples include a number of pages, a specification of length, width, and breadth, or a period in hours, minutes, and seconds.
Standard
A basis for comparison; a reference point against which other things can be evaluated.
ISO CompoundEquivalence iso-thes:plusUseTerm (and its inverse iso-thes:plusUFTerm) may be derived from iso-thes:CompoundEquivalence. For a iso-thes:CompoundEquivalence instance each derived iso thes:plusUseTerm has as: - subject: the iso thes:plusUF value - object: the iso thes:plusUse value In special cases where the iso thes:SplitNonPreferredTerm has more than one decomposition, the inverse inference may not be possible.
Concept groups have several applications. One such application is illustrated by the EUROVOC and the UNESCO thesaurus. Both of these use a super structure of Domain and MicroThesaurus. Bothe of these structuring elements can be moddeled using Concept Group.
Concept groups typically are constructed based on properties of the concepts. A complete overview is not in the scope of this mapping. In practice, a second thesaurus or classification system is sometimes used to tag the concepts of the thesaurus. Use rdfs:label for the ConceptGroup label. Optional label attributes typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified These can be attached (if needed) to the rdfs:label using owl:Axiom annotations. Depending on the value of the ISO conceptGroupType a sub-class of iso thes:ConceptGroup should be defined. e.g.: EUROVOC and UNESCO use - Domain - MicroThesaurus (an iso-thes:hasSubGroup of a Domain)
ISO PreferredTerm Instances of iso-thes:PreferredTerm are objects of skos xl:prefLabel statements. Making the class explicit allows RDF/OWL consistency checks for CompoundEquivalence.
Relation to ISO Equivalence In SKOS/-XL, Equivalence may be derived between the skos/skos xl:prefLabel statements on one hand and the skos/skos xl:altLabel or the skos/skos xl:hiddenLabel statements on the other hand where: - the subject of all these statements is the same instance of skos:Concept, - the language of all the bound labels is the same, - the prefLabel has the role USE, and - the altLabel and hiddenLabel have the role UF.
ISO SimpleNonPreferredTerm Instances of iso:SimpleNonPreferredTerm are object of either of skos xl:altLabel or skos xl:hiddenLabel statements.
iso SplitNonPreferredTerm The term represents some 'virtual' concept, distinct from the 'real' ThesaurusConcept in the thesaurus (Concept-Scheme). This label is provided by the object property iso thes:splitAltLabel - domain: skos:Concept (optional) - range: iso-thes:SplitNonPreferredTerm skos:altLabel is a super property of the chain iso-thes:splitAltLabel o skos-xl:literalForm Making the class explicit allows RDF/OWL consistency checks for CompoundEquivalence (detailed below).
ISO ThesaurusArray Instances of ThesaurusArray should be instances of skos:OrderedCollection (a subclass of skos:Collection) if the the array needs to be an ordered array (in ISO-25964 model: value of the its Boolean attribute "ordered" is true). Concepts in a thesaurus array are sibling concepts in the thesaurus. The node label(s) of a thesaurus array are mapped to rdfs:label. Optional node label attributes typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified These can be attached (if needed) to the rdfs:label using owl:Axiom annotations
super class of ISO ThesaurusConcept The mandatory attribute identifier may be mapped to the Dublin Core property dc:identifier. Attributes or associations not detailed below typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified
super class of ISO Thesaurus The mandatory attribute identifier may be mapped to the Dublin Core property dc:identifier. A typical representation of a thesaurus should document a (scoped) relationship between an identifier of this thesaurus and the URI of the RDF Concept Scheme URI. The mandatory attribute lang can be mapped to either of the Dublin Core properties dc:language or dct:language. The value space is defined by RFC 4646. For multilingual thesaurus, one lang attribute is needed per supported language. Typically these can be mapped to the corresponding Dublin Core dc: (or dct:) properties: - dc:contributor - dc:coverage - dc:creator - dct:created - dct:modified - dc:date - dc:description - dc:format - dc:publisher - dc:relation, dct:relation or a specialization - dc:rights - dc:source - dc:subject - dc:title - dc:type The association "hasVersion" is discussed in VersionHistory.
Super class of ISO ThesaurusTerm. A ThesaurusTerm has mandatory attributes lexicalValue and identifier. lexicalValue can be mapped to skos xl:literalForm. The value of identifier can be used as the URI of the skos xl:Label or as the object of a dc:identifier statement on that skos-xl:Label. The optional ISO25964 lang attribute of ThesaurusTerm must be mapped to RDF language tag for RDF plain literals. Attributes or associations not detailed below typically are mapped to dc: (or dct:) properties: - dct:created - dct:modified - dc:source
Simple super property of ISO hasPreferredLabel Basic SKOS allows labels (as simple literals) to be attached directly to Concepts using skos:prefLabel; this is the preferred simple scenario where label relations are not explicit.
Complex super property of ISO hasNonPreferredLabel Applies if the value of "hasNonPreferredLabel" is of class SimpleNonPreferredTerm with the Boolean attribute "hidden" either absent or with value false.
As an extension to SKOS, sub-properties of skos:related may be needed to model the different associative relationships identified by the ISO 25964 attribute "role".
Can be used to derive ISO isTopConceptOf (which is different from skos:isTopConceptOf). The ISO isTopConceptOf can be derived in SKOS from skos:narrowerTransitive where the skos:narrowerTransitive has as subject a concept that is object of a skos:hasTopConcept statement (i.e., a ThesaurusConcept having topConcept = true).
Simple or basic super property of ISO hasNonPreferredLabel Applies if the value of "hasNonPreferredLabel" is of class SimpleNonPreferredTerm with the Boolean attribute "hidden" either absent or with value false.
Can be used to derive ISO hasTopConcept (which is different from skos:hasTopConcept). The ISO hasTopConcept can be derived in SKOS from skos:broaderTransitive where the object of skos:broaderTransitive is a concept having the property skos:topConceptOf (i.e., a ThesaurusConcept having topConcept = true).
As an extension to SKOS, sub-properties of skos:broader and skos:narrower may be needed to model the different hierarchical relationships identified by the ISO 25964 attribute "role" (e.g., BTP/NTP, BTI/NTI, BTG/NTG).
Captures ISO TopLevelRelationship
Super property of ISO isPartOf of a ThesaurusConcept having its attribute topConcept = true. Captures ISO TopLevelRelationship
ISO - hasMemberArray<ordered=true> - hasMemberConcept<ordered=true>
Best practice in SKOS is to (RDF) type the notation value object. This allows multiple notation value types for the same concept or term to be distinguished. Note: In ISO 25964-1, such typing is implicit in the thesaurus or it is part of the "notation" value.
Complex super property of ISO hasPreferredLabel When a label is represented as skos xl:Label, a skos:prefLabel statement is derived from the skos-xl:prefLabel one. (Likewise for altLabel and hiddenLabel.)
In ISO 25964, "hasHistoryNote" can apply to a term or to a concept.
Complex super property of ISO hasNonPreferredLabel Applies if the value of "hasNonPreferredLabel" is of class SimpleNonPreferredTerm with the Boolean attribute "hidden" having value true.
Rules: - skos:altLabel is a super property of the chain: iso-thes:splitAltLabel o skos-xl:literalForm
Simple or basic super property of ISO hasNonPreferredLabel Applies if the value of "hasNonPreferredLabel" is of class SimpleNonPreferredTerm with the Boolean attribute "hidden" having value true.
ISO - hasMemberArray<ordered=false> - hasMemberConcept<ordered=false> - hasAsMember By definition, used to represent members of a thesaurus Array or of a thesaurus Group. An Array may have as members thesaurus Concepts or other thesaurus Arrays. Thesaurus Group members are thesaurus Concepts.