Given in Appendix A could be moved into Section 3.
Allowing every URI path segment to have a well-known location
(e.g., "/images/.well-known/") would increase the risks of
colliding with a preexisting URI on a site, and generally these
solutions are found not to scale well because they're too
"chatty".
An example like https://foo.example/.well-known/fooapp/baz.example/stuff, making it extra clear that well-known names are namespaces, and showing how to use them for multi-tenancy, would help.
See today's thread on gen-art about this.
The answer to:
Given in Appendix A could be moved into Section 3.
An example like
https://foo.example/.well-known/fooapp/baz.example/stuff
, making it extra clear that well-known names are namespaces, and showing how to use them for multi-tenancy, would help.