Changes for page Application details

Last modified by lzehl on 2021/10/13 13:11
From version 38.2
edited by lzehl
on 2021/03/17 14:35
Change comment: There is no comment for this version
To version 38.1
edited by lzehl
on 2021/03/17 14:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -50,7 +50,7 @@
50 50  **##"@id": "http:~/~/localhost/YYY/ZZZ"##**
51 51  
52 52  (% style="text-align: justify;" %)
53 -where **##YYY##** and **##ZZZ##** should be replaced with the openMINDS schema (e.g., **##ContactInformation##**) and your own collection-unique identifier (e.g. **##email_openMINDS##**), respectively. While locally this instance identifier only has to be unique within your collection or system, it has to be globally unique if you want to share your instances with the world. Within the EBRAINS Knowledge Graph (KG) this identifier is therefore replaced with an universally unique identifier (UUID) with integration of your openMINDS collection into the public graph database.
53 +where **##YYY##** and **##ZZZ##** should be replaced with the openMINDS schema (e.g., **##ContactInformation##**) and your own collection-unique identifier (e.g. **##email_openMINDS##**), respectively. Within the EBRAINS Knowledge Graph (KG) this identifier has to be a universally unique identifier (UUID), and, therefore, will be replaced accordingly with a UUID by the EBRAINS Knowledge Graph system during the integration process of your openMINDS collection.
54 54  
55 55  (% style="text-align: justify;" %)
56 56  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 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:
Public

openMINDS