h3abionet / afpo Goto Github PK

In order to facilitate the integration of AfPO with other ontologies, such as HANCESTRO, the addition of a BFO-compliant version should be considered.
Following the HANCESTRO model, this could be:

• material entity: Population, Continent, Region
• organization: Country

The 6th OBO Foundry principle requires textual definitions for most of an ontology's classes.

AfPO should make use of existing annotations to define a textual definition pattern for populations that can be built from the existing ontologies without the need to write additional definitions manually.

ERROR duplicate_label Kru rdfs:label Kango
31
ERROR duplicate_label Kango rdfs:label Kango
32
ERROR duplicate_label Tutsi rdfs:label Birwa
33
ERROR duplicate_label Birwa rdfs:label Birwa
34
ERROR multiple_labels Tutsi rdfs:label Birwa

Instead of using names, change to ORCID. Use dcterms:contributor instead of oboInOwl:created_by.

The geographical classification within AfPO currently does not follow a strict is_a hierarchy and instead follows a country > region > continent model. In order to comply with accepted OWL ontology practice, this should be refactored into 3 orthogonal hierarchies for countries, regions and continents, with relevant concepts interlinked using partonomy (part_of) relationships.

According to OBO Foundry Principle 1:

OBO Foundry Ontologies MUST EITHER be released under a Creative Commons Attribution 3.0 Unported (CC BY 3.0) license or later (e.g. Attribution 4.0 International (CC BY 4.0), OR released into the public domain under Creative Commons CC0 1.0 Public Domain Dedication (CC0 1.0).

https://obofoundry.org/principles/fp-001-open.html#recommendations-and-requirements

The OBO Foundry dashboard uses the annotation property http://purl.obolibrary.org/obo/IAO_0000115 to identify textual definitions of classes. Using a different property will lead to a failure of the OBO dashboard for this indicator