Loading content
The canonical data model promotes interoperability between systems and facilitates data integration. By providing a uniform structure, data exchange is optimized and misunderstandings are reduced.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A canonical data model defines shared business objects and their relationships in a form that can be reused across integrations.
The approach grew from integration and enterprise-architecture practice: shared message models were intended to reduce point-to-point translations between many systems. Patterns such as the Canonical Data Model made that idea explicit.
Each source system translates its vocabulary once into a canonical middle; each target translates from that middle into its own format. The middle stabilizes connections but requires deliberate stewardship of shared meanings.
The shared structure for a business object.
A translation between a system-specific and canonical format.
The agreed expectation for data structure and meaning.
A canonical model reduces bespoke integration links and makes meanings comparable. It becomes a bottleneck when very different domains are forced into one oversized model.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.