- From: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
- Date: Fri, 3 Mar 2017 13:54:54 +0100
- To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
- Message-ID: <c8e4c053-e8ba-68e9-e77b-2e13d195e593@schunter.org>
Hi Folks, enclosed are topics for our call next Monday. Note that I now use labels to manage issues in the tool. Matthias ------------------------------------------- AGENDA I propose to discuss the following topics next week: ----------- 1. Timeline & weekly calls Our charter mandates that we publish a new CR soon. I propose this timeline: - March 06 (our next call): Closing the list of issues. After this date, no new issues can be raised. - April 01: Discussion closes. This means that all issues that have been resolved by then will be implemented. - Unresolved issues will be pushed to Version 2. - April 15: Spec freeze: By April 15, the spec should be frozen and only debugging / proof-reading continues. I agree that this timeline is short. However, we can always publish future updates to the TPE. If someone has an alternative timeline how we can reach the deadlines specified in our charter, feel free to post them in writing to the mailing list. -------------- 2. Implementation/Validation Strategy To reach REQ state, we have to demonstrate implmentation and interoperability. We have to document our test&validation strategy to validate it with W3C. The proposals I have seem so far are (a) We use plugins and example sites to demonstrate interoperability (b) We hope that a browser vendor re-joins; else we die (c) We retrofit our standard to the existing IE/Edge implementation If we reach consensus in this call what to propose, I volunteer for workign with W3C to get feedback. Else I suggest we use our Call-for-Objections process to determine consensus. ------ 3. Usability for hosted sites https://github.com/w3c/dnt/issues/10 https://github.com/w3c/dnt/issues/11 We concluded that one should not try to implement DNT without explicit support of the hosting provider. (I.e.. the TSR remains unchanged). This discussion continues to try to identify the best way how the content owner can interact with the site owner. One proposal was to use http-equiv (issue 10). another proposal was using JSON (issue 11). Third proposal was to do nothing. ---------- 4. Returning promises - Did we reach a conclusion on Issue 11? https://github.com/w3c/dnt/issues/12 ------------------- 5. Other issues from our tracker: https://github.com/w3c/dnt/issues UPDATED Webex Info -- This is a placeholder for the biweekly TPWG Telco. We agreed to calendar a placeholder and cancel if needed CHAT: irc.w3.org channel #dnt PHONE: 12:00 pm | Eastern Daylight Time (New York, GMT-04:00) | 1 hr Meeting number: 642 521 085 Meeting password: dnt Meeting link: https://mit.webex.com/mit/j.php?MTID=m1e591a8d322ec7d4989b2dd6fbf11c35 Audio connection: +1-617-324-0000
Received on Friday, 3 March 2017 12:56:14 UTC