Changes between Version 11 and Version 12 of CMDI 1.2/Vocabularies

Timestamp:

01/16/14 14:37:22 (10 years ago)

Author:

twagoo

Comment:

--

CMDI 1.2/Vocabularies

@@ -194 +194 @@
 Another thing: Would it be useful to be able to select from a ''union of vocabularies'', instead of just one? True, such a need could be satisfied by choosing one vocabulary and declaring it open.  But if all the additional items are to selected from another vocabulary, it would be nice to be able to say so.
 
+ Twan & Menzo: This could be done but maybe that could better be solved in CLAVAS, e.g. by having 'virtual vocabularies' (either pre-defined or dynamic unions of arbitrary concept schemes).
+
 '''Multilingual vocabularies'''
 You say: "Notice that there currently is no way to represent multilingual vocabularies, so the language will have to be specified in the vocabulary URI with a fallback to the default language of the vocabulary". Do you mean "no way to represent in CMDI?" If closed vocabularies are handled "by reference", as the open ones, there is no need to represent multilinguality in CMDI components, at least in the cases where multilingual SKOS vocabularies are realised by generating one prefLabel per language, (e.g. "French"@en), retaining one single URI for the whole vocabulary. If prefLabel is to be used as default VocabValueProperty, CMDI 1.2 must be able to handle multilingual prefLabel sets from the start.