Dear Jan -
This is actually a well-known problem/feature (depending on your pov) in SKOS.
SKOS Concepts are often 'classes' in the generic sense, but the SKOS RDF vocabulary makes them instances.
SKOS is really a bridging vocabulary to help move traditional 'vocabularies' into RDF, but stops short of modelling them fully as classes.
Your reference to 'punning' is on point. Don't expect DL compliance.
Simon Cox
Simon J D Cox
Research Scientist
Environmental Information Infrastructures
Land and Water
CSIRO
E [log in to unmask] T +61 3 9545 2365 M +61 403 302 672
Until 2015-09-06:
37 Graham Road, Highett, Vic 3190
PO Box 56, Highett, Vic 3190
From 2015-09-07:
Bayview Avenue, Clayton, Vic 3168
Private Bag 10, Clayton South, Vic 3169
people.csiro.au/C/S/Simon-Cox
orcid.org/0000-0002-3884-3420
researchgate.net/profile/Simon_Cox3
PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.
------------------------------
Date: Tue, 11 Aug 2015 16:55:54 +0100
From: Jan Voskuil <[log in to unmask]>
Subject: dcterms:type and SKOS (retried)
Dear all,
In recent work I have struck on a problematic interaction between SKOS and DC. These standards should strengthen each other. Using SKOS to publish value lists and then to use the skos:Concepts therein as the value of, for instance, dcterms:subject, offers significant benefits. However, there is a problem with dcterms:type, because it is declared with rdfs:Class as its range. This complicates the use of instances of skos:Concept as its value.
|