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.