- From: Justin Brookman <justin.brookman@consumer.org>
- Date: Fri, 24 Feb 2023 12:51:05 -0500
- To: public-privacycg@w3.org
- Message-ID: <CAL0pBL1tsdWpW-P24m40kXsJ6uZnCU=8CsuUWMQV3EUosi4r=g@mail.gmail.com>
Hey, I wanted to give folks a heads up that we discussed whether to maintain the optional well-known resource for GPC on the Privacy-CG call yesterday (issue 33 <https://github.com/privacycg/gpc-spec/issues/33>). Based on that discussion (notes here <https://docs.google.com/document/d/1DZEhS1UHJ1PKxt5ZwKmn5LZ4bo10UFyNXeLp2dUuzRM/edit#>), we decided to retain the resource and close the issue next week, but wanted to flag for the broader community to see if others who were not on the call had a strong objection to this approach. Separately, Pete Snyder opened a pull request <https://github.com/privacycg/gpc-spec/pull/48> to propose revising the well-known resource to provide dynamic information as to whether individual users' GPC requests are honored. Assuming we do in fact retain the resource, we will consider this and other proposals to convey more fine-grained information about GPC compliance going forward. Feedback on the PR would be appreciated. Finally, there aren't a lot of open issues on the spec right now, so if folks have other points they want to raise I encourage you to open a new issue or PR. -- *** This e-mail message is intended only for the designated recipient(s) named above. The information contained in this e-mail and any attachments may be confidential or legally privileged. If you are not the intended recipient, you may not review, retain, copy, redistribute or use this e-mail or any attachment for any purpose, or disclose all or any part of its contents. If you have received this e-mail in error, please immediately notify the sender by reply e-mail and permanently delete this e-mail and any attachments from your computer system. ***
Received on Friday, 24 February 2023 17:53:10 UTC