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
-
... ... @@ -7,5 +7,19 @@ 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 openMINDS integrationpipeline, as well as the openMINDSschemaemplate.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 + 13 +=== Overview of the openMINDS layout === 14 + 15 +In summary, openMINDS is the overall umbrella for a set of distributed GitHub repositories, each defining a particular metadata model for neuroscience research products. 16 + 17 +=== The openMINDS schema template syntax === 18 + 19 +(% style="text-align: justify;" %) 20 +All openMINDS metadata models use a light-weighted schema template syntax for defining the metadata schemas. 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, 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. 21 + 22 + 23 +=== The openMINDS integration pipeline === 24 + 25 +(//**coming soon**//)