| ... | ... | @@ -81,17 +81,12 @@ 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.
|
|
|
|
|
|
|
|
: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]().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In JSON schema fields like "external reference" that could carry an emg.owl class label and "identifier" carrying the related class IRIs is encouraged.
|
|
|
|
|
|
|
|
:construction: under construction - further content will be added :construction:
|
|
|
|
### 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.
|
|
|
|
|
| ... | ... | |
| ... | ... | |