Changes between Version 14 and Version 15 of CMDI 1.2/Vocabularies/Summary

Timestamp:

03/05/14 15:28:19 (10 years ago)

Author:

teckart

Comment:

minor changes

CMDI 1.2/Vocabularies/Summary

@@ -29 +29 @@
 
 * New element ''Vocabulary'' in ''!ValueScheme'' replaces ''enumeration''
-* ''Vocabulary'' '''optionally''' has an ''enumeration'' element. If so, this defines an internal, closed vocabulary (imported or locally specified). If ''enumeration'' is not present, then the Vocabulary will be considered to be external and open, and should be accessed by means of the API by tools supporting this.
+* ''Vocabulary'' '''optionally''' has an ''enumeration'' element. If so, this defines an internal, closed vocabulary (imported or locally specified). If ''enumeration'' is not present, then the vocabulary will be considered to be external and open, and should be accessed by means of the API by tools supporting this.
 
 Attributes for ''Vocabulary'' 
@@ -39 +39 @@
 === Instance changes ===
 
-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
+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.
 
 === Impact on tools ===
 * Metadata editors must facilitate vocabulary lookup. Arbil, as the most generic editor - should be prioritized.
-* Component Registry must facilitate import of vocabularies. Interface for specifying value domains for elements and Attributes must be updated.
+* Component Registry must facilitate import of vocabularies. Interface for specifying value domains for elements and attributes must be updated.
 * Discovery services (VLO a.o.) could provide assistance for users through vocabularies. E.g. vocabulary-based browsing.