RE: Compliance edits per CfOs on 219 and 235

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Nick,

Are we having a call today?

Mike

From: Nick Doty [mailto:npdoty@w3.org]
Sent: 18 February 2015 08:12
To: public-tracking@w3.org (public-tracking@w3.org)
Subject: Compliance edits per CfOs on 219 and 235

gpg4o
 Unknown Signature from 40203EE90BBAB306 1 10 01 1424247137 9
 
 (No call tomorrow, btw, sorry that I didn't check that with our chairs sooner. Next call to be announced.)

I've made the edits to implement the CfO results on issues 219 and 235: prohibiting use of data collected in a different context and removing auditability requirement respectively. On 219, I've tried to implement the Option B (with lesser objection) but using the current language ("party to a given user action", etc.). I would welcome group review to make sure I've made these changes correctly.

https://lists.w3.org/Archives/Public/public-tracking-commit/2015Feb/0003.html
https://lists.w3.org/Archives/Public/public-tracking-commit/2015Feb/0002.html

If you want to review more Compliance changes I've made, the list of Pending Review issues on this Tracker would be relevant:
https://www.w3.org/2011/tracking-protection/track/products/5
while I'm not sure that's actually exhaustively up to date on what we have completed, I do think all the Pending Review issues there can be closed if we're satisfied that I've implemented our text or addressed concerns adequately.

Thanks,
Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)
Comment: Using gpg4o v3.4.19.5391 - http://www.gpg4o.com/
Charset: utf-8

iQEcBAEBAgAGBQJU7e1HAAoJEHMxUy4uXm2JDzgH/1TdTCOM8RIHaQkjDz1Y3ekO
Ts7YoSF1RvxMHJft6CD3bulT0SOk8vrdVMw4m3KAmTO8So2n58PqO6+JbnAlXAJA
HB/Ht4IaCn5vsx+QXrwhUvbl3fOiixlga/kqTu+ORzsHGgb6sjn7+UnCW9Dn52+U
DsAcGevRbKjtnNaxDHamtzySBymPybwwpdeVfAZqv/Vwf9XpF2bABCNubjadZDrz
Vz/WwMu6LwN6QKIeqfOgccvMOaPWlbGb1Uf+XPe9TVz0RakNmbbAlw/2zgkngOy6
JkalkEdkBkBcUgaRgYS0SmH6gtzLUgiVUN+nYbnUErlYP+0KjdDwR4yvH3FEMLY=
=luLN
-----END PGP SIGNATURE-----