Summary

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

Details

Page properties

Content

...	...	@@ -9,3 +9,26 @@
9	9	(% style="text-align: justify;" %)
10	10	Please find below, a general description of a typical JSON-LD as used in the EBRAINS Knowledge Graph and the different approaches in place for writing a metadata description for your research product in form of an openMINDS conform JSON-LD metadata collection.
11	11	)))
	12	+
	13	+=== JSON-LD - the openMINDS serialization format ===
	14	+
	15	+(% style="text-align: justify;" %)
	16	+As stated above, openMINDS supports JSON-LD as serialization format for the metadata representations (instances) of its schemas. In the following we will briefly explain the JSON-LD syntax essential for writing a correct openMINDS instance.
	17	+
	18	+(% style="text-align: justify;" %)
	19	+Let us first start with the example of an openMINDS core schema that is not linked to any other openMINDS schema: the ##ContactInformation##. According to its schema template (cf. its HTML), the only required property for a contact information instance is ##"email"##. Nonetheless, every valid JSON-LD needs two more properties: ##@type## and ##@id##.
	20	+
	21	+=== The openMINDS Python API ===
	22	+
	23	+(% style="text-align: justify;" %)
	24	+For users with at least some programming experience, one possible way to write openMINDS conform JSON-LDs is to use the openMINDS Python API.
	25	+
	26	+=== The openMINDS spreadsheet templates ===
	27	+
	28	+(% style="text-align: justify;" %)
	29	+For users with no programming experience, it is possible to provide at least openMINDS conform metadata by using the openMINDS spreadsheet templates.
	30	+
	31	+=== The Knowledge Graph Editor ===
	32	+
	33	+(% style="text-align: justify;" %)
	34	+For curators of the EBRAINS Share Data service, it is possible to register openMINDS conform metadata into the EBRAINS Knowledge Graph database by using the Knowledge Graph Editor.