AG2 0.10 release introduces A2A support, enabling agents to communicate
across different processes, machines, applications, and even different
frameworks and languages. So, I think it would be great to add this
integration to the list.
## Problem
**The "filename” metadata label** in key-concept.md does not quite align
with FileBase property. As indicated in the specification.md, name,
mineType or bytes labels are part of the FilePart metadatas, instead of
using filename label.
<img width="950" height="557" alt="image"
src="https://github.com/user-attachments/assets/de687e31-e184-4036-a35b-763649bae682"
/>
## Solution
Replace “filename” metadata label with “name” label to align with
FileBase property.
## Changes
Modify A2A\docs\topics\key-concepts.md and **replace “filename” metadata
label with “name” label** to better align with FileBase property from
specification.
## Testing
✅ Documentation builds successfully with mkdocs
✅ Markdown linting passes
✅ All internal anchor links verified
✅ No broken cross-references
## Issue
Fixes#1167
# Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:
- [x] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [x] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)
- [x] Fix existing linting errors (I guess they were already on the main
upstream)
Fixes#761🦕
---------
Signed-off-by: Eden Reich <eden.reich@gmail.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
### Issues with this approach
- Style updates or link changes relating to other documentation pages
won't be propagated to the specification doc when other pages are
updated.
### Alternatives
- Maintain copies of the specification docs for each minor version
`0.X.0`
- Similar to MCP Docs
https://github.com/modelcontextprotocol/modelcontextprotocol/tree/main/docs/specification
- This would also allow us to not use mike for versioning (would get rid
of `latest` in URLs and could simplify SEO)
Follow-up to #1077
# Webhook Certificate Checks
## User Benefit
While it is specified that Clients SHOULD verify Server identity through
the certificate, it is not currently explicit that Servers also have
this responsibility when delivering an update to a web hook URL. It
would be beneficial to users if uniform requirements on identity
verification were explicitly specified. Having a variation in
requirements that depends on whether responses are delivered
synchronously or asynchronously is surprising and seems unintentional.
The risk involved in not confirming the web hook certificate includes a
potential breach of confidentiality of response payload.
## This Change
This PR proposes an additional statement making explicit the A2A Server
responsibility when delivering asynchronous payload updates to
authenticate the destination certificate.
## Compatibility
In theory, a previously fully conforming implementation that did not
perform a check on a web hook server certificate would not meet the new
SHOULD statement. I couldn't locate information about what this implies
eg. with respect to versioning.
In practice, it seems at least somewhat unlikely that implementations
does this because verification of server certificates is the default
behavior across many different software toolsets for some time.
Closes#978
# Description
fix typo `forseeable` -> `foreseeable`
- [ ✅ ] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [ ✅ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [ ✅ ] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [ ✅ ] Appropriate docs were updated (if necessary)
Fixes#972🦕
Signed-off-by: Sun Yuhan <sunyuhan1998@users.noreply.github.com>
Co-authored-by: Sun Yuhan <sunyuhan1998@users.noreply.github.com>
There are a few links in the spec doc that are clearly meant to link to
the github repo as the files they link to are outside the docs folder.
This fixes them so they work on the generated site hosted at
https://a2a-protocol.org/
Ideally we would use relative links so that when reading the markdown
file in your IDE the links take you to the corresponding file within the
repo. I tried setting up a redirect in mkdocs.yml but the locally
running website kept downloading the file from github instead of
navigating to it. There is probably some plugin that will make this work
however for now I would like to simply fix the docs on the website.
# Description
This change adds support for a new JSON-RPC method
`agent/getAuthenticatedExtendedCard` for fetching authenticated extended
card.
This is only applicable if `AgentCard.supportsAuthenticatedExtendedCard`
bit is set to `true` that allows fetching authenticated context specific
agent card.
In the previous versions, the extended card was served via
`{AgentCard.url}/../agent/authenticatedExtendedCard` endpoint. This
endpoint is being removed in favor of the JSON-RPC method. This endpoint
will be deprecated in the SDKs and will be removed in a future release.
Release-As: 0.3.0
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>