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
For example, when serialized in YAML, a LinkML schema does not need to declare the name or text of its entities. In fact, it bloats the files and is a potential source of conflict (relative to the out-dented key that introduces the thing that bears some name or text)
For example, this:
enums:
AeroStrucEnum:
name: AeroStrucEnumdescription: permissible values, used by term aero_strucfrom_schema: https://w3id.org/mixspermissible_values:
glider:
text: gliderplane:
text: planeAnimalBodyCondEnum:
name: AnimalBodyCondEnumdescription: permissible values, used by term animal_body_condfrom_schema: https://w3id.org/mixspermissible_values:
normal:
text: normalover conditioned:
text: over conditionedunder conditioned:
text: under conditioned
could be
enums:
AeroStrucEnum:
description: permissible values, used by term aero_strucfrom_schema: https://w3id.org/mixspermissible_values:
glider:
plane:
AnimalBodyCondEnum:
description: permissible values, used by term animal_body_condfrom_schema: https://w3id.org/mixspermissible_values:
normal:
over conditioned:
under conditioned:
The text was updated successfully, but these errors were encountered:
For example, when serialized in YAML, a LinkML schema does not need to declare the
name
ortext
of its entities. In fact, it bloats the files and is a potential source of conflict (relative to the out-dented key that introduces the thing that bears somename
ortext
)For example, this:
could be
The text was updated successfully, but these errors were encountered: