Skip to content

Commit 467528b

Browse files
pfabrymatentzn
andauthored
Adding IRIs verification in pre-registration checklist (#2409)
* Updated NOR manager role Added some tasks to be done manually. * Update docs/roles/RoleNORManager.md Co-authored-by: Nico Matentzoglu <[email protected]> * Update docs/roles/RoleNORManager.md Co-authored-by: Nico Matentzoglu <[email protected]> * Update docs/roles/RoleNORManager.md Co-authored-by: Nico Matentzoglu <[email protected]> * Update docs/roles/RoleNORManager.md * Adding IRIs verification in Pre-registration checklist --------- Co-authored-by: Nico Matentzoglu <[email protected]>
1 parent 62d79ae commit 467528b

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

.github/ISSUE_TEMPLATE/new-ontology.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -264,6 +264,8 @@ body:
264264
required: false
265265
- label: My ontology has a specific release file with a version IRI and a `dc:license` annotation, serialised in RDF/XML.
266266
required: false
267+
- label: My identifiers (classes and properties IRIs) are formatted according to the [OBO Foundry Identifier Policy](http://obofoundry.org/id-policy)
268+
required: false
267269
- 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, using the [IAO:0000115](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000115) property.
268270
required: false
269271
- 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).

0 commit comments

Comments
 (0)