Define privacy, Ben's suggestion

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

@@ -55,7 +55,7 @@
           <li><a href="#background">Background</a></li>
           <li><a href="#scope">Scope</a></li>
           <li><a href="#deliverables">Deliverables</a></li>
-		  <li><a href="#success-criteria">Success Criteria</a></li>
+                  <li><a href="#success-criteria">Success Criteria</a></li>
           <li><a href="#coordination">Coordination</a></li>
           <li><a href="#participation">Participation</a></li>
           <li><a href="#communication">Communication</a></li>
@@ -85,7 +85,7 @@ <h1 id="title">PROPOSED Private Advertising Technology Working Group Charter</h1
          publishers, ad buyers, advertising platforms and intermediaries,
          privacy advocates, web application developers, and other interested
          parties.
-      </p>                                                                
+      </p>
 
       <div class="noprint">
         <p class="join"><a href="https://www.w3.org/groups/wg/[shortname]/join">Join the Private Web Advertising Working Group.</a></p>
@@ -106,7 +106,7 @@ <h1 id="title">PROPOSED Private Advertising Technology Working Group Charter</h1
             <td>
               <i class="todo">See the <a href="https://www.w3.org/groups/wg/[shortname]/charters">group status page</A> and <a href="#history">detailed change history</a>.</i>
             </td>
-          </tr>		
+          </tr>
           <tr id="Duration">
             <th>
               Start date
@@ -163,8 +163,16 @@ <h2>Scope</h2>
         <p>
             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 <a href="https://w3ctag.github.io/privacy-principles/#hl-recognition-cross-site">cross-site
+            or cross context recognition</a> of users or
+            enabling <a href="https://w3ctag.github.io/privacy-principles/#hl-recognition-same-site">same-site
+            or same-context recognition</a> of users across the clearing of
+            state.
         </p>
         <p>
           The Working Group may consider designs that allow user agents for the
@@ -186,7 +194,7 @@ <h2>
 
         <p><i class="todo">Updated document status is available on the <a href="https://www.w3.org/groups/wg/[shortname]/publications">group publication status page</a>. [or link to a page this group prefers to use]</i></p>
 
-        <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. 
+        <p><i>Draft state</i> 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.</p>
 
         <section id="normative">
@@ -251,12 +259,12 @@ <h3>Timeline</h3>
         </section>
       </section>
 
-	<section id="success-criteria">
-	  <h2>Success Criteria</h2>
-	  <p>The WG will progress its normative specifications through the following
-    standardization process: 
+        <section id="success-criteria">
+          <h2>Success Criteria</h2>
+          <p>The WG will progress its normative specifications through the following
+    standardization process:
     <a href="https://www.w3.org/2021/Process-20211102/#RecsWD">First Public
-      Working Draft</a>, 
+      Working Draft</a>,
     <a href="https://www.w3.org/2021/Process-20211102/#RecsWD">Working
       Draft</a>,
     <a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-draft">Candidate
@@ -266,12 +274,12 @@ <h2>Success Criteria</h2>
     It is expected that to reach the Candidate Recommendation Snapshot stage, each normative
     specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
 
-	  <p>Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
+          <p>Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
 
-	  <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
+          <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
 
     <p>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.</p>
-	</section>
+        </section>
 
       <section id="coordination">
         <h2>Coordination</h2>
@@ -288,8 +296,8 @@ <h2>Coordination</h2>
           such that the group is encouraged to coordinate with the appropriate groups at the WHATWG, Ecma, and IETF as needed.
         </p>
 
-		<p>
-			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 <a href="https://www.w3.org/2021/Process-20211102/#rec-track" title="The W3C Recommendation Track">state change</a>, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback.
+                <p>
+                        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 <a href="https://www.w3.org/2021/Process-20211102/#rec-track" title="The W3C Recommendation Track">state change</a>, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback.
 
         <p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
 
@@ -364,7 +372,7 @@ <h2>
         </p>
         <p>
           Most Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
-          
+
         </p>
         <p>
           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.