SMP
SMP stands for Service Metadata Publisher, and also names the OASIS protocol that clients use to query one. It is where a recipient of business documents publishes what a sender needs to reach it: the document types it can receive, the address of its endpoint, the transport it uses and the certificates that secure that connection. In the architecture the WE BUILD consortium proposes for the European Digital Directory (EDD), the SMP is the last of three lookups: the EDD identifies the recipient and the SMP says how to connect.
The OASIS standard Service Metadata Publishing (SMP) Version 2.0, approved on 14 February 2021, describes a protocol for publishing service metadata within a 4-corner network. In such a network, entities exchange business documents through intermediary gateway services, often called Access Points. To send a document, a sender must discover critical metadata about the recipient, such as the types of document it can receive and the transport methods it supports. The recipient makes that metadata available through a Service Metadata Publisher, and the client asking for it can be an end-user business application or an Access Point.
For each process, the metadata holds either one or more endpoints or a redirect to another SMP, never both. An endpoint carries the transport profile used between Access Points, its address as a URL, optional activation and expiry dates, and one or more certificates used to validate the communication with it. The publisher may sign its responses with an enveloped XML signature, so that the client can check where an answer came from.
Finding the right SMP is a separate step. The specification describes discovery as a two-step process: look up the SMP that holds the metadata about a participant, then retrieve that metadata from it. The first lookup may use the BDXL protocol, which registers each participant with one and only one SMP, but the specification makes BDXL optional, so a network can locate its SMPs another way.
The link to the EDD comes from WE BUILD, not from the regulation. Article 10 of COM(2025) 838 establishes the European Digital Directory and does not mention SMP or BDXL. The consortium's WP4 architecture decision gives the EDD identification only: it resolves an actor to an ISO 6523 compliant identifier such as the EUID and returns references to discovery locators. BDXL 2.0 then resolves that identifier to the SMP of the right ecosystem, and the SMP returns the endpoint address, protocol and certificate reference that the sender needs to connect to an Access Point, a QERDS gateway or an eFTI gateway.
The same decision draws a boundary. The EDD does not store SMP-style capability data, namely document type capabilities, AS4 endpoint addresses and transport certificates, and it does not replace ecosystem registries such as the Peppol SMP, QERDS provider registries or eFTI gateway registries. Each ecosystem runs its own SMP, which keeps the directory lean and lets capabilities change without touching it. This is a design decision for the pilot, not law: the supporting analysis covers infrastructure-mediated document exchange only, leaves direct wallet-to-wallet discovery for OpenID4VC flows as an open issue, and notes that an EDD implementing act specifying a different protocol would require migration.
- OASIS Service Metadata Publishing (SMP) Version 2.0
- The WE BUILD architecture decision
- The WE BUILD supporting analysis
Related terms
Is SMP the same as BDXL?
No. They work together but do different jobs. BDXL answers which SMP holds the metadata about a given participant, and the SMP answers how to reach that participant: the endpoint address, the transport profile and the certificates. In the WE BUILD design the EDD comes before both, because it only resolves the recipient to an identifier.
The SMP specification makes BDXL optional, so another network can find its SMPs by other means.
Does the European Digital Directory store SMP data?
Not under the WE BUILD architecture decision. It says the EDD must not store capability registry data such as document type capabilities, endpoint addresses and transport certificates, and must not perform routing. Those stay in the SMP of each ecosystem.
That is the consortium's design for its pilot. The proposal itself leaves the technical detail of the directory to implementing acts, so the final design can differ.