Changes between Version 9 and Version 10 of CmdiClavasIntegration

Timestamp:

05/24/13 07:11:15 (11 years ago)

Author:

twagoo

Comment:

cmd:ValueConceptLink on instances

CmdiClavasIntegration

@@ -45 +45 @@
 {{{
 #!xml
-<language cmd:VocabItem="http://cdb.iso.org/lg/CDB-00138580-001">Dutch</language>
+<language cmd:ValueConceptLink="http://cdb.iso.org/lg/CDB-00138580-001">Dutch</language>
 }}}
 
 Notice the ''cmd''-prefix to disambiguate and prevent clashes with potential custom attributes of this name.
 
-Each vocabulary item has an CLAVAS URI and optionally a 'source URI' (which generally will come from the primary data source, e.g. ISOCat), as in the example above.  There will be a deterministic fall-back mechanism in Arbil that chooses the source URI if available, otherwise the CLAVAS URI.
+Each item in the vocabulary has an OpenSKOS URI and optionally a 'source URI' (which generally will come from the primary data source, e.g. ISOCat), as in the example above.  There will be a deterministic fall-back mechanism in Arbil that chooses the source URI if available, otherwise the CLAVAS URI.
 
-The value that serves as the text content should come from one of the child elements of the concept definition. Typically this will be the preferred label as specified in the vocabulary item returned from the API but it could also come from another element (e.g. a notation element that has a language code). Which path to use should be determined in the component specification (possibly part of the vocabulary URI).
-
+The value that serves as the text content should come from one of the child elements of the concept definition. Typically this will be the preferred label as specified in the vocabulary item returned from the API but it could also come from another element (e.g. to choose between item full name and item code). Which path to use should be determined in the component specification (possibly part of the vocabulary URI).
 
 ===== Closed vocabularies =====