Changes between Version 9 and Version 10 of CMDI 1.2/Vocabularies

Timestamp:

01/16/14 14:14:27 (10 years ago)

Author:

twagoo

Comment:

added comment on skos features

CMDI 1.2/Vocabularies

@@ -185 +185 @@
 I find the above a bit confusing. According to my understanding, OpenSKOS provides APIs specifically to SKOS, and I take this to mean that the vocabularies we are trying to integrate with CMDI are all represented in SKOS. As you know, SKOS (plain version) has 3 types of labels, prefLabel, altLabel and hiddenLabel. Still, in the above examples additional label elements seem to be anticipated, like "name" and "organisation-name". So apparently, openSKOS.org allows for richer descriptions than SKOS? Does openSKOS.org have preferances for other ontologies, like FOAF, for instance?
 
+ Twan & Menzo: You are right, the SKOS namespace does not allow for such specifications. Either we will be limited to selecting one of these three label types (which in itself is problematic because there can be any number of altLabels), or we would need to depend on some extension available in CLAVAS. This is a bit unclear at the moment, so let's try to get things a bit more clear w.r.t. CLAVAS. In any case the code example on this page is not the best possible example so we will try to adapt.
+
 '''Open vs. closed vocabularies'''
 As far as I understand, whether a vocabulary is open or closed represents - in this context at least -  merely a ''mode of application'',- it is not a feature of the vocabulary as such. Maybe I am missing something, but I fail to see the sense in  treating open and closed vocabularies differently in the way proposed here. More specifically.  I question the wisdom of snapshotting (possibly huge) vocabularies into the components and profiles. After all, the vocabularies are not static, and how do we make sure that the vocabulary copies are kept updated? My guess is that this - after a time - will result in as many vocabulary variants as there are components using it. So why not referring to closed vocabularies the same ways as open? The we probably need to encode in another way whether the vocabulary is to be used in a closed or open way.