obsolete haplotype block [GENO_0000916]

A sequence feature representing a region of the genome over which there is little evidence for historical recombination, such that sequences it contain are typically co-inherited/transmitted across generations. A haplotype block is a class of genomic sequence defined by a lack of evidence for historical recombination, such that sequence alterations within it tend to be co-inherited across successive generations. A haplotype is considered to be one of many possible versions of a ‘haplotype block’ - defined by the set of co-inherited alterations it contains. In this sense, the relationship between ‘haplotype’ and ‘haplotype block’ is analogous to the relationship between ‘gene allele’ and ‘gene’* - a ‘gene allele’ is one of many possible instances of a ‘gene’, while a ‘haplotype’ is one of many possible instances of a ‘haplotype block’. The boundaries of haplotype blocks are defined in efforts to identify haplotypes that exist in organisms or populations. A haplotype block may span any number of sequence alterations, and may cover small or large chromosomal regions - depending on the number of recombination events that have occurred between the alterations defining the haplotype. ———————– * One difference however is that gene instnaces are necessarily ‘functional’ - so non-functional alleles of a gene locus wont qualify as gene instances. no such requirement exists for haplotype block instnaces.

Open obsolete haplotype block in VFB

Term Information

  • ID: GENO_0000916
  • Name: obsolete haplotype block
  • Definition: A sequence feature representing a region of the genome over which there is little evidence for historical recombination, such that sequences it contain are typically co-inherited/transmitted across generations.
  • Synonyms:
  • Type:
  • Comment: A haplotype block is a class of genomic sequence defined by a lack of evidence for historical recombination, such that sequence alterations within it tend to be co-inherited across successive generations. A haplotype is considered to be one of many possible versions of a ‘haplotype block’ - defined by the set of co-inherited alterations it contains. In this sense, the relationship between ‘haplotype’ and ‘haplotype block’ is analogous to the relationship between ‘gene allele’ and ‘gene’* - a ‘gene allele’ is one of many possible instances of a ‘gene’, while a ‘haplotype’ is one of many possible instances of a ‘haplotype block’. The boundaries of haplotype blocks are defined in efforts to identify haplotypes that exist in organisms or populations. A haplotype block may span any number of sequence alterations, and may cover small or large chromosomal regions - depending on the number of recombination events that have occurred between the alterations defining the haplotype. ———————– * One difference however is that gene instnaces are necessarily ‘functional’ - so non-functional alleles of a gene locus wont qualify as gene instances. no such requirement exists for haplotype block instnaces.

VFB Term Json

{
    "term": {
        "core": {
            "iri": "http://purl.obolibrary.org/obo/GENO_0000916",
            "symbol": "",
            "types": [
                "Entity",
                "Class",
                "Deprecated"
            ],
            "short_form": "GENO_0000916",
            "unique_facets": [
                "Deprecated"
            ],
            "label": "obsolete haplotype block"
        },
        "description": [
            "A sequence feature representing a region of the genome over which there is little evidence for historical recombination, such that sequences it contain are typically co-inherited/transmitted across generations."
        ],
        "comment": [
            "A haplotype block is a class of genomic sequence defined by a  lack of evidence for historical recombination, such that sequence alterations within it tend to be co-inherited across successive generations. A haplotype is considered to be one of many possible versions of a 'haplotype block' - defined by the set of co-inherited alterations it contains.  In this sense, the relationship between 'haplotype' and 'haplotype block' is analogous to the relationship between 'gene allele' and 'gene'* - a 'gene allele' is one of many possible instances of a 'gene', while  a 'haplotype' is one of many possible instances of a 'haplotype block'.\n\nThe boundaries of haplotype blocks are defined in efforts to identify haplotypes that exist in organisms or populations. A haplotype block may span any number of sequence alterations, and may cover small or large chromosomal regions - depending on the number of recombination events that have occurred between the alterations defining the haplotype.\n\n-----------------------\n\n* One difference however is that gene instnaces are necessarily 'functional' - so non-functional  alleles of a gene locus wont qualify as gene instances. no such requirement exists for haplotype block instnaces."
        ]
    },
    "query": "Get JSON for Class",
    "version": "c58c844",
    "parents": [],
    "relationships": [],
    "related_individuals": [],
    "xrefs": [],
    "anatomy_channel_image": [],
    "pub_syn": [],
    "def_pubs": [
        {
            "core": {
                "symbol": "",
                "iri": "http://flybase.org/reports/Unattributed",
                "types": [
                    "Entity",
                    "Individual",
                    "pub"
                ],
                "short_form": "Unattributed",
                "unique_facets": [
                    "pub"
                ],
                "label": ""
            },
            "FlyBase": "",
            "PubMed": "",
            "DOI": ""
        }
    ]
}