W3C home > Mailing lists > Public > public-tracking@w3.org > August 2014

RE: Using "tracking" in compliance document (ISSUE-203)

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Sat, 2 Aug 2014 12:46:39 +0100
To: "'Roy T. Fielding'" <fielding@gbiv.com>, <public-tracking@w3.org>
Message-ID: <31ac01cfae47$6c9f3d40$45ddb7c0$@baycloud.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi Roy,

Thanks for your intelligent work on this. Could you give a bit more explanation on what you mean by TSR freshness in Scope 1 and Compliance 3.3 (do you mean cache and what happens if the server says always revalidate).

Mike


From: Roy T. Fielding [mailto:fielding@gbiv.com]
Sent: 02 August 2014 05:10
To: public-tracking@w3.org (public-tracking@w3.org)
Subject: Re: Using "tracking" in compliance document (ISSUE-203)

Hi all,

As mentioned on the last teleconference, I have been working on a draft
proposal to address tracking-ISSUE-203 by rewriting TCS based on the
WG decisions made for the TPE last call working draft.  I have finished
a complete draft and uploaded it to

http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance-i203.html

Please note that this is just a draft proposal.  I used the ED format in
order to make it easier to read and much easier for the TCS editors to
copy and paste whatever is acceptable to the group.

I have left the issue markers where they are most appropriate, but have
not checked for any open issues not already reflected in the TCS ED.
I did not meddle with the definition of de-identify in this pass.

Since this will be discussed on the next call, I will not be making
any more changes to the draft until after the call (unless the chairs
ask for something to be changed).  However, please try to review it
early in the week and feel free to send comments to the list, since
that will make the call go faster.

Cheers,

Roy T. Fielding                     <http://roy.gbiv.com/>
Senior Principal Scientist, Adobe   <http://www.adobe.com/>

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

iQEcBAEBAgAGBQJT3M+eAAoJEHMxUy4uXm2JxcwIAImkCxbnys3TT+buNu3hy3Ht
hFVYlkKJ6U8FMJPGhb8DOQjKYjAQH9lbykffMrO8vBe4dR2Vzt/j4c7w40v5YWsG
sj/6dqg+15k8RPzrrA3uhURRByLc3PRyxiVqUL10bUHspGpsYLsR6CLRfAlBgOyB
Jn6wwB5QvkWTnVm5F2gW1ezLqErfoBhNzPGYNcFb0wreESkKU0IknQZVyD+hArX8
yhNc6bZhxZb6RAdH3ruqVUIumg11Qto5ZRqIcS3zt5+c3SStiUoxW+fQrlkMK45i
zP7sEHPNs4fQDIUUE6VogaYc9tw20vRFzmFYUpUDduQuTFruajvdcRxeo7VKqI8=
=n3gu
-----END PGP SIGNATURE-----

Received on Saturday, 2 August 2014 11:47:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:12 UTC