- From: David Singer <singer@mac.com>
- Date: Thu, 20 Apr 2017 13:46:43 -0700
- To: "Matthias Schunter (Intel Corporation)" <mts-std@schunter.org>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Hi Matthias, friends Monday the 24th I will be in China for the AC meeting…regrets > On Apr 20, 2017, at 0:23 , Matthias Schunter (Intel Corporation) <mts-std@schunter.org> wrote: > > Hi Folks, > > this is our final call for resolving issues for the next CR. > After this call, we focus on introducing any edits corresponding to the > resolved issues and then publish our CR end of May. > > 30min: 1. to tackle the question "what extra field and qualifiers do we > need", > we now focus on the final open new usecase which is online ad auctions. > Rob will present his proposal. > > 20min: 2. We then look at the remaining high-priority issue: > https://github.com/w3c/dnt/issues/13 > > 10min: 3. Then at the other lower priority issues > > Our list of issues is at: > https://github.com/w3c/dnt/issues/ > Note that issues that are not resolved by end of April will be > auto-pushed out to potential future releases. > > > Regards, > matthias > > ----- > DISCUSSIONS FOR MONDAY > > 1. Issue triage: Are there issues that are high priority and must be > resolved in April? If not, we can process without change. > > 2. What additional fields are desired for simplifying compliance in the EU? > > Note: So far I have not seen any submitted proposals for an additional > concrete field on the list. If I receive none, IMHO we can close this > discussion on monday. > > 2. Best way to communicate "consent context". > Our current approach was that the TSR serves two roles: > A. Discovery (before visiting site) of essential tracking > information > B. Sufficient context to give clear meaning to > user-granted exception. This role triggered that we > plan to require TSR if the exception API is used. > It also fuels our discussion "what extra fields are > needed" > Roy suggested that TSR may be the best place for (B). Let us see whether > we find a better place for the consent-context information. > One suggestion was that it should be part of the API call. > > 3. Asyncronous API / Update Events (Continued) > https://github.com/w3c/dnt/issues/13 > > 4. Anything else we want to discuss > > Dave Singer singer@mac.com
Received on Thursday, 20 April 2017 20:47:33 UTC