<scribe> scribe: debbie
debbie: to help with attendance, send agenda a few days before
dirk: will send agenda around Monday or Tuesday
debbie: will still have time
discrepancy for the next call, but after that will be in
sync
... sending irc links to the Google chat
dirk: will add irc information to the invite
debbie: should focus on next steps with architecture
<Bev> Hello
debbie: dirk has finished his
updates
... still need to review English
... need to make a list of suggestions
bev: no suggestions about architecture document yet
debbie: should we send out
another poll?
... for time
<scribe> ACTION: dirk to send around a poll for a new time
<scribe> ACTION: debbie to review English
dirk: set up a new document about
interfaces
... more detail
<Bev> Sorry, the call dropped again for me. Will dial back in again.
debbie: should we focus on one
specific interface first
... dialog registry underlies all the interoperability
dirk: some existing implementations go directly to different services like Sound Hound
debbie: I was thinking that you would want your smart speaker to be able to find, for example, your bank
dirk: generic way to go from
smart speaker to go to a web service like Sound Hound or a
weather service
... an adapter or bridge
debbie: some platforms have built in services
dirk: between dialog and
API's
... this is the provider selection service
... this is for generic platforms and for providers
debbie: do we need a new use
case?
... this is from the user perspective, but maybe we need the
developer perspective
... provider API's are mostly web services
... we should focus on one
... come up with a few requirements
... for a standard
dirk: what we expect the services to provide
debbie: proper security
... need to be able to fully express user intents, with the
ability to specify entities
... we could try working through an example, like the visa
expert
dirk: this might lead us away from generic interfaces
debbie: we should work through a couple of examples
dirk: weather would be a good
example because it needs to integrate user-specific
information
... can start new document
debbie: how about "Intelligent personal assistant interfaces"?
dirk: will add weather use case
and will try to come up with a more formal graphic
... would UML be suitable
... to draw the images
debbie: we should do whatever we can to make the ideas clear.
dirk: agree that we should use SVG as much as possible
<scribe> ACTION: dirk to start new document
debbie: the next call is March 26, time will still be different between Europe and US
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: dirk debbie bev No ScribeNick specified. Guessing ScribeNick: ddahl Found Scribe: debbie WARNING: No "Topic:" lines found. WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: debbie dirk WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]