Link Search Menu Expand Document

Class: GeneToGeneHomologyAssociation

A homology association between two genes. May be orthology (in which case the species of subject and object should differ) or paralogy (in which case the species may be the same)

URI: biolink:GeneToGeneHomologyAssociation

img

Parents

  • is_a: GeneToGeneAssociation - abstract parent class for different kinds of gene-gene or gene product to gene product relationships. Includes homology and interaction.

Referenced by class

Attributes

Own

  • object 1..1
    • Description: connects an association to the object of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • predicate 1..1
    • Description: A high-level grouping for the relationship type. AKA minimal predicate. This is analogous to category for nodes.
    • Range: PredicateType
  • subject 1..1
    • Description: connects an association to the subject of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing

Inherited from association:

  • subject 1..1
    • Description: connects an association to the subject of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • predicate 1..1
    • Description: A high-level grouping for the relationship type. AKA minimal predicate. This is analogous to category for nodes.
    • Range: PredicateType
  • object 1..1
    • Description: connects an association to the object of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • negated 0..1
    • Description: if set to true, then the association is negated i.e. is not true
    • Range: Boolean
  • qualifiers 0..*
    • Description: connects an association to qualifiers that modify or qualify the meaning of that association
    • Range: OntologyClass
  • publications 0..*
    • Description: One or more publications that report the statement expressed in an Association, or provide information used as evidence supporting this statement.
    • Range: Publication
  • has evidence 0..*
    • Description: connects an association to an instance of supporting evidence
    • Range: EvidenceType
  • knowledge source 0..1
    • Description: An Information Resource from which the knowledge expressed in an Association was retrieved, directly or indirectly. This can be any resource through which the knowledge passed on its way to its currently serialized form. In practice, implementers should use one of the more specific subtypes of this generic property.
    • Range: InformationResource
  • primary knowledge source 0..1
    • Description: The most upstream source of the knowledge expressed in an Association that an implementer can identify. Performing a rigorous analysis of upstream data providers is expected; every effort is made to catalog the most upstream source of data in this property. Only one data source should be declared primary in any association. “aggregator knowledge source” can be used to caputre non-primary sources.
    • Range: InformationResource
  • aggregator knowledge source 0..*
    • Description: An intermediate aggregator resource from which knowledge expressed in an Association was retrieved downstream of the original source, on its path to its current serialized form.
    • Range: InformationResource
  • timepoint 0..1
    • Description: a point in time
    • Range: TimeType
  • original subject 0..1
    • Description: used to hold the original subject of a relation (or predicate) that an external knowledge source uses before transformation to match the biolink-model specification.
    • Range: String
  • original predicate 0..1
    • Description: used to hold the original relation/predicate that an external knowledge source uses before transformation to match the biolink-model specification.
    • Range: Uriorcurie
  • original object 0..1
    • Description: used to hold the original object of a relation (or predicate) that an external knowledge source uses before transformation to match the biolink-model specification.
    • Range: String
  • type 0..*
  • 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}

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..*
  • description 0..1
    • Description: a human-readable description of an entity
    • Range: NarrativeText
    • in subsets: (translator_minimal)
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Inherited from macromolecular machine mixin:

  • name 0..1
    • Description: A human-readable name for an attribute or entity.
    • Range: LabelType
    • in subsets: (translator_minimal,samples)

Domain for slot:

  • object 1..1
    • Description: connects an association to the object of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • predicate 1..1
    • Description: A high-level grouping for the relationship type. AKA minimal predicate. This is analogous to category for nodes.
    • Range: PredicateType
  • subject 1..1
    • Description: connects an association to the subject of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing