[voiceinteraction] agenda call July 15, 2020

Let's talk about the Provider Selection Service, which is in the API's/Date
box in our architecture diagram
(https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paArchi
tecture.htm#architecture) and how the information that it uses could be
represented. We can start by brainstorming about what information would be
needed for a voice assistant to identify another specialized voice assistant
(for example, an assistant for a specific enterprise) and give the user
access to it. 

 

Some background about related standards. The last time we talked about this,
June 17
(https://lists.w3.org/Archives/Public/public-voiceinteraction/2020Jun/0006.h
tml),  Jim Larson suggested that information about voice assistants is very
similar to information for websites. Consequently, we should explore
modeling a voice assistant registry along the lines of the DNS service that
connects Web domain names to URL's and the Registration Data Access Protocol
(RDAP) that carries information about domain owners
https://www.icann.org/rdap, (this replaces the "whois" information on domain
name owners that you might be familiar with). RDAP was developed by ICANN
(Internet Corporation for Assigned Names and Numbers). If you look at the
FAQ for RDAP in the previous link, there is a section on "Understanding RDAP
results" that lists all the fields in the domain name access protocol. I
think most of them could be used as metadata for voice assistants, but we
would probably need to add more.

You can look up individual domain names here https://lookup.icann.org/lookup
to see examples.