Changes for page Technical details
Last modified by lzehl on 2021/07/05 18:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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 expectedname (written in **##lowerCamelCase##**) and value of the metadata,typically called property,under the key **##properties##** as nested dictionaries. Furthermore, the names of obligatory metadata 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 { ... ... @@ -66,7 +66,7 @@ 66 66 If an openMINDS schema template //does not// define a key **##"_type"##** (as in the first example above), it is interpreted as a **context template** which //has to be// extended to a target template. 67 67 68 68 (% style="text-align: justify;" %) 69 -Context templates are and should be used when multiple target templates have the same subset of properties. Such a common subset of properties can then be defined within a single context schema instead of each target template which facilitates the long-term maintenance of these properties. 69 +Context templates are and should be used when multiple openMINDS schemas (target templates) have the same subset of properties. Such a common subset of properties can then be defined within a single context schema instead of each target template which facilitates the long-term maintenance of these properties. 70 70 71 71 (% style="text-align: justify;" %) 72 72 To define that a target template is the extension of a context template, the target template can state under **##"_extends"##** the relative path to the context template. For example, the openMINDS core target template **##Dataset##** extends the core concept template **##researchProduct##** as indicated here: