Version 10 (modified by gordonrachar, 14 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
In this example you have a number of applications that are connected directly to a common database. Whenever one of the applications changes, care will have to be taken to mare sure it interacts properly with the database. If your applications are commercial software, the vendors have little incentive to keep them compatible with your master database. You wish to decouple an application from the master database to enable you to modify it independently of the rest of the applications.
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