-
Notifications
You must be signed in to change notification settings - Fork 52
Add direct catalog entry lookup by identifier #74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
hstaudacher
wants to merge
2
commits into
ards-project:main
Choose a base branch
from
hstaudacher:hstaudacher-add-entry-lookup-endpoint
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+369
−39
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| # ADR-0010: Direct Catalog Entry Lookup by Identifier | ||
|
|
||
| ## Status | ||
|
|
||
| Proposed | ||
|
|
||
| ## Context | ||
|
|
||
| ARD identifiers are stable, globally unique primary keys, but the Registry API previously offered only semantic Search and optional deterministic List operations. Search requires natural-language input and adds ranking metadata. List returns a paginated collection and does not define canonical exact-identifier semantics. Neither operation lets a client efficiently resolve an identifier retained from earlier discovery. | ||
|
|
||
| The lookup operation also needs a clear federation boundary. Automatically forwarding a primary-key lookup would make latency and authority unpredictable, while returning a Search result would expose fields that are not part of the canonical Catalog Entry Object. | ||
|
|
||
| ## Decision | ||
|
|
||
| Agent Registries expose mandatory `GET /agents/{identifier}` lookup. | ||
|
|
||
| The complete identifier is UTF-8 percent-encoded as one path segment. A registry decodes it exactly once, validates the decoded ARD identifier, and performs an exact, case-sensitive lookup against its local index. The registry does not query upstream registries for this operation. Entries ingested from external publishers remain eligible because they are part of the local index. | ||
|
|
||
| A successful lookup returns the canonical Catalog Entry Object without Search-only fields. Malformed identifiers return `400 INVALID_ARGUMENT`; valid identifiers absent from the local index return `404 NOT_FOUND`. The endpoint follows the deployment's existing Registry authentication policy and standard HTTP caching semantics. | ||
|
|
||
| ## Consequences | ||
|
|
||
| - Clients can resolve a retained ARD identifier in one deterministic request. | ||
| - OpenAPI clients receive a typed identifier parameter and Catalog Entry response. | ||
| - Registries need an indexed exact-match route in addition to semantic Search. | ||
| - Clients retaining federated Search results should retain `source` with the identifier and use it to resolve the entry at its originating registry. | ||
| - Conformance testing verifies encoded success, malformed identifiers, and unknown identifiers. | ||
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.