Description
Title
Experimental Measurements, Purposes, and Treatments ontologY
Short Description
An ontology of experimental measurements in the sciences, the purposes for which experimental measurements were made, and experimental treatments, with a focus on life sciences.
Description
The Experimental Measurements, Purposes, and Treatments ontologY (EMPTY) is a structured vocabulary designed to capture and standardize the scientific reasoning behind experimental measurements. It addresses a critical gap in existing metadata standards, which primarily focus on technical specifications rather than scientific intent. The ontology provides a common language to express why a measurement was taken and the conceptual conditions under which it should be interpreted. By focusing on experimental purposes and treatments, EMPTY is designed to significantly improve the findability, interoperability, and reusability of scientific data. This enables researchers to discover relevant datasets for meta-analyses and cross-disciplinary research based on shared scientific goals.
Identifier Space
EMPTY
License
CC-BY 4.0
Domain
investigations
Source Code Repository
https://github.com/Waltham-Data-Science/empty-ontology
Homepage
https://github.com/Waltham-Data-Science/empty-ontology
Issue Tracker
https://github.com/Waltham-Data-Science/empty-ontology/issues
Contribution Guidelines
https://github.com/Waltham-Data-Science/empty-ontology/blob/main/CONTRIBUTING.md
Ontology Download Link
https://github.com/Waltham-Data-Science/empty-ontology/blob/main/empty.owl
Contact Name
Andrea Gaede
Contact Email
Contact GitHub Username
andreagaede
Contact ORCID Identifier
0000-0002-1909-7004
Formats
- OWL RDF/XML (.owl)
- OBO (.obo)
- OBO Graph JSON (.json)
Dependencies
- uberon
- cl
- ro
- pato
- omo
Related
UBERON, CL, PATO
Usages
- user: https://www.ndi-cloud.com/
description: NDI cloud uses EMPTY to annotate neurophysiology experimentsIntended Use Cases and/or Related Projects
We intend that EMPTY will be used in sharing and describing scientific data so that it can be more easily analyzed or viewed by humans and AIs.
Data Sources
The ontology is built from suggestions from scientists and curators who need to share data according to FAIR standards.
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.