14:57:14 RRSAgent has joined #voiceinteraction 14:57:14 logging to https://www.w3.org/2022/10/19-voiceinteraction-irc 14:57:31 meeting: Voice Interaction 14:57:42 chair: debbie 14:57:47 scribe: debbie 14:57:55 scribe:ddahl 15:02:09 agenda: https://lists.w3.org/Archives/Public/public-voiceinteraction/2022Oct/0004.html 15:02:20 rrsagent, format minutes 15:02:20 I have made the request to generate https://www.w3.org/2022/10/19-voiceinteraction-minutes.html ddahl 15:04:12 dirk: need to move the emergency use case to version 1.3 15:06:48 noreen: will make a new pull request for the same changes in 1.3 15:07:05 present: debbie, jim, dirk, noreen 15:08:20 topic: implied requirements 15:09:34 section 1 15:10:34 Specialized assistants MUST be able to interoperate with general IPA's 15:10:47 ...we all agree 15:12:43 dirk: IPA's SHOULD be able to execute operations in a user's environment 15:13:15 noreen: the environment that the user controls regardless of the location 15:16:20 ...IPA's SHOULD be able to execute operations 15:16:59 jim: IPA's should be about to execute user-requested operations 15:17:13 ...we agree 15:22:09 dirk: IPA's MAY be able to interact with users through other modalities. 15:24:11 2.1.1 IPA's MUST be able to transfer a partially completed task to another IPA 15:26:24 IPA's MUST be able to transfer a task to another IPA, including incomplete tasks 15:28:00 IPA's MUST be able to transfer a task to another IPA, including tasks that MAY be partially completed 15:28:33 jim: some database tasks can't be partially completed, all or none 15:28:56 noreen: a task could be a series of transactions 15:30:05 we agree 15:31:08 dirk: The architecture SHOULD support question answering 15:31:31 dirk: The architecture SHOULD support information retrieval requirements 15:36:25 dirk: need to number the requirements 15:36:42 .. then we can refer to them in other sections 15:37:53 debbie: cross-reference The architecture SHOULD support executing local services to accomplish tasks The architecture SHOULD support executing remote services to accomplish tasks 15:38:34 The architecture MUST support dynamically adding local and remote services or knowledge sources. 15:38:53 jim: also dynamically remove 15:39:24 dirk: for example, adding devices in a smart home 15:40:10 noreen: that could be a task that needs to be completed by more than one IPA 15:40:53 jim: if we move a lamp to another room, do we need to remove it and add it 15:41:25 dirk: this is more about context 15:42:05 noreen: when you move the lamp its attributes can change (like location) 15:43:19 jim: just "add or remove" 15:43:40 debbie: we should multiply out all the options 15:44:55 It MUST be possible to forward requests from one IPA to another with the same architecture 15:45:27 ...this is similar to the partially completed tasks 15:46:13 noreen: the topic level heading of section 2? 15:47:07 dirk: problem statement and use cases 15:47:57 It MUST be possible to forward requests from one IPA to another with the same architecture, omitting the client layer 15:49:26 debbie: that rules out smart speakers 15:50:22 dirk: this means one IPA becomes the client for another IPA 15:51:56 ...in the case of cars, the client can forward requests to Amazon, etc. 15:57:38 noreen: It MUST be possible to forward requests from one IPA to another using the standard architecture 15:58:22 (we just finished the 5th item in the architecture section) 15:59:25 dirk: still working on changes to interfaces document, also trying to add some sample requests using JSON notation 15:59:51 ...there's one example in Github 16:00:05 ...we can talk about that next time 16:01:24 debbie: will create a new requirements document 16:01:51 dirk: reverted changes to 1.2 and noreen put in a new pull request for 1.3 16:02:41 rrsagent, format minutes 16:02:42 I have made the request to generate https://www.w3.org/2022/10/19-voiceinteraction-minutes.html ddahl 16:02:50 rrsagent, make logs public