[w3ctag/design-reviews] Service discovery (Issue #1243)

matatk created an issue (w3ctag/design-reviews#1243)

We have seen a number of proposals that relate to facilitating service discovery. Due to the not exactly 1:1 mapping between a (sub-)domain, and what the user may see as a self-contained website or app, approaches that use the `.well-known` namespace have to come up with their own approach to routing. We're tracking various proposals here, in the hopes of creating a more harmonized approach in future.

* #1217 ([Tag Bot for #1217](https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1217))

* [Discoverable Destinations](https://github.com/w3c/adapt/blob/main/explainers/discoverable-destinations.md) (formerly used well-known URLs, but moved away from that, to `<link>`s and `rel` attributes)

* [A Well-Known URL for Changing Passwords](https://github.com/w3c/webappsec-change-password-url) (could this benefit from being able to also target distinct sites hosted deeper in the URL tree?)

* [Well-Known URI for Accessibility Issue Reporting](https://github.com/AutoSponge/well-known-accessibility-report)

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1243


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1243
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1243@github.com>