Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57
From version 56.1
edited by lzehl
on 2021/06/23 14:01
Change comment: There is no comment for this version
To version 66.2
edited by lzehl
on 2021/06/24 17:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -60,13 +60,12 @@
60 60  Through the integration pipeline of the openMINDS generator, the openMINDS vocabulary is automatically gathered and stored in the main openMINDS GitHub in order to centrally maintain general definitions and references for **types** and **properties** used in schemas across all openMINDS repositories. How this works is explained in the following.
61 61  
62 62  (% style="text-align: justify;" %)
63 -Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries. Here a cutout of the **##types.json##** and **##properties.json##**:
63 +Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries. Here a cutout of the **##types.json##**:
64 64  
65 -{{code language="json" title="Cutout of the openMINDS/vocab/types.json"}}
65 +{{code language="json"}}
66 66  {
67 67   ...,
68 68   "https://openminds.ebrains.eu/core/Person": {
69 - "deprecated": false,
70 70   "description": "Structured information on a person (alive or dead).",
71 71   "name": "Person",
72 72   "translatableTo": [
... ... @@ -77,10 +77,33 @@
77 77  }
78 78  {{/code}}
79 79  
79 +... and a cutout of the **##properties.json##**:
80 +
81 +{{code language="json"}}
82 +{
83 + ...,
84 + "givenName": {
85 + "description": "Name given to a person, including all potential middle names, but excluding the family name.",
86 + "name": "Given name",
87 + "nameForReverseLink": "Is given name of",
88 + "sameAs": [
89 + "https://schema.org/givenName"
90 + ],
91 + "schemas": [
92 + "core/v3/actors/person.schema.tpl.json"
93 + ]
94 + },
95 + ...
96 +}
97 +{{/code}}
98 +
80 80  (% style="text-align: justify;" %)
81 -The keywords of those nested dictionaries are pre-defined to consistently capture for all schema types and properties their namespace, their occurrence, their general description, and possible references to related or matching schema types and properties of other metadata initiatives (e.g., schema.org). This setup also allows us to define some values/entries to be automatically filled in by the openMINDS integration pipeline with each commit to one of the openMINDS repositories (e.g., the namespace and occurrence) and others to be manually editable later on (e.g., the general description and references).
100 +The keywords of those nested dictionaries are pre-defined to consistently capture for all schema types and properties their namespace, their occurrence (cf. **##"schemas"##** in **##properties.json##**), their general description (cf. **##"description"##** in **##types.json##** and **##properties.json##**), and possible references to related or matching schema types (cf. **##"translatableTo"##** in **##types.json##**) and properties (cf. **##""sameAs""##** in **##properties.json##**) of other metadata initiatives (e.g., schema.org).
82 82  
83 83  (% style="text-align: justify;" %)
103 +This setup also allows us to define some values/entries to be automatically filled in by the openMINDS integration pipeline with each commit to one of the openMINDS repositories (**##"name"##**, **##"schemas"##**) and others to be manually editable later on (**##"description"##**, **##"translatableTo"##**, **##"sameAs"##**, **##"nameForReverseLink"##**).
104 +
105 +(% style="text-align: justify;" %)
84 84  For security, outdated entries in those openMINDS vocabulary files (e.g., because the namespace of the schema type or property changed or the schema type or property was deleted) are not automatically deleted, but kept and marked as being deprecated. After evaluation, deprecated schema types or properties can be deleted manually from openMINDS vocabulary.
85 85  
86 86  (% style="text-align: justify;" %)
... ... @@ -89,20 +89,18 @@
89 89  === The openMINDS schema template syntax ===
90 90  
91 91  (% style="text-align: justify;" %)
92 -All openMINDS metadata models use a light-weighted schema template syntax for defining the expected metadata. The correspondingly formatted schema files use the extension: **##.schema.tpl.json##**.
114 +All openMINDS metadata models use a light-weighted schema template syntax for defining the expected metadata. Although this schema template syntax is inspired by JSON-Schema, it outsources most schema technicalities to be handled in the openMINDS integration pipeline, making the openMINDS schemas more human-readable, especially for untrained eyes. Within the openMINDS integration pipeline (cf. below), the schema template syntax is interpreted, extended and flexibly translated to various formal metadata formats (e.g., JSON-Schema).
93 93  
94 94  (% style="text-align: justify;" %)
95 -Although, as the file extension suggests, this openMINDS schema template syntax is inspired by JSON-Schema, it facilitates or even excludes technical aspects that are generally expected for the openMINDS schemas making them more human-readable, especially for untrained eyes. Behind the scenes, within the openMINDS integration pipeline (cf. below), this schema template syntax is then interpreted and flexibly translated to various formal metadata formats (e.g., JSON-Schema).
117 +Please find in the following a full documentation of the openMINDS schema template syntax specifications.
96 96  
97 -(% style="text-align: justify;" %)
98 -Despite the simplification in comparison to JSON-Schema, the openMINDS schema templates are also, at the core, specially formatted JSON files using a particular syntax, meaning special key-value pairs that define the validation rules of a schema.
119 +==== Specifications ====
99 99  
100 -(% style="text-align: justify;" %)
101 -Please find in the following a full documentation of the openMINDS schema template syntax and how it's key-value pairs need to be defined and interpreted.
121 +All openMINDS schemas are human and machine-readable text files with the extension **##.schema.tpl.json##** which define the structure and content of correctly instantiated openMINDS metadata instances. Many features are adopted from JSON-Schema.  According to the schema template syntax each schema is defined as a nested associative array (dictionary).
102 102  
103 -(% style="text-align: justify;" %)
104 -(//**coming soon**//)
105 105  
106 106  === The openMINDS integration pipeline ===
107 107  
108 -(//**coming soon**//)
126 +(//**coming soon**//) If you'd like to learn more about the openMINDS integration pipeline, especially if you'd like to contribute to it, please get in touch with us (the openMINDS development team) via the issues on the openMINDS or openMINDS_generator GitHub or the support email: openminds@ebrains.eu
127 +
128 +{{putFootnotes/}}
Public

openMINDS