What happened?
The A2A JSON Schema definition are being generated from proto file part of the build docs process and is published here - https://a2a-protocol.org/latest/definitions/#json
However, the generated JSON schema has few issues:
$refs in the document references some external location and not the entity definitions part of the current document.
Example:
lf.a2a.v1.AgentCapabilities.jsonschema.json is a non-existent location. This should instead refer to $defs/Agent Capabilities.
"capabilities": {
"$ref": "lf.a2a.v1.AgentCapabilities.jsonschema.json",
"description": "A2A Capability set supported by the agent."
}
- Redudant
$schema attribute for child definitions. These are not valid without $id attribute. The $schema property should be removed for child resources.
Example:
"Struct": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Struct",
"type": "object"
},
definitions has been replaced with $defs for 2020-12 schema version.
Relevant log output
Code of Conduct
What happened?
The A2A JSON Schema definition are being generated from proto file part of the build docs process and is published here - https://a2a-protocol.org/latest/definitions/#json
However, the generated JSON schema has few issues:
$refsin the document references some external location and not the entity definitions part of the current document.Example:
lf.a2a.v1.AgentCapabilities.jsonschema.json is a non-existent location. This should instead refer to $defs/Agent Capabilities.
$schemaattribute for child definitions. These are not valid without$idattribute. The$schemaproperty should be removed for child resources.Example:
definitionshas been replaced with$defsfor 2020-12 schema version.Relevant log output
Code of Conduct