What is the Catalog Server designed for in MVD, and what is its intended role in the dataspace?

[aef24]

Hi,
I would like to understand the intended design and role of the Catalog Server in MVD.

From its configuration, it looks like a full DSP participant with its own DID and strict security validation, not just a simple public catalog endpoint.

Could you please clarify:

Is the Catalog Server meant to be a centralized/federated catalog aggregator?

Should it be queried directly by consumer and provider connectors?

Is it considered an infrastructure component or just a specialized participant connector?

In short, is the Catalog Server designed as a central discovery service for the dataspace, or mainly as a reference/specialized connector for catalog use cases?

Thanks!

[paullatzelsperger]

either this is generated by an AI bot, or you are unwilling - or unable - to read the answer provided here eclipse-edc/Connector#5463.
in any case, this will be closed.