search

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

Broker vs. Connector #469

Closed MoritzKeppler closed 2 years ago

MoritzKeppler commented 3 years ago

A broker is a subclass of a connector. Does that mean that a broker can provide own artifacts? Or asking the other way round: A broker will just list own Resources in its self-description, not resources pushed to it by other connectors. Right?

Moritz Keppler moritz.keppler@daimler.com, Daimler TSS GmbH, legal info/Impressum

clange commented 3 years ago

Interesting question. Indeed a Broker is a Connector, also by its specification:

In order to ensure the necessary interoperability and general interactions, an IDS Meta Data Broker (like the App Store) is also defined as a specialized IDS Connector. The communication between an IDS Connector and an IDS Meta Data Broker is based on the same principles as any other Connector-Connector communication within the International Data Spaces. Still, an IDS Meta Data Broker provides a collection of additional functionalities.

@sebbader can you help with the full answer to the question? Would it, e.g., be possible that a Broker assumed the Connector role and advertised some Resources to another Broker? If so, what would these Resources look like?

sebbader commented 2 years ago

Hello @MoritzKeppler,

that's true, a Metadata Broker could also publish its own Resources, and own access endpoints for instance. The difference can be outlined by using an ids:sovereign attribute pointing to the identifier of the Metadata Broker's operator. Then the client connectors can see that these resources are "owned" by the organization behind this Metdata Broker.