You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: json-schema-autogen/bke_taxonomy.json
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2409,7 +2409,7 @@
2409
2409
},
2410
2410
"GeneAnnotation": {
2411
2411
"additionalProperties": false,
2412
-
"description": "An annotation describing the location, boundaries, and functions of individual genes within a genome annotation.",
2412
+
"description": "Represents a single gene. Includes metadata about the gene, such as its molecular type and the genome annotation it was referenced from.",
2413
2413
"properties": {
2414
2414
"category": {
2415
2415
"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}. NOTE: The category slot was modified to have a curie range and a pattern for bican categories.",
@@ -2531,7 +2531,7 @@
2531
2531
"type": "string"
2532
2532
}
2533
2533
],
2534
-
"description": "The genome annotation that this gene annotation was referenced from.",
2534
+
"description": "The genome annotation that this gene was referenced from.",
2535
2535
"type": "string"
2536
2536
},
2537
2537
"source_id": {
@@ -2724,7 +2724,7 @@
2724
2724
},
2725
2725
"GenomeAnnotation": {
2726
2726
"additionalProperties": false,
2727
-
"description": "Location and nomenclature of genes and all of the coding regions in a genome assembly and the classification of genes and transcripts into types.",
2727
+
"description": "Represents a genome annotation. Includes metadata about the genome, such as its version and reference assembly.",
2728
2728
"properties": {
2729
2729
"authority": {
2730
2730
"$ref": "#/$defs/AuthorityType",
@@ -2911,7 +2911,7 @@
2911
2911
},
2912
2912
"GenomeAssembly": {
2913
2913
"additionalProperties": false,
2914
-
"description": "Genome assembly to contain version and label information",
2914
+
"description": "Represents a genome assembly. A genome assembly is a computational representation of a genome sequence.",
2915
2915
"properties": {
2916
2916
"category": {
2917
2917
"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}. NOTE: The category slot was modified to have a curie range and a pattern for bican categories.",
id: str = Field(default=..., description="""A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI""", json_schema_extra = { "linkml_meta": {'alias': 'id',
0 commit comments