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
-
... ... @@ -10,23 +10,11 @@ 10 10 Please find below a documentation of the layout and requirements needed to keep the openMINDS modularity, the syntax of the openMINDS schema template, as well as the openMINDS integration pipeline. 11 11 ))) 12 12 13 -=== The openMINDSumbrella ===13 +=== Overview of the openMINDS layout === 14 14 15 15 (% style="text-align: justify;" %) 16 16 In summary, openMINDS is the overall umbrella for a set of distributed GitHub repositories, each defining a particular metadata model for neuroscience research products. 17 17 18 -(% style="text-align: justify;" %) 19 -The main (or central) [[openMINDS GitHub repository>>https://github.com/HumanBrainProject/openMINDS||rel="noopener noreferrer" target="_blank"]] ingests all these GitHub repositories as submodules. Furthermore it defines the openMINDS vocabulary (**##vocab##**) used for **##types##** and **##properties##** across all schemas independent of their original repository (cf. below). And last but not least, it holds the schema representations for all supported metadata formats created by the openMINDS integration pipeline (cf. below). 20 - 21 -(% style="text-align: justify;" %) 22 -For this to work smoothly for the existing, but also for all new openMINDS metadata models, the corresponding openMINDS submodules (GitHub repositories) have to meet the following requirements: 23 -((% style="color:#7f8c8d" %)//**coming soon**//(%%)) 24 - 25 -=== The openMINDS vocabulary === 26 - 27 -(% style="text-align: justify;" %) 28 -((% style="color:#7f8c8d" %)//**coming soon**//(%%)) 29 - 30 30 === The openMINDS schema template syntax === 31 31 32 32 (% style="text-align: justify;" %) ... ... @@ -115,7 +115,7 @@ 115 115 + **##"array"##** 116 116 + **##"boolean"##** 117 117 + **##"null"##** 118 -+ **##"object"##** 106 ++ **##"object"##** 119 119 120 120 Also very similar to JSON-Schema, additional type-specific keys can be used to set further requirements for the expected value. H 121 121