This document enumerates the possible participant identity topologies in a dataspace. Note that identity topologies are independent of the underlying identity technology used by the dataspace (e.g. centralized or decentralized).
In this scenario, a one identifier is used by all participant agents. A single connector deployment and single FCC deployment can operate against multiple dataspaces.
Note that crawled contract offers will need to be disambiguated by dataspace and participant since it is insufficient to track offers by participant id alone. For example, it must be possible to determine the offers available by dataspace.
In this topology, a single participant deploys multiple agents with different identifiers. Participant agents will therefore consist of isolated deployments:
In this topology, a single participant deploys multiple agents with different identifiers, each communicating with different dataspaces. Participant agents will therefore consist of isolated deployments:
