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


Ignore:
Timestamp:
01/16/14 14:41:35 (10 years ago)
Author:
twagoo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CMDI 1.2/Vocabularies

    v12 v13  
    199199You 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.
    200200
    201 
    202 
    203 
     201 Twan & Menzo: That's correct, see also out point above about open and closed. ''Internal'' vocabularies of course get frozen not just on the value domain but also on the selected label - that includes a language selection. And we probably don't want to consider multilingual closed (internal) vocabularies in CMDI 1.2 although the idea itself is interesting.
    204202
    205203