15:48:15 RRSAgent has joined #voiceinteraction 15:48:15 logging to https://www.w3.org/2021/03/10-voiceinteraction-irc 15:48:29 meeting: Voice Interaction Community Group 15:48:41 chair: Debbie 15:48:48 scribe: ddahl 15:49:04 regrets:Bev 15:49:27 regrets+ Jon (partial) 15:49:34 rrsagent, format minutes 15:49:34 I have made the request to generate https://www.w3.org/2021/03/10-voiceinteraction-minutes.html ddahl 15:49:42 rrsagent, make logs public 15:52:06 agenda: https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0001.html 16:15:19 topic: Jim's suggestions 16:15:29 present:jim, debbie 16:16:28 Jim's comments: https://lists.w3.org/Archives/Public/public-voiceinteraction/2021Mar/0002.html 16:18:59 jim: the document should discuss interfaces 16:19:27 debbie: there's another document called "interfaces", very rudimentary 16:19:36 jim: who is the audience? 16:20:04 debbie: one audience is developers for application developers 16:20:14 ...also platform developers 16:20:27 jim: there should be a sentence describing audience 16:20:37 debbie: we should add that 16:21:15 jim: what is the problem? 16:21:23 debbie: I think it's interoperability 16:21:40 jim: I think that's the main purpose 16:22:12 ...describe principles about how the partition was arrived at 16:22:37 ...general software principles could be referenced 16:23:11 ...there is a nice hierarchical partitioning 16:24:15 debbie: we were using a traditional partitioning for conversational systems 16:24:30 jim: this should be included in the document 16:24:34 debbie: agree 16:26:16 jim: 2.1 this is a specialized IPA 16:27:27 debbie: it was supposed to be general, maybe we should remove this because it's not consistent with the later walkthrough 16:27:44 jim: what is the difference between general and specialized IPA 16:28:25 debbie: the general IPA does general things, but it's a portal to more specialized IPA's 16:28:52 jim: the general IPA is something like current smart speakers 16:29:13 ...our audience will be building specialized IPA's, not the general IPA's 16:29:39 ...maybe the document should focus on specialized IPA's 16:30:00 debbie: I think we have to talk about both because they have to interoperate 16:30:34 jim: the target should be specialized IPA's 16:30:56 debbie: what's the role of standards with specialized IPA's 16:31:20 jim: they could share components like ASR or TTS 16:32:14 ...maybe only the front end is generalized 16:34:02 ...a generalized IPA can answer anything in the world 16:34:11 ...it could be a portal to a specialized IPA 16:35:29 debbie: the generalized IPA knows about public information 16:35:48 jim: generalized IPA could be a portal to a specialized IPA 16:36:02 ...much like a web browser 16:36:30 ...a specialized IPA knows information about a particular business 16:37:26 debbie: more general, e.g. government, nonprofit, school 16:38:18 ...we should not drop this because we need them to interoperate 16:38:46 ...we should have more explanation about the difference 16:40:09 ...between general and specialized IPA's 16:40:54 jim: this document provides information for specialized IPA's 16:41:15 ...there will be few generalized IPA's 16:44:07 jim: begin architecture section with 3 high level boxes and then expand 16:44:41 debbie: I like the idea of making it more multimodal 16:45:06 jim: more IPA's will have screens 16:46:04 ...move ASR and TTS out of dialog box into client box 16:46:33 +1 16:46:50 jim: what is a "session"? 16:47:15 debbie: we should define what we mean by "session" 16:47:31 jim: may extend over days, multiple users could come and go 16:48:14 ...standards committees have ongoing sessions with multiple meetings 16:48:45 debbie: credentials 16:49:32 next time restart at "client activation strategy" 16:52:46 rrsagent, format minutes 16:52:46 I have made the request to generate https://www.w3.org/2021/03/10-voiceinteraction-minutes.html ddahl 16:52:53 rrsagent, make logs public