A canonical model is a
design pattern used to communicate between different data formats. Essentially: create a data model which is a superset of all the others ("canonical"), and create a "translator" module or layer to/from which all existing modules exchange data with other modules. The canonical model acts as a middleman. Each model now only needs to know how to communicate with the canonical model and doesn't need to know the implementation details of the other modules.
Details
A form of
enterprise application integration, it is intended to reduce costs and standardize on agreed data definitions associated with integrating business systems. A canonical model is any model that is
canonical in nature, meaning a model that is in the simplest form possible based on a standard enterprise application integration (EAI) solution. Most organizations also adopt a set of standards for message structure and content (message payload). The desire for consistent message payload results in the construction of an enterprise or business domain canonical model common view within a given context. Often the term canonical model is used interchangeably with integration strategy and often entails a move to a message-based integration methodology. A typical migration from point-to-point canonical data model, an enterprise design pattern which provides common data naming, definition and values within a generalized data framework. Advantages of using a canonical data model are reducing the number of data translations and reducing the maintenance effort.
Adoption of a comprehensive enterprise interfacing to message-based integration begins with a decision on the
middleware to be used to transport messages between endpoints. Often this decision results in the adoption of an
enterprise service bus (ESB) or enterprise application integration (EAI) solution. Most organizations also adopt a set of standards for message structure and content (message payload). The desire for consistent message payload results in the construction of an enterprise form of
XML schema
An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type, above and beyond the basic syntactical constraints imposed by XML itself. These constrai ...
built from the common model objects thus providing the desired consistency and re-usability while ensuring data integrity.
See also
*
Canonical schema pattern
*
Common data model
*
Enterprise information integration
*
Enterprise integration
Enterprise integration is a technical field of enterprise architecture, which is focused on the study of topics such as system interconnection, electronic data interchange, product data exchange and distributed computing environments.
It is a con ...
*
Information architecture
*
List of XML schemas
*
Service-oriented architecture
*
Web service
A web service (WS) is either:
* a service offered by an electronic device to another electronic device, communicating with each other via the Internet, or
* a server running on a computer device, listening for requests at a particular port over a n ...
*
XML schema
An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type, above and beyond the basic syntactical constraints imposed by XML itself. These constrai ...
References
Bibliography
*
*{{cite web , url=http://www.enterpriseintegrationpatterns.com/ramblings/03_hubandspoke.html , title=Metadata Hub and Spokes (Canonical Data Domain)
External links
Forrester Research, Canonical Model Management ForumCanonical Model, Canonical Schema, and Event Driven SOA Forrester Research, Canonical Information Modeling
Enterprise application integration
Enterprise architecture
Enterprise modelling
Software design patterns