Define, compose and maintain semantically meaningful Concepts across data sources, projects and future federated servers — with traceable revisions and controlled publication.
A Concept is a reusable, identifiable, semantically enriched building block from which OpenSPAD assembles information requirements and Use Cases. It is not merely a label, an IFC class, an OWL class or a source-file row.
Identity, label, definition, domain, classification and relationships to source ontologies.
Classes, property sets, properties and possible constraints, linked to provenance.
Revision, approval state, combination rules and stable references from Use Cases.
The canonical property graph represents Concept identity separately from its revisions and source-specific evidence. This diagram is the target conceptual model; individual relationships may not yet exist in the stored 7.8.53 schema.
A stable Concept identity can have multiple revisions. A Use Case should retain a reference to the revision it was created with until an explicit migration is approved.
Do not confuse class membership, source alignment, Concept hierarchy and a workflow dependency between two Use Cases. Each is a distinct edge type with distinct governance.
A new Concept is reviewed before publication. A correction produces a new revision, preserving existing published references and allowing administrators to assess the impact.
ALLOWS_CHILD → Boilers relationship in the 7.8.53 pilot. Changing allowed children should create and evaluate a new draft revision; already saved Use Cases must not be silently rewritten.The persisted graph pilot evaluates direct ALLOWS_CHILD / EXCLUDES rules from selected revisions. A permitted child in the draft pilot is not automatically production-approved.
Broaden rule evaluation to include root eligibility, Concept types, multi-hop dependencies, REQUIRES, PRECEDES, global exclusions, cycle detection and explainable failure traces.
Use Case workflow dependencies must remain separate from Concept-child rules.
| Input | Evaluation | Output |
|---|---|---|
| Parent revision + candidate child | Selected revision, publishing mode, direct rule set | Allowed / blocked, reason, responsible rule, provenance |
| Composite graph (future) | Root, type, dependency and global checks | Explainable validation findings and suggested repair |
External inputs produce normalized graph fragments and alignment candidates. They must not overwrite published Concept revisions or bypass governance.
General OWL ontologies, IFC schema definitions, classifications and published reference Concepts can be reused across projects.
An uploaded IFC model, Excel sheet or project ontology contributes to a project-specific graph. This does not automatically change global knowledge.
| Action | Administrator | BIM Manager | Standard User |
|---|---|---|---|
| Create / correct / publish global Concepts | Yes | No | No |
| Select approved Concepts in project Use Cases | Yes | Yes | Via references |
| Create / edit project Use Cases | Yes | Yes | No |
| Assemble approved Use Cases into IDM | Yes | Yes | Yes |
| Manage source registration / backup | Yes | No | No |
A manufacturer or partner may manage its own graph, expose only selected resource fragments and maintain its own revisions. Consumer servers link to authorized remote resources rather than assuming complete ownership of the provider’s data.
Global resource identifiers distinguish an entity from an aligned, equivalent or related entity on another server.
Each source owner controls published versions, availability and access policy for its resources.
Tenant isolation, resource-level permissions, authorized query federation and policy-aware caching are planned, not implemented in the 7.8.53 pilot.
| Capability | Assessment | Evidence / qualification |
|---|---|---|
| Concept Editor and revision-related routes | Code/routes observed | Registered in Administration; individual user flows require separate testing. |
| Persisted Rule Reader and Graph Pilot 7.8.52/53 | Pilot verified | Direct draft-mode rule evaluation and observed successful/blocked examples. |
| New-source alignment and global Concept approval workflow | Partly designed | Full end-to-end governance and change propagation not verified. |
| Cross-server Concept federation and multi-tenant policies | Future | Target architecture only. |
| Use Case revision migration and full rule engine | Planned | Root, multi-hop and global rule checks remain open. |