Changes for page Application details

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

From version 8.1
edited by lzehl
on 2021/02/24 12:00
Change comment: There is no comment for this version
To version 10.1
edited by lzehl
on 2021/02/24 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,11 +13,15 @@
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. In the following we will briefly explain the JSON-LD syntax essential for writing a correct openMINDS instance.
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 17  
18 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"##**.
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 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 +
21 21  === The openMINDS Python API ===
22 22  
23 23  (% style="text-align: justify;" %)
Public

openMINDS