Explore a model
DiCon 0.5 module map
No nodes match. Clear filters to restore this example.
Drag a node to pin its position. Drag the background to pan; scroll to zoom. Node size shows connection count, not influence. Solid lines are verified ontology imports; dashed lines are editorial catalogue/model relations. Use the cards for the same information without the diagram.
Cards follow the filters. JSON contains the complete case: nodes, connections, provenance and correction notes. CSV contains all nodes and their fields, with arrays and objects encoded as JSON; it does not contain connections or case-level notes. The diagram download contains the current view.
HS2 RDF record
The graph and all RDF views share the same dataset. Turtle contains the complete HS2 case, including its snapshot description, sources and original values for corrected metadata. This is valid RDF syntax; formal consistency and the truth of the project assertions are separate questions.
Search the RDF triples
| Subject | Predicate | Object |
|---|
Read the complete Turtle text
How to read this example · corrections · provenance
Read the arrow before the picture
An ontology supplies names and constraints for concepts and relationships. A case model chooses which real or illustrative things to describe with those terms. A source supporting a fact does not automatically validate its ontology mapping.
An import makes another ontology’s definitions available. A role is something an agent bears. An appointment records a relationship between an appointing and an appointed party. The diagram layout is only an aid to reading.
To share the interactive example, use this page’s link. Discussion tools such as Loomio may remove scripts from pasted content; use a link, or an iframe only where the host permits it.
Corrections in this case
Full retention and verification record · Versioned ontology source hashes · DiCon 0.5 specification