Summary

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

Details

Page properties

Content

...	...	@@ -60,8 +60,23 @@
60	60	Through the integration pipeline of the openMINDS generator, the openMINDS vocabulary is automatically gathered and stored in the main openMINDS GitHub in order to centrally maintain general definitions and references for **types** and **properties** used in schemas across all openMINDS repositories. How this works is explained in the following.
61	61
62	62	(% style="text-align: justify;" %)
63		-Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries.
	63	+Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries. Here a cutout of the **##types.json##** and **##properties.json##**:
64	64
	65	+{{code language="json" title="Cutout of the openMINDS/vocab/types.json"}}
	66	+{
	67	+ ...,
	68	+ "https://openminds.ebrains.eu/core/Person": {
	69	+ "deprecated": false,
	70	+ "description": "Structured information on a person (alive or dead).",
	71	+ "name": "Person",
	72	+ "translatableTo": [
	73	+ "https://schema.org/Person"
	74	+ ]
	75	+ },
	76	+ ...
	77	+}
	78	+{{/code}}
	79	+
65	65	(% style="text-align: justify;" %)
66	66	The keywords of those nested dictionaries are pre-defined to consistently capture for all schema types and properties their namespace, their occurrence, their general description, and possible references to related or matching schema types and properties of other metadata initiatives (e.g., schema.org). This setup also allows us to define some values/entries to be automatically filled in by the openMINDS integration pipeline with each commit to one of the openMINDS repositories (e.g., the namespace and occurrence) and others to be manually editable later on (e.g., the general description and references).
67	67