◀ Documentation HubConcept GovernanceConcept Types & Hierarchy Rules
Chapter 03 · Semantic governance specification

Concept Types
& Hierarchy Rules

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 governance

01. Three distinct graph responsibilities

Shared Knowledge

Concept Graph

Reusable semantic definitions, controlled versions, source mappings, and composition rules. Owned by the designated administrative authority.

Project Scope

Project Knowledge Graph

Project-specific IFC instances, spreadsheets, ontology mappings and references to selected Concept revisions. Project data does not silently modify global Concepts.

Process Scope

IDM Graph

Use Case prerequisites, information exchanges, responsible parties, BPMN activities and associated BCF topics. Dependencies between Use Cases are not Concept parent-child rules.

02. Proposed Concept type system

The following is a classification proposal for review, not an enumeration of types already enforced in production.

TypePurposeIllustrative examplesPotential root?
DomainHigh-level area of knowledge and groupingBuilding Services, AccessibilityYes, if approved
SystemFunctional building systemHeating SystemsPolicy-dependent
ElementPhysical or logical objectBoilers, DoorsNormally contextual
RequirementInformation requirement or acceptance conditionDoor fire-rating requirementNormally no
Property GroupStructured group of propertiesProperty SetNo
PropertyNamed data attributeFireRating, NominalWidthNo
Classification / ReferenceLink to external semantics or classificationsIFC class, bSDD referencePolicy-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.

03. Typed hierarchy and rule evaluation

Heating SystemsSystem · Draft revision 1BoilersALLOWS_CHILD · pilot allowedAccessibilityNo allowlist match · blockedDraft-mode rule outcome ≠ production publication approval

ALLOWS_CHILD

Explicitly permits a child under a parent in a selected rule revision and evaluation mode. Supported in the 7.8.53 pilot example.

EXCLUDES

Explicit negative rule, interpreted with the governing rule-set semantics. Direct handling exists in the pilot scope.

REQUIRES / PRECEDES

Dependency and ordering constraints that need separate validation semantics. Not implemented in the persisted pilot evaluator.

Root eligibility

Root validation requires a dedicated policy. A pilot graph anchor is not proof that a Concept is approved as a root.

04. Decision sequence for a graph edit

1 · Resolve identity

Determine exact Concept ID, authority and revision, not merely an ambiguous display label.

2 · Select scope

Apply global versus project rules and Draft versus Published evaluation mode.

3 · Check type and root policy

Validate proposed parent/child type pairing and approved root status.

4 · Evaluate explicit rules

Check allowlists and exclusions; later extend to requirements, ordering and global graph invariants.

5 · Explain decision

Return allow / deny / unknown with rule reference, source Concept revision and explanation.

6 · Keep provenance

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.

05. Administrator: create or correct a Concept

New Concept

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.

Correct Existing Concept

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.

New data source arrives

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.

06. Permissions and federated ownership

ActionAdministratorBIM ManagerStandard User
Create or publish global Concept revisionsAuthorizedNot authorizedNot authorized
Compose project Use Cases with approved ConceptsAuthorizedAuthorizedNot authorized
Compose project IDM from approved reference Use CasesAuthorizedAuthorizedAuthorized
View restricted provider resourcesRequires 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.

07. Current verified baseline and open specification questions

Observed 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.

Not yet established

Fully enforced type taxonomy, approved root policy, REQUIRES / PRECEDES graph execution, tenant isolation, distributed query authorization and production-level impact analysis.

Questions to resolve together

  1. Should domain Concepts always be root-eligible, or only when the administrator explicitly approves them?
  2. Can an Element Concept appear under multiple parents without becoming a separate Concept identity?
  3. Do we enforce a strict hierarchy or a directed graph with multiple relation types?
  4. What is the minimal publish checklist for a new Concept revision?
  5. How are project-specific constraints separated from global Concept-definition changes?

← Return to Concept Governance · Documentation Hub