Chapter 04 · Administrator guide · Design specification

Concept Creation, Correction & Versioning

A controlled lifecycle for creating reusable semantic concepts, improving existing definitions, integrating emerging data sources and protecting published Use Cases from unintended change.

Concept IdentityDraft → Review → PublishImmutable ReferencesSource ProvenanceFederation Ready

OpenSPAD 7.8.53 baseline · Target design and pilot behavior explicitly distinguished · 17 October 2026

04.1 · Operating principles

Govern the shared library. Never silently rewrite project history.

Stable identity

Concept identity survives across revisions. Each published revision is a separately addressable, immutable snapshot.

Scoped knowledge

Global Concepts are administered centrally or by their authorized owner. Project-specific data can map to them without altering their definitions.

Validated relationships

Directed parent/child edges, typed relations, root eligibility and cycle constraints are evaluated against versioned business rules.

Traceable change

Every proposed correction records rationale, source evidence, reviewers and impact on dependent Use Cases.

Design decision: The graph may contain multiple valid parents; the tree is a navigational projection, not the storage model. Global Concept changes require administrator authority.
04.2 · Concept graph model

Separate identity, revisions, evidence and usage

This proposed logical model avoids conflating a global Concept with its current version or a project's local interpretation.

Concept identityURI / owner / scopePublished revisionVersion 1 · immutableDraft revisionVersion 2 · proposedUse Case snapshotPinned to published revision 1Source & rule evidenceMappings · provenance · constraintsTarget logical design · relationship labels and schema subject to implementation review

Identity

concept_id, stable URI, responsible authority, semantic domain, global/project scope.

Revision

Revision ID, state, classes/properties, rule set version, source mappings, rationale and timestamps.

References

Use Cases refer to explicit revision snapshots rather than an unqualified “latest” revision.

04.3 · Administrator procedure A

Create a new Concept

Example: “Heat Pump” is not represented by a reusable Concept, but appears in a manufacturer catalog or an IFC project model.

01 / REQUESTIdentify gapPropose a new Concept from reviewed source evidence.
02 / IDENTITYAssign identityDetermine owning authority, scope, type and stable URI.
03 / CONTENTDescribe semanticsDefine labels, classes, Psets, properties and intended use.
04 / GRAPHSet relationshipsReview roots, parent candidates, ALLOWS_CHILD and exclusions.
05 / REVIEWAudit qualityCheck duplicates, cycles, rules, provenance and mapping confidence.
06 / RELEASEPublish revisionApprove version 1 and expose it to authorized users.
Governance requirement: A project IFC upload, IDS import or external supplier must never publish a new shared Concept automatically. Imported content first creates evidence or a proposal for administrator review.
04.4 · Administrator procedure B

Correct an existing Concept

Example: a published “Door” Concept is missing a property mapping found in an updated classification or IFC schema source.

Published v1Existing referencesDraft v2Changes proposedReviewDiff + impact auditPublished v2New consumers opt inPreviously pinned Use Cases remain bound to revision v1
01CloneStart a new Draft from a selected published revision.
02ChangeEdit description, source mappings, class/property scope or relationships.
03CompareShow a structured diff with added, removed and changed elements.
04Assess impactList dependent Concepts and Use Cases; detect compatibility risks.
05ApprovePublish only after administrator approval and graph validation.
04.5 · Versions & promotion

Versioned knowledge without forced migration

StateMeaningAllowed behavior
DraftEditable candidate revisionAdmin review and pilot tests; not a generally approved production rule.
In ReviewTarget governance stateQuality checks, source/impact review, rule validation.
PublishedReleased, immutable revisionAvailable to authorized Use Case composition and consumers.
DeprecatedDiscouraged for new workExisting pinned Use Cases continue to resolve their snapshots.
Version policy: Revisions and Concept identity are distinct; changing source evidence or a rule must produce a reviewable proposal, not silent mutation of a published Use Case.
04.6 · Source evolution

New data sources enrich knowledge through proposals

SourcesIFC · Excel · IDSOWL · API · ProductsNormalizeCanonical graphProvenanceAlign & proposeMatch / conflictConfidence + evidenceAdmin decisionAccept / defer / rejectCreate new revisionFuture architecture · change detection, federation sync and granular permissions not yet production-verified

Record at least source identifier, server identity, original URI/GlobalId, import timestamp, model/release version, mapping method, transformation version and licensing/access constraints. Resolve potential duplicates by alignment before creating new shared nodes.

04.7 · Use Case impact control

A published Concept is a dependency, not a moving target

Snapshot stability

A project Use Case pins Concept revision IDs and rule-set revisions relevant to its creation.

Impact analysis

Before publishing a correction, report affected Use Cases, incompatible mappings and newly available properties.

Controlled upgrade

Propose migrations and compare old/new results. A BIM Manager accepts project changes within their permissions; global definition remains admin-controlled.

Open decision: Should reference Use Cases auto-recommend the newest published Concept revision, or require explicit manual upgrade? Recommended default: recommend, never silently migrate.
04.8 · Governance and access

Keep authoring authority separate from project use

ActionAdministratorBIM ManagerStandard User
Create or correct global ConceptAllowedNot allowedNot allowed
Review/publish Concept revisionAllowedNot allowedNot allowed
Register federation/source adapterAllowedUse approved sourcesUse via references
Compose project Use CasesAllowedAllowedNot allowed
Assemble reference Use Cases into project IDMAllowedAllowedAllowed
Operate backups and global policiesAllowedNot allowedNot allowed

Future: Tenant ownership, provider-managed selective disclosure and fine-grained resource permissions must be enforced across APIs, federated queries, search indexes, caches and exports. This is not part of verified 7.8.53 security enforcement.

04.9 · Evidence & implementation boundaries

Current pilot versus target specification

CapabilityMaturityEvidence / limitation
Concept editor with revision-oriented flowPilot7.8.41 module and observed Draft/Published snapshots; complete governance workflow not yet demonstrated.
Stored rule reading and direct child checksVerified pilot7.8.52/53 tested with “Heating Systems” → “Boilers” allowed; “Accessibility” blocked in Draft mode.
Published-mode production rule enforcementNot verifiedDraft pilot rules are not production approval; publication validation remains to be demonstrated.
REQUIRES / PRECEDES / full root and cycle validationPlannedNot implemented by direct 7.8.53 pilot checks.
Impact audit and automated source change proposalsPlannedTarget governance capability.
Federated concept authority and tenant permissionsFuture architectureDocumented design only, not deployed.

The publicly deployed documentation describes intent and evidence; it must not be used as proof that every UI control, API or validation rule is in production.