Summary

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

Details

Page properties

Content

...	...	@@ -22,12 +22,11 @@
22	22	To simplify the human-readability for all openMINDS users, technical properties specifically required for the JSON-LD syntax are, on purpose, not defined in the openMINDS schema templates. Instead, these technical properties are first added to the required property list of all openMINDS schemas after their template is transformed into an established, full-blown metadata schema format, such as JSON-Schema (cf. [[Technical details>>Technical details]]).
23	23
24	24	(% style="text-align: justify;" %)
25		-The JSON-LD property **##"@type"##** expects an entry (value) of type string that defines which schema is used to validate the particular JSON-LD. Within openMINDS each schema can be identified through its namespace (type) with the following naming convention:
	25	+In general, the JSON-LD property **##"@type"##** expects an entry (value) of type string that defines which schema is used to validate the particular JSON-LD. Within openMINDS each schema can be identified through its namespace (type) with the following naming convention:
26	26
27	27	(% style="text-align: justify;" %)
28		-(% class="small" %)##**"@type": "https:~/~/openminds.ebrains.eu/XXX/YYY"**##
	28	+(% class="small" %)##"https:~/~/openminds.ebrains.eu/" + <openMINDS-submodule label> + "/" + <openMINDS schema label>##
29	29
30		-The JSON-LD property **##"@id"##** expects an entry (value) of type string that provides a unique
31	31
32	32	=== The openMINDS Python API ===
33	33