Skip to content

catalog entry types for OpenAPI #82

Description

@sdatapix

What is the reason to not include newer media types (application/openapi+json, application/openapi+yaml) used for OpenAPI documents in the following? OpenAPI spec 3.1.1 https://spec.openapis.org/oas/v3.1.1.html refers these. I thought they should be in https://www.iana.org/assignments/media-types/media-types.xhtml but it seems https://www.ietf.org/archive/id/draft-ietf-httpapi-rest-api-mediatypes-09.html#name-iana-considerations is still an I-D.

Integrated Ecosystem & Third-Party Types (Governed externally):

  • application/a2a-agent-card+json — an A2A Agent Card
  • application/mcp-server-card+json — an MCP Server Card
  • application/agent-skills+json — Agent Skill Metadata json file
  • application/agent-skills+md — an Agent Skill defined in a standard Markdown file (the suffix +md is to be registered)
  • application/agent-skills+zip — an Agent Skill bundle (ZIP archive)
  • application/agent-skills+gzip — an Agent Skill bundle (gzipped tarball)

These values are designed to align with official IANA media type registration standards. Standard ecosystem types use registered structured syntax suffixes (+json, +zip, +gzip). For any new or custom types not listed here, it is up to the specific client implementation to handle them correctly.

Sorry if this issue is already addressed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions