ProtocolSchemas
The specification's own schema documents, embedded in the library.
A catalog is not self-contained. Nearly every property it defines is a $ref into common_types.json — thirty-two of them to DynamicString alone — and the definition that combines a component's envelope with its catalog-defined half lives in agent_to_renderer.json. Resolving those over the network would let whoever sent the payload choose what the payload is validated against, so the documents ship with the library instead.
The text is generated from a2ui-core/spec/ at build time and is byte-for-byte the specification's own; see a2ui-core/spec/README.md for the revision each was taken from.
Properties
The URI agent_to_renderer.json publishes as its $id.
agent_to_renderer.json.
catalog_definition.json, which describes a catalog rather than a message.
The URI common_types.json publishes as its $id.
common_types.json.
Where a component is checked from: agent_to_renderer.json#/$defs/Component.
Every document, in the shape SchemaRegistry.of takes.
Where a FunctionCall is checked from: common_types.json#/$defs/FunctionCall.
The URI of the JSON Schema 2020-12 meta-schema. See metaSchemaStandIn.
The URI renderer_to_agent.json publishes as its $id.
renderer_to_agent.json.