Here I describe the emphasis on avoiding transformation technologies.
Why avoiding transformation technologies?
Non-standardized contracts result in the creation and implementation of different data models representing the same body of data. The differences are addressed by the use of a data transformation technology and mapping logic between one schema and another (e.g. XSLT style sheet).
Problems of data transformation:
- increased development effort through the definition of the mapping logic
- increased performance overhead through the mapping logic executed at runtime
- increased architectural complexity due to the transformation layers
- increased governance burden due to maintenance and evolution of the transformation layers
In order to support the goal of intrinsic interoperability, transformation technologies have to be avoided in a long-term. This goal is supported through contract standardization principle.