Changes between Version 7 and Version 8 of CMDI 1.2/Vocabularies

Timestamp:

12/05/13 16:10:26 (10 years ago)

Author:

mwindhouwer

Comment:

--

CMDI 1.2/Vocabularies

@@ -38 +38 @@
 ==== Open vocabularies ==== 
 
-Each concept within a vocabulary is identified by an OpenSKOS specific URI and optionally has a reference to a 'source' URI (e.g. ISOCat). For fields that link to vocabularies as open vocabularies, we want to store one of these URIs as an attribute in CMDI metadata '''instances'''. 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.
+Each concept within a vocabulary is identified by an OpenSKOS specific URI and optionally has a reference to a 'source' URI (e.g. ISOCat). For fields that link to vocabularies as open vocabularies, we want to store one of these URIs as an attribute in CMDI metadata '''instances'''. 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. 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).
@@ -116 +116 @@
 {{{
 #!xml
-<language cmd:ValueConceptLink="http://openskos.org/api/institution/beng">Sound and Vision</language>
+<Institution cmd:ValueConceptLink="http://openskos.org/api/institution/beng">Sound and Vision</Institution>
 }}}