Iva Sokolaj ae6a562d5d
docs: rename "Stream Message" to "Send Streaming Message" and replace legacy method names (#1784)
## 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.
2026-04-23 13:54:31 +02:00
..
2026-04-07 13:09:37 -04:00
2026-03-31 09:43:27 -07:00
2026-03-10 11:44:17 -07:00

A2A Docs

https://a2a-protocol.org

Developing A2A docs

  1. Clone this repository and cd into the repository directory
  2. Run pip install -r requirements-docs.txt
  3. Run mkdocs serve, edit .md files, and live preview
  4. 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.yml in the repository root contains all of the docs config, including the site navigation and organization
  • There is a GitHub Action in .github/workflows/docs.yml that builds and publishes the docs and pushes the built assets to the gh-pages branch in this repository using mkdocs gh-deploy --force. This happens automatically for all commits / merges to main.
  • 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

  1. Run the following command to build the HTML documentation:

    sphinx-build -b html docs/sdk/python docs/sdk/python/api
    
  2. The generated HTML files will be in the sdk/python/api directory. You can open sdk/python/api/index.html in your browser to view the documentation.