Actions

debbie: no actions due today

Speech XG

dan: some kind of protocol which can handle various codecs
... might be done in outside W3C?

debbie: regarding XG extension, no idea about the procedure

dan: as an XG it should be OK to extend up to one more year. Need to check with Coralie.

debbie: or maybe recharter as the Emotion XG did

dan: it's possible
... the primary goal is done before TPAC
... and kick-off meeting at TPAC

debbie: the point is where is the appropriate place to the discussion (existing WGs or a new WG, etc.)

doug: (joins)

debbie: we're talking about HTML Speech XG

dan: expected to bring our ideas to the existing WGs
... but WGs, e.g., HTML WG, are overloaded these days
... some of the XG participants think it would make sense to do our work within Web Apps WG
... need to ask Doug about opinion

janina: seems to useful to do this

dan: standard track work should be done
... the real question is where to do this as standard track work

janina: ok

doug: read the minutes from your meeting (XG meeting)
... interested in all the audio related topics within W3C
... think Web Apps is out
... clearly not in the scope of the Web Apps group
... the target is APIs and Widgets
... could suggest another group, e.g., DAP
... also could be a TF within the HTML WG
... is Bjorn included?

dan: we have Bjorn from Google
... also another communicating with the Google Chrome Team

doug: how about Web RTC?

dan: never happened
... I'm one of the editors in that group
... but no way to add Speech XG's work to their scope

doug: what's the specific objection?
... browser vendors involved?

dan: btw, you said Web Apps is working for APIs. And API means JavaScript API. right?

doug: I guess I'm saying...
... scope in the Web Apps
... but everybody comes to Web Apps, and it's getting not manageable

dan: the concern raised by Google
... their main concern is mainly speech industry joined the XG
... but lacking Web technology guys
... need sufficient input from Web community
... you have large participation from normal Web tech guys

debbie: regarding input from non-speech
... doesn't Google have non-speech guys as well, do they?

dan: don't know how we can do that

doug: if you scare people enough, people will do that
... for example, when I did DOM3 events, I tried to get feedback from people
... if you get a call for Web Apps group, need a review
... personally very reluctant to new work
... I understand it's API
... but it's a speech API
... most people in the Web Apps don't have speech expertise
... why doing it in the Web Apps group is problematic, the group already has very broad scope
... and it would take long to update the charter
... need to talk with lawyers
... my suggestion is trying it in your WG, and try to get browser vendors involved

debbie: any opinion from Bert?

bert: no...
... sounds completely different
... would agree with Doug

dan: ok

debbie: speech technology has a bit different IP area from Web tech
... might cause extra delay

doug: my advice is starting discussion with broader community
... including Web Apps, DAP and HTML
... whoever the staff contact should try to get Web browser vendors
... the number is growing, but it's still difficult for everybody to review the charter
... I think the next step could be drafting the charter in your working group
... and ask specific Webby guys for review

dan: I mentioned several options right before your joining
... the goal is bringing speech capability into HTML
... there are various options
... the APIs and/or markups
... some people would like to add reco element
... but some really don't like it
... there is a third piece
... the group is calling protocol
... no one knew protocol from IETF viewpoint
... regarding protocol carried over WebSockets, it's rather IETF work, I think

doug: similar situation in Web RTC

dan: right

doug: separation between W3C and IETF is clear now
... suggest you write your charter right now

dan: we'd like to hold a kick-off meeting at TPAC
... I wanted to use the time for XG report, but we can start new discussion instead

doug: would suggest you start new charter
... who is the staff contact

dan: it's a XG, so no staff contact. just have Coralie as the Activity Lead

doug: she doesn't usually do much technical review of charters and specs

dan: invited Matt Womer to the last meeting

doug: if I were you, would draft a charter based on the WebRTC charter
... you can talk with Doug, Matt, Francois, Mike Smith, PLH, etc.
... also Kaz ahd PH from UbiWeb
... HTML, WebApps

dan: Audio as well?
... audio capture API is needed

doug: we'll have multiple specs

debbie: not a bad idea to have discussion within HCG about which groups are related

dan: I just need to draft a charter

debbie: checking with Kaz

kaz: we need to create a new WG in any case, I think

debbie: we've got consensus about creating a new WG

doug: Audio WG, DAP WG and this group work for APIs
... audio and multimedia
... all these need same kind of people
... maybe need some sort of coordination call?
... I think we should have discussion how to drive the right people
... we can try to get more attention for this topic

kaz: maybe Web and TV IG could be also involved, because speech interface should be useful for TV remote

doug: need more exposure in interaction domain

kaz: btw, where to send the minutes, public or member?

all: public :)

RESOLUTION: we advise this HTML Speech XG to write a charter for a Speech APIs WG in Interaction domain, and circulate it first among the W3C staff and then ask for review from groups including HTML, Web Apps, Web RTC, DAP, and WHAT-WG, etc.

<scribe> ACTION: burnett to draft a charter based on the Web RTC charter [recorded in http://www.w3.org/2011/08/12-hcg-minutes.html#action01]

<trackbot> Created ACTION-65 - Draft a charter based on the Web RTC charter [on Daniel Burnett - due 2011-08-19].

(some more discussion about visibility of the group's work)

[ adjourned ]