- From: timcowen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jun 2022 06:33:59 +0000
- To: public-patcg@w3.org
Martin, You reference a previous discussion that appears to have been resolved with: “The purpose of these features is to support web advertising in private ways. Here "private" refers to appropriate processing of personal information.” Would that work here? Kind regards, Tim Tim Cowen | Chair Antitrust Practice ddl +44 20 7332 5645<tel:+44%2020%207332%205645> m +44 78 0224 1629<tel:+44%2078%200224%201629> ***@***.*** Preiskel & Co LLP, 4 King's Bench Walk, Temple, London EC4Y 7DL t +44 20 7332 5640<tel:+44%2020%207332%205640> f +44 20 7332 5641<tel:+44%2020%207332%205641> www.preiskel.com<http://www.preiskel.com/> personal profile<http://www.preiskel.com/people/tim-cowen/> Chambers & Partners Competition, IT & Telecoms Leading Firm 2018 Legal 500 Technology, Media and Telecoms Leading Firm 2017 WhosWhoLegal Telecoms Media & Tech Leading Lawyers 2017 Global Law Experts Communications Law Firm of the Year 2016 Preiskel & Co LLP is a law firm authorised and regulated by the Solicitors Regulation Authority and is incorporated in England & Wales with partnership number OC306371 and Registered Office at 4 King's Bench Walk, Temple, London EC4Y 7DL. A list of members is available for inspection at the office. The SRA rules can be found at http://www.sra.org.uk/solicitors/handbook/code/content.page. Preiskel & Co LLP takes the privacy and security of personal data and confidential information seriously. The content of this e-mail, including any attachments, is intended only for the recipient(s) named above, and may be confidential, privileged or otherwise legally protected against disclosure. If you have received this e-mail in error please notify us ***@***.******@***.***> and delete it from your system. On 30 Jun 2022, at 05:14, Martin Thomson ***@***.***> wrote: @AramZS<https://github.com/AramZS>: privacy is not defined nowhere. It is specifically defined in the charter's scope I want to push back on this a little. #6<https://github.com/patcg/patwg-charter/issues/6> didn't resolve with a definition. As @npdoty<https://github.com/npdoty> says, privacy is more complex than that. What the resolution to #6<https://github.com/patcg/patwg-charter/issues/6> does is what we often do in charters: sets some bounds on what we are doing. That resolution is what I see as being equivalent guard rails: something where we can easily identify as being unacceptable. Ideally, there is some distance between that and what we eventually produce. But the exact parameters of that are open for discussion. What "privacy" means here is - at least to the extent to which it applies to what we are doing - open to discussion. It is entirely possible that we never completely agree, but we produce a specification that we can all get behind anyway. That might be because it is flexible enough to allow for some variation in how it is interpreted or implemented. It might just be that it only captures the stuff we can achieve consensus on and so it is limited in applicability or scope. Asking that we have a precise definition for something that is so complex and subjective might make sense in a legal context (I'm not sure that it does). Here, we don't need that level of definition, especially as a constraint on the work we undertake. That is because our work is to build something out of the intersection of the competing definitions, concepts, and ideas that we each have. Not just about privacy, but security, accessibility, openness, fairness, and all the other things we each might value. — Reply to this email directly, view it on GitHub<https://github.com/patcg/patwg-charter/issues/31#issuecomment-1170735429>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZYERR2OPH754RFNON66PI3VRUNL5ANCNFSM52GCPI4Q>. You are receiving this because you were mentioned.Message ID: ***@***.***> -- GitHub Notification of comment by timcowen Please view or discuss this issue at https://github.com/patcg/patwg-charter/issues/31#issuecomment-1170823192 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 June 2022 06:34:00 UTC