feat: discovery by PURL as an alternative to TEI - #265
Merged
Merged
Conversation
/discovery accepts either `tei` or `purl`; exactly one shall be given, a request with neither or both is rejected with 400. OpenAPI cannot express that constraint across query parameters, so `tei` becomes optional and the rule is stated in the descriptions. Discovery by TEI resolves across TEA servers through the domain the TEI carries; discovery by PURL resolves within the inventory of the server receiving the request, since a PURL carries no domain. Spec only; documentation unchanged. Validated with openapi-generator v7.12.0 (validate; Go batch generation as CI runs it). Signed-off-by: Pavel Shukhman <pavel@reliza.io>
oej
requested changes
Sep 10, 2026
Signed-off-by: Pavel Shukhman <pavel@reliza.io>
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
2 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.
/discovery accepts either
teiorpurl; exactly one shall be given, a request with neither or both is rejected with 400. OpenAPI cannot express that constraint across query parameters, soteibecomes optional and the rule is stated in the descriptions.Discovery by TEI resolves across TEA servers through the domain the TEI carries; discovery by PURL resolves within the inventory of the server receiving the request, since a PURL carries no domain.
Spec only; documentation unchanged to prevent conflicts with #261 . Validated with openapi-generator v7.12.0 (validate; Go batch generation as CI runs it).