From 23d8d77e57cafb5a13abd319f22174f150d63322 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 18 May 2022 11:01:05 +1000 Subject: [PATCH 1/5] Define privacy, Ben's suggestion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Tweaked some, but essentially as Ben has proposed. Note the addition of "minimally" here to ensure that we don't foreclose on discussion of *other* privacy imperatives. I've also used prose rather than a list, but ¯\\\_(ツ)\_/¯. Closes #20. Closes #6. --- charter.html | 42 +++++++++++++++++++++++++----------------- 1 file changed, 25 insertions(+), 17 deletions(-) diff --git a/charter.html b/charter.html index 9caf246..367d8ed 100644 --- a/charter.html +++ b/charter.html @@ -55,7 +55,7 @@
  • Background
  • Scope
  • Deliverables
    • -
  • Success Criteria
    • +
  • Success Criteria
  • Coordination
  • Participation
  • Communication
    • @@ -85,7 +85,7 @@

    PROPOSED Private Advertising Technology Working Group Charter

    +

    Join the Private Web Advertising Working Group.

    @@ -106,7 +106,7 @@

    PROPOSED Private Advertising Technology Working Group Charter

    See the group status page and detailed change history. - + Start date @@ -163,8 +163,16 @@

    Scope

    The Working Group will specify new web platform features intended to be implemented in browsers or similar user agents. The purpose of - these features is to support web advertising and provide users with - privacy guarantees with a strong technical basis. + these features is to support web advertising without compromising + user privacy. Here "privacy" minimally refers to appropriate + process of personal information. Ways in which new features might + enable inappropriate process 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 Working Group may consider designs that allow user agents for the @@ -186,7 +194,7 @@

    Updated document status is available on the group publication status page. [or link to a page this group prefers to use]

    -

    Draft state indicates the state of the deliverable at the time of the charter approval. +

    Draft state indicates the state of the deliverable at the time of the charter approval. The Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots) and does not intend to advance their documents further.

    @@ -251,12 +259,12 @@

    Timeline

    -
    -

    Success Criteria

    -

    The WG will progress its normative specifications through the following - standardization process: +

    +

    Success Criteria

    +

    The WG will progress its normative specifications through the following + standardization process: First Public - Working Draft, + Working Draft, Working Draft, Candidate @@ -266,12 +274,12 @@

    Success Criteria

    It is expected that to reach the Candidate Recommendation Snapshot stage, each normative specification is expected to have at least two independent implementations of every feature defined in the specification.

    -

    Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.

    +

    Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.

    -

    There should be testing plans for each specification, starting from the earliest drafts.

    +

    There should be testing plans for each specification, starting from the earliest drafts.

    Normative specifications which have user-facing features should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.

    -
    +

    Coordination

    @@ -288,8 +296,8 @@

    Coordination

    such that the group is encouraged to coordinate with the appropriate groups at the WHATWG, Ecma, and IETF as needed.

    -

    - The WG will coordinate with the Private Advertising Technology Community Group to solicit feedback from a wider community of interest. At any time, but always when a specification is undergoing a state change, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback. +

    + The WG will coordinate with the Private Advertising Technology Community Group to solicit feedback from a wider community of interest. At any time, but always when a specification is undergoing a state change, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback.

    Additional technical coordination with the following Groups will be made, per the W3C Process Document:

    @@ -364,7 +372,7 @@

    Most Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis. - +

    At the discretion of the Chairs and subject to a consensus call, the Working Group may designate a Design Team to study a particular subject, and report back to the Working Group their findings and a recommendation. These Design Teams shall consist of a small group of volunteers who commit to investing significant amounts of time on the task over a short, time-bound, period. From ff729426b7daf93bd92c3a8cce4722da64c3bac3 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 19 May 2022 09:28:38 +1000 Subject: [PATCH 2/5] whitespace inconsistency --- charter.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.html b/charter.html index 367d8ed..6b86727 100644 --- a/charter.html +++ b/charter.html @@ -55,7 +55,7 @@

  • Background
  • Scope
  • Deliverables
    • -
  • Success Criteria
    • +
  • Success Criteria
  • Coordination
  • Participation
  • Communication
    • From fa0a38922bb6a185f05a681c982bf6c7230bc8dd Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 19 May 2022 10:08:51 +1000 Subject: [PATCH 3/5] processing Co-authored-by: benjaminsavage <52456851+benjaminsavage@users.noreply.github.com> --- charter.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.html b/charter.html index 6b86727..14c66f3 100644 --- a/charter.html +++ b/charter.html @@ -165,7 +165,7 @@

    Scope

    be implemented in browsers or similar user agents. The purpose of these features is to support web advertising without compromising user privacy. Here "privacy" minimally refers to appropriate - process of personal information. Ways in which new features might + processing of personal information. Ways in which new features might enable inappropriate process include (but are not limited to) enabling of cross-site From f0fa27609b43b12c3283cda24c7cd08857fb53db Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 19 May 2022 09:31:07 +1000 Subject: [PATCH 4/5] More whitespace --- charter.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charter.html b/charter.html index 14c66f3..f173f30 100644 --- a/charter.html +++ b/charter.html @@ -296,8 +296,8 @@

    Coordination

    such that the group is encouraged to coordinate with the appropriate groups at the WHATWG, Ecma, and IETF as needed.

    -

    - The WG will coordinate with the Private Advertising Technology Community Group to solicit feedback from a wider community of interest. At any time, but always when a specification is undergoing a state change, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback. +

    + The WG will coordinate with the Private Advertising Technology Community Group to solicit feedback from a wider community of interest. At any time, but always when a specification is undergoing a state change, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback.

    Additional technical coordination with the following Groups will be made, per the W3C Process Document:

    From 22541e898d4394ea512e5720caccd04f6c547fc2 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 19 May 2022 15:52:09 +1000 Subject: [PATCH 5/5] ---ing --- charter.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charter.html b/charter.html index f173f30..446ce92 100644 --- a/charter.html +++ b/charter.html @@ -166,7 +166,7 @@

    Scope

    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 process include (but are not limited to) + enable inappropriate processing include (but are not limited to) enabling of cross-site or cross context recognition of users or