W3C home > Mailing lists > Public > public-privacy@w3.org > January to March 2018

Re: Web Audio API for review

From: David Singer <singer@apple.com>
Date: Tue, 27 Mar 2018 09:36:12 -0700
Cc: Chris Lilley <chris@w3.org>, public-privacy@w3.org
Message-id: <BB9C99C3-13BE-4DBD-91CB-E3EBF2AB2D5C@apple.com>
To: Tom Ritter <tom@ritter.vg>


> On Mar 27, 2018, at 7:50 , Tom Ritter <tom@ritter.vg> wrote:
> 
>> The Security & Privacy appending of High Resolution Time should be consulted for further information on clock resolution and drift.
> 
> I think that's a typo: 'Appendix'?
> 
> The added text, and in particular 'Does this specification expose any
> other data to an origin that it doesn’t currently have access to?'
> section is pretty good.
> 
> I am curious though - Is the Security and Privacy Implications section
> complete? Normally this section is written out in more of a prose
> style than in the Q/A style to the questionnaire, isn't it?

Yes, the questionnaires are, I think, designed to help you think (and they are, I think, still missing the important “and what else about your spec. raises privacy concerns that these questions have not exposed?”). 


> 
> -tom
> 
> 
> 
> On 27 March 2018 at 08:55, Chris Lilley <chris@w3.org> wrote:
>> Tom,
>> 
>> The issue you raised has been discussed by the Audio WG and the spec
>> updated. Please see
>> 
>> https://github.com/WebAudio/web-audio-api/issues/1457
>> 
>> and let us know whether the language added to the spec addresses your
>> concern?
>> 
>> 
>> --
>> Chris Lilley
>> @svgeesus
>> Technical Director @ W3C
>> W3C Strategy Team, Core Web Design
>> W3C Architecture & Technology Team, Core Web & Media
>> 
> 

David Singer
Manager, Software Standards, Apple Inc.
Received on Tuesday, 27 March 2018 16:36:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:49:34 UTC