Playground¶
Self-contained examples for each converter. Located at playground/ in the project root.
See playground/README.md for the full reference including TriG vs Turtle explanation, SPARQL examples, and configuration details.
Quick start¶
Scripts¶
| Script | Converter | Format | Config |
|---|---|---|---|
run-archimate-trig.sh |
ArchiMate | TriG | none |
run-archimate-ttl.sh |
ArchiMate | Turtle | none |
run-bpmn-full-trig.sh |
BPMN | TriG | none |
run-bpmn-full-ttl.sh |
BPMN | Turtle | none |
run-bpmn-lite-trig.sh |
BPMN | TriG | config/type-mapping-bpmn-lite.yml |
run-plantuml-class-trig.sh |
PlantUML | TriG | none |
run-plantuml-class-ttl.sh |
PlantUML | Turtle | none |
run-plantuml-sequence-trig.sh |
PlantUML | TriG | none |
run-leanix-trig.sh |
LeanIX | TriG | config/type-mapping-leanix.yml (second run) |
run-leanix-pull.sh |
— (fetches, converts nothing) | — | config/leanix-pull.yml |
run-leanix-trig.sh also passes --emit-stakeholders, so the output shows arch:conceptOwner pointing at
the accountable subscriber and not the responsible one. run-leanix-pull.sh introspect reads a real
workspace's schema and writes a configuration from it, which is the step that removes the guesswork about
relation field names.
run-leanix-pull.sh is the one script that talks to a live system, so it needs LEANIX_API_TOKEN and
LEANIX_SUBDOMAIN and is deliberately left out of run-all.sh — otherwise "run the playground"
would fail for everyone without a LeanIX tenant. Without credentials it prints the GraphQL queries it
would send instead, which is the half worth reading: fact sheet fields and relation names are configured
per workspace, so the only way to know whether a query is right is to try it in your own GraphiQL.