[patwg-charter] Charter should include baseline privacy boundaries (#61)

ShivanKaul has just created a new issue for https://github.com/patcg/patwg-charter:

== Charter should include baseline privacy boundaries  ==
For this group to be successful, it needs to have a very clear definition of what the minimum privacy goals and boundaries are, and the charter currently lacks this.

The charter currently says:

>The purpose of these features is to support web advertising without compromising user privacy. Here “privacy” minimally refers to appropriate processing of personal information. Ways in which new features might enable inappropriate processing include (but are not limited to) enabling of cross-site or cross context recognition of users or enabling same-site or same-context recognition of users across the clearing of state.

The goal of this group is to produce specs that enable web advertising (easy) without compromising privacy (hard). Without the privacy bit, the advertising use-cases are straightforward. So for this group to be meaningfully deliver on its stated goal, we need to be very clear about what exactly we mean by the "privacy" constraint. To be clear, I'm not suggesting that try to put down every single privacy risk that could ever arise - some of those will be clear once the proposals start taking more shape. But we need a minimum baseline of privacy boundaries that will not be violated by any spec that we work on, and right now we don't have it. This baseline cannot be defined post facto, once we already have a technical solution that we like. Otherwise, we seriously risk overfitting the privacy and security boundaries around whatever spec we work on and decide to ship. 

Please view or discuss this issue at https://github.com/patcg/patwg-charter/issues/61 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 8 May 2023 20:09:48 UTC