A2A/docs/tutorials/python/8-next-steps.md
Gijs Walraven 7245512250
docs: correct Part discriminator values and remove stale v0.3.x type names (#1490)
## Summary

Fixes documentation inconsistencies related to Part discriminator field
values, identified in #1365.

## Changes

### `docs/specification.md` — Appendix A.2.1

- **Legacy Part `kind` values**: corrected from PascalCase (`"kind":
"TextPart"`, `"kind": "FilePart"`, `"kind": "DataPart"`) to lowercase
(`"kind": "text"`, `"kind": "file"`, `"kind": "data"`), consistent with
what `whats-new-v1.md` documents as the v0.3.0 format
- **Legacy FilePart structure**: added the missing nested `file` object
wrapper
- **Legacy streaming event `kind` values**: corrected from PascalCase
(`TaskStatusUpdateEvent`, `TaskArtifactUpdateEvent`) to camelCase
(`taskStatusUpdate`, `taskArtifactUpdate`)
- **Current `DataPart` migration target**: removed incorrect
double-wrapping (`{ "data": { "data": {...} } }` → `{ "data": {...},
"mediaType": "application/json" }`)
- **Current streaming event member names**: aligned with
`whats-new-v1.md` (`taskStatusUpdate` / `taskArtifactUpdate`)

### `docs/topics/key-concepts.md`

- Updated Part description to use v1.0 terminology, removing references
to the removed `TextPart`, `FilePart`, and `DataPart` types

### `docs/tutorials/python/8-next-steps.md`

- Replaced reference to removed `DataPart` type with v1.0 Part field
names

### `CONTRIBUTING.md`

- Added **Documentation Guidelines** section with correct v1.0 Part
examples (member-presence pattern) and guidance on the correct v0.3.x
lowercase `kind` discriminator values for migration docs

## Related

- Closes #1365
- External community site fix:
https://github.com/sing1ee/a2a-directory/pull/12

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
2026-02-18 10:11:37 -06:00

3.0 KiB

Next Steps

Congratulations on completing the A2A Python SDK Tutorial! You've learned how to:

  • Set up your environment for A2A development.
  • Define Agent Skills and Agent Cards using the SDK's types.
  • Implement a basic HelloWorld A2A server and client.
  • Understand and implement streaming capabilities.
  • Integrate a more complex agent using LangGraph, demonstrating task state management and tool use.

You now have a solid foundation for building and integrating your own A2A-compliant agents.

Where to Go From Here?

Here are some ideas and resources to continue your A2A journey:

  • Explore Other Examples:
  • Deepen Your Protocol Understanding:
  • Review Key A2A Topics:
  • Build Your Own Agent:
    • Try creating a new A2A agent using your favorite Python agent framework (like LangChain, CrewAI, AutoGen, Semantic Kernel, or a custom solution).
    • Implement the a2a.server.AgentExecutor interface to bridge your agent's logic with the A2A protocol.
    • Think about what unique skills your agent could offer and how its Agent Card would represent them.
  • Experiment with Advanced Features:
    • Implement robust task management with a persistent TaskStore if your agent handles long-running or multi-session tasks.
    • Explore implementing push notifications if your agent's tasks are very long-lived.
    • Consider more complex input and output modalities (e.g., handling file uploads/downloads via file Parts, or structured data via data Parts).
  • Contribute to the A2A Community:

The A2A protocol aims to foster an ecosystem of interoperable AI agents. By building and sharing A2A-compliant agents, you can be a part of this exciting development!