Skip to content

GenomicBackgroundExposure

A genomic background exposure is where an individual's specific genomic background of genes, sequence variants or other pre-existing genomic conditions constitute a kind of 'exposure' to the organism, leading to or influencing an outcome.

classDiagram ExposureEvent <|-- GenomicBackgroundExposure GeneGroupingMixin <|-- GenomicBackgroundExposure PhysicalEssence <|-- GenomicBackgroundExposure GenomicEntity <|-- GenomicBackgroundExposure ThingWithTaxon <|-- GenomicBackgroundExposure OntologyClass <|-- GenomicBackgroundExposure Attribute <|-- GenomicBackgroundExposure GenomicBackgroundExposure : category GenomicBackgroundExposure : description GenomicBackgroundExposure : has_attribute GenomicBackgroundExposure : has_attribute_type GenomicBackgroundExposure : has_biological_sequence GenomicBackgroundExposure : has_gene_or_gene_product GenomicBackgroundExposure : has_qualitative_value GenomicBackgroundExposure : has_quantitative_value GenomicBackgroundExposure : id GenomicBackgroundExposure : in_taxon GenomicBackgroundExposure : iri GenomicBackgroundExposure : name GenomicBackgroundExposure : provided_by GenomicBackgroundExposure : source GenomicBackgroundExposure : timepoint GenomicBackgroundExposure : type GenomicBackgroundExposure : xref

Parent Classes

  • Entity
    • NamedThing
      • Attribute [ ontology class]
        • GenomicBackgroundExposure [ exposure event gene grouping mixin physical essence genomic entity thing with taxon ontology class]

Slots

Name Description
category Name of the high level ontology class in which this entity is categorized. Corresponds to the label for the biolink entity type class. In a neo4j database this MAY correspond to the neo4j label tag. In an RDF database it should be a biolink model class URI. This field is multi-valued. It should include values for ancestors of the biolink class; for example, a protein such as Shh would have category values biolink:Protein, biolink:GeneProduct, biolink:MolecularEntity, etc. In an RDF database, nodes will typically have an rdf:type triples. This can be to the most specific biolink class, or potentially to a class more specific than something in biolink. For example, a sequence feature f may have a rdf:type assertion to a SO class such as TF_binding_site, which is more specific than anything in biolink. Here we would have categories {biolink:GenomicEntity, biolink:MolecularEntity, biolink:NamedThing}
description a human-readable description of an entity
has_attribute connects any entity to an attribute
has_attribute_type connects an attribute to a class that describes it
has_biological_sequence connects a genomic feature to its sequence
has_gene_or_gene_product connects an entity with one or more gene or gene products
has_qualitative_value connects an attribute to a value
has_quantitative_value connects an attribute to a value
id A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
in_taxon connects an entity to its taxonomic classification. Only certain kinds of entities can be taxonomically classified; see 'thing with taxon'
iri An IRI for an entity. This is determined by the id using expansion rules.
name A human-readable name for an attribute or entity.
provided_by The value in this node property represents the knowledge provider that created or assembled the node and all of its attributes. Used internally to represent how a particular node made its way into a knowledge provider or graph.
source None
timepoint a point in time
type None
xref Alternate CURIEs for a thing

Mappings

Mapping Type Mapped Value
self ['https://w3id.org/biolink/biolink-model/:GenomicBackgroundExposure']
native ['https://w3id.org/biolink/biolink-model/:GenomicBackgroundExposure']