Skip to content
This repository was archived by the owner on Nov 14, 2025. It is now read-only.

Mutual recognition and collaboration between Gaia-x style federated dataspaces (eg Catena-X) and UNTP style decentralised communities. #493

@onthebreeze

Description

@onthebreeze

This ticket continues the technical discussion in issue #320 about interoperability with AAS (Asset Administration Shell) and databases. It expands the discussion towards more formal mutual recognition and partnership to the benefit of both frameworks. Our premise is that mutual recognition and collaboration towards interoperability between Gaia-X (federated model) and UNTP (decentralised model) is better than competition and is advantageous for both.

The distinction between federated (Gaia-x) and decentralised (UNTP) is important. Both have a place and EU has been using both terms. This is not a competition between two instruments of the same architecture. Instead these are different but not incompatible frameworks.

  • Federated frameworks work well when there is a governing community owner that issues identities and defines rules. That could work well where there are logical political Groupings (eg EU)
  • A global framework just by its nature has to be more decentralised. So there is no reason at all why any number of federated communities cannot be linked up using a decentralised model.

There is some conceptual similarity too between UNTP core and it's extensions - and Gaia-X as a core architecture and it's industry specific implementations like catena-x.

Attached to this ticket is what a deep research AI thinks about UNTP / Gaia-X collaboration (Thanks @JohnOnGH). It may not be 100% accurate but it looks pretty good to me and certainly offers us a good starting point.

Please comment on this ticket with your thoughts and opinions on this topic.

UN Protocol, GAIA-X Collaboration_.pdf

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions