> 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/analytics/technical-specifications/8.-standards.md).

# 8. Standards

Standards and frameworks the Analytics Building Block must comply with or align to, including climate-specific standards.

{% hint style="info" %}
📐 **REQUIRED is the floor.** RECOMMENDED and OPTIONAL entries extend it — several of the latter are specific to climate deployments.
{% endhint %}

The Analytics Building Block must comply with or align to the following standards and frameworks. Education-specific standards and national data models apply when the Building Block is deployed for education use cases.

| Standard / Framework                         | Scope                                                                                           | Applicability         |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------- | --------------------- |
| OpenAPI 3.x                                  | API specification for all external interfaces                                                   | REQUIRED              |
| OpenID Connect 1.0 / SAML 2.0                | Federated authentication with Identity / Access Management BB                                   | REQUIRED              |
| OAuth 2.0 (RFC 6749)                         | Token-based authorisation for API access                                                        | REQUIRED              |
| TLS 1.2 / 1.3                                | Transport encryption for all inter-BB communications                                            | REQUIRED              |
| Apache Parquet / Iceberg / Delta Lake        | Open table formats for lakehouse storage                                                        | REQUIRED              |
| Apache Arrow                                 | In-memory columnar format for analytical processing                                             | RECOMMENDED           |
| DCAT v3 (Data Catalogue Vocabulary)          | Metadata interoperability for the data catalogue                                                | RECOMMENDED           |
| ISO/IEC 11179                                | Metadata registries for governed code sets and controlled vocabularies                          | RECOMMENDED           |
| W3C PROV-O                                   | Data provenance and lineage representation                                                      | RECOMMENDED           |
| UN/CEFACT SDMX 3.0                           | Statistical data and metadata exchange (indicators, aggregates)                                 | RECOMMENDED           |
| OGC STAC / OGC API / ISO 19115               | Spatio-temporal catalogue and geographic metadata for geospatial and Earth-observation datasets | RECOMMENDED (climate) |
| IPCC 2006 Guidelines & 2019 Refinement       | Sectors, categories, gases and methodological tiers for GHG inventory data                      | OPTIONAL (climate)    |
| UNFCCC ETF Common Reporting Tables           | Reporting structure for national climate transparency                                           | OPTIONAL (climate)    |
| ISO/IEC 27001                                | Information security management                                                                 | RECOMMENDED           |
| GovStack Cross-Cutting Requirements          | Baseline non-functional requirements for all BBs                                                | REQUIRED              |
| GovStack Security & Identity Building Blocks | Security and access-control architecture alignment                                              | REQUIRED              |


---

# 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/analytics/technical-specifications/8.-standards.md?ask=<question>&goal=<user_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.