Out-of-scope requirements (Information Mediator)

Note that the Information Mediator is not responsible for manipulating the payloads sent to and from various applications—in a sense, it is both the postal service and the roads/bridges/train tracks—but it does not read the contents of your mail.

The Information Mediator Building Blocking does NOT handle communication between human users and applications.

The Information Mediator Building Blocking does NOT handle ingress and egress access from external applications to and from GovStack’s internal components (This may be handled by a public API Gateway in the domain of the Security Building Block).

The current specification does NOT assume the possibility of different Information Mediator implementations working together. In one instance of the GovStack ecosystem, only one implementation of the Information Mediator Building Block can exist.

The following requirements have been identified as “out of scope” because they fall into the realm of the Workflow Building Block or the Security Building Block.

Supports the handling of transactions and associated communication errors and exceptions.
Translates data from one format to another, and interoperates with handshake protocols to enable interoperability between diﬀerent ICT Building Blocks duplications.
Map data structures and fields from the identification system to the registration system and vice versa.
Hold authentication and credentials for each system.
Allow the definition of steps for a particular transaction.
Provide an API for both systems to access – and execute all necessary steps for that transaction (including error handling, retries, and notifications).
Provide an API for external systems to access GovStack Building Blocks.