9 Data Structures
The resource model shows the relationship between data objects that are used by the Information Mediator building block.
The data elements provide detail for the resource model. All data element schemas can be viewed, commented on, and modified in the schemas section of the IM BB Github repository.
The following standards are applicable to data structures in the BB:
- Requests will be made using HTTPS.
- Request bodies will be valid JSON.
- The description of specific services and the data formats they require will be specified in an OpenAPI 3.1 specification.
The Mediator BB key element is Service. The Service is used by a consuming building block or an application and offered by a provider building block or Application. Both Provider and Consumer MUST be Members of Mediator BB. Members of the mediator BB can be an organization (governmental or not, business or not) or a person (citizen as a rule).
Draw.io source in github: https://github.com/aleksander-reitsakas/InformationMediatorAPI/blob/main/IM/diagrams/Mediator-BB-entities.drawio.png.
To become a Member of Mediator BB participant must fulfil declared requirements and apply for onboarding. In the process of onboarding a Member is registered with Mediator BB and gets credentials to connect to Mediator BB. Normally it is done the way that a Member provides a certificate of recognized CA and requests signed with this certificate are considered as legitimate requests of the Member. A member entity can access the PubSub configuration and register a room to publish its own event type as a publisher through its own admin.
Members can browse a directory of Services available in Mediator BB. Each service is described in OpenAPI.
Member:
Member Class enumeration
Member Code string
Signing Key:
Token enumeration (where to put)
Name string
Name of CA enumeration
Application:
Connection type enum http/https
TLS certificate cert
Services:
Service Code string
Description URL url OpenAPI spec
Service URL url base address for endpoint (prefix)
Access Rights ACL
Resource Model is extension of Access Layer model:
Draw.io source in github: https://github.com/aleksander-reitsakas/InformationMediatorAPI/blob/main/IM/diagrams/Mediator-BB-PubSub-entities.drawio.png
An event is a set of data described by event type. Each event has an id, and this is most likely a uuid.
An event type is a service described by OpenAPI. Each event type is owned by a certain authority. (E.g. the MoH might own the “new_birth” event type and define its schema.)
A publisher is a GovStack application that produces events and sends them to Rooms.
A room is a GovStack application that handles the distribution of events. Each Room has a set of connected event types. (E.g., the “birth” room might contain three event types: “new_birth”, “birth_complication”, and “infant_death”.) A room is located in the member’s local IM BB implementation and the member is responsible for all types of events in that particular room.
A subscriber is a GovStack application that can process events. Subscribers are independent of each other and their business logic is different (as rule). Each subscriber processes events from their own perspective.
Last modified 9mo ago