Summary

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

Details

Page properties

Content

...	...	@@ -111,16 +111,34 @@
111	111	=== The openMINDS schema template syntax ===
112	112
113	113	(% style="text-align: justify;" %)
114		-All openMINDS metadata models use a light-weighted schema template syntax for defining the expected metadata. Although this schema template syntax is inspired by JSON-Schema, it outsources most schema technicalities to be handled in the openMINDS integration pipeline, making the openMINDS schemas more human-readable, especially for untrained eyes. Within the openMINDS integration pipeline (cf. below), the schema template syntax is interpreted, extended and flexibly translated to various formal metadata formats (e.g., JSON-Schema).
	114	+All openMINDS metadata models are defined using a light-weighted schema template syntax. Although this schema template syntax is inspired by JSON-Schema, it outsources most schema technicalities to be handled in the openMINDS integration pipeline, making the openMINDS schemas more human-readable, especially for untrained eyes. The few remaining customized technical properties which need additional interpretation are prefixed in the syntax with **##"_"##**. Within the openMINDS integration pipeline (cf. below), the schema template syntax is interpreted, extended and flexibly translated to various formal metadata formats (e.g., JSON-Schema). The specifications of the openMINDS schema template syntax are described in following.
115	115
116	116	(% style="text-align: justify;" %)
117		-Please find in the following a full documentation of the openMINDS schema template syntax specifications.
	117	+All openMINDS schemas need to have the extension **##.schema.tpl.json##** and each schema is defined as a nested associative array (dictionary) with the following conceptual structure:
118	118
119		-==== Specifications ====
	119	+{{code language="json"}}
	120	+{
	121	+ "_type": "https://openminds.ebrains.eu/LABEL_OF_METADATA_MODEL/SCHEMA_NAME",
	122	+ "properties": {
	123	+ "PROPERTY_NAME": {
	124	+ "type": "DATA_TYPE",
	125	+ "_instruction": "METADATA_ENTRY_INSTRUCTION"
	126	+ },
	127	+ "required": [
	128	+ "PROPERTY_NAME"
	129	+ ]
	130	+}
	131	+{{/code}}
120	120
121		-All openMINDS schemas are human and machine-readable text files with the extension **##.schema.tpl.json##** which define the structure and content of correctly instantiated openMINDS metadata instances. Many features are adopted from JSON-Schema.  According to the schema template syntax each schema is defined as a nested associative array (dictionary).
	133	+(% style="text-align: justify;" %)
	134	+**##"_type"##** defines the schema type (or namespace) with the depicted naming convention, where the label of the respective openMINDS metadata model (e.g., **##"core"##**) and the schema name (format: UpperCamelCase; e.g. **##"Person"##**) have to be specified. The schema name should be meaningful and provide some insides into what metadata content the schema covers.
122	122
	136	+(% style="text-align: justify;" %)
	137	+Under **##"properties"##** a nested associated array is defined, where each key defines the property name (format: lowerCamelCase; e.g. **##"givenName"##**) and the associated value is again a nested associated array defining the expected data **##"type"##** and the **##"_instructions"##** for entering the correct metadata for the respective property. Currently the openMINDS schema template syntax supports the following data types: **##"string, **##"integer"##**, **##"float"##**, **##"boolean"##**, **##"array"##** and **##"object"##**. Depending on the expected data type additional constraints can be made for the metadata entry of a respective property (cf. below).
123	123
	139	+(% style="text-align: justify;" %)
	140	+Under **##"required"##** a list of property names can be provided that are obligatory to be present in a correctly instantiated metadata instance of the respective schema. If none of the properties are required, this key-value pair does not have to be specified.
	141	+
124	124	=== The openMINDS integration pipeline ===
125	125
126	126	(//**coming soon**//) If you'd like to learn more about the openMINDS integration pipeline, especially if you'd like to contribute to it, please get in touch with us (the openMINDS development team) via the issues on the openMINDS or openMINDS_generator GitHub or the support email: openminds@ebrains.eu