15:00:08 <RRSAgent> RRSAgent has joined #voiceinteraction
15:00:08 <RRSAgent> logging to https://www.w3.org/2021/04/07-voiceinteraction-irc
15:00:23 <ddahl> meeting: Voice Interaction Community Group
15:00:29 <ddahl> chair: debbie
15:00:41 <ddahl> scribe:ddahl
15:04:26 <ddahl> look at minutes from last time https://www.w3.org/2021/03/24-voiceinteraction-minutes.html
15:05:29 <ddahl> debbie: didn't update the text description ACTION: debbie to update text description in Section 4
15:05:50 <ddahl> ACTION: dirk to change arrows to reflect the primary use case
15:06:06 <ddahl> dirk: didn't do that
15:06:21 <ddahl> ACTION: debbie to pull together list of outstanding comments
15:06:25 <ddahl> debbie: did do that
15:08:54 <ddahl> debbie: here's the link to github issues https://github.com/w3c/voiceinteraction/issues
15:11:12 <ddahl> dirk: how to track issues?
15:12:46 <ddahl> dirk: should we track in the minutes as well as github?
15:13:01 <ddahl> debbie: no point in the minutes, so just use GitHub
15:14:51 <ddahl> dirk: we can use some labels like "projects" that map to documents, "milestones" for the next version to publish
15:15:40 <ddahl> dirk: version tracking?
15:15:49 <ddahl> dirk: use this to track actions
15:17:27 <ddahl> dirk: what is the audience for the document?
15:18:53 <ddahl> debbie: application developers, platform developers, anyone else?
15:19:16 <ddahl> jim: add the reason why this audience should be interested?
15:19:19 <ddahl> dirk: yes
15:19:57 <ddahl> jim: one reason is that it could provide insight into future platforms
15:20:36 <ddahl> jim: who else?
15:21:19 <ddahl> debbie: buyers of conversational agents
15:21:39 <ddahl> dirk: offerers of conversational agents
15:22:36 <ddahl> jon: coders, e.g. open source, also secondarily, purchasers, and the third would be legislators and regulators -- what are best practices
15:22:55 <ddahl> ...what are tradeoffs in control
15:23:39 <ddahl> dirk: also platform architects is another primary group
15:24:18 <ddahl> ...there is a big difference between developers and architects
15:25:33 <ddahl> this is issue 2
15:26:23 <ddahl> jon: can do this and update document in GitHub
15:28:08 <ddahl> action: make sure jon has access to GitHub
15:29:24 <ddahl> issue 3: what is the problem?
15:29:51 <ddahl> debbie: interoperability
15:30:29 <ddahl> dirk: identify components that contribute to an IPA
15:30:45 <ddahl> debbie: that's a prerequisite to interoperability
15:32:30 <ddahl> debbie: some of partitioning is tradition
15:33:09 <ddahl> ... it's consistent from most existing technology
15:34:38 <ddahl> jim: similar issues to voice registry system
15:36:54 <ddahl> jon: could say publicly that VRS is under development by OVN
15:37:18 <ddahl> jim: some principles -- Single Responsibility Loose Coupling Event-Driven Availability and Partitioning of Network Eventual Consistency Interface segregation Automation (CICD, DevOps, Containerization, Service Mesh, Observability, etc.)
15:37:40 <ddahl> ...from the OVN
15:38:15 <ddahl> debbie: what is eventual consistency?
15:38:28 <ddahl> jim: eventually components will be consistent
15:39:06 <ddahl> debbie: what is "interface segregation"?
15:39:20 <ddahl> jim: not sure
15:39:54 <ddahl> debbie: what is "service mesh"?
15:40:12 <ddahl> jim: each module is subject to automation
15:40:55 <ddahl> dirk: "interface segregation" interfaces should not be forced to depend on interfaces that they do not use
15:41:45 <ddahl> dirk: will add something about software principles
15:42:06 <ddahl> debbie: could talk about interoperability
15:42:51 <ddahl> jon: purpose of document is to define components and interoperability
15:44:26 <ddahl> topic: issue4
15:46:22 <ddahl> jim: Travel Planning seems to be specialized
15:46:32 <ddahl> debbie: I was thinking that it was both
15:47:23 <ddahl> jim: there could be a continuum
15:47:45 <ddahl> jon: independent vs. developed by a platform
15:49:39 <ddahl> jim: this is for informational purposes for the reader
15:50:03 <ddahl> ...we don't need to do anything for the document
15:50:58 <ddahl> jon: I think this is an architecture beyond the platform, if you're just developing a skill you don't need this
15:53:11 <ddahl> topic: issue5
15:54:32 <ddahl> debbie: agree with the last three points
15:55:06 <ddahl> dirk: agree with the second and third
15:55:33 <ddahl> ...if we move ASR and TTS to the client it may confuse architects
15:56:57 <ddahl> jim: ASR and TTS are closely tied to input/output devices
15:57:29 <ddahl> dirk: the components are related to each other, but this doesn't match current practice
15:57:53 <ddahl> ... very little local ASR
15:58:03 <ddahl> ...but conceptually it makes sense
15:58:45 <ddahl> jim: should we just concentrate on the conceptual in Figure 1
15:59:08 <ddahl> dirk: we can move these components to the client and say that this is a conceptual view
15:59:24 <ddahl> ...what about NLU and NLG
16:01:49 <ddahl> jim: do we have a deadline?
16:02:12 <ddahl> dirk: there are lots of issues, say two months
16:03:39 <ddahl> debbie: we could work on things off-line before the next call
16:03:53 <ddahl> rrsagent, make logs public
16:04:01 <ddahl> rrsagent, format minutes
16:04:01 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/07-voiceinteraction-minutes.html ddahl
17:35:01 <ddahl> present:jon, jim, dirk, debbie
17:35:09 <ddahl> rrsagent, format minutes
17:35:09 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/07-voiceinteraction-minutes.html ddahl
17:39:17 <ddahl> the next call will be in two weeks, April 21
17:39:26 <ddahl> rrsagent, format minutes
17:39:26 <RRSAgent> I have made the request to generate https://www.w3.org/2021/04/07-voiceinteraction-minutes.html ddahl
17:43:09 <ddahl> ddahl has left #voiceinteraction