Summary

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

Details

Page properties

Content

...	...	@@ -35,11 +35,14 @@
35	35	(% style="text-align: justify;" %)
36	36	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:
37	37
38		-(% style="text-align: justify;" %)
39		-**##"_type": "https:~/~/openminds.ebrains.eu/<<schema-model>>/<<schema-name>>"##**
	38	+{{code language="json"}}
	39	+{
	40	+ "_type": "https:~/~/openminds.ebrains.eu/<<schema-model>>/<<schema-name>>"
	41	+}
	42	+{{/code}}
40	40
41	41	(% style="text-align: justify;" %)
42		-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.
	45	+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 name of that schema (written in **##CamelCase##**).
43	43
44	44	(% style="text-align: justify;" %)
45	45	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.
...	...	@@ -48,8 +48,17 @@
48	48	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.
49	49
50	50	(% style="text-align: justify;" %)
51		-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. Note that this requires the context and corresponding target templates to be located in the same openMINDS metadata model repository.
	54	+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. For example, the openMINDS core schema **##Dataset##** (target template) extends the core concept template **##researchProduct##**:
52	52
	56	+{{code language="json"}}
	57	+{
	58	+ "_type": "https:~/~/openminds.ebrains.eu/core/Dataset"
	59	+ "_extends": "products/researchProduct.schema.tpl.json"
	60	+}
	61	+{{/code}}
	62	+
	63	+Note that this convention requires the context and corresponding target templates to be located in the same openMINDS metadata model repository.
	64	+
53	53	(% style="text-align: justify;" %)
54	54	===== String properties =====
55	55