... | ... | @@ -10,6 +10,18 @@ for getting used to co-editing, and setting up our basic hierarchies in HDO: |
|
|
- If the definition is not clear or unsettled, then leave the class without a SubClass Of entry and change the has curation status field to requires discussion (in the IRI Editor, that's [http://purl.obolibrary.org/obo/IAO_0000428](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000428))
|
|
|
- Save, git add-commit-push your changes (results would look like [this](https://gitlab.hzdr.de/hmc/hmc-public/hob/hdo/-/commit/29e79535fb4326286e71b20f00bd7d401f412f85)) to your branch and then we'll merge stuff in on Tuesday.
|
|
|
|
|
|
# HDO IRIs format and naming conventions
|
|
|
|
|
|
The format for HDO IRIs includes an 8-digit numeric ID preceded by the prefix `HDO_` (e.g. https://purls.helmholtz-metadaten.de/hob/HDO_00001076), following the naming conventions of the [OBO Foundry](https://obofoundry.org/):
|
|
|
|
|
|
* use rdfs:label for the primary label
|
|
|
* include exactly one rdfs:label for every declared entity (e.g. class, property)
|
|
|
* write labels, synonyms, etc as if writing in plain English text. ie use spaces to separate words, only capitalize proper names (e.g. Parkinson disease). Do not use CamelCase, do_not_use_underscores
|
|
|
* avoid extra spaces between words, or at the beginning or end of the term label
|
|
|
* spell out abbreviations. Abbreviations can be included as a separate property.
|
|
|
* make the primary labels to be as unambiguous as possible. Remember, your ontology may be used in a different context than it was originally intended for. Remember also of course that the label should be unambiguous without looking at parent terms
|
|
|
* labels should be unique within an ontology
|
|
|
|
|
|
# ID Ranges for the contributors
|
|
|
|
|
|
| assignee | range |
|
... | ... | |