What LinkML cannot state
explanations/what-linkml-cannot-stateNobody has checked this yet
still a draft
Written 2026-11-06 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- About
- Pointed to by
- Rosetta metadata (related to)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/common-domain-model/knowledge/explanations/what-linkml-cannot-state- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
What LinkML cannot state
Section titled “What LinkML cannot state”About half of the CDM’s conditions are stated, and each class’s comments name the rest, with their Rosetta text.1 just linkml-report counts them and gives the reasons.2
A <> condition is stated, as a none_of over the equality it denies, because Rune reads null <> X as true. Rune also reads a comparison with an absent value as false, so a comparison on an optional attribute requires that attribute too.1