Link

Class: Zygosity

URI: biolink:Zygosity


img


Parents

  • is_a: 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.

Referenced by class

Attributes

Inherited from attribute:

  • attribute➞name 0..1
    • Description: The human-readable ‘attribute name’ can be set to a string which reflects its context of interpretation, e.g. SEPIO evidence/provenance/confidence annotation or it can default to the name associated with the ‘has attribute type’ slot ontology term.
    • Range: LabelType
  • has attribute type 1..1
    • Description: connects an attribute to a class that describes it
    • Range: OntologyClass
    • in subsets: (samples)
  • has quantitative value 0..*
    • Description: connects an attribute to a value
    • Range: QuantityValue
    • in subsets: (samples)
  • has qualitative value 0..1
    • Description: connects an attribute to a value
    • Range: NamedThing
    • in subsets: (samples)

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
    • Description: a lightweight analog to the association class ‘has provider’ slot, which is the string name, or the authoritative (i.e. database) namespace, designating the origin of the entity to which the slot belongs.
    • Range: LabelType
    • in subsets: (translator_minimal)
  • provided by 0..*
    • Description: connects an association to the agent (person, organization or group) that provided it
    • Range: Agent
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Other properties

     
Exact Mappings:   GENO:0000133