Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57
From version 10.1
edited by lzehl
on 2021/03/08 19:20
Change comment: There is no comment for this version
To version 7.1
edited by lzehl
on 2021/02/26 19:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,25 +7,17 @@
7 7  In parallel, openMINDS tries to consider the various programming skills present in the neuroscience research community. For this reason, openMINDS established an integration pipeline which gradually increases the level of technical detail: starting from a user-friendly, lightweight schema template and ending with established, highly technical metadata schema formats (e.g., JSON-Schema).
8 8  
9 9  (% style="text-align: justify;" %)
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.
10 +Please find below a documentation of the layout and requirements needed to keep the openMINDS modularity, the openMINDS integration pipeline, as well as the openMINDS schema template.
11 11  )))
12 12  
13 13  === Overview of the openMINDS layout ===
14 14  
15 -(% style="text-align: justify;" %)
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.
15 +(//**coming soon**//)
17 17  
18 18  === The openMINDS schema template syntax ===
19 19  
20 -(% style="text-align: justify;" %)
21 -All openMINDS metadata models use a light-weighted schema template syntax for defining the metadata. The correspondingly formatted schema files use the extension: 
22 -##**.schema.tpl.json**##
19 +(//**coming soon**//)
23 23  
24 -(% style="text-align: justify;" %)
25 -Although 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 it 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, such as JSON-Schema. Please find in the following a full documentation on the openMINDS schema template syntax.
26 -
27 -
28 -
29 29  === The openMINDS integration pipeline ===
30 30  
31 31  (//**coming soon**//)
Public

openMINDS