7
1
Fork
You've already forked interop
0

Elaborate on the concept of tiers #19

Merged
txels merged 1 commit from discovery-tiers into main 2026年06月22日 13:31:51 +02:00
Owner
Copy link

...I had expressed this idea a few times but never put it in writing.

...I had expressed this idea a few times but never put it in writing.
Add an elaboration on the concept of tiers
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
3802c514fc
@ -0,0 +33,4 @@
Fairplayer started prototyping a search endpoint. The basic idea is to:
- add a standard `link` tag e.g. `<link rel="search" href="/search?q=%s" />`
- (optionally) that search URL can handle content negotiation to offer two versions of the results (HTML and JSON)
- For JSON results, use a standard schema. We could use a mininum required well-known subset of Canimus (that includes entity type, name, url, image, ...) to make this compatible with [catalog](../specs/catalog/data-model.md)
Author
Owner
Copy link

This is something I would like to change on the Fairplayer side, so that search result entities follow the same schema as the "standard catalog" (i.e. a very basic subset of Canimus). cc @MaciAc

...which makes me think we should start thinking of shaping the Canimus spec as being a "basic schema" with "add-ons" for different use cases. To some extent it is, but has a very binary definition of "required vs optional", and maybe things could be "required" or not within the context of an "add-on" (like streaming, purchasing, etc...).

This is something I would like to change on the Fairplayer side, so that search result entities follow the same schema as the "standard catalog" (i.e. a very basic subset of Canimus). cc @MaciAc ...which makes me think we should start thinking of shaping the Canimus spec as being a "basic schema" with "add-ons" for different use cases. To some extent it is, but has a very binary definition of "required vs optional", and maybe things could be "required" or not within the context of an "add-on" (like streaming, purchasing, etc...).
txels force-pushed discovery-tiers from 3802c514fc
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
to 0e18cc1499
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
2026年06月19日 13:18:32 +02:00 Compare
txels changed title from (削除) Add an elaboration on the concept of tiers (削除ここまで) to Elaborate on the concept of tiers 2026年06月19日 14:26:59 +02:00
txels force-pushed discovery-tiers from 0e18cc1499
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
to e4a1c5e303
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
2026年06月22日 13:31:36 +02:00 Compare
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fairplayer/interop!19
Reference in a new issue
fairplayer/interop
No description provided.
Delete branch "discovery-tiers"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?