## Summary Standardizes the operation names used throughout the spec and Python tutorials so they match the canonical A2A operation names (`Send Message` / `Send Streaming Message`) instead of the older JSON-RPC-style identifiers (`message/send`, `message/stream`) or the inconsistent short form `Stream Message`. ## Changes - **`docs/specification.md`** - Architecture diagram: `Stream Message` → `Send Streaming Message`. - Section 3.1.3 (Get Task): `message/send` → `Send Message`. - Event delivery section: `Stream Message` → `Send Streaming Message`. - Multi-protocol functionality table: `Stream message` → `Send Streaming Message`. - **`docs/tutorials/python/4-agent-executor.md`**: `message/send` / `message/stream` → `Send Message` / `Send Streaming Message`. - **`docs/tutorials/python/6-interact-with-server.md`**: same rename in the `test_client.py` description. - **`docs/tutorials/python/7-streaming-and-multiturn.md`**: `message/send` → `Send Message` in the `CurrencyAgentExecutor` walkthrough. ## Why The docs previously mixed three different names for the same operations (`message/stream`, `Stream Message`, `SendStreamingMessage`), which was confusing for readers cross-referencing the spec, tutorials, and SDK. This change picks one human-readable form per operation and uses it consistently in prose, while leaving the code-level identifiers (`SendMessage`, `SendStreamingMessage`, `POST /message:stream`, etc.) untouched in the protocol-binding tables.
A2A Docs
Developing A2A docs
- Clone this repository and
cdinto the repository directory - Run
pip install -r requirements-docs.txt - Run
mkdocs serve, edit.mdfiles, and live preview - Contribute docs changes as usual
How it works
- The A2A docs use mkdocs and the mkdocs-material theme
- All of the source documentation / Markdown files related to the A2A docs are
in the
docs/directory in the A2A repository mkdocs.ymlin the repository root contains all of the docs config, including the site navigation and organization- There is a GitHub Action in
.github/workflows/docs.ymlthat builds and publishes the docs and pushes the built assets to thegh-pagesbranch in this repository usingmkdocs gh-deploy --force. This happens automatically for all commits / merges tomain. - The A2A documentation is hosted in GitHub pages, and the settings for this are in the A2A repository settings in GitHub.
Building the Python SDK Documentation
The Python SDK documentation is built using Sphinx.
Prerequisites
Ensure you have installed the documentation dependencies:
pip install -r ../../requirements-docs.txt
Building the Docs
-
Run the following command to build the HTML documentation:
sphinx-build -b html docs/sdk/python docs/sdk/python/api -
The generated HTML files will be in the
sdk/python/apidirectory. You can opensdk/python/api/index.htmlin your browser to view the documentation.