From ac352f830c957b4a650c5b2eff63d0f41738b963 Mon Sep 17 00:00:00 2001 From: Selam Waktola Date: Tue, 12 May 2026 14:27:11 -0700 Subject: [PATCH] bump specification stable to v0.9 and draft to v0.10 --- README.md | 2 +- docs/concepts/overview.md | 19 ++++++--- docs/guides/a2ui-in-mcp-apps.md | 44 ++++++++++----------- docs/index.md | 15 +++---- docs/introduction/what-is-a2ui.md | 10 ++--- docs/quickstart.md | 33 +++++++++++++++- docs/specification/v0.10-a2ui.md | 16 ++++++++ docs/specification/v0.10-evolution-guide.md | 12 ++++++ docs/specification/v0.8-a2a-extension.md | 6 +-- docs/specification/v0.8-a2ui.md | 9 +++-- docs/specification/v0.9-a2ui.md | 7 ++-- docs/specification/v0.9-evolution-guide.md | 4 +- mkdocs.yaml | 23 ++++++----- 13 files changed, 133 insertions(+), 67 deletions(-) create mode 100644 docs/specification/v0.10-a2ui.md create mode 100644 docs/specification/v0.10-evolution-guide.md diff --git a/README.md b/README.md index cc6b87980..694425dac 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ _A gallery of A2UI rendered cards, showing a variety of UI compositions that A2U ## ⚠️ Status: Early stage public preview -> **Note:** A2UI is currently in **v0.8 (Public Preview)**. The specification and +> **Note:** A2UI is currently in **v0.9 (Public Preview)**. The specification and > implementations are functional but are still evolving. We are opening the project to > foster collaboration, gather feedback, and solicit contributions (e.g., on client renderers). > Expect changes. diff --git a/docs/concepts/overview.md b/docs/concepts/overview.md index 7fb2d8d8b..32f9c3683 100644 --- a/docs/concepts/overview.md +++ b/docs/concepts/overview.md @@ -28,24 +28,33 @@ How components connect to application state using JSON Pointer paths. Covers rea ## Message Types -=== "v0.8 (Stable)" +=== "v0.9 (Stable)" - Version 0.8 uses the following message types: + Version 0.10 uses the following message types: - **`surfaceUpdate`**: Define or update UI components - **`dataModelUpdate`**: Update application state - **`beginRendering`**: Signal the client to render - **`deleteSurface`**: Remove a UI surface -=== "v0.9 (Draft)" +=== "v0.10 (Draft)" - Version 0.9 uses the following message types: + Version 0.10 uses the following message types: - **`createSurface`**: Create a new surface and specify its catalog - **`updateComponents`**: Add or update UI components in a surface - **`updateDataModel`**: Update application state - **`deleteSurface`**: Remove a UI surface - v0.9 separates surface creation from rendering — `createSurface` replaces both `beginRendering` and the implicit surface creation in `surfaceUpdate`. All messages include a `version` field. + v0.10 introduces the `actionResponse` message type, enabling robust client-to-server synchronous RPC capabilities. + +=== "v0.8 (Legacy)" + + Version 0.8 uses the following message types: + + - **`surfaceUpdate`**: Define or update UI components + - **`dataModelUpdate`**: Update application state + - **`beginRendering`**: Signal the client to render + - **`deleteSurface`**: Remove a UI surface For complete technical details, see [Message Reference](../reference/messages.md). diff --git a/docs/guides/a2ui-in-mcp-apps.md b/docs/guides/a2ui-in-mcp-apps.md index ae3257549..f5da99be2 100644 --- a/docs/guides/a2ui-in-mcp-apps.md +++ b/docs/guides/a2ui-in-mcp-apps.md @@ -104,29 +104,27 @@ MCP Apps are typically delivered as a single HTML resource from the MCP Server. 2. Use a post-build script (like the [`inline.js`](https://github.com/google/A2UI/blob/main/samples/mcp/a2ui-in-mcpapps/server/apps/src/inline.js) script in the sample) to read the `index.html` and replace external `