Summary

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

Details

Page properties

Content

...	...	@@ -40,7 +40,8 @@
40	40	(% style="text-align: justify;" %)
41	41	The JSON-LD property **##"@id"##** is also used to link two different metadata instances. Let us introduce a second openMINDS instance of the openMINDS core schema Person (cf. its HTML) which can link to an openMINDS instance of the openMINDS core schema ContactInformation. Here a valid JSON-LD for a person with a link to the contact information we defined above:
42	42
43		-{{code language="json"}}{
	43	+{{code language="json"}}
	44	+{
44	44	"@type": "https://openminds.ebrains.eu/core/Person",
45	45	"@id": "http://localhost/person/lyuba_zehl",
46	46	"givenName": "Lyuba",
...	...	@@ -48,10 +48,15 @@
48	48	"contactInformation": [
49	49	{"@id": "http://localhost/contactInformation/email_openMINDS"}
50	50	]
51		-}{{/code}}
	52	+}
	53	+{{/code}}
52	52
	55	+(% style="text-align: justify;" %)
53	53	Note that we did not use all schema defined properties for this person instance, but only the required property **##"givenName"##** and the two optional properties **##"familyName"##** and **##"ContactInformation"##**. Please also note, that a person is allowed to link to multiple contact information instances, hence it expects a list of dictionaries, instead of a single dictionary.
54	54
	58	+(% style="text-align: justify;" %)
	59	+You learned now how to write a valid JSON-LD for an openMINDS metadata instance and how you can link different openMINDS metadata instances. In the following sections you will learn that you do not have to manually write such JSON-LDs, but that there are different tools that support you to create your own openMINDS metadata collection.
	60	+
55	55	=== The openMINDS Python API ===
56	56
57	57	(% style="text-align: justify;" %)