Registry and Discovery — the federation half of MSF

Registry and Discovery — the federation half of MSF An architecture diagram generated by Archify. Consumer Actor · players · partner platforms · Architecture component Consumer Actor players · partner platforms Federation Actor · CDI and testbed operators · Architecture component Federation Actor CDI and testbed operators Trusted Actor · programme governance · Architecture component Trusted Actor programme governance Consumer View · read-only projection · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw Consumer View read-only projection Federation View · register · advertise · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw Federation View register · advertise Trusted View · approve · suspend · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw Trusted View approve · suspend Content Discovery API · what content exists · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw · HNR · WP 2.4.3 Content Discovery API what content exists HNR · WP 2.4.3 Service Registry (SReg) · where to obtain it · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw · HNR · WP 2.4.3 Service Registry (SReg) where to obtain it HNR · WP 2.4.3 Provider governance · admission · revocation · Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw · HNR Provider governance admission · revocation HNR Offering · a title · Federation Catalogue Offering a title Representation · an encoding of it · Federation Catalogue Representation an encoding of it Pathway · a route it travels · Federation Catalogue Pathway a route it travels Pending · Provider lifecycle — only Approved providers appear in any view Pending Approved · Provider lifecycle — only Approved providers appear in any view Approved Suspended · Provider lifecycle — only Approved providers appear in any view Suspended Revoked · Provider lifecycle — only Approved providers appear in any view Revoked Registry (HNR, WP 2.4.3) — the catalogue is never exposed raw Federation Catalogue Provider lifecycle — only Approved providers appear in any view

Read it this way

  • • Three actor roles on the left, three projections of the same catalogue in the middle, one catalogue on the right.
  • • No actor touches the catalogue directly. Every path goes through a role-projected view — that is what makes it federated rather than merely shared.
  • • The Registry is HNR-owned under WP 2.4.3, but the content in it belongs to the partners who registered it.

Why three levels

  • • Offering → Representation → Pathway lets one title be addressable over several transmission routes at once.
  • • A Pathway is the unit Supply & Demand Control selects. Everything above it is descriptive.
  • • Registering a Pathway does not schedule anything. It makes a delivery possible; SC-Sel is what makes one happen.

What this licenses

  • • Nothing can be selected that was not first registered here — the registry bounds the space SDC chooses from.
  • • Suspension is reversible and revocation is not; a suspended provider keeps its registrations but serves none of them.
  • • Service Discovery registers endpoints; Content Steering picks among them at playout. Different layers, not interchangeable.