Summary

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

Details

Page properties

Content

...	...	@@ -56,19 +56,22 @@
56	56	=== The openMINDS vocabulary ===
57	57
58	58	(% style="text-align: justify;" %)
59		-Located under the folder **##vocab##** in the main branch of the central 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.
	59	+Located under the folder **##vocab##** in the main branch of the central 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 **schema types** 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.
60	60
61	61	(% style="text-align: justify;" %)
62		-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:
	62	+The **##types.json##** file is an associative array listing all existing openMINDS schema types. For each openMINDS schema type, a small list of general attributes are provided in a nested associative array. Currently, the following attributes are captured:
63	63
64	64	{{code language="json"}}
65	65	{
66		- "OPENMINDS_SCHEMA_TYPE": {
67		- "description": "GENERAL_DESCRIPTION",
68		- "label": "HUMAN-READABLE_LABEL",
69		- "name": "SIMPLIFIED_SCHEMA_TYPE",
	66	+ "https://openminds.ebrains.eu/«METADATA_MODEL_LABEL»/«SIMPLIFIED_SCHEMA_NAME»": {
	67	+ "description": "«GENERAL_DESCRIPTION»",
	68	+ "label": "«HUMAN-READABLE_LABEL»",
	69	+ "name": "«SIMPLIFIED_SCHEMA_TYPE»",
	70	+ "schemas": [
	71	+ "«METADATA_MODEL_LABEL»/«VERSION_BRANCH»/«SIMPLIFIED_SCHEMA_TYPE»"
	72	+ ],
70	70	"translatableTo": [
71		- "REFERENCE_TO_RELATED_SCHEMA_OF_OTHER_INITIATIVE"
	74	+ "«REFERENCE_TO_RELATED_SCHEMA_OF_OTHER_INITIATIVE»"
72	72	]
73	73	}
74	74	}