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

FW: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call]

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Wed, 22 Oct 2014 10:08:54 +0100
To: "'David Singer'" <singer@apple.com>
Cc: "Shane M Wiley" <wileys@yahoo-inc.com>, <public-tracking@w3.org>
Message-ID: <025201cfedd7$cf2c9230$6d85b690$@baycloud.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David, here it is again. It is HTML using ReSpec JS in a file, and can just replace 7.4.1 in the TPE


Mike


From: Mike O'Neill [mailto:michael.oneill@baycloud.com]
Sent: 28 September 2014 12:54
To: 'Nicholas Doty'; 'Tracking Protection Working Group'
Subject: RE: tracking-ISSUE-266: automatic expiration of a tracking preference exception via API parameter [TPE Last Call]

gpg4o
 Valid Signature from 7331532E2E5E6D89 Mike O'Neill <michael.oneill@btinternet.com>
 
 As promised, here is the WebIDL for automatic expiry in a ReSpec file, to replace the section “7.4.1 API to Request a Site-specific Exception”.
The web-wide API uses the same property bag so does not need changing.
I mirrored  both the Max-Age and Expires attributes with Max-Age taking precedence as it does in RFC6265.
It is pretty self-evident but if people think it is necessary I can also write a descriptive paragraph to go into the Exception model section.
Mike
> -----Original Message-----
> From: Nicholas Doty [mailto:npdoty@w3.org]
> Sent: 25 September 2014 01:24
> To: Tracking Protection Working Group
> Subject: Re: tracking-ISSUE-266: automatic expiration of a tracking preference
> exception via API parameter [TPE Last Call]
>
> *** gpg4o | Unknown Signature from 40203EE90BBAB306 1 2 01 1411604644 9
> ***
>
> This is the more specific issue we decided to open in discussing issue-258
> regarding automatic expiration in general. Mike O'Neill has voluntereed to write
> up a text proposal for it this weekend.
>
> Thanks,
> Nick
>
> On September 24, 2014, at 5:16 PM, Tracking Protection Working Group Issue
> Tracker <sysbot+tracker@w3.org> wrote:
>
> > tracking-ISSUE-266: automatic expiration of a tracking preference exception
> via API parameter [TPE Last Call]
> >
> > http://www.w3.org/2011/tracking-protection/track/issues/266
> >
> > Raised by: Rob van Eijk
> > On product: TPE Last Call
> >
> > In discussing the automatic expiration Last Call comment, we decided to open
> a separate issue for any proposals for an API parameter for storing user-granted
> exceptions to tracking preferences.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)
Comment: Using gpg4o v3.3.26.5094 - http://www.gpg4o.com/
Charset: utf-8

iQEcBAEBAgAGBQJUR3QkAAoJEHMxUy4uXm2JMHYIALGOnCrRLqu7Tfz52+WhYBBW
FfiHQEhdxzknsks5VrYMRfkfJJRsDphK6Y0Mmy/F0waDgpjckQdXxkoKI4D15YPd
8FqNzuMP1oKolHJ9PsragedQjj2lRLik77U6ABDxY6hO7hg00RVZTH7NWFSWjiav
hufeY9k/rK1Q34rEXQQztp4yptnnmDm9fle9uAwG0Urf9ZDEfbQcnxcU/+0nt6sd
kAnoF+L5sfjRQja7XLYnclMGUL60UOthFFlKB0zHZ0YoBDFoSNH1fPtxS/ucgf8O
Ta0Ntas40XqA45dUJ3EIOJ5I4kNkx/hEH89YPgUq8mA9pnib/al4lt3L80q/gyo=
=PpnG
-----END PGP SIGNATURE-----



Received on Wednesday, 22 October 2014 09:09:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:24 UTC