Skip to content

Commit

Permalink
Update new-ontology.yml instructions to better conform to principle 6
Browse files Browse the repository at this point in the history
In order to promote the importance of term descriptions, the instructions have been revised to remove the clause "while not necessary". At the same time, the necessity of descriptions for top-level terms is now emphasized. These changes bring the new ontology request form in better alignment with principle 6.
  • Loading branch information
nataled authored Nov 14, 2023
1 parent 53804e4 commit 9ee8c63
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/new-ontology.yml
Original file line number Diff line number Diff line change
Expand Up @@ -268,7 +268,7 @@ body:
required: false
- label: My term labels are in English and conform to the OBO Foundry [Naming Conventions](http://obofoundry.org/http://obofoundry.org/principles/fp-012-naming-conventions.html)
required: false
- label: I understand that term definitions, while not mandatory, are key to understanding the intentions of a term especially when the ontology is used in curation. I made sure that a reasonable majority of terms in my ontology have definitions, in English, using the [IAO:0000115](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000115) property.
- label: I understand that term definitions are key to understanding the intentions of a term, especially when the ontology is used in curation. I made sure that a reasonable majority of terms in my ontology--and all top level terms--have definitions, in English, using the [IAO:0000115](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000115) property.
required: false
- label: For every term in my ontology, I checked whether another OBO Foundry ontology has one with the same meaning. If so, I re-used that term directly (not by cross-reference, by directly using the IRI).
required: false
Expand Down

0 comments on commit 9ee8c63

Please sign in to comment.