Integrate by graph meaning, not by file format.
Every data source contributes to a common semantic property graph model while retaining its identity, provenance, version and access permissions. A data source is not necessarily an ontology: a project IFC or Excel file is input data; an OWL graph may be a vocabulary and relationship source.
Sources are typed. Meaning is mapped.
IFC Schema & IFC Models
Schema classes and Psets are shared semantic references; model instances, GlobalIds, quantities and properties belong to individual projects.
IDS XML
Import specifications, applicability and requirements. Map constraints to concepts; validate expressible rules and export IDS with traceability.
OWL / RDF
Classes, properties and subclass relationships. Maintain ontology URI and version; do not confuse ontology definitions with project records.
Excel / JSON
Normalize rows, columns, units, identifiers and classifications as data; import custom properties with explicit mapping assumptions.
bSDD & NATSPEC
External classification, property and dictionary catalogs. Track provider namespaces, external IDs, versions and license requirements.
REST / GraphQL
Connector-specific authentication, pagination, incremental changes, rate limits, schema evolution and transformation mappings.
Manufacturer Data
Vendors publish governed product and specification fragments without transferring full internal databases.
BigQuery / Enterprise Data
Future enterprise connection using narrow, authorized extracts or queries; never imply a live integration without proof.
Important: this table is a connector and information-model specification. It does not certify that each integration is deployed or operational.
Every mapping must be explainable.
A canonical graph is an interoperability contract, not a requirement that every remote server copies the entire graph or uses identical physical storage. The target design separates references, project records and source evidence.
Identifiers
Stable internal graph IDs; source-scoped external IDs and URIs; IFC GlobalId where applicable; mapping identity and version.
Semantic references
Concept identity plus an immutable published revision; typed classes, property sets and properties; alignment confidence and reviewer decision.
Governance metadata
Provider, ingestion timestamp, source version, project/tenant scope, validity interval, access policy reference and evidence path.
Illustrative graph pattern (design, not existing schema guarantee)
(:SourceResource {uri, provider, version})
-[:SUPPLIES]-> (:GraphFragment {fragment_id, scope})
-[:CONTAINS]-> (:Entity {entity_id, external_id})
-[:MAPS_TO {method, score, reviewed}]-> (:ConceptVersion {concept_id, revision})
-[:HAS_PROPERTY]-> (:PropertyValue {value, unit, datatype})
(:UseCaseVersion)-[:REFERENCES_CONCEPT]->(:ConceptVersion)
(:ValidationResult)-[:EVALUATES]->(:Entity)These label and edge names illustrate an architectural contract. The existing OpenSPAD Neo4j model should be mapped deliberately rather than overwritten by the diagram.
From candidate match to governed relation.
Register connector, provider, source identity and scope.
Parse classes, properties, units and external identifiers.
Rank candidate Concepts with URI, lexical, structural and vector evidence.
Confirm, reject, defer or request a Concept correction.
Store mapping, reviewer, confidence, source and Concept revision.
Detect upstream changes and enqueue impact analysis.
Worked example: external door classification
Provider: bSDD
External Door
URI / class / semantic evidence
Maps to IFC Door
IFC Door → Psets → Properties
The alignment does not convert every bSDD item into a new root concept. Review and typed rules determine placement. Confidence scores are proposals, not permissions.
Global knowledge ≠ project facts.
| Global / reusable | Project-specific | Boundary rule |
|---|---|---|
| OWL ontologies and IFC schema definitions | Imported IFC building elements and their property values | Reference ontology/schema revisions; do not promote project facts automatically. |
| Reviewed bSDD classifications and published Concepts | Excel imports, custom Psets, local alignments | Keep project-scoped mapping and property values attached to the project. |
| Reference Use Cases and published graph rules | Project Use Cases, IDS, IDM, BPMN, BCF topics | Project compositions pin their chosen shared revisions. |
| Published shared transformations | Validation runs, snapshots, findings and viewer links | Results remain traceable to source versions and model revisions. |
A logical graph across independently controlled servers.
Federation means authorized data and semantic references can be resolved across servers. It does not require a single physical central Neo4j database, blind replication or permission-free traversal.
Remote reference
Use stable server/resource identifiers plus revision selectors. Resolve remote nodes only through authorized interfaces.
Controlled replication
Optional policy-driven materialized snapshots with provenance and expiry; no default full graph copying.
Failure behavior
Surface offline providers, partial graph completeness, stale mappings and unavailable permissions explicitly.
IDS is both a source and a deliverable.
Read XML specification, applicability, facets and requirements.
Attach constraints to Concept revisions and IFC entities where expressible.
Edit requirements in a governed project information profile.
Write schema-valid XML for supported constraints with provenance.
Record PASS/FAIL/NOT_EVALUATED and IFC GlobalId references.
A lossless IDS round trip and cross-object/geometric rule checks are goals, not capabilities proven by the current pilot. Keep unsupported constraints explicit instead of silently omitting them.
A new source must not silently mutate old Use Cases.
New ontology or dictionary version, changed API data or additional manufacturer product.
Compare source identities, semantic claims, classes and properties.
Identify affected mappings, Concepts, rules and dependent Use Case versions.
Reject, defer, map to existing revision, or create a new draft revision.
Published Concept versions remain immutable; existing Use Cases upgrade only by explicit choice and revalidation.
Recommended impact report fields
source resource + versionadded / changed / removedcandidate Conceptsaffected Use Case revisionsconfidence and human reviewproposed actionvalidation consequencesaudit trailVisibility follows the resource, not just the link.
Future multi-tenant federation must evaluate organization, provider, server, project, object, revision and action-level policies. A visible cross-server relationship must never imply access to the remote node or its properties.
Administrator
Manage globally shared source registrations, concept publishing and alignment governance within assigned authority.
BIM Manager
Import project data, compose project information requirements, submit mapping or Concept change proposals.
Standard User
Compose or reference approved Use Cases within permitted projects, without modifying the shared Concept library.
Provider / Manufacturer
Choose the subset of product data shared to authorized partners and revoke or update publication deliberately.
Design review checklist: protect against data leaks through graph traversal, search rankings, embeddings, previews, caches, exports and diagnostic logs. Enforcement is not yet a verified deployed feature.
Document what runs; label what is intended.
| Component | Status | Evidence / limitation |
|---|---|---|
| Neo4j graph runtime and persisted Concept rule pilot | Verified baseline / Pilot | Separate productive Neo4j installation and persisted ALLOWS_CHILD pilot in 7.8.53; not general policy enforcement. |
| Concept library, source inspection and OWL / IFC / IDS explorations | Partial / Pilot | Historical module experiments and ontology/mapping workflows; individual deployment and end-to-end behavior must be rechecked. |
| Unified ingestion and reviewed semantic alignment workflow | Planned | Target data contract; no claim that all listed connectors are production-ready. |
| IDS lossless round trip, model checks and 3D issue highlighting | Planned | Requires supported-facet coverage, IFC validation implementation and evidence. |
| Federated cross-server query and selective publication | Future | Architecture vision only; remote permission and synchronization enforcement pending. |
| Multi-tenancy and cross-server security | Future | Threat modeling, policy model, test harness and independent verification required. |
Source of maturity assertions: OpenSPAD development snapshot through 7.8.53 and agreed architecture decisions as of 17 October 2026. This document is a design specification, not a verified installation inventory.