In LinkML enums are a special kind of element, distinct from TypeDefinition, ClassDefinition (even they are rendered as strings).
Sometimes it can be useful to bind an existing slot value to an enum.
One use case is when we have a generic Concept class that is typically non-lined, and referred to by id. We may want to have a slot usage that restricts the id to ne PVs in some contexts; e.g.
classes:
Concept:
attributes:
id:
identifier: true
name:
Biosample:
attributes:
name:
sample_material_type:
range: Concept
bindings:
- binds_value_of: id
range: ENVOMaterialEnum
strength: RECOMMENDED
description: Material type from the ENVO ontology
enums:
ENVOMaterialEnum:
description: Material type from the ENVO ontology
reachable_from:
source_ontology: obo:envo
source_nodes:
- ENVO:00010483 ## environmental material
is_direct: false
relationship_types:
- rdfs:subClassOf
In LinkML enums are a special kind of element, distinct from TypeDefinition, ClassDefinition (even they are rendered as strings).
Sometimes it can be useful to bind an existing slot value to an enum.
One use case is when we have a generic
Conceptclass that is typically non-lined, and referred to by id. We may want to have a slot usage that restricts the id to ne PVs in some contexts; e.g.See also https://build.fhir.org/terminologies-binding-examples.html