| Version 2 (modified by gordonrachar, 14 years ago) |
|---|
TracNav menu
- Back to Avalon Collaboration Page
-
Introduction
- Overview
- Entry Points to Learning About ISO 15926
- Case Studies
- Principles of Interoperability
- Building a Business Case
-
Using ISO 15926 Tools
- Discovering the Right Class
- TC 184 SC 4 WG 3
- Using the RDS/WIP (RDL Façade)
- POSC/CAESER RDS
-
Tutorials
- Mapping to ISO 15926-4
- Using Templates
- Diagnostic Page
Interoperability and Integration
Status of this document: Working Draft
This document is open for feedback, please post questions and comments in the forum at the bottom of this page. You will need a login to post in the forum.
Contents
Abstract
[Enter abstract]
Interoperation and Integration are often (incorrectly) used as synonyms of each other. Of course they often come as a pair: to get interoperability, you need integration; If you want integration you need interoperability. But they are not the same thing.
Interoperability
Interoperability is the ability to connect and transport information between points of encapsulation. Integration Integration is the ability to create a relationship between two different bits of information. Integration is saying that “that information” is related to “that information”. DOES NOT MEAN YOU MERGE DATA. Merging is taking two representations and combine them into one representation. It is often done this way (and often incorrectly), but it is not required, or even necessarily desirable It is richer if you say: • Stuff over here – is related to – stuff over there
- and, by the way, the relationship is of a certain type
Integration
... ...
Back
