Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57
From version 28.1
edited by lzehl
on 2021/03/08 22:07
Change comment: There is no comment for this version
To version 30.1
edited by lzehl
on 2021/03/08 22:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,7 +33,7 @@
33 33  ===== Target & context templates =====
34 34  
35 35  (% style="text-align: justify;" %)
36 -Same as in JSON-Schema, all openMINDS schema templates define the name (written in lowerCamelCase) and value of the metadata (typically called property) they expect under the key **##properties##** as nested dictionaries. Furthermore, the names of obligatory metadata/properties can be listed under the key **##required##**. Here a generalized example:
36 +Same as in JSON-Schema, all openMINDS schema templates define the name (written in **##lowerCamelCase##**) and value of the metadata (typically called property) they expect under the key **##properties##** as nested dictionaries. Furthermore, the names of obligatory metadata/properties can be listed under the key **##required##**. Here a generalized example:
37 37  
38 38  {{code language="json"}}
39 39  {
... ... @@ -78,10 +78,8 @@
78 78  }
79 79  {{/code}}
80 80  
81 -Note that this convention requires the context and corresponding target templates to be located in the same openMINDS metadata model repository.
81 +Note that this convention requires the context and corresponding target templates to be located in the same openMINDS metadata model repository. Note also that for properties, the following rules apply for target and concept template: 
82 82  
83 -Note also that for properties, the following rules apply for target and concept template: 
84 -
85 85  1. A concept template has to define some properties which will be inherited by all extending target templates.
86 86  1. If a concept template additionally states that some of these properties are required, all extending target templates will require the same properties. 
87 87  1. A target template can require properties of the concept template, that are not explicitly required within the concept template. In such a case, the other target templates extending the same concept template will not require those properties.
Public

openMINDS