Attention: The Keycloak upgrade has been completed. As this was a major upgrade, there may be some unexpected issues occurring. Please report any issues you find to support by using the contact form found at https://www.ebrains.eu/contact/. Thank you for your patience and understanding. 


Changes for page Technical details

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

From version 9.1
edited by lzehl
on 2021/03/08 19:13
Change comment: There is no comment for this version
To version 10.1
edited by lzehl
on 2021/03/08 19:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,14 +12,20 @@
12 12  
13 13  === Overview of the openMINDS layout ===
14 14  
15 +(% style="text-align: justify;" %)
15 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 16  
17 17  === The openMINDS schema template syntax ===
18 18  
19 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 +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**##
21 21  
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.
22 22  
27 +
28 +
23 23  === The openMINDS integration pipeline ===
24 24  
25 25  (//**coming soon**//)
Public

openMINDS