well-known resource

[martinthomson]

Google's Q3 report to the UK CMA says:

Yes, the submission guidelines have been changed, and the primary domain must serve a JSON file at /.well-known/related-website-set.json.

But I see no evidence of that URL in either explainer or specification.

[krgovind]

@martinthomson Thanks for the question. The .well-known file is processed out-of-band relative to the user agent, so it is defined as a separate document that is housed here. It's linked from the introduction section of the specification:

This document defines how user agents should integrate with the Related Website Sets list. For a canonical reference of the structure of the RWS list and technical validations that are run at time of submission, please see the Related Website Sets Submission Guidelines.

Happy to incorporate if you have any feedback on improving this.

[martinthomson]

That link is broken, but I found the file here.

I would recommend a specification for this. See Section 5.1 of RFC 8615 for details on what a specification should contain.

[krgovind]

I would recommend a specification for this. See Section 5.1 of RFC 8615 for details on what a specification should contain.

Ack. Thank you. #150 is related and we intend to resolve this in the next few weeks.

[sjledoux]

I would recommend a specification for this. See Section 5.1 of RFC 8615 for details on what a specification should contain.

The well-known URI related-website-set.json is now registered with IANA. There is also now a specification document for the well-known file in the submission repository.