Version 7 (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
Encapsulate an Application
In this example, information flow between the applictions is already automated by means of custom database maps. But you would like to be able to modify one of them without disrupting the entire landscape of applications. One way to do this is to map the output of upstream applications, and the input of the the target application to ISO 15926-4.
Figure 1 - Hard-Coded Custom Maps
This is called Encapsulating. The application using the 15926-4 dictionary. After you do this, the application can be modified, or changed out entirely, as long as the inputs are still mapped to 15926-4
Figure 2 - Encapsulate an Application