Privacy Working Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
Global Privacy Control (GPC) published as a Working Draft. History of Global Privacy Control (GPC)
-
Past meetings
-
1 meeting.
Participants
-
4 participants joined.
-
Tom Ritter (Mozilla Foundation) joined.
-
David Pham (The Washington Post) joined.
-
Laura Book (Snap) joined.
-
Joey Knightbrook (Snap) joined.
-
-
1 organization joined.
-
Snap joined.
-
GitHub
w3c/gpc
-
1 issue closed.
-
4 issues received 7 new comments.
-
Add privacy and security considerations sections w3c/gpc#84 (3 comments by @pes10k, @SebastianZimmeck)
-
Clarify "targeted advertising" versus "cross-site targeted advertising"? w3c/gpc#83 (2 comments by @j-br0, @michaelkleber)
-
w3c/gpc#80 (1 comment by @j-br0)
-
Clarify that GPC signal does not legitimize cross-site tracking as default web condition w3c/gpc#82 (1 comment by @j-br0)
-
-
2 pull requests opened.
-
1 pull request merged.
-
Move laws to explainer w3c/gpc#81.
-
-
1 pull request reopened.
-
Move laws to explainer w3c/gpc#81, by @j-br0.
-
-
2 pull requests received 7 new comments.
-
Update Explainer to add new 6.4 (Consent to Track Notwithstanding a Universal GPC Signal) w3c/gpc#88 (4 comments by @j-br0, @jyasskin, @martinthomson, @rinchen)
-
Clarify GPC not intended as endorsement of tracking or opt-out regulatory models w3c/gpc#87 (3 comments by @martinthomson, @rinchen)
-
w3cping/tracking-issues
-
5 issues opened.
-
ClipboardChange event API w3cping/tracking-issues#492, by @w3cbot.
-
Implicit consent via getUserMedia should allow access to non-miked speakers w3cping/tracking-issues#491, by @w3cbot.
-
What is the purpose of requiring a successful gUM call before enumerateDevices? w3cping/tracking-issues#490, by @w3cbot.
-
PING review for v1.0 w3cping/tracking-issues#489, by @w3cbot.
-
Discuss or address possible implementor privacy and security relevant concerns w3cping/tracking-issues#488, by @w3cbot.
-
w3cping/privacy-request
-
2 issues opened.
-
Final Review Request of seven (7) W3C VCWG Specifications w3cping/privacy-request#153, by @msporny.
-
WebRTC API 2024-10-12 > 2025-01-31 w3cping/privacy-request#152, by @dontcallmedom.
-
-
3 issues closed.
-
WebAssembly 2024-10-07 > 2024-10-31 w3cping/privacy-request#143.
-
Several Verifiable Credential Documents 2024-11-01 > 2024-12-01 w3cping/privacy-request#146.
-
Input Events 2024-11-21 > 2024-12-19 w3cping/privacy-request#147.
-
-
4 issues received 5 new comments.
-
Final Review Request of seven (7) W3C VCWG Specifications w3cping/privacy-request#153 (1 comment by @kdenhartog)
-
Several Verifiable Credential Documents 2024-11-01 > 2024-12-01 w3cping/privacy-request#146 (1 comment by @npdoty)
w3c/privacywg
-
1 issue opened.
-
[agenda] 2024-12-19 w3c/privacywg#4, by @npdoty.
-
-
1 issue closed.
-
[agenda] 2024-12-05 w3c/privacywg#3.
-
-
1 issue received 5 new comments.
w3c/security-questionnaire
-
1 issue closed.
-
use automatic publishing w3c/security-questionnaire#101.
-
-
2 pull requests merged.
-
Add auto-publish script w3c/security-questionnaire#171.
-
Create w3c.json w3c/security-questionnaire#179.
-
-
1 pull request received 3 new comments.
TR publications
-
2 documents published.
-
Global Privacy Control (GPC) published as a Working Draft. History of Global Privacy Control (GPC)
-
Global Privacy Control (GPC) published as a First Public Working Draft. History of Global Privacy Control (GPC)
-
Past meetings
Participants
-
12 participants joined.
-
Rob van Eijk (W3C Invited Experts) joined.
-
Benjamin VanderSloot (Mozilla Foundation) joined.
-
Aram Zucker-Scharff (The Washington Post) joined.
-
Justin Brookman (W3C Invited Experts) joined.
-
Bartosz Niemczura (Meta) joined.
-
David Schinazi (Google LLC) joined.
-
Tom Van Goethem (Google LLC) joined.
-
Severin Ferrand (Google LLC) joined.
-
Sid Sahoo (Google LLC) joined.
-
Mike West (Google LLC) joined.
-
Steven Valdez (Google LLC) joined.
-
Ari Chivukula (Google LLC) joined.
-
-
3 organizations joined.
-
Mozilla Foundation joined.
-
The Washington Post joined.
-
Meta joined.
-
GitHub
w3cping/tracking-issues
-
1 issue opened.
-
Add privacy considerations for the clipboardchange event w3cping/tracking-issues#487, by @w3cbot.
-
-
2 issues closed.
-
Links from sec/priv sections back to normative mitigations? w3cping/tracking-issues#171.
-
Privacy considerations w3cping/tracking-issues#472.
-
w3cping/privacy-request
-
2 issues opened.
-
Input Events 2024-11-21 > 2024-12-19 w3cping/privacy-request#147, by @siusin.
-
Several Verifiable Credential Documents 2024-11-01 > 2024-12-01 w3cping/privacy-request#146, by @iherman.
-
-
3 issues closed.
-
Accessibility Conformance Testing (ACT) Rules Format 1.1 2024-07-24 w3cping/privacy-request#141.
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3cping/privacy-request#144.
-
Vision for W3C 2024-10-23 > 2024-11-20 w3cping/privacy-request#145.
-
-
1 issue reopened.
-
Accessibility Conformance Testing (ACT) Rules Format 1.1 2024-07-24 w3cping/privacy-request#141, by @plehegar.
-
-
3 issues received 7 new comments.
-
Vision for W3C 2024-10-23 > 2024-11-20 w3cping/privacy-request#145 (3 comments by @plehegar, @rinchen, @sandandsnow)
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3cping/privacy-request#144 (1 comment by @npdoty)
w3c/privacywg
-
2 issues opened.
-
[agenda] 2024-12-05 w3c/privacywg#3, by @npdoty.
-
[agenda] 2024-11-21 w3c/privacywg#2, by @npdoty.
-
-
2 issues closed.
-
[agenda] 2024-11-21 w3c/privacywg#2.
-
[agenda] 2024-11-07 w3c/privacywg#1.
-
-
2 issues received 6 new comments.
w3c/security-questionnaire
-
1 issue opened.
-
There are three active versions of this questionnaire w3c/security-questionnaire#175, by @domenic.
-
-
2 issues received 3 new comments.
-
Questionnaire markdown file is not actually convenient w3c/security-questionnaire#172 (2 comments by @domenic, @johannhof)
-
There are three active versions of this questionnaire w3c/security-questionnaire#175 (1 comment by @jyasskin)
-
-
4 pull requests opened.
-
Create w3c.json w3c/security-questionnaire#179, by @plehegar.
-
Link to Lukasz' specific analysis on visited links. w3c/security-questionnaire#178, by @jyasskin.
-
Make questionnaire.markdown convenient for copying into an explainer. w3c/security-questionnaire#177, by @jyasskin.
-
Add `class=question` to a header so it's included in questionnaire.markdown. w3c/security-questionnaire#176, by @jyasskin.
-
-
1 pull request closed.
-
Switch the CI to spec-prod, and enable it for PR validation. w3c/security-questionnaire#169.
-
-
4 pull requests received 8 new comments.
-
Add auto-publish script w3c/security-questionnaire#171 (5 comments by @jyasskin, @pes10k, @plehegar)
-
Link to Lukasz' specific analysis on visited links. w3c/security-questionnaire#178 (1 comment by @lflores-ms)
-
Switch the CI to spec-prod, and enable it for PR validation. w3c/security-questionnaire#169 (1 comment by @jyasskin)
-
w3c/gpc
-
2 issues opened.
-
Add privacy and security considerations sections w3c/gpc#84, by @plehegar.
-
-
1 issue reopened.
-
Use HTTP structured field values w3c/gpc#6, by @annevk.
-
-
5 issues received 7 new comments.
-
Clarify "targeted advertising" versus "cross-site targeted advertising"? w3c/gpc#83 (2 comments by @AramZS, @npdoty)
-
Clarify that GPC signal does not legitimize cross-site tracking as default web condition w3c/gpc#82 (1 comment by @AramZS)
-
w3c/gpc#35 (1 comment by @rinchen)
-
-
2 pull requests opened.
-
Fix inline `navigator` to use `<code>` w3c/gpc#86, by @tomayac.
-
Use HTTP/1.1 in header example w3c/gpc#85, by @flano-yuki.
-
-
1 pull request received 2 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 8 October 2026. Participants had to rejoin under this charter.
-
Participants
-
3 chairs appointed.
-
Nick Doty became a chair.
-
Christine Runnegar became a chair.
-
Peter Snyder became a chair.
-
-
1 Team contact appointed.
-
Tara Whalen became a Team contact.
-
-
23 participants joined.
-
Sebastian Zimmeck (W3C Invited Experts) joined.
-
Joey Stanford (W3C Invited Experts) joined.
-
Theodore Olsauskas-Warren (Google LLC) joined.
-
Michael Kleber (Google LLC) joined.
-
Jeffrey Yasskin (Google LLC) joined.
-
Michael Markevich (W3C Invited Experts) joined.
-
Samuel Weiler (W3C Invited Experts) joined.
-
Nick Doty (Center for Democracy and Technology) joined.
-
Lionel Basdevant (Criteo) joined.
-
Andrew Pascoe (NextRoll) joined.
-
Benjamin Goering (Protocol Labs) joined.
-
Christine Runnegar (W3C Invited Experts) joined.
-
John Wilander (Apple Inc.) joined.
-
Anne van Kesteren (Apple Inc.) joined.
-
Matthew Finkel (Apple Inc.) joined.
-
Theresa O'Connor (Apple Inc.) joined.
-
Kyle Den Hartog (Brave Software Inc.) joined.
-
Peter Snyder (Brave Software Inc.) joined.
-
Don Marti (W3C Invited Experts) joined.
-
Chris Needham (British Broadcasting Corporation) joined.
-
Junichi Yoshii (Kodansha, Publishers, Ltd.) joined.
-
Tara Whalen (W3C) joined.
-
Philippe Le Hegaret (W3C) joined.
-
-
10 organizations joined.
-
Google LLC joined.
-
Center for Democracy and Technology joined.
-
Criteo joined.
-
NextRoll joined.
-
Protocol Labs joined.
-
Apple Inc. joined.
-
Brave Software Inc. joined.
-
Raptive joined.
-
British Broadcasting Corporation joined.
-
Kodansha, Publishers, Ltd. joined.
-
GitHub
w3c/gpc
-
1 issue opened.
-
2 issues received 2 new comments.
-
w3c/gpc#6 (1 comment by @SebastianZimmeck)
-
w3c/gpc#80 (1 comment by @j-br0)
-
-
1 pull request received 1 new comment.
-
w3c/gpc#81 (1 comment by @chrisn)
-
w3cping/tracking-issues
-
1 issue opened.
-
[css-fonts] Reference font subsets without privacy leaks w3cping/tracking-issues#486, by @w3cbot.
-
-
8 issues closed.
-
Add in-line privacy and security considerations to VISS transport w3cping/tracking-issues#347.
-
VISS core: what is a pseudo-VIN w3cping/tracking-issues#354.
-
VISS Core: why is access control non-normative? w3cping/tracking-issues#353.
-
Automotive Working Group recharter w3cping/tracking-issues#156.
-
Web & Networks Interest Group rechartering w3cping/tracking-issues#157.
-
HTML WG 2021 w3cping/tracking-issues#243.
-
Q: will implementations provide additional builtin functions/structures? w3cping/tracking-issues#312.
-
Clarify that `null` is never exposed to the page w3cping/tracking-issues#470.
-
-
3 issues received 3 new comments.
-
w3cping/tracking-issues#312 (1 comment by @plehegar)
-
w3cping/tracking-issues#470 (1 comment by @pes10k)
-
w3cping/tracking-issues#471 (1 comment by @himorin)
-
w3c/fingerprinting-guidance
-
1 issue opened.
-
relevant research: Identified-and-Targeted / FPTrace w3c/fingerprinting-guidance#65, by @npdoty.
-
w3cping/privacy-request
-
2 issues opened.
-
Vision for W3C 2024-10-23 > 2024-11-20 w3cping/privacy-request#145, by @tantek.
-
EPUB 3.3 Recommendation with Candidate Corrections 2024-10-17 > 2024-12-19 w3cping/privacy-request#144, by @iherman.
-
-
1 issue received 2 new comments.
-
1 pull request closed.
-
Create recognition-methods.md w3cping/privacy-request#124.
-
w3c/privacywg
-
1 issue opened.
-
[agenda] 2024-11-07 w3c/privacywg#1, by @npdoty.
-
-
1 issue received 5 new comments.
w3c/security-questionnaire
-
1 issue opened.
-
Example 10 is not supported by referenced article w3c/security-questionnaire#174, by @lflores-ms.
-