Summary

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

Details

Page properties

Content

...	...	@@ -60,13 +60,13 @@
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. Here a cutout of the **##types.json##** and **##properties.json##**:
	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##**:
64	64
65	65	{{code language="json"}}
66	66	{
67	67	...,
68	68	"https://openminds.ebrains.eu/core/Person": {
69		- "description": "Structured information on a person.",
	69	+ "description": "Structured information on a person (alive or dead).",
70	70	"name": "Person",
71	71	"translatableTo": [
72	72	"https://schema.org/Person"
...	...	@@ -76,6 +76,8 @@
76	76	}
77	77	{{/code}}
78	78
	79	+... and a cutout of the properties.json:
	80	+
79	79	{{code language="json"}}
80	80	{
81	81	...,