Robert Rothenberg

> Wouldn't this be better declared in the webpage metadata? Not every document is a web-page, e.g. images. There might even be a separate web server that serves images, or...

Also note in Section 7.1.1 (Making zero requests), the lack of a file at this location indicates that the website is not asking for consent.

> Replying with an empty file at a well-known location Also replying with 404 (Not Found).

> > > Replying with an empty file at a well-known location > > > > > > Also replying with 404 (Not Found). > > No, that is a...

> Also conceptually, it seems intuitive that the website initiates the interaction, as it is the website that requests consent. The website doesn't initiate interaction. The user agent does. Requiring...

> Indeed. But note that most websites already use a plugin or third-party Consent Management Platform (CMP) to ask for consent and handle the responses. Most? No, a lot of...

> Adding an extra round-trip before visiting a website sounds like something nobody is waiting for. The `.well-known` file could be requested in parallel though, or even after the page...

I don't see it as being relevant for Content_negotiation. ETags are used for conditional requests, not content negotiation. Nothing in the content negotiation page mentions conditional requests or ETags.

To make upgrading easier, it would make sense to have it fall back to the exact entry for cron jobs if the comment was not found.

> It took me a while to figure out what you might mean by that exactly, but I believe it's this: "if there's already a cronjob that is an exact...