> 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/roadmap/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. ## Frameworks for digital public infrastructure What DPI is, how mature a country's DPI is, how to approach it and how to keep it safe and inclusive. * **UNDP Compendium** — UNDP, *Accelerating the SDGs through Digital Public Infrastructure: A Compendium of the Potential of Digital Public Infrastructure*, 21 August 2023 — * **UNDP Compass** — UNDP, *Digital Development Compass — Methodology*, web page — * **UNDP Playbook** — UNDP, *The DPI Approach: A Playbook*, 21 August 2023 — * **Safeguards Framework** — United Nations, *Universal DPI Safeguards Framework: A Guide to Building Safe and Inclusive DPI for Societies*, September 2024, developed under the stewardship of the Office of the Secretary-General's Envoy on Technology and UNDP. ITU is a member of its consultative group of international organisations, not its author. — ## 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 course adds none of its own, because a roadmap puts in order the architecture that the enterprise architecture method designs. * **PAERA** — GovStack, *Public Administration Ecosystem Reference Architecture (PAERA)*, version 1.0, dated 25 May 2024. Cited by section. — 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 data exchange layer and its rules. * **X-Road documents** — NIIS, X-Road release 7.7.0: Architecture (ARC-G), Security Server User Guide (UG-SS), Message Protocol for REST (PR-REST), Operational Monitoring Protocol (PR-OPMON) — * **IM** — GovStack, Information Mediator Building Block specification, version 1.1.1 — * **EIF** — European Commission, European Interoperability Framework, whose four layers the interoperability course teaches — 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** — GovStack, *Public Administration Ecosystem Reference Architecture (PAERA)*, version 1.0, dated 25 May 2024. Cited by section. — * **REG** — GovStack, Registration Building Block specification, the site's default edition (site label "23Q4", version history to 1.0) — * **DR** — GovStack, Digital Registries Building Block specification, "Version 3.0-alpha; June 2026". DR names a section, DRS a numbered requirement; this is an early release whose requirement numbers may change, so a requirement is cited by its number and its short title together. — * **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 — * **CON** — GovStack, Consent Building Block specification, version 1.3.0 — * **MSG** — GovStack, Messaging Building Block specification (site label "messaging-23Q4.1", version history to 1.0) — * **GovStack Architecture** — GovStack, Architecture specification, edition 2.1.0 — ## 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, the edition in which this course's interface contracts are written — * **OpenID Connect** — OpenID Foundation, OpenID Connect Core 1.0, the sign-in protocol the Identity specification uses — * **ISO 4217** — International Organization for Standardization, ISO 4217, the codes for currencies the Payments specification uses — ## Other public sources this guide cites These are the reports, pages and documentation that the subtopics cite for a figure, a case or a method, beside the frameworks above. * **UNDP DPI page** — UNDP, "Digital public infrastructure", web page — * **ITU Academy course** — ITU Academy with UNDP, training course "Accelerating digital public infrastructure with safeguards" — * **World Bank Cost Drivers** — World Bank, *Understanding Cost Drivers of Identification Systems*, 2018 — * **World Bank ID4D Guide** — World Bank, *ID4D Practitioner's Guide: Version 1.0 (October 2019)* — * **World Bank G20 report** — World Bank, *G20 Policy Recommendations for Advancing Financial Inclusion and Productivity Gains through Digital Public Infrastructure*, Global Partnership for Financial Inclusion, 2023 — * **BIS Bulletin 52** — Bank for International Settlements, *BIS Bulletin* No 52, "Central banks, the monetary system and public payment infrastructures: lessons from Brazil's Pix", 23 March 2022 — * **e-Estonia** — e-Estonia, "e-Estonia story" and "Frequently asked questions — Story of e-Estonia" — * **Giga data flow** — UNICEF Giga, repository `giga-dagster`, files `docs/dataflow.md` and `docs/README.md`, at commit `46b72af67066363a29d3d933dcdc619489bd0be5` — * **Databricks** — Databricks, "What is Medallion Architecture?" — * **GovStack Sandbox** — GovStack Sandbox documentation, edition 1.1.1 — * **GovStack testing** — GovStack testing application, with the GovStack website pages "How is Compliance Measured?" and "How to Submit Software?" — ## 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-17 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; PAY 6.4-r3 is formed the same way for Payments. Every block is cited by its edition. --- # 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/roadmap/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.