14:59:59 <RRSAgent> RRSAgent has joined #voiceinteraction
15:00:00 <RRSAgent> logging to https://www.w3.org/2022/11/02-voiceinteraction-irc
15:00:17 <ddahl> meeting: Voice Interaction Community Group
15:00:25 <ddahl> chair: debbie
15:00:31 <ddahl> scribe: ddahl
15:00:37 <ddahl> regrets: dirk
15:02:18 <ddahl> regrets+ jon
15:07:30 <ddahl> Web-based Digital Twins for Smart Cities Interest Group on GitHub:   https://github.com/w3c/smartcities-workshop/tree/main/draft-charter   (rendered version: https://w3c.github.io/smartcities-workshop/draft-charter/index.html [1])
15:07:49 <ddahl> draft charter for W3C Smart Cities
15:12:31 <ddahl> topic: requirements
15:13:53 <ddahl> 6.	It MUST be possible to forward requests from one IPA to another with the same architecture, omitting the client layer
15:14:35 <ddahl> jim: let's talk about 2.	Specialized virtual assistants MUST be able to provide enterprise-specific information
15:25:21 <ddahl> jim: not all IPA's should have to provide a Client
15:26:02 <ddahl> noreen: it should also be able to use a voice interface
15:26:26 <ddahl> jim: thinking about an IPA acting as a service
15:26:41 <ddahl> ...like math functions, time of day, weather
15:27:04 <ddahl> noreen: or the IPA sends a message to a client
15:28:04 <ddahl> change 8.	IPA's MAY include a Client layer from MUST
15:28:37 <ddahl> how about 9.	IPA's MUST include a Dialog layer?
15:33:41 <ddahl> number 10 should stay "MAY"
15:43:15 <ddahl> 1.	The IPA Client MUST be activated by means of a Client Activation Strategy.
15:43:22 <ddahl> jim: hand gestures?
15:43:31 <ddahl> debbie: always on?
15:44:06 <ddahl> noreen: it needs to be minimally active even to notice hotwords
15:44:21 <ddahl> jim: timer
15:44:39 <ddahl> ...the alarm goes off and it starts producing stuff that you can hear
15:45:08 <ddahl> debbie: like a clock radio that you can talk to
15:45:57 <ddahl> debbie: we could add these to the document
15:46:07 <ddahl> ...in Client Activation Strategy
15:46:44 <ddahl> jim: leave open-ended
15:50:04 <ddahl> noreen: should add "deactivation" to the Client Activation section
15:51:31 <ddahl> ... you want to be able to tell it not to accept any external commands while deactivated
15:51:41 <ddahl> jim: are there levels of activation?
15:51:58 <ddahl> bev: in a security environment there are levels of activation
15:53:27 <ddahl> debbie: what are the levels of activation?
15:54:18 <ddahl> noreen: only local activation
15:54:29 <ddahl> bev: only local network
15:54:45 <ddahl> jim: active for some people but not others
15:55:04 <ddahl> ...children, employees
15:55:54 <ddahl> debbie: only listening for hotwords
15:56:57 <ddahl> bev: segmentation is parts of the network, not the main network
16:02:20 <ddahl> debbie: resume at section 3.1.3, number 1
16:02:27 <ddahl> rrsagent, format minutes
16:02:27 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/02-voiceinteraction-minutes.html ddahl
16:02:41 <ddahl> rrsagent, make logs public
17:06:02 <ddahl> present: jim,debbie, noreen, bev
17:06:11 <ddahl> rrsagent, format minutes
17:06:11 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/02-voiceinteraction-minutes.html ddahl
17:20:32 <ddahl> ddahl has left #voiceinteraction