Summary

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

Details

Page properties

Content

...	...	@@ -9,3 +9,30 @@
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 necessary for writing a correct openMINDS instance.
	17	+
	18	+(% style="text-align: justify;" %)
	19	+Let us first start with the most simple example: the openMINDS core schema ContactInformation. According to its schema template (cf. [[ContactInformation HTML>>https://humanbrainproject.github.io/openMINDS/core/schemas/v3/actors/contactInformation.html||rel="noopener noreferrer" target="_blank"]]), the only required property for a contact information instance is **##"email"##**. Nonetheless, every valid JSON-LD needs two more technical properties: **##"@type"##** and **##"@id"##**.
	20	+
	21	+(% style="text-align: justify;" %)
	22	+To simplify the human-readability for all users, technical properties specifically required for the JSON-LD syntax are, on purpose, not defined in the openMINDS schema templates to simplify their readability. Instead, these technical properties are first added to the required property list of all openMINDS schemas after their template is transformed into a full-blown metadata schema format, such as JSON-Schema (cf. [[Technical details>>Technical details]]).
	23	+
	24	+
	25	+=== The openMINDS Python API ===
	26	+
	27	+(% style="text-align: justify;" %)
	28	+For users with at least some programming experience, one possible way to write openMINDS conform JSON-LDs is to use the openMINDS Python API.
	29	+
	30	+=== The openMINDS spreadsheet templates ===
	31	+
	32	+(% style="text-align: justify;" %)
	33	+For users with no programming experience, it is possible to provide at least openMINDS conform metadata by using the openMINDS spreadsheet templates.
	34	+
	35	+=== The Knowledge Graph Editor ===
	36	+
	37	+(% style="text-align: justify;" %)
	38	+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.