- From: David Singer <singer@apple.com>
- Date: Wed, 08 Jan 2014 17:31:31 -0800
- To: Nicholas Doty <npdoty@w3.org>
- Cc: "Roy T. Fielding" <fielding@gbiv.com>, "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
On Jan 8, 2014, at 8:43 , Nicholas Doty <npdoty@w3.org> wrote: > I wasn't suggesting that any of these UI suggestions were good or likely, but in defining the terms that will be communicated over the protocol, we generally add them only if we think they may be used by the client. If we don't think any users will review the compliance array and we don't expect or don't want user agents to block/allow resources based on those values, then providing the extra configurability is not valuable. I think that there is great value in providing transparency (in both directions) for researchers and others, even if during much of the time fields are not inspected in real-time. I.e. I think it a non-sequitur that information should not be available at all if it’s not used all the time in real-time. David Singer Multimedia and Software Standards, Apple Inc.
Received on Thursday, 9 January 2014 01:31:59 UTC