legalthesaurus.org

Mapping SKOS and ISO 25964

IRI:
http://purl.org/iso25964/skos-thes
Date:
2015-03-17
Imported Ontologies:
http://www.w3.org/2004/02/skos/core (visualise it with LODE)
http://www.w3.org/2008/05/skos-xl (visualise it with LODE)
Other visualisation:
Ontology source

Abstract

These notes apply to the published mapping between the ISO 25964 data model and the SKOS schema (http://www.niso.org/schemas/iso25964/correspondencesSKOS/).

Remarks can be exchanged using: 25964info@list.niso.org

Subscription info and archive is on: http://www.niso.org/lists/25964info/

General information about ISO 25964: http://www.niso.org/schemas/iso25964/
The annotation http://www.w3.org/2003/06/sw-vocab-status/ns#term_status indicates “proposed” properties that are not part of the mapping documentation.

Todo:

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 http://eurovoc.europa.eu/).

– 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)

– BTG/NTG – BTP/NTP – BTI/NTI :
Currently these are only defined as direct (one-step) sub-properties of skos:broader / skos:narrower.

Some constraints currently expressed only in natural language (in rdfs:comment) may be formally expressed as OWL(2) axioms.

We have postponed the implementation of the iso-thes properties mentioned in the VersionHistory section of the mapping documentation.

Classes

Compound Equivalencecback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#CompoundEquivalence

is defined by
http://purl.org/iso25964/skos-thes

Comment

ISO CompoundEquivalence

iso-thes:plusUseTerm (and its inverse iso-thes:plusUFTerm) may be derived from iso-thes:CompoundEquivalence.

For an iso-thes:CompoundEquivalence instance each derived iso-thes:plusUseTerm has as:
– subject: the iso-thes:plusUF value
– object: the iso-thes:plusUse value

An ISO 25964 compliant thesaurus only has one compound equivalence relation for each split non preferred term.

