Repository navigation
spec: distinguish base URL from search endpoint for ai-registry+json urls (§5.3) - #99
Merged
mindpower merged 1 commit intoOct 11, 2026
Conversation
…gistry+json (§5.3)
sachinsharma3191
requested review from
evalstate,
mindpower and
rvguha
as code owners
September 23, 2026 16:46
mindpower
approved these changes
Oct 11, 2026
mindpower
left a comment
mindpower
left a comment
Collaborator
There was a problem hiding this comment.
Makes sense. This keeps the prose consistent with the existing referrals[] examples and ard.openapi.yaml without breaking current implementations.
LGTM, thanks!
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
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.
Fixes #91, taking option 1 from the issue.
§5.3 says the registry base URL is discovered from entries of type
application/ai-registry+json, whileRegistryReferral.url(OpenAPI and the prose examples) is the search endpoint itself. Nothing told a client which it held, so appending/searchto a referral URL gives/search/searchand a 404.This states the split explicitly: a well-known entry's
urlis a base URL; a referral'surlis the complete search endpoint and MUST NOT have/searchappended. It also updates the OpenAPIRegistryReferral.urldescription. This matches whathf-discoverandgo-ardalready do and doesn't break the published examples or live registries.Docs-only; no schema shape change. Happy to switch to option 3 (clients accept either) if maintainers prefer.