Re: [patwg-charter] jwrosewell: "primarily non-technical" -> "do not have any technical component" (#8)

Why would the explicit exclusion of supporting professions and components of solutions they develop do anything other than improve the chances of the group producing solutions that provide the best outcome for the 5 billion users of the web?

There is plenty of precedent for such considerations including First Party Sets that requires an Independent Enforcement Entity (IEE) to be viable. The W3C itself is pre-occupied with issues of ethics and values with selective consideration of unintended consequences.

@martinthomson 

> I don't not want to spend my time on proposals that provide no technical guarantees.

Why would providing legal guarantees support by technical guarantees not be a good proposal to improve privacy in advertising using technology?

I'm interested in finding the best proposals and not constraining innovation by restricting proposals.

@alexcone

> Features designed primarily for privacy-related transparency and control should be developed elsewhere..

Why would the W3C not want to include such approaches to Private Advertising Technology (PATs) in its work?

@lukwlodarczyk 

> I am afraid that the output of this particular change will make it hard for any participant to differentiate the scope of work between PATCG and PATWG.

The only difference is incubation (CG) versus standards setting (WG).

@bedfordsean 

> The original idea for the creation of this group was to only focus on the technical details for advertising use cases, with an aim to actually make progress.

Now that the group has met a few times and more people joined I'm advocating to broaden that and ensure that solutions other than those that restrict data sharing are bought forward in the standards setting arena. There are already enough groups that require W3C member attention!

-- 
GitHub Notification of comment by jwrosewell
Please view or discuss this issue at https://github.com/patcg/patwg-charter/issues/8#issuecomment-1076617444 using your GitHub account


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

Received on Wednesday, 23 March 2022 17:36:09 UTC