Link Search Menu Expand Document

Class: Attribute

A property or characteristic of an entity. For example, an apple may have properties such as color, shape, age, crispiness. An environmental sample may have attributes such as depth, lat, long, material.

URI: biolink:Attribute


img


Identifier prefixes

  • EDAM-DATA
  • EDAM-FORMAT
  • EDAM-OPERATION
  • EDAM-TOPIC

Parents

  • is_a: NamedThing - a databased entity or concept/class

Uses Mixins

  • mixin: OntologyClass - a concept or class in an ontology, vocabulary or thesaurus. Note that nodes in a biolink compatible KG can be considered both instances of biolink classes, and OWL classes in their own right. In general you should not need to use this class directly. Instead, use the appropriate biolink class. For example, for the GO concept of endocytosis (GO:0006897), use bl:BiologicalProcess as the type.

Children

  • BehavioralExposure - A behavioral exposure is a factor relating to behavior impacting an individual.
  • BiologicalSex
  • BioticExposure - An external biotic exposure is an intake of (sometimes pathological) biological organisms (including viruses).
  • ChemicalExposure - A chemical exposure is an intake of a particular chemical entity.
  • ChemicalRole
  • ClinicalAttribute - Attributes relating to a clinical manifestation
  • ComplexChemicalExposure - A complex chemical exposure is an intake of a chemical mixture (e.g. gasoline), other than a drug.
  • DiseaseOrPhenotypicFeatureExposure - A disease or phenotypic feature state, when viewed as an exposure, represents an precondition, leading to or influencing an outcome, e.g. HIV predisposing an individual to infections; a relative deficiency of skin pigmentation predisposing an individual to skin cancer.
  • EnvironmentalExposure - A environmental exposure is a factor relating to abiotic processes in the environment including sunlight (UV-B), atmospheric (heat, cold, general pollution) and water-born contaminants.
  • 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.
  • OrganismAttribute - describes a characteristic of an organismal entity.
  • PathologicalAnatomicalExposure - An abnormal anatomical structure, when viewed as an exposure, representing an precondition, leading to or influencing an outcome, e.g. thrombosis leading to an ischemic disease outcome.
  • PathologicalProcessExposure - A pathological process, when viewed as an exposure, representing a precondition, leading to or influencing an outcome, e.g. autoimmunity leading to disease.
  • SeverityValue - describes the severity of a phenotypic feature or disease
  • SocioeconomicAttribute - Attributes relating to a socioeconomic manifestation
  • SocioeconomicExposure - A socioeconomic exposure is a factor relating to social and financial status of an affected individual (e.g. poverty).
  • Zygosity

Referenced by class

Attributes

Own

  • name 0..1
    • Description: A human-readable name for an attribute or entity.
    • Range: LabelType
    • in subsets: (translator_minimal,samples)
  • has attribute type 1..1
    • Description: connects an attribute to a class that describes it
    • Range: OntologyClass
    • in subsets: (samples)
  • has qualitative value 0..1
    • Description: connects an attribute to a value
    • Range: NamedThing
    • in subsets: (samples)

Inherited from chemical exposure:

Inherited from entity:

  • id 1..1
    • Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
    • Range: String
    • in subsets: (translator_minimal)
  • iri 0..1
    • Description: An IRI for an entity. This is determined by the id using expansion rules.
    • Range: IriType
    • in subsets: (translator_minimal,samples)
  • category 0..*
    • Description: 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, … 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}
  • type 0..1
  • description 0..1
    • Description: a human-readable description of an entity
    • Range: NarrativeText
    • in subsets: (translator_minimal)
  • source 0..1
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Inherited from gene product mixin:

  • xref 0..*
    • Description: Alternate CURIEs for a thing
    • Range: Uriorcurie
    • in subsets: (translator_minimal)

Inherited from named thing:

  • provided by 0..*
    • Description: 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.
    • Range: String
  • category 0..*
    • Description: 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, … 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}

Domain for slot:

Other properties

     
In Subsets:   samples
Exact Mappings:   SIO:000614