3.4.5 Publishing and using Data Apps
Last updated
IDS-RAM 4
Last updated
IDS Apps can be used by IDS Connectors for specific data processing or transformation tasks. They can perform tasks of different complexity, ranging from simple data transformation to complex data analytics. An example of data transformation may be a IDS App parsing a single string field with address information and producing a data structure consisting of street name and number, zip code, name of the city, and name of the country.
IDS Apps are created by an App Provider and then published at an IDS App Store, as depicted by the "IDS App Publication Process" in Figure 3.4.5.1. In order to be published, certain IDS Apps require certification from the Certification Body (see ), as depicted in the first step of the "IDS App Publication Process". Whether a certification is needed or not, publishing an IDS App requires the App Provider to push the app image to the app store's App Container Registry and then publish the app metadata. For each IDS App that was successfully published, the corresponding metadata and app image are stored in the IDS App Store and can be retrieved by IDS Participants via a search interface offered by the App Store.
When it comes to using a IDS App that is offered by an IDS App Store, IDS Participants need to execute the process that is depicted in Figure 3.4.5.2. An IDS Participant, here called "App User", can use the search interface of the IDS App Store to look for a suitable IDS App through its IDS Connector, as depicted by the "Find IDS App" subprocess in Figure 3.4.5.3. After the "Find IDS App" process is finished, the App User might need to pay for the selected IDS App. This is indicated by the "IDS App Payment" subprocess, which is conceptually similar to the Contract Negotiation detailed in Section 3.4.3 and can be done directly between the App User and App Provider or through a Clearing House if necessary.
If the participant finds a suitable IDS App in an IDS App Store, e.g. matching in functionality and compatible with the App User's IDS Connector technical requirements, the IDS App can then be requested through the "Retrieve IDS App" subprocess depicted in Figure 3.4.5.4. This subprocess consists of two main interactions of the App User with the App Store, first to retrieve the IDS App's metadata and then to pull its image before deploying it in the App User's IDS Connector.
