Version 3 (modified by gordonrachar, 15 years ago) |
---|
TracNav menu
- An Introduction to ISO 15926
-
What is ISO 15926
- How Information Exchange is Supposed to Work
- How Information Exchange Actually Works
- How Information Exchange Works with ISO 15926
- How ISO 15926 Works
- A Bit of History
- Long Tail
-
Areas of Current Work
- Norwegian Continental Shelf
- MIMOSA
- JORD
- iRING
- Development of Standards
- Educational Material
- Getting Started With ISO 15926
- Other ISO 15926 Resources
-
Introduction to ''An Introduction to ISO 15926''
- ISO 15926 is Like a Babel Fish
- ISO 15926 is Like HTML
- ISO 15926 is Like English on Your Cell Phone
- About the Author
- ISO15926Primer_DiagnosticPage
Decouple an Application from a Confederation of Applications
Status of this document: Ready for Cold Eyes Review
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.
In this example you have a number of applications that are linked by a common database. The custom maps will need maintenance whenever any of the applications change. Even new updates to commercial software can break a link. You wish to be able to modify the applications without breaking the information flow to the database.
Figure 1 - Applications Mapped to a Common Database
In order to isolate, say, Application A so that you can update it independently, you will need to create a map between it and the common database. Use ISO 15926-4 instead of making a custom map.
Figure 2 - Map an Application to ISO 15926-4