- From: Matthew Paradis <matthew.paradis@bbc.co.uk>
- Date: Tue, 25 Sep 2018 10:50:17 +0000
- To: "Phillips, Addison" <addison@lab126.com>, "public-audio@w3.org" <public-audio@w3.org>
- CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
- Message-ID: <993DAE42-40A3-453A-9507-6F262413376B@bbc.co.uk>
Hello Addison, I’m sure that our staff contact Chris Lilley can provide more information here. However reading through our transition request I see the following noted regarding internationalisation. “Web Audio API was discussed at TPAC 2016 with the I18n Core chair, who confirmed that JavaScript APIs which do not expose human-readable text strings or take natural-language input do not constitute a problem for Internationalization.” I apologise if we should still have notified you. Given the above statement I hope that the review is relatively easy. Regards Matt (Co-chair web audio working group). -- Matthew Paradis Senior R&D Engineer – Audio Team, BBC Research & Development 030304 09889 | 07841 506241 www.bbc.co.uk/rd/sound From: "Phillips, Addison" <addison@lab126.com> Date: Monday, 24 September 2018 at 21:31 To: "public-audio@w3.org" <public-audio@w3.org> Cc: "public-i18n-core@w3.org" <public-i18n-core@w3.org> Subject: [web audio] I18N self-review? [I18N-ACTION-756] Resent-From: <public-audio@w3.org> Resent-Date: Monday, 24 September 2018 at 21:30 Hello webaudio, The Internationalization (I18N) Working Group has tasked [1] me with writing to you about your recent CR transition of the Web Audio API document [2]. Congratulations on this important milestone. As near as I can tell, your WG did not request a review from the I18N WG. If for some reason we missed your request or otherwise were unresponsive, please let me know. Assuming otherwise and based on the transition announcement, I have added your document to our review radar [3]. “Horizontal” review of specifications is one way that the W3C helps ensure universal access. While your specification doesn’t appear to have many areas for potential gaps, it puts a lot of pressure on our working group when we don’t have sufficient time to perform a review—and it can be disruptive if we eventually discover issues that need to be addressed. To that end, could you let us know: 1. Did you have a chance to perform a self-review or did you otherwise consider requesting an I18N WG review? 2. Were you aware of horizontal reviews as part of the process? If not, how can we better make you aware or make it easier to work with us? Thanks (for I18N), Addison Phillips Sr. Principal SDE – I18N (Amazon) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture. [1] https://www.w3.org/International/track/actions/756 [2] https://www.w3.org/TR/2018/CR-webaudio-20180918/ [3] https://github.com/w3c/i18n-activity/projects/1 ---------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. ---------------------
Received on Tuesday, 25 September 2018 10:50:48 UTC