W3C

- DRAFT -

voiceinteraction

03 Jun 2020

Attendees

Present
dirk, debbie, bev
Regrets
Chair
dirk
Scribe
debbie

Contents


<scribe> scribe: debbie

Open Voice Network

dirk: dirk and debbie invited to join OVN call
... we can start with Debbie's slide deck

debbie: it's in the voice interaction email archive

https://lists.w3.org/Archives/Public/public-voiceinteraction/2020May/0006.html

debbie: will send PowerPoint version

bev: thought it was interesting, didn't dig into it
... the concept seemed interesting

debbie: need to find out more about what they're doing
... w3c is pretty flexible
... formal agreements need to go through legal

interfaces document

debbie: last time we talked about moving forward on interfaces

dirk: added some words to introduction, purpose of document
... modeled in UML
... source document is https://github.com/w3c/voiceinteraction/blob/master/voice%20interaction%20drafts/pa-architecture.EAP

debbie: was supposed to link up interfaces to related standards, didn't do that but I will

dirk: are interfaces complete or is something missing

debbie: can check that
... will look at Web of Things registry to see if we can use that kind of format
... is "dialog registry" more of a "service registry"?

dirk: could add dialog to capabilities of IPA
... dialog registry would know about all dialogs that can handle e.g. weather forecasts
... the other part is provider selection service

debbie: like the National Weather Service in the US

dirk: how to add complete IPA providers, e.g. Alexa

Debbie: is Alexa an example of the IPA Service?

dirk: need to think about relationship between existing IPA platforms and this architecture

bev: where does authentication take place?

debbie: maybe there needs to be more than one point

dirk: you might need authentication to access the IPA service itself
... you would need to authenticate access to the IPA as well as to the data

debbie: usually on the web you have to authenticate yourself when you first access the service

bev: should we include bridges as well as API's?
... here's an example https://dl.acm.org/doi/10.1145/2792745.2792775
... bridges are used more with scientific data

debbie: it does sound like something we should include

bev: another one https://www.psc.edu/bvt/
... bridges are used more for complex data
... API's are more for business data

dirk: an example would be helpful

bev: could help with use case for weather
... would start with bullet points
... users tend to be scientists
... or other professionals

debbie: users could be professionals/scientists as well as ordinary users

dirk: add authentication to IPA

debbie: finish up use cases

bev: outline weather use case

https://sciencegateways.org/resources/catalog

debbie: could report back on OVN call

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/06/03 16:07:37 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/interfaced/interfaces/
Succeeded: s/interfaces/interfaced/
Succeeded: s/interfaced/interfaces/
Succeeded: s/invited to join OVN/invited to join OVN call/
Present: dirk debbie bev
No ScribeNick specified.  Guessing ScribeNick: ddahl
Found Scribe: debbie

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: 

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]