- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Tue, 13 Jun 2017 13:21:55 +0100
- To: Matthias Schunter <mts-std@schunter.org>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
> On Jun 13, 2017, at 7:30 AM, Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote: > > Hi Folks, > > some people had trouble accessing the tool. > I granted a 1-day extension. > > If you still cannot access the tool, please email your input to the list > and we can add it later. The poll is currently read-only, so I will just reiterate here what I have said in past meetings (and ditto to what Apple placed in the tool). Adobe objects to Option A because the proposed text is a placeholder for something to be defined later that is currently disconnected from TPE. It serves no purpose in the existing protocol; presumably, based on what has been implied by the discussion, the intended purpose is to provide information specific to an imagined user interface for a mechanism of configuration of some form of selective blocking. However, the terms being used here are inadequately and inconsistently defined for that purpose, at least partly because the WG decided not to use region-specific legal terms (such as those in the GDPR) for TPE to avoid making the protocol region-specific. We don't need to predefine such a property. The TSR representation is already defined to be extensible, specifically through the addition of new properties that might or might not be required by some set of compliance regimes. It is entirely possible for this under-specified feature to be completely specified in a compliance specification without any change to TPE, authored by anyone, and capable of using defined legal terms consistent with a given region. As such, Option B is preferred. Cheers, Roy T. Fielding <http://roy.gbiv.com/> Senior Principal Scientist, Adobe <https://www.adobe.com/>
Received on Tuesday, 13 June 2017 12:22:26 UTC