Skip to content

Request for new ontology UberVariO #2847

@mvihinen

Description

@mvihinen

Title

Ontology of biological heterogeneity

Short Description

UberVariO is an ontology for the standardised, systematic description of pervasive heterogeneity throughout biological entities. It facilitates the systematic characterisation of the various types, effects, consequences, mechanisms, regulatory and limiting factors, and other properties of heterogeneity.

Description

UberVariO is an ontology for the standardised, systematic description of pervasive heterogeneity throughout biological entities. It facilitates the systematic characterisation of the various types, effects, consequences, mechanisms, regulatory and limiting factors, and other properties of heterogeneity.

Identifier Space

UberVariO

License

CC0

Domain

biochemistry

Source Code Repository

https://variationontology.org/UberVariO

Homepage

https://variationontology.org/UberVariO

Issue Tracker

https://variationontology.org/UberVariO

Contribution Guidelines

https://variationontology.org/UberVariO

Ontology Download Link

https://variationontology.org/UberVariO/UberVariO100.xml

Contact Name

Mauno Vihinen

Contact Email

mauno.vihinen@med.lu.se

Contact GitHub Username

mvihinen

Contact ORCID Identifier

0000-0002-9614-7976

Formats

  • OWL RDF/XML (.owl)
  • OBO (.obo)
  • OBO Graph JSON (.json)

Dependencies

UberVariO contains terms from 80 ontologies in total.

Related

VariO is the closest one.
UberVariO contains terms from 80 ontologies in total.

Usages

Intended Use Cases and/or Related Projects

Description of any kind of biological heterogeneity.

Data Sources

Literature
Databases

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:license annotation, 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    new ontologyUse for new ontology registration requests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions