Description
Title
Exercise Medicine Ontology
Short Description
A core reference ontology built upon BFO about exercise medicine and it contains the related terms for healthy people, people with chronic conditions and people living with diability to exercise.
Description
The concept of "exercise is medicine" is gaining traction globally, highlighting the importance of personalized exercise prescriptions for better efficacy than standardized approaches. However, current guidelines often need more support for individualized prescriptions, posing a significant challenge. To bridge this gap, we gathered data from established guidelines, databases, and articles to develop the Exercise Medicine Ontology (EXMO), intending to offer comprehensive support for personalized exercise prescriptions. EXMO encompasses physical activity terms, health status terms, exercise prescription terms, and other related concepts. It has successfully undergone expert evaluation and consistency validation using the ELK and JFact reasoners. EXMO has the potential to provide a much-needed standard for individualized exercise prescription. Beyond prescription standardization, EXMO can also be an excellent tool for supporting databases and recommendation systems. In the future, it could serve as a valuable reference for the development of sub-ontologies and could facilitate the formation of an ontology network.
Identifier Space
EXMO
License
CC-BY 4.0
Domain
health
Source Code Repository
https://github.com/DarkKnight0-0/exmo
Homepage
https://github.com/DarkKnight0-0/exmo
Issue Tracker
https://github.com/DarkKnight0-0/exmo/issues
Contribution Guidelines
https://github.com/DarkKnight0-0/exmo/blob/master/CONTRIBUTING.md
Ontology Download Link
https://github.com/DarkKnight0-0/exmo/blob/master/exmo.owl
Contact Name
Xingyun Liu
Contact Email
Contact GitHub Username
DarkKnight0-0
Contact ORCID Identifier
0000-0002-9295-2767
Formats
- OWL RDF/XML (.owl)
- OBO (.obo)
- OBO Graph JSON (.json)
Dependencies
- bfo
- ro
- doid
- hsapdv
Related
No response
Usages
No response
Intended Use Cases and/or Related Projects
No response
Data Sources
No response
Additional comments or remarks
No response
OBO Foundry Pre-registration Checklist
- I have read and understood the registration process instructions and the registration checklist.
- There is no other ontology in the OBO Foundry which would be an appropriate place for my terms. If there were, I have contacted the editors, and we decided in mutual agreement that a separate ontology is more appropriate.
- My ontology has a specific release file with a version IRI and a
dc:licenseannotation, serialised in RDF/XML. - My identifiers (classes and properties IRIs) are formatted according to the OBO Foundry Identifier Policy
- My term labels are in English and conform to the OBO Foundry Naming Conventions
- 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 property.
- 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).
- For all relationship properties (Object and Data Property), I checked whether the Relation Ontology (RO) includes an appropriate one. I understand that aligning with RO is an essential part of the overall alignment between OBO ontologies!
- For the selection of appropriate annotation properties, I looked at OMO first. I understand that aligning ontology metadata and term-level metadata is essential for cross-integration of OBO ontologies.
- If I was not sure about the meaning of any of the checkboxes above, I have consulted with a member of the OBO Foundry for advice, e.g., through the obo-discuss Google Group.
- The requested ID space does not conflict with another ID space found in other registries such as the Bioregistry and BioPortal, see here for a complete list.