Changes between Version 10 and Version 11 of CmdiClavasIntegration

Timestamp:

05/24/13 07:16:25 (11 years ago)

Author:

twagoo

Comment:

more info on closed vocabs

CmdiClavasIntegration

@@ -56 +56 @@
 ===== Closed vocabularies =====
 
-Closed vocabularies will be no different from standard CMDI closed vocabularies on the instance level. All required information will be available from the schema (see below).
+Closed vocabularies will be no different from standard CMDI closed vocabularies on the instance level. All required information will be available from the schema due to the vocabulary import (see below).
 
 ==== Specifying vocabularies in CMDI component specifications ====
@@ -101 +101 @@
 ===== Closed vocabularies =====
 
-For closed vocabularies we add the vocabulary uri as an attribute to the element and re-use the existing !ConceptLink attribute on the enumeration items to store the identifier of individual vocabulary items.
+Closed vocabularies will be 'imported' into the component design-time, resulting in an internalized 'snapshot copy' of the vocabulary at the time of creation. The ComponentRegistry will be extended with functionality to allow this. The vocabulary URI will be stored in the component specification and transferred to the schema so that editors can query the API for additional information but this is optional as all information including the item URI's will be available from the schema.
+
+We will add the vocabulary uri as an attribute to the element and re-use the existing !ConceptLink attribute on the enumeration items to store the identifier of individual vocabulary items.
 
 {{{