Changes for page Application details

Last modified by lzehl on 2021/10/13 13:11

From version 5.1
edited by lzehl
on 2021/02/22 19:11
Change comment: There is no comment for this version
To version 6.2
edited by lzehl
on 2021/02/24 11:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,8 +13,11 @@
13 13  === JSON-LD - the openMINDS serialization format ===
14 14  
15 15  (% style="text-align: justify;" %)
16 -As stated above, openMINDS supports JSON-LD as serialization format for the metadata representations (instances) of its schemas.
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 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, a valid JSON-LD needs two more properties: @type and @id.
20 +
18 18  === The openMINDS Python API ===
19 19  
20 20  (% style="text-align: justify;" %)
... ... @@ -24,3 +24,8 @@
24 24  
25 25  (% style="text-align: justify;" %)
26 26  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.
Public

openMINDS