Resolve #58: Add ADR-0017 (Loose Coupling) and migrate to extensions array#77
Open
mindpower wants to merge 1 commit into
Open
Resolve #58: Add ADR-0017 (Loose Coupling) and migrate to extensions array#77mindpower wants to merge 1 commit into
mindpower wants to merge 1 commit into
Conversation
…, and migrate metadata to extensions array This commit formalizes the resolution to Issue #58 regarding extensibility and JSON-LD namespaces. Based on working group consensus (July 9, 2026), we are adopting a loosely coupled architecture with ARD to preserve AI-Catalog's minimalist parser. Changes included: - Added ADR-0017 to formally document the rejection of JSON-LD @context and the decision to loosely couple the ARD specification. - Updated `specification/ai-catalog.md` to remove the legacy `metadata` property across Catalog Entry and Trust Manifest schemas. - Replaced the Extensibility section with the new `extensions` array design, enforcing URL/reverse-DNS keys for vendor-specific fields.
Contributor
|
Preview: https://ai-catalog.io/pr/77/ This comment is updated automatically while the pull request preview is available. |
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
1 participant
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.
Summary
This PR formally resolves Issue #58 (Proposal for JSON-LD
@contextNamespaces) by implementing the consensus reached during the July 2 and July 9 Working Group meetings and also comments on that issue.To preserve the AI-Catalog's minimalist parser and avoid the complexity of JSON-LD graph resolution, the TSC agreed to reject the
@contextproposal. Instead, we are adopting a loosely coupled architecture with the Agentic Resource Discovery (ARD) specification and replacing the legacymetadataproperty with a strictextensionsarray.Changes Included
ADR-0017: Documents the decision to loosely couple ARD and AI-Catalog, preserving AI-Catalog as a strictly-typed "publishing format" while allowing ARD to evolve independently as a rich "discovery format."ai-catalog.md:metadataproperty from the Catalog Entry, Trust Manifest, and root schemas.extensionsarray mechanism.Motivation
This architecture allows AI-Catalog to remain a lightweight, fast "thin pointer," while freeing downstream aggregators (like ARD) to build the complex semantic envelopes they need for federated discovery without forcing those requirements into the base protocol.
Closes #58