Meeting minutes
Web-based Digital Twins for Smart Cities Interest Group on GitHub: https://
draft charter for W3C Smart Cities
requirements
6. It MUST be possible to forward requests from one IPA to another with the same architecture, omitting the client layer
jim: let's talk about 2. Specialized virtual assistants MUST be able to provide enterprise-specific information
jim: not all IPA's should have to provide a Client
noreen: it should also be able to use a voice interface
jim: thinking about an IPA acting as a service
… like math functions, time of day, weather
noreen: or the IPA sends a message to a client
change 8. IPA's MAY include a Client layer from MUST
how about 9. IPA's MUST include a Dialog layer?
number 10 should stay "MAY"
1. The IPA Client MUST be activated by means of a Client Activation Strategy.
jim: hand gestures?
debbie: always on?
noreen: it needs to be minimally active even to notice hotwords
jim: timer
… the alarm goes off and it starts producing stuff that you can hear
debbie: like a clock radio that you can talk to
debbie: we could add these to the document
… in Client Activation Strategy
jim: leave open-ended
noreen: should add "deactivation" to the Client Activation section
… you want to be able to tell it not to accept any external commands while deactivated
jim: are there levels of activation?
bev: in a security environment there are levels of activation
debbie: what are the levels of activation?
noreen: only local activation
bev: only local network
jim: active for some people but not others
… children, employees
debbie: only listening for hotwords
bev: segmentation is parts of the network, not the main network
debbie: resume at section 3.1.3, number 1