Meeting minutes
interfaces document
dirk: goal is to provide examples to clarify document
… use cases -- information retrieval and accessing remote services
… looking at messages about weather forecast
… audio output, but could also include text
… will also include text
… also flight reservation use case
debbie: change log would include examples
dirk: didn't publish the first version of this
dirk: create reference implementation
… going to existing IPA's
… should be possible to map to proprietary formats
debbie: web page as endpoint?
jim: should these examples include endpoints?
debbie: endpoints are defined in the architecture document
jim: should include a screen
debbie: it's a MAY requirement
look at GitHub issues
dirk: worked on GitHub
dirk: after closing, should be able to release document
… addedd labels in GitHub issues
… let's revisit issues
requirements
debbie: next requirement is "3. The Dialog Manager MUST consider ongoing workflows that must not be interrupted"
dirk: is this MUST or SHOULD
bev: medical device
jim: processing of emergency message
jon: automotive user management
debbie: who decides what must not be interrupted?
jim: priority list of interruptions
… with a boundary
debbie: does user decide?
dirk: interruptibility of user and interruptibility of workflow
jim: depends on application, so is this out of scope?
debbie: users must always be able to interrupt the system
jon: calls to 911 have priority, there may be societal concerns
bev: how to insure that technologies in systems cannot be weaponized
jim: partial shutdown
bev: what to log and not log?
jim: you might not want to log some things
debbie: should we remove "5. The Dialog Manager MUST determine the Dialog that is best suited to serve the current user input"
… is that just saying the DM should do its job
stop at "5. The Dialog Manager MUST receive the next dialog move as output from the selected Dialog or the IPA Service'