- From: Samuel Weiler <weiler@w3.org>
- Date: Sun, 15 Sep 2019 23:54:27 -0400 (EDT)
- To: public-privacy@w3.org
- cc: psnyder@brave.com, runnegar@isoc.org, tjwhalen@google.com
- Message-ID: <alpine.OSX.2.20.1909152352580.6320@celebrate-2015-macbook-pro.local>
The Audio WG requests a re-review. They offered that they're meeting tomorrow morning and, if we prefer to meet them in person, they're available then. (I'm not available.) -- Sam ---------- Forwarded message ---------- Date: Sun, 15 Sep 2019 17:24:32 -0700 From: Chris Lilley <notifications@github.com> Reply-To: w3cping/tracking-issues <reply+AF6OSPSWB4665HKUEQQYOGF3RQLNBEVBNHHB23W7CM@reply.github.com> To: w3cping/tracking-issues <tracking-issues@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [w3cping/tracking-issues] WebAudio API: re-review requested (#13) Audio WG requests privacy re-review of the Web Audio API. This specification has already had a round of Privacy review; however we are readying an updated CR, and would like to be sure that the changes since the 18 September 2018 CR do not introduce any new privacy concerns. The changes are primarily clarifications and bugfixes; no new features have been added since the previous CR. The Security and Privacy Considerations from the last review remains available. We are happy to visit you in in Yoh, 3F for a brief meeting at TPAC, if any issues are noticed (we are in Kashi, 1F). Alternatively, if you agree that the changes are all minor and don't introduce any new privacy issues, please feel free to close this issue so we can reference it in our CR transition request. Many thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute thethread.[AF6OSPWAHQPFXYLQQJQMWJLQJ3G4BA5CNFSM4IW4PPSKYY3PNVWWK3TUL52HS4DFUVE XG43VMWVGG33NNVSW45C7NFSM4HLO34JQ.gif]
Received on Monday, 16 September 2019 03:54:36 UTC