Changes between Version 4 and Version 5 of CMDI 1.2/Vocabularies/Summary


Ignore:
Timestamp:
03/05/14 13:09:12 (10 years ago)
Author:
Twan Goosen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Vocabularies/Summary

    v4 v5  
    3838Attributes for <Vocabulary>
    3939* @URI (mandatory)
    40 * @ValueProperty (mandatory; which field of the vocabulary items to return, typically prefLabel)
    41 * @ValueLanguage (optional; preferred  language of the item field value)
     40* @!ValueProperty (mandatory; which field of the vocabulary items to return, typically prefLabel)
     41* @!ValueLanguage (optional; preferred  language of the item field value)
    4242
    4343
    4444=== Instance changes ===
    4545
    46 An attribute ''ValueConceptLink'' (in the CMDI namespace) will be allowed on fields that have a vocabulary linked to hold the URI of the selected value, semantically marking the chosen option
     46An attribute ''!ValueConceptLink'' (in the CMDI namespace) will be allowed on fields that have a vocabulary linked to hold the URI of the selected value, semantically marking the chosen option
    4747
    4848=== Impact on tools ===
    … …  
    5757Since imported vocabularies are to be part of elements, and elements are not reusable, great care must be taken so that large enumeration lists are not duplicated across components. One way of achieving this is
    58581. to consider which vocabularies are likely to be relevant in many profiles
    59 2. for each concept property that is relevant as ValueProperty for some  element in CR, define a component in CR containing one element only and import the property values of the vocabulary concepts as its closed value domain.
    60  * Example: The component [http://catalog.clarin.eu/ds/ComponentRegistry?item=clarin.eu:cr1:c_1271859438110 iso-language-639-3] contains one element only - iso-639-3-code - taking values from a controlled vocabulary of language codes. (With the proposed 1.2 model, and given the CLAVAS vocabulary of langauges,  ValueProperty would have been set to "notation"). Some modelers may prefer to store the ''language names'' instead of or in addition to ''codes''. To make sure this can be reused independently of language codes, another component containing a language name element (with ValueProperty=prefLabel) should be defined.
     592. for each concept property that is relevant as !ValueProperty for some  element in CR, define a component in CR containing one element only and import the property values of the vocabulary concepts as its closed value domain.
     60 * Example: The component [http://catalog.clarin.eu/ds/ComponentRegistry?item=clarin.eu:cr1:c_1271859438110 iso-language-639-3] contains one element only - iso-639-3-code - taking values from a controlled vocabulary of language codes. (With the proposed 1.2 model, and given the CLAVAS vocabulary of langauges,  !ValueProperty would have been set to "notation"). Some modelers may prefer to store the ''language names'' instead of or in addition to ''codes''. To make sure this can be reused independently of language codes, another component containing a language name element (with !ValueProperty=prefLabel) should be defined.
    6161
    6262Note: If the same effect is to be obtained for Attributes, they also will have to be wrapped separately in a component.