A typed, versioned and governed semantic composition model: which Concepts can start a graph, which may follow another Concept, and which combinations must be rejected.
Current baseline 7.8.53Pilot vs target designAdministrator governanceReusable semantic definitions, controlled versions, source mappings, and composition rules. Owned by the designated administrative authority.
Project-specific IFC instances, spreadsheets, ontology mappings and references to selected Concept revisions. Project data does not silently modify global Concepts.
Use Case prerequisites, information exchanges, responsible parties, BPMN activities and associated BCF topics. Dependencies between Use Cases are not Concept parent-child rules.
The following is a classification proposal for review, not an enumeration of types already enforced in production.
| Type | Purpose | Illustrative examples | Potential root? |
|---|---|---|---|
| Domain | High-level area of knowledge and grouping | Building Services, Accessibility | Yes, if approved |
| System | Functional building system | Heating Systems | Policy-dependent |
| Element | Physical or logical object | Boilers, Doors | Normally contextual |
| Requirement | Information requirement or acceptance condition | Door fire-rating requirement | Normally no |
| Property Group | Structured group of properties | Property Set | No |
| Property | Named data attribute | FireRating, NominalWidth | No |
| Classification / Reference | Link to external semantics or classifications | IFC class, bSDD reference | Policy-dependent |
Type and root eligibility are separate properties. The same type can have different root permissions depending on its domain, active Concept revision and governing rule set.
Explicitly permits a child under a parent in a selected rule revision and evaluation mode. Supported in the 7.8.53 pilot example.
Explicit negative rule, interpreted with the governing rule-set semantics. Direct handling exists in the pilot scope.
Dependency and ordering constraints that need separate validation semantics. Not implemented in the persisted pilot evaluator.
Root validation requires a dedicated policy. A pilot graph anchor is not proof that a Concept is approved as a root.
Determine exact Concept ID, authority and revision, not merely an ambiguous display label.
Apply global versus project rules and Draft versus Published evaluation mode.
Validate proposed parent/child type pairing and approved root status.
Check allowlists and exclusions; later extend to requirements, ordering and global graph invariants.
Return allow / deny / unknown with rule reference, source Concept revision and explanation.
Record who proposed the edit, evidence, review outcome and pinned dependencies.
Fail-safe design: In a Published workflow, missing or unresolved authoritative rules must not be interpreted as permission. The current Draft pilot and production policy must remain separate.
Define identity and type → select governing sources → describe intended parent/child placement → propose explicit rules → validate conflicts → submit for review → publish approved revision.
Design status: Target workflow; existing editor and rule-lab functions provide only part of this flow.
Open exact version → create new Draft revision → amend semantics / source alignments / rule definitions → inspect impact on dependent Use Cases → approve and publish while preserving prior snapshots.
Design status: Versioned editing exists; complete impact analysis and governance are planned.
A newly registered IFC, OWL, bSDD, IDS, Excel or external API source contributes provenance-aware graph candidates. Alignment proposals are reviewed against existing Concepts; source metadata may be added to a new Concept revision. No importer may silently publish a new global Concept.
| Action | Administrator | BIM Manager | Standard User |
|---|---|---|---|
| Create or publish global Concept revisions | Authorized | Not authorized | Not authorized |
| Compose project Use Cases with approved Concepts | Authorized | Authorized | Not authorized |
| Compose project IDM from approved reference Use Cases | Authorized | Authorized | Authorized |
| View restricted provider resources | Requires explicit resource-level authorization in the future multi-tenant design | ||
Federation will distinguish provider-owned resources, tenant-scoped graph fragments, published semantic identifiers, and fine-grained access policies. These protections are future architecture, not verified production enforcement in 7.8.53.
Persisted Concept Graph pilot route; Draft revision rule reading; direct ALLOWS_CHILD / EXCLUDES behavior; allowing Boilers beneath Heating Systems and rejecting Accessibility in the pilot example.
Fully enforced type taxonomy, approved root policy, REQUIRES / PRECEDES graph execution, tenant isolation, distributed query authorization and production-level impact analysis.