Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -21,24 +21,33 @@
21	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##**.
22	22
23	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.
	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. 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).
25	25
26	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.
	27	+Despite the simplification in comparison to JSON-Schema, the openMINDS schema templates are also, at the core, specially formatted JSON files using a particular syntax, meaning special key-value pairs that define the validation rules of a schema. Please find in the following a full documentation of the openMINDS schema template syntax and how the key-value pairs need to be defined and interpreted.
28	28
29	29	(% style="text-align: justify;" %)
30	30	===== Target & context templates =====
31	31
32		-All openMINDS schemas have to have a **##"_type"##** to be recognized as target templates. In other words, the **##"_type"##** is used to define the openMINDS namespace of a corresponding schema using the following naming convention:
	32	+(% style="text-align: justify;" %)
	33	+An openMINDS schema //HAS TO HAVE// a **##"_type"##** to be recognized as **target template**. In other words, the **##"_type"##** is used to define the openMINDS namespace of a corresponding schema using the following naming convention:
33	33
34	34	(% style="text-align: center;" %)
35	35	**##"_type": "https:~/~/openminds.ebrains.eu/<<schema-model>>/<<schema-name>>"##**,
36	36
	38	+(% style="text-align: justify;" %)
37	37	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.
38	38
39		-If an openMINDS schema template file does not define a **##"_type"##**, it is interpreted as a context template which requires an extension to become a target template. Context templates are and should be used when multiple openMINDS schemas (target templates) have the same subset of properties. This common subset of properties can then be defined within a single context schema instead of each target template which facilitates the long-term maintenance of these properties.
	41	+(% style="text-align: justify;" %)
	42	+If an openMINDS schema template file //DOES NOT// define a **##"_type"##**, it is interpreted as a **context template** which //HAS TO BE// extended to a target template with a corresponding openMINDS namespace. The context and corresponding target templates have to be located in the same openMINDS metadata model repository.
40	40
41	41	(% style="text-align: justify;" %)
	45	+Context templates are and should be used when multiple openMINDS schemas (target templates) have the same subset of properties. This common subset of properties can then be defined within a single context schema instead of each target template which facilitates the long-term maintenance of these properties.
	46	+
	47	+(% style="text-align: justify;" %)
	48	+To define that a target template is the extension of a context template, the target template can state under **##"_extends"##** the relative path to the context template.
	49	+
	50	+(% style="text-align: justify;" %)
42	42	===== String properties =====
43	43
44	44	(% style="text-align: justify;" %)