- From: Rob van Eijk <rob@blaeu.com>
- Date: Wed, 20 Jun 2012 21:45:34 -0700
- To: Tamir Israel <tisrael@cippic.ca>
- CC: "Roy T. Fielding" <fielding@gbiv.com>, Rigo Wenning <rigo@w3.org>, Matthias Schunter <mts-std@schunter.org>, "publ >> \"public-tracking@w3.org\"" <public-tracking@w3.org>
Because an overly prescriptive objective will not leave room for other ways to accomplish the same. In order to have a meaningful global DNT standard, it is important to have technical building blocks built in. On 20-6-2012 20:34, Tamir Israel wrote: > If the WG's objective is to ensure user preferences are expressed, why > don't we simply make this a MUST? > > On 6/20/2012 10:15 PM, Rob van Eijk wrote: >> Tnx Roy, >> >> <PROPOSED CHANGE> >> Normative: "... users MAY be given a choice during installation, >> update or first startup." >> >> Non-normative: >> There are use cases, where a choice given on first startup would be >> the preferred choice mechanism. >> For example, >> - a device can have multiple user profiles per installation; >> - in cases where browsers are not installed by the user. >> </PROPOSED CHANGE> >> >> Rob >> >> On 20-6-2012 18:22, Roy T. Fielding wrote: >>> On Jun 20, 2012, at 5:31 PM, Rob van Eijk wrote: >>> >>>> <PROPOSED CHANGE> >>>> "... users may be given a choice during installation, update or >>>> first startup." >>>> </PROPOSED CHANGE> >>> Not during installation or update -- only during first use. >>> The preference should be stored in the user's browser config (along >>> with their other personal preferences); a device might want >>> to have multiple such user profiles per installation. >>> >>> In normal enterprise environments and the vast majority of purchased >>> computers, browsers are not installed by the user. They are installed >>> by sysadmins, vendors, etc. Likewise, updates should not modify >>> user preferences. >>> >>> ....Roy >>> >>> >> >
Received on Thursday, 21 June 2012 04:47:32 UTC