spec: Updates based on discussions during last meeting#33
Merged
Conversation
Spec changes (per issue #28 action items): - Remove top-level collections array and CollectionRef type - Eliminate bundle as a distinct concept (nested catalogs only) - Rename inline -> data (oneOf with url) - Add dual-protocol agent example (MCP + A2A) - Reduce max nesting depth from 8 to 4 - Replace ASCII tree diagrams with JSON examples - Standardize MCP media type to application/mcp-server-card+json - Standardize skill media type to application/agentskill+zip - Remove Claude Code Plugin Entry example section ADRs from 2026-04-02 working group meeting: - 0001: Nesting depth limit of 4 - 0002: Defer entry dependency expression - 0003: Remove collections in favor of entries - 0004: Eliminate bundle concept - 0005: Add data member (oneOf with url) - 0006: Single url per entry - 0007: url field name over href - 0008: Media type only (no artifactType) - 0009: Trust manifest substitution attack - 0010: AI Card terminology - 0011: No .well-known URI requirement - 0012: Extensibility via metadata property - 0013: AI Catalog as authoring format, OCI as distribution Refs: #28 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fixes: - Replace stale 'inline' terminology with 'embed' - Fix typo in researchAssistant URL - Remove 'bundle' terminology from discovery section - Fix missing space in conformance levels - Fix indentation in nested data JSON block - Update 'MCP manifest' to 'MCP Server Card' New examples added for: - Host Info object - Multi-Version Entries (same identifier, different versions) - Trust Manifest (complete standalone example) - Trust Schema object - Attestation object (SOC2 with digest) - Provenance Link object (full lineage chain) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Added 7 new security subsections: circular references, trust manifest substitution, catalog poisoning, identifier typosquatting, stale attestations, embedded content safety, and privacy considerations - Fixed MCP Registry mapping to correctly distinguish server.json (Registry package metadata) from Server Cards (SEP-1649 discovery) - Added Note box clarifying the two MCP artifact types - Changed Registry examples to use application/json with server.json URLs - Fixed Decentralized Discovery prose that conflated the two formats - Added Metadata Extensibility section with key naming conventions - Added Version Handling section with compatibility rules Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restructure Security Considerations around a four-layer trust model: - Layer 0: HTTPS transport security - Layer 1: Trust Manifest with provenance digests (advisory) - Layer 2: Signed Trust Manifest (closes substitution gap) - Layer 3: OCI content-addressed distribution Explicitly notes that digest verification without signature verification does not protect against catalog-level substitution. Catalog Poisoning section now cross-references the trust layers. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The upstream build pipeline now generates the ReSpec HTML. No need to commit it in the source branch. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- ADR-0011: Soften position from 'no .well-known' to '.well-known is optional but registered as a convention' - Add IANA Well-Known URI registration section for ai-catalog.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
diff can be seen here https://agent-card.github.io/ai-catalog/pr/33/index.html |
Contributor
|
Preview unavailable. The pull request preview was removed because this pull request is closed. |
mindpower
approved these changes
Apr 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #28 for details.
Replaces #29