> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/frameworks-and-standards.md). # Frameworks and standards The public frameworks and standards this guide cites, in the five kinds the terms of reference name, each with its address. Every framework and standard this guide cites is public, and each is given here with the address where it can be read. They are arranged in the five kinds that section 4.2 of the terms of reference names. The short name in bold is the one the subtopic pages use. The full table of public sources, with the edition of each, is on [the page of the public sources](/experience-digital-transformation/building-block/the-public-sources.md). ## Frameworks for digital public infrastructure What DPI is and what it makes possible. * **UNDP DPI page** — UNDP, "Digital public infrastructure", web page — * **UNDP Compendium** — UNDP, *Accelerating the SDGs through Digital Public Infrastructure: A Compendium of the Potential of Digital Public Infrastructure*, 21 August 2023 — ## Enterprise architecture frameworks Section 2.3 of PAERA, on the role of enterprise architecture. The frameworks themselves are taught in the enterprise architecture course; this guide adds none of its own. * **PAERA** — *Public Administration Ecosystem Reference Architecture (PAERA)*, version 1.0, GovStack, dated 25.05.2024. Cited by section. The site shows no version or date on its pages, only "Last updated 2 years ago" (read 4 October 2026). — The enterprise architecture course in this knowledge base is [Developing a Gov Enterprise Architecture (GEA)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea). ## Interoperability standards How public bodies exchange data: the Information Mediator specification, the X-Road documents and, through the interoperability course, the European Interoperability Framework. * **IM** — GovStack, Information Mediator Building Block specification, version 1.1.1 (the page label shows "1.1"; its version history table ends at 1.1.1) — * **X-Road documents** — NIIS, X-Road release 7.7.0: Architecture (ARC-G), Message Protocol for REST (PR-REST) — * **EIF** — European Commission, European Interoperability Framework, cited through the interoperability course, which teaches its four layers — The interoperability course in this knowledge base is [Building a Government Interoperability Framework (GIF)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-interoperability-framework-gif/building-a-government-interoperability-framework-gif). ## Reference architectures for digital government The architecture of the public administration as a whole, and the published specifications of the shared building blocks. * **PAERA** — *Public Administration Ecosystem Reference Architecture (PAERA)*, version 1.0, GovStack, dated 25.05.2024. Cited by section. The site shows no version or date on its pages, only "Last updated 2 years ago" (read 4 October 2026). — * **REG** — GovStack, Registration Building Block specification, the site's default edition (site label "23Q4", version history to 1.0) — * **DR and DRS** — GovStack, Digital Registries Building Block specification, "Version 3.0-alpha; June 2026". DR names a section, DRS a numbered requirement. — * **ID** — GovStack, Identity Building Block specification, "Version 2.0; December 2025" — * **PAY** — GovStack, Payments Building Block specification, "Version 3.0; December 2025" — * **IM** — GovStack, Information Mediator Building Block specification, version 1.1.1 (the page label shows "1.1"; its version history table ends at 1.1.1) — * **CON** — GovStack, Consent Building Block specification, version 1.3.0 — * **WF** — GovStack, Workflow Building Block specification, the site's default edition (site label "23Q4", version history to 1.0) — * **GovStack Architecture** — GovStack, Architecture specification, edition 2.2.0 as the page label shows it on 4 October 2026 (its version history table ends at 2.1.0, released 13 March 2026) — ## Open standards for interfaces and data exchange The open standards in which the interfaces of the blocks are written and called. * **OpenAPI** — OpenAPI Initiative, OpenAPI Specification, version 3.0.3 — * **OIDC** — OpenID Foundation, OpenID Connect Core 1.0 incorporating errata set 2, 15 December 2023, as the Identity specification uses it — * **VC** — W3C, Verifiable Credentials Data Model v2.0, W3C Recommendation, 15 May 2025 — ## How the specifications are cited References to the GovStack specifications are written as follows: REG §6.3.2.7 is the section of that number in the Registration specification; DRS-33 is the Digital Registries requirement of that number; ID 6.2-r2 is the second requirement under heading 6.2 of the Identity specification, which does not number its requirements. Every block is cited by its edition. The Digital Registries edition is an early release whose requirement numbers may change again, so a registry requirement is cited by its number and its short title together. A PAERA section is cited by its number, as in PAERA 2.3. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/frameworks-and-standards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.