Skip to content

What each Rosetta construct becomes

Explanationexplanations/rosetta-to-linkml

Nobody 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
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/common-domain-model/knowledge/explanations/rosetta-to-linkml
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

docs/about.md holds the table, one row per Rosetta construct.1 A Rosetta condition binds every subtype. The JSON Schema generator applies an ancestor’s rules to a subclass itself, but reads a class expression from the class alone, so the converter states each ancestor’s class expressions again on every subtype and leaves its rules to the generator.1

A name two Rosetta namespaces declare takes the last part of its namespace as a prefix, as in CsaAdditionalTerminationEvent.2

  1. .linkml/docs/about.md, What each Rosetta construct becomes ↩ ↩2

  2. .linkml/scripts/rosetta_to_linkml.py ↩