Wiki source code of Technical details

Version 78.5 by lzehl on 2021/07/05 10:21

version	line-number	content
3.1	1	(% class="box infomessage" %)
	2	(((
5.1	3	(% style="text-align: justify;" %)
4.1	4	openMINDS is designed as modular as possible, in order to facilitate extensions and maintenance of existing, as well as development and integration of new metadata models and schemas. The layout and technical requirements for this modularity are described below.
	5
5.1	6	(% style="text-align: justify;" %)
4.1	7	In parallel, openMINDS tries to consider the various programming skills present in the neuroscience research community. For this reason, openMINDS established an integration pipeline which gradually increases the level of technical detail: starting from a user-friendly, lightweight schema template and ending with established, highly technical metadata schema formats (e.g., JSON-Schema).
	8
5.1	9	(% style="text-align: justify;" %)
8.1	10	Please find below a documentation of the layout and requirements needed to keep the openMINDS modularity, the syntax of the openMINDS schema template, as well as the openMINDS integration pipeline.
3.1	11	)))
5.2	12
42.1	13	=== The openMINDS umbrella ===
5.2	14
10.1	15	(% style="text-align: justify;" %)
78.3	16	openMINDS is the overall umbrella for a set of integrated metadata models for describing neuroscience research products in graph databases. The correct integration of these metadata models as well as the provision of a central access point is handled by an integration pipeline. All metadata models are developed on separate GitHub repositories, in order to facilitate extensions and maintenance of existing, as well as development and integration of new openMINDS metadata models and schemas. The integration pipeline ensures that the central openMINDS GitHub repository ingests all these GitHub repositories as [[git-submodules>>https://git-scm.com/docs/git-submodule\|\|rel="noopener noreferrer" target="_blank"]], integrates the respective metadata models and builds the openMINDS GitHub pages, as well as ZIP files containing the respective openMINDS schemas in the supported formats, such as the openMINDS syntax (cf. below), JSON-Schema, or HTML. In the following we will summarize the contents and requirements for the central openMINDS GitHub repository as well as all metadata model git-submodules. The openMINDS integration pipeline will be handled in a separate chapter (cf. below).
6.1	17
42.1	18	(% style="text-align: justify;" %)
78.5	19	Let us start with the [[central openMINDS GitHub repository>>https://github.com/HumanBrainProject/openMINDS\|\|rel="noopener noreferrer" target="_blank"]] which has a main branch, a documentation branch, and version branches (naming convention: vX; e.g., v1). Official releases (naming convention: vX.Y; e.g., v1.0) are tagged and provided as release packages.
78.3	20
	21	(% style="text-align: justify;" %)
	22	The main branch hosts the general README, the LICENSE document, the CONTRIBUTING document, and the general openMINDS logo. In addition, it maintains the openMINDS vocabulary (vocab; cf. below) which provides general definitions and references for schema types and properties used across all openMINDS metadata models and their versions, as well as the bash script that builds the content of the documentation and version branches.
	23
	24	(% style="text-align: justify;" %)
78.5	25	The documentation branch hosts the HTML files that build the [[openMINDS GitHub pages>>https://humanbrainproject.github.io/openMINDS/\|\|rel="noopener noreferrer" target="_blank"]], as well as a ZIP file for each version branch and official release containing the respective openMINDS schemas in the currently supported formats, such as the openMINDS syntax (`.schema.tpl.json`; cf. below), JSON-Schema (`.schema.json`), or HTML (`.html`).
78.3	26
	27	(% style="text-align: justify;" %)
78.4	28	The version branches host the respective openMINDS schemas of a major version by ingesting the corresponding metadata models as git-submodules. Note that these version branches can have official release tags. If a version branch has an official release tag, only backwards compatible changes can be merged on this branch. This can include corrections of typos in instructions, introduction of additional properties to schemas, loosening constraints on expected value numbers or formats, granting additional relations between schemas, and adding new schemas (if they do not require relational changes in existing schemas). Except for typo corrections, these changes are typically tagged as sub-releases for the respective major version (e.g., v1.1). If a version branch does not have an official release tag, yet, also non-backwards compatible changes can be merged on this branch. This can include renaming of existing properties, increasing constraints on expected value numbers or formats, removing relations between schemas and adding new schemas, if they cause relational changes in existing schemas. In case all version branches have official release tags, a new non-backwards compatible change would lead to the creation of a new version branch (with a respectively increased major version number).
42.1	29
	30	(% style="text-align: justify;" %)
78.5	31	As mentioned already above, the setup of the central openMINDS GitHub repository is maintained by the openMINDS integration pipeline (cf. below). Note that the pipeline is configured in such a way, that each commit on one of the openMINDS submodules will trigger a new build of the central openMINDS repository ensuring that its content is always up-to-date.
78.4	32
	33	(% style="text-align: justify;" %)
42.1	34	For this to work smoothly for the existing, but also for all new openMINDS metadata models, the corresponding openMINDS submodules (GitHub repositories) have to meet the following requirements:
	35
54.1	36	(% style="text-align: justify;" %)
	37	(1) The openMINDS metadata model has to be located on a public GitHub repository and published under an MIT license.
45.1	38
54.1	39	(% style="text-align: justify;" %)
78.5	40	(2) The GitHub repository of such a metadata model should have at least one version branch (naming convention: vX, where X is a major version number).
53.1	41
54.1	42	(% style="text-align: justify;" %)
78.5	43	(3) The version branch should have the following folders & files:
53.1	44
78.5	45	* ##schemas/## (required) - contains the schemas of that metadata model implemented in the reduced openMINDS syntax (cf. below). The sub-directory of the "schemas" folder can be further structured or flat.
	46	* ##tests/## (recommended) - contains test-instances (JSON-LDs) for checking the constraints defined in the schemas of the metadata model. The sub-directory of the "tests" folder should follow the same structure as the "schemas" folder. The file names of the test-instances should state in lowerCamelCase first the name of the respectively tested schema and second, separated with an underscore, what schema constrain is tested (e.g., ##contactInformation_validEmail.jsonld##). If a test-instance is expected to fail the schema validation the file name should receive the postfix ##"_nok"## (e.g., ##contactInformation_invalidEmail_nok.jsonld##).
	47	* ##examples/## (recommended)
	48	* ##img/## (optional) - contains typically the logo of the openMINDS submodule.
	49	* ##instances/## (optional) - contains the controlled metadata instances (JSON-LDs) for selected schemas of the metadata model. The sub-directory of the "instances" folder should follow the same structure as the "schemas" folder.
	50	* ##version.txt## (required)
	51	* ##README.md## (required)
	52	* ##LICENSE.txt## (required)
53.1	53
78.5	54
54.1	55	(% style="text-align: justify;" %)
78.5	56	(5) The ##tests## folder should for the schemas in a flat directory. The file names for these test-instances should follow the convention of
53.1	57
55.1	58	(% style="text-align: center;" %)
	59	##<<XXX>>-<<YYY>>.jsonld##
	60
54.1	61	(% style="text-align: justify;" %)
55.1	62	for files that should pass the tests, and
	63
	64	(% style="text-align: center;" %)
	65	##<<XXX>>-<<YYY>>-nok.jsonld##
	66
	67	(% style="text-align: justify;" %)
	68	for files that should fail the test. In both cases, ##<<XXX>>## should be replaced with the label of the schema that is tested, and ##<<YYY>>## with a user defined label for what aspect is tested (e.g., ##person-withoutCI.jsonld##).
	69
	70	(% style="text-align: justify;" %)
54.1	71	(6) The ##examples## folder should contain examples for valid instance collections for that metadata model. Each example should receive its own directory (folder) with a ##README.md## describing the example, and an ##metadataCollection## subfolder containing the openMINDS instances (JSON-LDs). This subfolder can be further structured or flat.
53.1	72
54.1	73	(% style="text-align: justify;" %)
	74	(7) The ##img## folder should contain image files used on that GitHub repository (e.g., the logo of the new openMINDS metadata model). The directory of the images can be further structured or flat.
53.1	75
43.1	76	=== The openMINDS vocabulary ===
	77
	78	(% style="text-align: justify;" %)
75.1	79	Located under the folder ##vocab## in the main openMINDS GitHub directory, the openMINDS vocabulary is semi-automatically gathered and stored in dedicated JSON files ([[##types.json##>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS/v2/vocab/types.json\|\|rel="noopener noreferrer" target="_blank"]] and [[##properties.json##>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS/v2/vocab/properties.json\|\|rel="noopener noreferrer" target="_blank"]]). The openMINDS integration pipeline makes sure that both files are updated with each commit to any of the GitHub repositories for the openMINDS metadata models. With that, the openMINDS vocab reflects always an up-to-date status of the general attributes of existing schemas and properties across all openMINDS metadata models, while providing the opportunity to centrally review and maintain their consistency. In addition, this design allows us to centrally define and maintain multiple references to related schemas and matching schema properties of other metadata initiatives. How this works in detail is explained in the following.
43.1	80
49.1	81	(% style="text-align: justify;" %)
71.1	82	The ##types.json## file is an associative array listing all existing openMINDS schemas (via their type). For each openMINDS schema, a small list of general attributes are provided in a nested associative array. Currently, the following attributes are captured:
49.1	83
57.1	84	{{code language="json"}}
56.1	85	{
68.2	86	"OPENMINDS_SCHEMA_TYPE": {
	87	"description": "GENERAL_DESCRIPTION",
	88	"name": "DISPLAY_LABEL",
56.1	89	"translatableTo": [
68.2	90	"REFERENCE_TO_RELATED_SCHEMA_OF_OTHER_INITIATIVE"
56.1	91	]
68.2	92	}
56.1	93	}
	94	{{/code}}
	95
68.2	96	(% style="text-align: justify;" %)
72.1	97	With each new schema committed to one of the openMINDS metadata models, a new entry is appended to the ##types.json## file, with the display label automatically derived from the respective schema type and the remaining attributes predefined with a null value. Once an entry for a schema is made in the ##types.json## file, the values of all attributes (##"name"##, ##"description"##, and ##"translatableTo"##) can be manually edited. All manual editions will be preserved and not overwritten when the file is updated again with a new commit. In case a schema is deleted from the openMINDS metadata models, the corresponding entry in the ##types.json## file is marked as being deprecated (additional attribute-value pair; ##"deprecated": true##). It only can be permanently removed from the ##types.json## file, if the entry is manually deleted.
58.1	98
68.2	99	(% style="text-align: justify;" %)
71.1	100	Similar to the ##types.json## file, the ##properties.json## file is an associative array listing all properties across all existing openMINDS schemas (via the property name). For each openMINDS property, a small list of general attributes are provided in a nested associative array. Currently, the following attributes are captured:
68.2	101
57.1	102	{{code language="json"}}
	103	{
68.2	104	"PROPERTY_NAME": {
	105	"description": "GENERAL_DESCRIPTION",
	106	"name": "DISPLAY_LABEL",
	107	"nameForReverseLink": "DISPLAY_LABEL_OF_REVERSED_LINK",
57.1	108	"sameAs": [
68.2	109	"REFERENCE_TO_MATCHING_SCHEMA-PROPERTY_OF_OTHER_INITIATIVE"
57.1	110	],
	111	"schemas": [
71.1	112	"RELATIVE_PATH_TO_OPENMINDS-SCHEMA_USING_THIS_PROPERTY"
57.1	113	]
76.2	114	}
57.1	115	}
	116	{{/code}}
	117
49.1	118	(% style="text-align: justify;" %)
72.1	119	With each new property committed to a schema of one of the openMINDS metadata models, a new entry is appended to the ##properties.json## file, with the display label and list of schemas in which this property occurs automatically derived. The remaining attributes are initially provided with a null value. Once an entry for a property is made in the ##properties.json## file, the values of all attributes (##"name"##, ##"description"##, ##"nameForReversedLink"##, and ##"sameAs"##) can be manually edited, except for ##"schemas"## which will be always automatically updated. All those manual editions will be preserved and not overwritten when the file is updated again with a new commit. In case a property is not used anymore in any of the schemas from the openMINDS metadata models, the corresponding entry in the ##properties.json## file is marked as being deprecated (additional attribute-value pair; ##"deprecated": true##). It only can be permanently removed from the ##properties.json## file, if the entry is manually deleted.
49.1	120
78.2	121	=== The openMINDS syntax ===
6.1	122
9.1	123	(% style="text-align: justify;" %)
78.2	124	All openMINDS metadata models are defined using a light-weighted schema syntax. Although this schema syntax is inspired by JSON-Schema, it outsources most schema technicalities to be handled by the openMINDS integration pipeline, making the openMINDS schemas more human-readable, especially for untrained eyes.
6.1	125
10.1	126	(% style="text-align: justify;" %)
68.1	127	The few remaining customized technical properties which need additional interpretation or translation to a formal schema languages (e.g. JSON-Schema) have an underscore as prefix (e.g., ##"_type"##). Within the openMINDS integration pipeline (cf. below), the schema template syntax is interpreted, extended and flexibly translated to various formal schema languages. All further specifications of the openMINDS schema template syntax are described below.
	128
	129	(% style="text-align: justify;" %)
76.1	130	==== Basic openMINDS schema structure ====
	131
	132	(% style="text-align: justify;" %)
67.1	133	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:
9.1	134
67.1	135	{{code language="json"}}
	136	{
	137	"_type": "https://openminds.ebrains.eu/LABEL_OF_METADATA_MODEL/SCHEMA_NAME",
	138	"properties": {
	139	"PROPERTY_NAME": {
	140	"type": "DATA_TYPE",
	141	"_instruction": "METADATA_ENTRY_INSTRUCTION"
	142	},
	143	"required": [
	144	"PROPERTY_NAME"
	145	]
	146	}
	147	{{/code}}
10.1	148
67.1	149	(% style="text-align: justify;" %)
75.1	150	##"_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. ##"ContactInformation"##) have to be specified. Obviously, the schema name should be meaningful and provide some insides into what metadata content the schema covers.
18.1	151
67.1	152	(% style="text-align: justify;" %)
68.1	153	Under ##"properties"## a nested associative array is defined, where each key defines the property name (format: lowerCamelCase; e.g. ##"givenName"##). The corresponding value is again a nested associative array defining the expected data ##"type"## (cf. below) and the ##"_instructions"## for entering the correct metadata for the respective property.
61.1	154
67.1	155	(% style="text-align: justify;" %)
	156	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.
	157
68.1	158	(% style="text-align: justify;" %)
76.3	159	==== Schemas extending a context-schema ====
76.1	160
	161	(% style="text-align: justify;" %)
76.3	162	In the case that several schemas are highly related and contain a common set of properties, it is possible to define a non-type context-schema with these common properties that can be extended and modified by the group of related schemas.
68.1	163
76.3	164	(% style="text-align: justify;" %)
	165	All properties and constraints (e.g. required properties, expected data types) defined in the context-schema are passed on to the schemas extending this context-schema. Each of these schemas can define additional properties, or (if necessary) can overwrite the constraints of the context-schema (incl. ##"_instructions"##). In order to state that a schema is extending a context-schema, the following additional key-value pair has to be added to the schema template above:
	166
75.1	167	(% style="text-align: center;" %)
	168	##"_extends": "RELATIVE_PATH_TO_OPENMINDS-CONTEXT-SCHEMA"##
	169
	170	(% style="text-align: justify;" %)
76.2	171	This design not only makes it easier to identify highly related schemas, but also facilitates the maintenance of the commonly used properties. A good hands-on example, is the context-schema [[ResearchProduct>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS_core/v3/schemas/products/researchProduct.schema.tpl.json\|\|rel="noopener noreferrer" target="_blank"]] which is extended by the following schema set: [[Dataset>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS_core/v3/schemas/products/dataset.schema.tpl.json\|\|rel="noopener noreferrer" target="_blank"]], [[MetaDataModel>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS_core/v3/schemas/products/metaDataModel.schema.tpl.json]], [[Model>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS_core/v3/schemas/products/model.schema.tpl.json\|\|rel="noopener noreferrer" target="_blank"]], and [[Software>>https://raw.githubusercontent.com/HumanBrainProject/openMINDS_core/v3/schemas/products/software.schema.tpl.json\|\|rel="noopener noreferrer" target="_blank"]].
76.1	172
	173	(% style="text-align: justify;" %)
76.3	174	==== Data type depending constraints ====
	175
	176	(% style="text-align: justify;" %)
75.1	177	Depending on the expected data ##"type"## additional constraints can be made for the metadata entry of a respective property. Currently, the openMINDS schema template syntax supports the following data types: ##"string"##, ##"integer"##, ##"float"##, ##"boolean"##, ##"array"## and ##"object"##.
	178
77.2	179	(% style="text-align: justify;" %)
	180	If the expected data ##"type"## is a ##"string"## the expected number of characters, the format or a regular expression pattern of the string can be further defined.
	181
6.1	182	=== The openMINDS integration pipeline ===
	183
61.1	184	(//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
	185
	186	{{putFootnotes/}}

Wiki source code of Technical details

openMINDS