trackbot, start meeting

<trackbot> Sorry, but no Tracker is associated with this channel.

Update from WG F2F

padenot: Met Monday + Tues, addressed majoprity of issues in detail. Moved V2 issues to a new repo

https://github.com/WebAudio/web-audio-api-v2

padenot this is the place for new issues/prs to be raised on V2

hoch TAG dropped in on day 2. We will be filing a request for design review of the ADC. Initial feedback was positive.

hoch 48 issues transferred to V2. V1 has 16 open issues, mainly ready for editing.

hoch has an action to invite more developers to the CG

padenot a number of issues were closed around decoding/encoding. It is hoped tha these will be picked up in the webcodec spec

<padenot> https://github.com/WICG/web-codecs

padenot WAAPI is focussed on processing not en/decoding.

phila usecases - SSML1.1 circa 2010 used in all assistants bar siri. Need for updates to the spec.

phila how to markup a page to allow voice assistants to navigate more easily.

padenot mozilla are researching this area (ux and nav).

hoch speech recognition/synthesis is out of scope for WAAPI

padenot we closed issues during the F2F as we are unable to access speech data from the os

<hoch> Might be relevant: https://developers.google.com/actions/reference/ssml

padenot looking at V2 there are a number of categories: 1. Maintenance of the v1 and editorial updates (issue 50). 2. Enhancement to existing features (issue 39)3. New features

for example a noise generator. Issue 8

https://github.com/WebAudio/web-audio-api-v2/issues/8

padenot category 1 & 2 are more for the working group to deal with, category 3 is of most interest to the cg

padenot people have not yet really discovered the v2 repo or started to request features. Outreach will be needed to different groups. tweet, music dsp list, web audio conference, web audio weekly, icma, nime

hoch padenot to be successful we need to expand participation in the community group.

padenot it was hard to accept new features during v1 as the WG was focussed on pulling together a coherent spec, V2 gives a chance to build on this now

hoch if we have a v2 document do we need a TAG review? padenot not initially, have a period where we scope things and recharter correctly.

mdjp recharter should be on the next WG call agenda

hoch how do we handle 1 & 2 (updates to the spec)

padenot copy v1 spec and seperate document with new features. hoch Need to settle on an approach to updates before encouraging people to engage.

mdjp do this at WG level and then propose to the group.

mdjp proposing fortnightly call going forward alternating for different timezones

WG will continue to meet weekly to complete v1. mdjp will put a schedule for meetings to the end of year on the cg wiki/github wiki

mdjp any feedback or concerns on V2

rtoyg_m2 are we still pushing mathmatical processes off to audioworklet?

rtoyg_m2 mathmatical oscillators as native node?

rtoyg_m2 or an official standard library?

<padenot> https://github.com/tc39/proposal-javascript-standard-library

<padenot> adjourned

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)


WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: mdjp
Inferring Scribes: mdjp

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)