forked from biolink/biolink-model
-
Notifications
You must be signed in to change notification settings - Fork 0
/
disease_or_phenotypic_feature_config.yaml
63 lines (63 loc) · 2.93 KB
/
disease_or_phenotypic_feature_config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
# metamodel_version: 1.7.0# version: 3.0.3id: disease_or_phenotypic_feature
schema_generating: true
description: Either one of a disease or an individual phenotypic feature. Some knowledge
resources such as Monarch treat these as distinct, others such as MESH conflate. Please
see definitions of phenotypic feature and disease in this model for their independent
descriptions. This class is helpful to enforce domains and ranges that may involve
either a disease or a phenotypic feature.
display_name: disease or phenotypic feature
document_category: disease or phenotypic feature
weight: 20
fields:
- id: id
description: A unique identifier for an entity. Must be either a CURIE shorthand
for a URI or a complete URI
display_name: id
- id: iri
description: An IRI for an entity. This is determined by the id using expansion
rules.
display_name: iri
- id: type
display_name: type
- id: name
description: A human-readable name for an attribute or entity.
display_name: name
- id: description
description: a human-readable description of an entity
display_name: description
- id: source
display_name: source
- id: has_attribute
description: connects any entity to an attribute
display_name: has attribute
cardinality: multi
- id: provided_by
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.
display_name: provided by
cardinality: multi
- id: xref
description: Alternate CURIEs for a thing
display_name: xref
cardinality: multi
- id: category
description: "Name of the high level ontology class in which this entity is categorized.\
\ Corresponds to the label for the biolink entity type class.\n * In a neo4j database\
\ this MAY correspond to the neo4j label tag.\n * In an RDF database it should\
\ be a biolink model class URI.\nThis 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`,\
\ ...\nIn 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}"
display_name: named thing_category
cardinality: multi
- id: in_taxon
description: connects an entity to its taxonomic classification. Only certain kinds
of entities can be taxonomically classified; see 'thing with taxon'
display_name: in taxon
cardinality: multi