Context Navigation

Summary

v5	v6
56	56	==== Avoiding multiplication of large vocabularies in CR ====
57	57	Since 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
58		1. to consider which vocabularies are likely to be relevant in many profiles
	58	1. to consider which vocabularies are likely to be relevant ''as a closed vocabulary'' in many profiles
59	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	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.