The spec describes one way to find a feed from a website (the <link rel> in § Discovery). Two further mechanisms are widely assumed but never settled:
/.well-known/ote-feed<script type="application/ote+json"> embedded in the page
Both are implemented in the reference implementation, @opentechevents/discover-feed, behind the wellKnown / embedded options — off by default, and not exposed in the validator UI, precisely because the spec has not decided.
A third question rides along: application/ote+json vs. application/feed+json. Because it is open, the implementation matches media types laxly and accepts both. Once the spec picks one, the loser can become a definite answer plus a warning, instead of a silent accept.
What is needed
Downstream, in OpenTechEvents/ote-tools, that turns into: flip the defaults in packages/discover-feed, expose them in the validator UI, and replace the lax media-type match with an answer plus a warning.
Why this issue exists
ote-tools' handoff notes tracked this against #6 for a while. That is the umbrella "define the Feed Schema" issue, not a discovery one — so nothing was actually tracking the decision. This issue is that tracker.
The spec describes one way to find a feed from a website (the
<link rel>in § Discovery). Two further mechanisms are widely assumed but never settled:/.well-known/ote-feed<script type="application/ote+json">embedded in the pageBoth are implemented in the reference implementation,
@opentechevents/discover-feed, behind thewellKnown/embeddedoptions — off by default, and not exposed in the validator UI, precisely because the spec has not decided.A third question rides along:
application/ote+jsonvs.application/feed+json. Because it is open, the implementation matches media types laxly and accepts both. Once the spec picks one, the loser can become a definite answer plus a warning, instead of a silent accept.What is needed
/.well-known/ote-feedis part of discovery, and at what conformance level (MUST / SHOULD / MAY).<script type=…>mechanism.Downstream, in OpenTechEvents/ote-tools, that turns into: flip the defaults in
packages/discover-feed, expose them in the validator UI, and replace the lax media-type match with an answer plus a warning.Why this issue exists
ote-tools' handoff notes tracked this against #6 for a while. That is the umbrella "define the Feed Schema" issue, not a discovery one — so nothing was actually tracking the decision. This issue is that tracker.