README.md 1.98 KB
Newer Older
p.dbalzer's avatar
p.dbalzer committed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Using statements from the SKOS namespace within LIDO
====================================================

This is a brute-force extension to LIDO 1.0, allowing all instances of conceptComplexType and actorComplexType to carry statements from the SKOS RDF namespace.

Motivation
----------

lido:conceptComplexType permits any number of conceptID and term elements to identify a single vocabulary item. In practice, this element is often used to assemble various identifiers and terms, without indication of which term relates to which identifier (if any), and how terms relate to each other. Often, this rules out utilizing features of the controlled vocabulary, such as semantic relationships or synonym rings, in user interfaces for information retrieval.

Approach
--------

SKOS, being defined as an RDF application, does not fit easily into an XML schema definition. However, using RDF/XML syntax, any RDF statement can be embedded in an XML document, provided that (a) namespaces are declared properly, and (b) validating XML parsers are made aware of the fact that such statements can legally occur in certain contexts of the document.

We propose a simple addition to the schema definition for conceptComplexType and actorComplexType that permits XML renderings of skos:Concept instances to be included in any element derived from these types.

Intended usage
--------------

p.dbalzer's avatar
p.dbalzer committed
21
In its most basic form, an included skos:Concept can consist of nothing more but the (dereferencable) URI in the rdf:about attribute:
p.dbalzer's avatar
p.dbalzer committed
22
   
p.dbalzer's avatar
p.dbalzer committed
23
	<skos:Concept rdf:about="http://vocab.getty.edu/aat/300220539"/>
p.dbalzer's avatar
p.dbalzer committed
24
25

which permits LOD-enabled applications to fetch any required data from the vocabulary source item. Besides, the skos:Concept instance can be used to carry copies of any statement from the source vocabulary, including term values, semantic relationships, notes, mappings, and instances of the skosxl:Label classes. The latter will require an additional declaration for the skosxl namespace, either locally or for the LIDO XML document.