In special cases where the iso-thes:SplitNonPreferredTerm has more than one decomposition, the inverse inference may not be possible. (While this situation should not arise within a single thesaurus that complies with ISO 25964, it could occur if terms and relationships have been drawn from more than one thesaurus. For this reason the property skos:inScheme (http://www.w3.org/2004/02/skos/core#inScheme) should be used with each instance of the class Compound Equivalence, to relate it to its Thesaurus.)

has super-classes
component preferred term op min 2 Preferred Term c
split non preferred term op exactly 1 Split Non Preferred Term c
is in domain of
component preferred term op, split non preferred term op

Concept Groupcback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#ConceptGroup

is defined by
http://purl.org/iso25964/skos-thes

Comment

ISO ConceptGroup

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 micro-thesaurus. Both of these structuring elements can be modeled using ConceptGroup.

Definition

A concept group is a group of concepts making up a subset of the thesaurus. Member concepts may be drawn from many different facets or hierarchies of the thesaurus. While almost any criterion may be used to select the members, this construct is commonly used to define a micro-thesaurus that will be used by a particular user group or domain.

The skos:inScheme (http://www.w3.org/2004/02/skos/core#inScheme) property should be used to indicate the thesaurus to which an instance of skos:Collection applies (see ISO 25964: isPartOf).

Use rdfs:label or xl:prefLabel for the ConceptGroup label (1 per language).
Optional label attributes typically are mapped to dc: (or dct:) properties:
– dct:created
– dct:modified
These can be attached to the xl:Label instance that is the value of the xl:prefLabel.

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)

has super-classes
skos:Collection
is in domain of
micro-thesaurus of op, sub group op, super group op
is in range of
sub group op, super group op
is disjoint with
Thesaurus Array c

Preferred Termcback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#PreferredTerm

is defined by
http://purl.org/iso25964/skos-thes

Comment

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.

has super-classes
xl:Label c
is in range of
USE+ op, component preferred term op
is disjoint with
Simple Non Preferred Term c, Split Non Preferred Term c

Simple Non Preferred Termcback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#SimpleNonPreferredTerm

is defined by
http://purl.org/iso25964/skos-thes

Comment

ISO SimpleNonPreferredTerm

Instances of iso:SimpleNonPreferredTerm are the object of either of skos xl:altLabel or skos xl:hiddenLabel statements.

Identifying cases of 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.

has super-classes
xl:Label c
is disjoint with
Preferred Term c, Split Non Preferred Term c

Split Non Preferred Termcback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#SplitNonPreferredTerm

is defined by
http://purl.org/iso25964/skos-thes

Comment

iso SplitNonPreferredTerm

This class provides for an ‘imagined’ concept that may exist in a user’s mind but is not present in the thesaurus (Concept Scheme); it can, however, be represented by a combination of two or more preferred terms (skos-xl:prefLabel) in the thesaurus. (In contrast, concepts present in the thesaurus are provided for by the ThesaurusConcept class.)
This label is provided by the object property iso-thes:plusUF
– domain: iso-thes:CompoundEquivalence
– range: iso-thes:SplitNonPreferredTerm

has super-classes
xl:Label c
is in domain of
USE+ op
is in range of
split non preferred term op
is disjoint with
Preferred Term c, Simple Non Preferred Term c

Thesaurus Arraycback to ToC or Class ToC

IRI: http://purl.org/iso25964/skos-thes#ThesaurusArray

is defined by
http://purl.org/iso25964/skos-thes

Definition

Definition: ISO ThesaurusArray

An array is a group of sibling concepts

Instances of ThesaurusArray can be mapped to instances of skos:OrderedCollection (a subclass of skos:Collection) if and only if the array needs to be an ordered array (in the ISO-25964 model the value of its Boolean attribute “ordered” is true).
It is advised to use the skos:inScheme (http://www.w3.org/2004/02/skos/core#inScheme) property on such a skos:Collection to relate it to its Thesaurus (see ISO 25964: isPartOf).

Concepts in a thesaurus array are sibling concepts in the thesaurus.
If present, the node label (1 per language) of a thesaurus array is mapped to rdfs:label or xl:prefLabel.
Optional node label attributes typically are mapped to dc: (or dct:) properties:
– dct:created
– dct:modified
These can be attached (if needed) to the xl:Label instance that is the value of xl:prefLabel.

has super-classes
skos:Collection
is in range of
subordinate array op
is disjoint with
Concept Group c

Re-used Classes

skos:Conceptcback to ToC or Re-used Class ToC

IRI: http://www.w3.org/2004/02/skos/core#Concept

Comment

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

is in domain of
subordinate array op

skos:ConceptSchemecback to ToC or Re-used Class ToC

IRI: http://www.w3.org/2004/02/skos/core#ConceptScheme

Comment

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
– rdfs:comment
– 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 the Version_History section of the mapping documentation (http://www.niso.org/schemas/iso25964/correspondencesSKOS/).

is in range of
micro-thesaurus of op

xl:Labelcback to ToC or Re-used Class ToC

IRI: http://www.w3.org/2008/05/skos-xl#Label

Comment

Super class of ISO ThesaurusTerm and of ISO NodeLabel.

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.
A NodeLabel has mandatory attributes lexicalValue.

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

has sub-classes
Preferred Term c, Simple Non Preferred Term c, Split Non Preferred Term c

Object Properties

broader term (generic)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#broaderGeneric

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: BTG
The immediate (direct or one-step) class – generalized class relationship.
status: proposed

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
narrower term (generic) op

broader term (instantial)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#broaderInstantial

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: BTI
The immediate (direct or one-step) instance – class relationship.
status: proposed

Changed

The URI has been renamed: #broaderInstantive is replaced by #broaderInstantial according to the observed usage of these words in English. (2013-12-09)

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
narrower term (instantial) op

broader term (partitive)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#broaderPartitive

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: BTP
When the ISO 25964 standard is followed, the BTP/NTP relationship should qualify for a transitive closure.
status: proposed

Example

A “bicycle wheel” for instance belongs uniquely to a “bicycle” while a “wheel” does not.
A BTP/NTP relationship should not be established between “bicycles” and “wheels” because a wheel could be part of a motor car, a wheelbarrow or one of many other artefacts.

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
narrower term (partitive) op

component preferred termopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#plusUse

is defined by
http://purl.org/iso25964/skos-thes

Definition

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.

has domain
Compound Equivalence c
has range
Preferred Term c

micro-thesaurus ofopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#microThesaurusOf

is defined by
http://purl.org/iso25964/skos-thes

Definition

Concept groups published as sub-thesauri (e.g., having micro-thesaurus as ISO conceptGroupType)

has super-properties
skos:inScheme op
has domain
Concept Group c
has range
skos:ConceptScheme c

narrower term (generic)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#narrowerGeneric

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: NTG
The immediate (direct or one-step) class – specialized class relationship.
status: proposed

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
broader term (generic) op

narrower term (instantial)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#narrowerInstantial

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: NTI
The immediate (direct or one-step) class – instance relationship.
status: proposed

Changed

The URI has been renamed: #narrowerInstantive is replaced by #narrowerInstantial according to the observed usage of these words in English. (2013-12-09)

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
broader term (instantial) op

narrower term (partitive)opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#narrowerPartitive

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: NTP
When the ISO 25964 standard is followed, the BTP/NTP relationship should qualify for a transitive closure.
status: proposed

Example

A “bicycle wheel” for instance belongs uniquely to a “bicycle” while a “wheel” does not.
A BTP/NTP relationship should not be established between “bicycles” and “wheels” because a wheel could be part of a motor car, a wheelbarrow or one of many other artefacts.

has domain
skos:Concept c
has range
skos:Concept c
is inverse of
broader term (partitive) op

split non preferred termopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#plusUF

is defined by
http://purl.org/iso25964/skos-thes

Definition

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.

sub groupopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#subGroup

is defined by
http://purl.org/iso25964/skos-thes

Definition

All members of the (object) subGroup are members of the (subject) group.

has characteristics: transitive

has domain
Concept Group c
has range
Concept Group c
is inverse of
super group op

subordinate arrayopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#subordinateArray

is defined by
http://purl.org/iso25964/skos-thes

Definition

Explicitly links a (superordinate) concept to one or more subordinate arrays. Each array may either be composed of narrower concepts of the superordinate concept (in which case there may be an associated node label with a characteristic of division) or by concepts that need not be narrower concepts of the superordinate concept (in which case a node label may provide a facet name).

In other words, though each array only contains sibling concepts, no hierarchical relation may be automatically derived between a concept and the concepts in any of its subordinate arrays. The hierarchical relationship between these concepts has to be asserted explicitly.

has domain
skos:Concept c
has range
Thesaurus Array c
is inverse of
super ordinate op

super groupopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#superGroup

is defined by
http://purl.org/iso25964/skos-thes

Definition

All members of the (subject) group are members of the (object) superGroup.

has characteristics: transitive

has domain
Concept Group c
has range
Concept Group c
is inverse of
sub group op

super ordinateopback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#superOrdinate

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964: hasSuperOrdinateConcept
The (subject) array organizes a set of sibling concepts under the (object) concept.

has domain
Thesaurus Array c
has range
skos:Concept c
is inverse of
subordinate array op

UF+opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#plusUFTerm

is defined by
http://purl.org/iso25964/skos-thes

Definition

ISO 25964-1: UF+

The non-preferred term expressing a compound concept that should be represented by a combination of preferred terms

has super-properties
xl:labelRelation
has domain
Preferred Term c
has range
Split Non Preferred Term c
is inverse of
USE+ op

USE+opback to ToC or Object Property ToC

IRI: http://purl.org/iso25964/skos-thes#plusUseTerm

is defined by
http://purl.org/iso25964/skos-thes

Definition

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.

has super-properties
xl:labelRelation
has domain
Split Non Preferred Term c
has range
Preferred Term c
is inverse of
UF+ op

Re-used Object Properties

skos:broaderopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#broader

Comment

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”.

skos:broaderTransitiveopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#broaderTransitive

Comment

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).

skos:hasTopConceptopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#hasTopConcept

Definition

Captures ISO TopLevelRelationship

skos:inSchemeopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#inScheme

Comment

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.

has sub-properties
micro-thesaurus of op

skos:memberopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#member

Comment

ISO
– hasMemberArray
– hasMemberConcept
– hasAsMember

Note: SKOS S39 (any concept in a List of a skos:memberList is also a value of skos:member).

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.

skos:memberListopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#memberList

Comment

ISO
– hasMemberArray<ordered=true>
– hasMemberConcept<ordered=true>

skos:narroweropback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#narrower

Comment

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”.

skos:narrowerTransitiveopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#narrowerTransitive

Comment

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).

skos:relatedopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#related

Comment

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”.

skos:topConceptOfopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2004/02/skos/core#topConceptOf

Definition

Super property of ISO isPartOf of a ThesaurusConcept having its attribute topConcept = true.

Captures ISO TopLevelRelationship

xl:altLabelopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2008/05/skos-xl#altLabel

Comment

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.

xl:hiddenLabelopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2008/05/skos-xl#hiddenLabel

Comment

Complex super property of ISO hasNonPreferredLabel

Applies if the value of “hasNonPreferredLabel” is of class SimpleNonPreferredTerm with the Boolean attribute “hidden” having value true.

xl:prefLabelopback to ToC or Re-used Object Property ToC

IRI: http://www.w3.org/2008/05/skos-xl#prefLabel

Comment

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.)

Data Properties

statusdpback to ToC or Data Property ToC

IRI: http://purl.org/iso25964/skos-thes#status

is defined by
http://purl.org/iso25964/skos-thes

Comment

ISO status
– on ThesaurusConcept
– on ThesaurusTerm

has domain
skos:Concept c or xl:Label c
has range
xsd:string

Re-used Data Properties

skos:notationdpback to ToC or Re-used Data Property ToC

IRI: http://www.w3.org/2004/02/skos/core#notation

Comment

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.

Re-used Annotation Properties

skos:altLabelapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#altLabel

Comment

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.

skos:definitionapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

Caution

In ISO 25964, “hasDefinition” applies to a term rather than to a concept.

skos:editorialNoteapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#editorialNote

Caution

In ISO 25964, “hasEditorialNote” applies to a term rather than to a concept.

skos:hiddenLabelapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#hiddenLabel

Comment

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.

skos:historyNoteapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#historyNote

Caution

In ISO 25964, “hasHistoryNote” can apply to a term or to a concept.

skos:noteapback to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#note

Comment

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

skos:prefLabelapback to ToC or Re-used Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

Comment

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.

skos:scopeNoteapback to ToC or Re-used Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

Caution

In ISO 25964, “hasScopeNote” applies to a concept rather than to a term.

General Axioms

Namespace Declarationsback to ToC

dc
http://purl.org/dc/elements/1.1/
dcterms
http://purl.org/dc/terms/
iso-thes
http://purl.org/iso25964/skos-thes#
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
skos
http://www.w3.org/2004/02/skos/core#
voaf
http://purl.org/vocommons/voaf#
xl
http://www.w3.org/2008/05/skos-xl#
xsd
http://www.w3.org/2001/XMLSchema#