Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57

From version 89.1
edited by lzehl
on 2021/07/05 18:52
Change comment: There is no comment for this version
To version 90.1
edited by lzehl
on 2021/07/05 18:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -139,7 +139,7 @@
139 139  Under **##"properties"##** a nested associative array is defined, where each key defines the property name (format: lowerCamelCase; e.g. **##"givenName"##**). The corresponding value is again a nested associative array defining the expected data **##"type"##** (cf. below) and the **##"_instructions"##** for entering the correct metadata for the respective property.
140 140  
141 141  (% style="text-align: justify;" %)
142 -Under **##"required"##** a list of property names can be provided that are obligatory to be present in a correctly instantiated metadata instance of the respective schema. If none of the properties are required, this key-value pair does not have to be specified.
142 +Under **##"required"##** a list of property names can be provided that are obligatory to be present in a correctly instantiated metadata instance of the respective schema. If none of the properties are required, this key-value pair does not have to be specified. Note that within openMINDS, it is assumed that only the stated properties are allowed (additional undefined properties are prohibited per default).
143 143  
144 144  (% style="text-align: justify;" %)
145 145  ==== Schemas extending a context-schema ====
... ... @@ -250,7 +250,7 @@
250 250  {{/code}}
251 251  
252 252  (% class="wikigeneratedid" %)
253 -If the expected data **##"type"##** is an **##"array"##** the expected data type of the items in the array, as well as the expected length of the array can be further defined. Valid data types for items are **##"string"##**, **##"number"##**, ##**"integer"**##, **##"float"##**, **##"boolean"##**, and/or **##"object"##**. In addition, items can also be defined as n-tuples with expected data types. Note that any of the above data type depending constraints can be also applied to respective items. All array constraints can be applied to all item types. Here abstract examples for all possible  **##"array"##** constraints:
253 +If the expected data **##"type"##** is an **##"array"##** the expected data type of the items in the array, as well as the expected length of the array can be further defined. Valid data types for items are **##"string"##**, **##"number"##**, ##**"integer"**##, **##"float"##**, **##"boolean"##**, and/or **##"object"##**. In addition, items can also be defined as n-tuples with expected data types. Note that any of the above data type depending constraints can be also applied to respective items. Note that within openMINDS, it is assumed that only the stated item types are allowed (additional unconstrained items are prohibited per default). All array constraints can be applied to all item types. Here abstract examples for all possible  **##"array"##** constraints:
254 254  
255 255  {{code language="json"}}
256 256  {
Public

openMINDS