## 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>
41 lines
3.0 KiB
Markdown
41 lines
3.0 KiB
Markdown
# 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:**
|
|
- Check out the other examples in the [a2a-samples GitHub repository](https://github.com/a2aproject/a2a-samples/tree/main/samples) for more complex agent integrations and features.
|
|
- **Deepen Your Protocol Understanding:**
|
|
- 📚 Read the complete [A2A Protocol Documentation site](https://a2a-protocol.org) for a comprehensive overview.
|
|
- 📝 Review the detailed [A2A Protocol Specification](../../specification.md) to understand the nuances of all data structures and RPC methods.
|
|
- **Review Key A2A Topics:**
|
|
- [A2A and MCP](../../topics/a2a-and-mcp.md): Understand how A2A complements the Model Context Protocol for tool usage.
|
|
- [Enterprise-Ready Features](../../topics/enterprise-ready.md): Learn about security, observability, and other enterprise considerations.
|
|
- [Streaming & Asynchronous Operations](../../topics/streaming-and-async.md): Get more details on SSE and push notifications.
|
|
- [Agent Discovery](../../topics/agent-discovery.md): Explore different ways agents can find each other.
|
|
- **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:**
|
|
- Join the discussions on the [A2A GitHub Discussions page](https://github.com/a2aproject/A2A/discussions).
|
|
- Report issues or suggest improvements via [GitHub Issues](https://github.com/a2aproject/A2A/issues).
|
|
- Consider contributing code, examples, or documentation. See the [CONTRIBUTING.md](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md) guide.
|
|
|
|
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!
|