Changes for page Technical details

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

From version 41.1
edited by lzehl
on 2021/03/09 17:55
Change comment: There is no comment for this version
To version 42.1
edited by lzehl
on 2021/03/17 17:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,11 +10,18 @@
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 -=== Overview of the openMINDS layout ===
13 +=== The openMINDS umbrella ===
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. And last but not least, it holds the schema representations for all supported metadata formats created by the openMINDS generator pipeline.
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 +
18 18  === The openMINDS schema template syntax ===
19 19  
20 20  (% style="text-align: justify;" %)
... ... @@ -103,7 +103,7 @@
103 103  + **##"array"##**
104 104  + **##"boolean"##**
105 105  + **##"null"##**
106 -+ **##"object"##**
113 ++ **##"object"##** 
107 107  
108 108  Also very similar to JSON-Schema, additional type-specific keys can be used to set further requirements for the expected value. H
109 109  
Public

openMINDS