Class for "data space" and its configuration as a first-class citizen

[clange]

A requirement that came up in discussions around the Datenraum Mobilität:

It would be good to have a class ids:DataSpace or ids:DataEcosystem (name to be decided), which treats a data space / ecosystem and its configuration as a first-class citizen.

This configuration should be populated at some early time in the onboarding process, and would support further onboarding steps, e.g., a new participant joining. (We might take inspiration from Gaia-X, where onboarding is defined in a more systematic way, but should also follow the IDS Rule Book.)

Concrete example: in a data space, there can be one or more brokers. Vocabularies could be provided using a fully-featured component (Vocabulary Hub), or some participant would merely play the role in a lightweight way (e.g., by following the usual best practices for publishing vocabularies). Now think of a DHCP like protocol, which is aware of the URL(s) of the broker(s) and other central components and informs new participants of this.

[ticapix]

In the context of Gaia-X, the Gaia-X Compliance is applicable only on Participants and elements to build a Service Offering.
Interoperability is between 2+ services. Trust is between 2+ participants. Trying to enforce or assess compliance or interoperablity at a Dataspace level is not scalable.

Hence, there is no Dataspace class or Dataspace Self-Description concept in Gaia-X.