|
|
|
# Welcome to our WIKI
|
|
|
|
# Welcome to our Wiki
|
|
|
|
You have questions about how emg.owl is developed, what the community process behind the development is or how you can adopt terminology from the artefact for your own use or align your metadata with this artefact? Here we are trying to give you the answer!
|
|
|
|
|
|
|
|
# About the EM Glossary
|
| ... | ... | @@ -41,21 +41,38 @@ How to adapt and use terminology from emg.owl in your application level artefact |
|
|
|
|
|
|
|
# Documentation of emg.owl
|
|
|
|
used prefixes:
|
|
|
|
https://purls.helmholtz-metadaten.de/emg#
|
|
|
|
core http://www.w3.org/2004/02/skos/core#
|
|
|
|
obo http://purl.obolibrary.org/obo/
|
|
|
|
oboI http://www.geneontology.org/formats/oboInOwl#
|
|
|
|
owl http://www.w3.org/2002/07/owl#
|
|
|
|
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
|
|
|
|
rdfs http://www.w3.org/2000/01/rdf-schema#
|
|
|
|
sche https://schema.org/
|
|
|
|
term http://purl.org/dc/terms/
|
|
|
|
xml http://www.w3.org/XML/1998/namespace
|
|
|
|
xsd http://www.w3.org/2001/XMLSchema#
|
|
|
|
|
|
|
|
| prefix | url |
|
|
|
|
| - | - |
|
|
|
|
| emg | https://purls.helmholtz-metadaten.de/emg# |
|
|
|
|
| core | http://www.w3.org/2004/02/skos/core# |
|
|
|
|
| obo | http://purl.obolibrary.org/obo/ |
|
|
|
|
| oboI | http://www.geneontology.org/formats/oboInOwl# |
|
|
|
|
| owl | http://www.w3.org/2002/07/owl# |
|
|
|
|
| rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# |
|
|
|
|
| rdfs | http://www.w3.org/2000/01/rdf-schema# |
|
|
|
|
| sche | https://schema.org/ |
|
|
|
|
| term | http://purl.org/dc/terms/ |
|
|
|
|
| xml | http://www.w3.org/XML/1998/namespace |
|
|
|
|
| xsd | http://www.w3.org/2001/XMLSchema# |
|
|
|
|
|
|
|
|
|
|
|
|
### OWL build pipeline
|
|
|
|
### emg.owl release cycle
|
|
|
|
|
|
|
|
### emg.owl releases
|
|
|
|
We follow general best practice regarding release cycle, release management and [semantic versioning](https://semver.org/) of the emg.owl artefact.
|
|
|
|
|
|
|
|
#### Versioning
|
|
|
|
Version number is indicated in the OWL header. Further we generate versions IRIs consisting of base URI and version number, that deference to the respective version of the artefact. Previous versions are archived in this repository.
|
|
|
|
|
|
|
|
Our version number are in the form of X.Y.Z . X indicates _major version_ - related changes may include the addition or removal of classes or substantial changes to the hierarchy or relations. Y indicates _minor versions_ - related changes can include content changes e.g. of definitions or annotation properties that may adjust semantic meaning of a class. Z indicates _patches_ which may include changes in spelling, changes of annotation properties that doe not change semantic meaning.
|
|
|
|
|
|
|
|
A list of all changes compared to previous version is given in our [Glossary specification page](owl.emglossary.helmholtz-metadaten.de).
|
|
|
|
|
|
|
|
#### release cycle & management
|
|
|
|
|
|
|
|
Prior to a release edits are implemented in [emg-edit.owl
|
|
|
|
|
|
|
|
### legal info
|
|
|
|
- how to cite
|
|
|
|
- licensing |
|
|
\ No newline at end of file |
