<scribe> scribe: debbie
<scribe> agenda: Open Voice Network overview – goals, current activities, future plans, Jon W3C Voice Interaction community group – goals, current activities, future plans, Debbie Brainstorm about specific ideas for future voice standards Potential for cooperation between groups
jon: introduces himself and presents slides
slides https://lists.w3.org/Archives/Public/public-voiceinteraction/2020May/0009.html
jon: would like opportunity to
cooperate
... topics -- dns for voice, voice commerce, identification,
data privacy, interoperability
emmett: how does interoperability work without standards?
jon: we are interested in new standards
emmett: we do need to have standards
jon: doesn't want to become a standards body, but does advocate standards
jim: could you recommend a standard to the W3C?
jon: yes
debbie: is there a proposal for DNS?
jon: starting to proceed on that
debbie: can look at liaison with
W3C
... also need to clarify any IP questions
jon: would need to check with
counsel
... debbie and dirk should present paper to Open Voice
Network
... could join one of OVN meetings
debbie: could have some kind of joint task force
jon: we would welcome that
... will work on formal liaison
... jon and jim, debbie, dirk to join one of their meetings
jim: who is liaison?
debbie: can find out
... will forward liaison pages to jon
jim: debbie and dirk should present to technical committee
debbie: jon could join out
group
... will send url to jon
jon: or someone else from OVN could join
debbie: OVN could do more
outreach
... reviews slides
jim: OVN would be interested in architecture
debbie: would be great to get comments
dirk: haven't gotten many comments yet
emmett: could dialog manager be pulled out?
dirk: yes, each box could be
replaced by something that exists
... this is why we're identifying interfaces
jim: OVN needs to understand what these terms mean
<scribe> ACTION: debbie to forward liaison page
dirk: this is also in our document
<scribe> ACTION: debbie to find url to join
debbie: next agenda is to talk about component
jim: architecture and registry
dirk: dialog registry and provider selection service
emmett: can registry pass along context?
dirk: yes
debbie: reviews use case
... we haven't talked about privacy and security much but this
is important
dirk: we should consider trust as well
jim: relationship to MMI
debbie: MMI and Voice Browser
standards would be lower level than this architecture
... will review standards in the interfaces work
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: jonStine emmett dirk bev debbie No ScribeNick specified. Guessing ScribeNick: ddahl_ Found Scribe: debbie WARNING: No "Topic:" lines found. 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: debbie 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.)[End of scribe.perl diagnostic output]