Skip to the three cases

Early essai · Digital Construction ontology

What can an ontology say about a project?

And what must we still supply before it can explain the work required?

Start with a vocabulary, then inspect two project models. The DiCon module map, Tokyo stadium and HS2 roles keep their own contexts. Together they test a preliminary question behind Solway’s aim: an explainable work breakdown from an intended outcome, with a fair comparison to PDDL planning.

Before the work breakdown

Built — but ready for what?

A shelter gives climbers somewhere to wait out the night. Its walls, its sheltering function and a night spent inside are three different things. Bring that distinction to Solway’s tiny installation.

Explore the three source cases ↓

Select a box or an arrow to inspect its meaning. This is a supplied teaching model; no actual use has been observed.

People choose what “complete” will mean. Intended use prompts this choice; the vocabulary does not generate the conditions.

Derived · in the linked plannerA description is still incomplete

An installed item alone does not establish the selected handover conditions.

Inspect the complete Unit A plan →

Physical-only view: inspection evidence and a clear site have not been established.

Read a relationship

The arrow carries a claim

Select any box or arrow. The physical item, a stated function, chosen acceptance conditions and observed benefit stay separate.

Observed benefit · still an open question

Even a solved handover plan does not demonstrate service in operation. Inspection evidence is modelled; reliability, user benefit and actual tunnel operation are not.

Where this distinction comes from · inspect the local statements

The shelter study contributes object → function ← use: the shelter has a purpose; a particular use episode may realise it. Being occupied alone establishes neither successful sheltering nor survival. For Solway, the service label and the bridge to completion are authored illustrations.

A refuge halfway up a cliff

Toy scenario

The shelter is intended for occasional benighted climbers. Its setting connects the intended use to conditions that a parts list would miss:

Supplied shelter constraints and what they concern
Supplied conditionRelationship to inspect
Helicopter payloadConstrains the airlift and the mass of the panel batch it carries.
Wind exposureConstrains the shelter structure, including its anchoring.
Occupancy limitConstrains the permitted people and duration of a use episode.
Severe weatherMotivates the refuge while also constraining the airlift needed to build it.

With supplied methods and acceptance rules, these constraints can require lifting, access, inspection or maintenance work beyond the finished object's parts. The conditions and rules must be stated before that work can be derived; this diagram calculates no shelter plan.

BFO supplies upper-level distinctions. DiCon 0.5 Function, bearerOf and realizes provide relevant vocabulary. This diagram uses explicitly local relationships for intended function and possible use; it asserts no actual realisation or full BFO conformance.

@prefix example: <https://solway.example/purpose-use#> .
example:unitA example:hasIntendedFunction example:tunnelService .
example:plannedUse example:wouldRealize example:tunnelService .
example:handoverProfile example:requiresCondition example:installedA,
    example:inspectionEvidenceA, example:temporaryAccessAbsent .

The first two statements express the supplied teaching relationships. The final statement records a chosen profile; it is not inferred from them. Read the adaptation and verification record.

Read the sources

The Digital Construction 0.5 suite supplies terms and module imports. The project examples add selected facts, local relationships and evidence links. Their saved source hashes and retention record make those choices inspectable.

What these cases show

Imports connect definitions; they are not task dependencies. Tokyo separates objects, activities and information across several periods. HS2 separates an agent, its role and an appointment in a historical snapshot. Each arrow has a meaning to check against its source.

What is still missing

To explain necessary work we must supply the desired end state, initial and local conditions, accepted methods with preconditions and effects, and acceptance rules. These graphs do not derive work, perform new ontology inference or verify the project assertions empirically.

Continue to The work that must exist for a bounded construction that supplies those ingredients and compares ontology with executable PDDL. Its method and limits explain why the comparison establishes planning parity within that model, not ontology superiority.

Explore a model

DiCon 0.5 module map

Connections

Show node types · colour key
Ontology graphSelect a node in the searchable card list for a keyboard-accessible description of every connection.

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.

Node cards

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.

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

    Retention and verification source (Markdown) · Versioned ontology source hashes · DiCon 0.5 specification