> For the complete documentation index, see [llms.txt](https://docs.cdpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdpi.dev/fr/le-wiki-dpi/principes-de-larchitecture-technique-dpi/interoperabilite.md).

# Interopérabilité

**Résumé (ce qu'il faut viser)**

Accélérer les effets de réseau pour stimuler l'innovation et la concurrence grâce à des spécifications technologiques, des protocoles et des normes pour diverses fonctions qui permettent l'interopérabilité entre de multiples acteurs. Éviter le cloisonnement, la fragmentation du réseau, la monopolisation et le jardin clos par nature.

**Outils techniques (comment y parvenir)**

Protocoles et normes/spécifications publiés que l'écosystème doit adopter et respecter.&#x20;

**Résultats sociétaux (Pourquoi c'est important)**

Choix de solutions et de services pour les particuliers

Échelle d'accès et d'adoption pour les particuliers

Concurrence sur les marchés qui restent interopérables

Innovation des acteurs du marché pour favoriser la diversité des services

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cdpi.dev/fr/le-wiki-dpi/principes-de-larchitecture-technique-dpi/interoperabilite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
