Home.md

@@ -87,9 +87,29 @@ Note however that a disadvantage of embedding ontology links into JSON-Schema is
 
 </details>
 
-:construction: under construction - further content will be added :construction: 
+Alternatively, we encourage the use of formats that can make use of linked data principles by design:
+- [JSON-LD](https://json-ld.org/) - a lightweight Linked Data format. It is easy for humans to read and write.
+- [linkML](https://linkml.io/) a general purpose modeling language that can be used with linked data, JSON, and other formalisms, and
+- [YARRRML](https://rml.io/yarrrml/spec/#terminology) a human readable text-based representation for declarative generation rules. It is a subset of [YAML], a widely used data serialization language designed to be human-friendly.
+
+<details open>
+Here is an example how the use of EM Glossary terminology in a JSON-LD document could look like:
+
+
+```
+{
+  "@context": {
+    "CoherentBeam": "https://purls.helmholtz-metadaten.de/emg/EMG_00000009",
+    "TiltCorrection": "https://purls.helmholtz-metadaten.de/emg/EMG_00000047"
+  },
+  "@type": "ExampleDataSet",
+  "CoherentBeam": "Value1",
+  "TiltCorrection": "Value2",
+}
+```
+
+</details>
 
-There is a still emerging group of standards that are designated to connect schemas to linked data representations. These are e.g. [JSON-LD](), [YARRRMöL]() and [linkML]().
 
 ### Semantic file formats
 In semantic file formats, such as HDF5 based containers or NeXus we propose to introduce cross references as doc-strings or separate fields associated with key that carry emg.owl class IRIs. Stronger integration might be achieved through semantic import and alignment of related ontologies.