Encapsulate an Application

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, 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.

Error: Macro Image(GettingStarted_Encapsulate01.JPG, 400px) failed

Attachment 'wiki:ISO15926Primer_GettingStarted_Encapsulate: GettingStarted_Encapsulate01.JPG' does not exist.

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

Error: Macro Image(GettingStarted_Encapsulate02.JPG, 400px) failed

Attachment 'wiki:ISO15926Primer_GettingStarted_Encapsulate: GettingStarted_Encapsulate02.JPG' does not exist.

Figure 2 - Encapsulate an Application

Back to Getting Started

---

Discussion

You have no rights to see this discussion.