public-patcg@w3.org from March 2023 by subject

[docs-and-reports] Add a time/interaction budget scope to the general agreement doc (#39)

[docs-and-reports] Add new document to address working parameters (#35)

[docs-and-reports] Add note about rate of information release (#40)

[docs-and-reports] Closed Pull Request: Add note about rate of information release

[docs-and-reports] Merged Pull Request: Add a time/interaction budget scope to the general agreement doc

[docs-and-reports] Merged Pull Request: Add new document to address working parameters

[docs-and-reports] Pull Request: Add a time/interaction budget scope to the general agreement doc

[docs-and-reports] Pull Request: Add note about rate of information release

[docs-and-reports] Pull Request: Several tentative updates regarding private computation for ML, the usage of aggregator/collector terms and minor typos

[docs-and-reports] Pull Request: start a sources doc to collect some references for patcg principles doc

[docs-and-reports] Scope for PATCG Privacy Principles (#36)

[meetings] 2023 Meeting Schedule (#89)

[meetings] Add minutes from NYC (#105)

[meetings] Agenda Items - Open to Requests (#104)

[meetings] Agenda Request - Call for Scribes - 2023/03 (#109)

[meetings] Agenda Request - Individual Draft groups and meetings (#107)

[meetings] Agenda Request - Privacy Principles report (#110)

[meetings] Agenda Request - Work through open PRs on Working Group Charter (#108)

[meetings] Merged Pull Request: Add minutes from NYC

[meetings] Merged Pull Request: Agenda staging branch

[meetings] Privacy Principles for Web Advertising Features - Editorial Group (#18)

[meetings] Pull Request: Add minutes from NYC

[meetings] Pull Request: Agenda staging branch

[meetings] Review baseline requirements for Private Measurement from participants (#91)

[patwg-charter] +"Any proposed feature should increase the protection of data about a… (#58)

[patwg-charter] Add precision to scope (#50)

[patwg-charter] Addressing #35 - making explicit that proposals should detail the data they intend to use and return. (#36)

[patwg-charter] Closed Pull Request: +"Any proposed feature should increase the protection of data about a…

[patwg-charter] Closed Pull Request: Add precision to scope

[patwg-charter] Closed Pull Request: Clarify scope of group w/using open processes

[patwg-charter] Closed Pull Request: Simplified scope statement

[patwg-charter] Closed Pull Request: Trade-offs should be clear in the specifications

[patwg-charter] Deweaponize 'all known' (#60)

[patwg-charter] Following discussion with a number of colleagues this PR covers issue… (#18)

[patwg-charter] Merged Pull Request: An alternative approach for scoping

[patwg-charter] Merged Pull Request: Update Privacy Principles

[patwg-charter] Proposals should clearly state business factors and user risks (#59)

[patwg-charter] Pull Request: +"Any proposed feature should increase the protection of data about a…

[patwg-charter] Pull Request: Deweaponize 'all known'

[patwg-charter] Pull Request: Proposals should clearly state business factors and user risks

[patwg-charter] Pull Request: Update Privacy Principles

[patwg-charter] Require Data Section in Success Criteria (#35)

[patwg-charter] Simplified scope statement (#49)

[patwg-charter] Trade-offs should be clear in the specifications (#46)

[private-measurement] Evaluating off-device attribution proposals at larger scales (#21)

Closed: [meetings] Agenda Items - Open to Requests (#104)

Event Updated: Private Advertising Technology CG Meeting

Last message date: Thursday, 30 March 2023 13:20:16 UTC