| ... | ... | @@ -52,6 +52,8 @@ In order to do this you need to: |
|
|
|
2. Define the schema structure including properties that can represent EM Glossary IRIs.
|
|
|
|
3. Embed the IRIs as links to the respective EM Glossary class in the JSON Schema. For this keywords such as `description`, `examples` or custom annotations (using custom-defined keywords) can be used.
|
|
|
|
|
|
|
|
<details open>
|
|
|
|
|
|
|
|
Here an example how that could look in an example schema. The link to EM Glossary classes is established by embedding selected IRIs that relate to a data item in the schema by using and object called `ontologyLink`, with the properties `uri` and `label`. These are defined by custom-defined keywords:
|
|
|
|
```
|
|
|
|
{
|
| ... | ... | @@ -83,6 +85,8 @@ Here an example how that could look in an example schema. The link to EM Glossar |
|
|
|
|
|
|
|
Note however that a disadvantage of embedding ontology links into JSON-Schema is that the used keywords are not standard JSON Schema keywords and as a consequence might not be processed by tools that are programmed to process JSON schema on the standard keywords only.
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
|
:construction: under construction - further content will be added :construction:
|
|
|
|
|
|
|
|
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]().
|
| ... | ... | |
| ... | ... | |