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
-
... ... @@ -12,14 +12,28 @@ 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 openMINDSschema template syntax is inspired by JSON-Schema, it facilitatesr evenexcludes technical aspects that are generallyexpectedforthe openMINDS schemas making itmore human-readable, especially for untrainedeyes. Behind the scenes, within theopenMINDS integration pipeline, this schematemplate syntax is then interpreted andflexibly translatedto variousformal metadataformats, suchas JSON-Schema.Please find inthefollowing a full documentationon the openMINDSschemaemplatesyntax.21 +All openMINDS metadata models use a light-weighted schema template syntax for defining the metadata. The correspondingly formatted schema files use the extension: **##.schema.tpl.json##**. 21 21 23 +(% style="text-align: justify;" %) 24 +Although, as the file extension suggests, 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. 22 22 26 +(% style="text-align: justify;" %) 27 +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 (e.g., JSON-Schema). Please find in the following a full documentation of the openMINDS schema template syntax and how it needs to be interpreted. 28 + 29 +(% style="text-align: justify;" %) 30 +====== **##"_type"##** ====== 31 + 32 +The **##"_type"##** is used to define the type and with that the namespace of a corresponding schema using the following convention: 33 +**##"_type": "https:~/~/openminds.ebrains.eu/<<schema-model>>/<<schema-name>>"##** 34 +where **##<<schema-model>>##** has to be replaced with the label of the openMINDS metadata model the corresponding schema belongs to and **##<<schema-name>>##** exchanged with the label of that schema. 35 + 36 + 23 23 === The openMINDS integration pipeline === 24 24 25 25 (//**coming soon**//)