Spec: Update mediaType to type for catalogEntry and add known types#37
Spec: Update mediaType to type for catalogEntry and add known types#37mindpower wants to merge 9 commits into
Conversation
|
Preview: https://agent-card.github.io/ai-catalog/pr/37/ This comment is updated automatically while the pull request preview is available. |
…est (which is different from the type for catalog entry) and fix the type to application/mcp-server+json in examples
| - `application/ai-catalog+json` | ||
| - `application/ai-skills+tgz` | ||
| - `application/ai-skills+zip` | ||
| - `application/ai-skills+md` |
There was a problem hiding this comment.
As there is no registered suffix, it would not be possible at present to register this media type.
There was a problem hiding this comment.
Changed this application/ai-skills+md to text/markdown; profile=ai-skill
| - `application/a2a-agent-card+json` | ||
| - `application/mcp-server+json` | ||
| - `application/ai-catalog+json` | ||
| - `application/ai-skills+tgz` |
There was a problem hiding this comment.
There is a +gzip but there is not +tgz that is registered and so currently it would not be possible to register this media type.
There was a problem hiding this comment.
Updated the adr and spec. Added the +gzip but removed +tgz.
| - `application/ai-skills+zip` — an AI Skill bundle (ZIP archive) | ||
| - `application/ai-skills+md` — an AI Skill defined in Markdown | ||
|
|
||
| These values combine the artifact type with the payload format. For any new or custom types not listed here, it is up to the specific client implementation to handle them correctly. |
There was a problem hiding this comment.
Should we split the ai-catalog/ai-card managed media types, from the third party ones? I was envisioning something like:
AI Catalog types:
application/ai-catalog+json - nested AI Catalog
application/agent-card+json - reserved Agent Card media type
Third Party Types:
(A2A, MCP etc)
…d syntax standards
… and specification
|
The attestation object already has a "type" and "mediaType" and now type in the entry is actually a media type. It seems confusing and inconsistent to me when i read this again. |
Update AI-catalog spec based on meeting agreement on date: 04/30/2026, 05/14/2026
Move from
mediaTypetotypeinCatalogEntrymediaTypefield totypein catalog entries to avoid confusion with generic IANA media types.typefield is an open text format accepting any string value. However, a set of recognized "known types" is recommended for interoperability (e.g.,application/a2a-agent-card+json,application/mcp-server+json,application/ai-catalog+json,application/agent-registry, and format-specific skills like+gzip,+zip,+json). Clients are responsible for handling new or unknown types.