Configuration model and app routes should be able to link to broker

International-Data-Spaces-Association / InformationModel

The Information Model of the International Data Spaces implements the IDS reference architecture as an extensible, machine readable and technology independent data model.

Apache License 2.0

64 stars 37 forks source link

Configuration model and app routes should be able to link to broker #370

Closed clange closed 3 years ago

clange commented 3 years ago

As discussed with @HeinrichPet, it would make sense that an ids:ConfigurationModel points to one or multiple brokers, and that the ids:AppRoutes in this configuration model can point to a subset of this set of brokers. Idea:

in the configuration model of an ids:Connector, one can configure a set of ids:Brokers to which the connector might talk
each app route should be able to have its own subset of that set, such that it can, e.g., announce updates to its output resource to these brokers.

clange commented 3 years ago

@HeinrichPet a question about something we will probably not need now (I won't implement it) but might need later (and should then move to a separate issue): will it make sense to distinguish between the roles that different brokers have for the Connector that's being configured here? We talked about brokers to which this Connector announces Resources (e.g., after they have been updated internally). But are there also (possibly different?) brokers, from which this Connector would like to retrieve information?