<scribe> scribe: debbie

debbie: interested in talking about DNS process as it applies to personal assistants

jon: we could talk about two topics: DNS/ICANN or architecture
... Jim should be on the call when we talk about DNS

debbie: I think the ICANN/DNS process would be worth looking at
... when Jim is on the call
... so we can look at the architecture today

jon: does this meta-architecture make a distinction between cloud and local?

debbie: this doesn't make a distinction

jon: need to have a privacy-centric architecture

debbie: not just cloud vs. embedded
... also on-premise servers
... this doesn't address privacy, but we were thinking that privacy could be accommodated

jon: how does enterprise ipa protect my data?

debbie: one model would be to pattern after the web so that when you enter an enterprise's space it authenticates you

jon: could enter an enterprise as a guest

debbie: for example, Amazon lets you shop but if you want to buy you have to log in

jon: how do you keep Target's data out of the hands of Amazon?

debbie: like how do you keep you data out of the hands of Google
... use a different browser like Duck-Duck go
... all platforms have to provide privacy settings
... you just don't use Amazon
... two options, making it possible to enforce privacy or platforms actually being forced to respect privacy
... there is accessibility legislation, but people don't necessarily respect it

jon: standards for enforcing privacy should be developed first
... the EU would be interested in ideas
... consumer privacy is enforced by legislation
... commercial privacy
... what stops Amazon from claiming your data

debbie: some things are just another example of abuse that might happen on the web and some are specific to voice assistants
... we should make sure that voice data remains private

jon: consumer should be able to opt out of sharing voice data or try to sell me stuff

debbie: is there a list of privacy issues that need to be handled
... how to deal with what happens between dialog and provider
... some things don't work, like EULA's

jon: how to connect proprietary platform to providers

debbie: how about a proposal that would modify the architecture?

jon: will talk to Jim about coming up with a proposal

debbie: put proposals on the public list, you can also introduce yourself

jon: next time we can discuss DNS and architecture

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)

Present: debbie jon

WARNING: Fewer than 3 people found for Present list!

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: 

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.)