W3C home > Mailing lists > Public > public-digital-verification@w3.org > November 2018

Re: [AGENDA] W3C Credentials CG Call Tue, November 6th, 12 noon EST, 9 AM PST

From: heather vescent <heathervescent@gmail.com>
Date: Tue, 6 Nov 2018 06:53:11 -0800
Message-ID: <CA+C6qMxyU4fKbVPsskYg4HCeh2A9-RzPecAR8jpg6DABrK30Nw@mail.gmail.com>
To: "Jordan, John CITZ:EX" <John.Jordan@gov.bc.ca>
Cc: Sam Chase <samantha@venn.agency>, Joe Andrieu <joe@legreq.com>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>, "W3C Digital Verification CG (Public List)" <public-digital-verification@w3.org>, Christopher Allen <ChristopherA@lifewithalacrity.com>, Kim Hamilton Duffy <kim@learningmachine.com>, Joe Andrieu <joe@joeandrieu.com>
Sam,

Many people outside the identity space, don't understand the problems we've
worked to solve for decades... so you have to put the problem in more than
just a technical context. I like to use Kim Cameron's quote, "The internet
was not built with an identity layer" as an opening/reminder. We tried to
solve identity in a bunch of ways - and we succeeded, but... solutions
create new problems.

Then I build on my foresight research/long term view - that all solutions
create new problems. (Unintended consequences - sometimes good/sometimes
bad). Our past solutions created the situation we are in today. (And for
any aware individuals, you'll realize the solutions we build today will
introduce *new* problems years/decades out.) This is a feature of human
development.

New technology enables new solutions to the same/longstanding problems.
Blockchain is *just one* of a suite of technologies based on standards to
solve these long standing identity, privacy and security problems in a
previously new way.

Then you can go into DIDs, DID Docs, VCs and other technical meat. Drummond
and Kaliya both have great presos with that. You can also pull from the DID
spec. John Jordan's preso is great to introduce VC in the context of a real
live project.

A few other things I'd suggest you think about
- Who is your target audience? What is their background and what are they
trying to achieve? What do you *think* they can achieve using this new tech?
- Since you have 5 minutes, it's better to tease them a bit, with the
concepts, and draw them into the community to learn more. Inspire and
provoke them, and show them the path (that you also took) to coming and
playing with us.
- You're VR/AR native, you bridge the gap between these two communities...
what excites you about this tech, community? Maybe you can lead or close
with that passion.
- And finally, what do you want to achieve in this 5 minutes....

On Mon, Nov 5, 2018 at 10:10 PM Jordan, John CITZ:EX <John.Jordan@gov.bc.ca>
wrote:

> Hi Sam …
>
> Here is a link to our “full” standard set of slides …
> https://drive.google.com/open?id=1hElPRysMq7oAhIGVRgRLYiKpHTfqcbS_
>
> At about Slide 24 is a sequence of slides that are like a flipbook motion
> of a verifiable credential exchange between an issuer and a holder. This is
> followed by a sequence of holder to verifier. The credential is not
> specifically labelled so you can say what it is … identity attributes,
> proof of bank account or whatever … in the end its verifiable data. This is
> what most people will experience in some form or another if this path of
> technological change comes to fruition. This exchange of credentials is a
> mental model people are generally familiar if you draw their attention to
> their current day to day experience using their physical cards and so forth.
>
> To explain the role of blockchain, for a simple high level explanation I
> simple say it is like a large public key ring of “public keys” .. these
> public keys are discoverable because they all have a unique address. This
> was not previously possible these public keys were not discoverable or only
> discoverable when controlled by a single entity like a govt or certificate
> authority. You can say that the crypto needs these public keys to work (you
> need a public and private) and this satisfies most people. We don’t explain
> MAC address resolution, DNS resolution and so forth to help people use a
> web browser so diving into DIDs and DID docs and so forth is likely a
> rabbit hole to stay out of.
>
> If you think there is some use in some of these slides then feel free to
> use them as you see fit.
>
> Best
> John
>
>
> From: Sam Chase <samantha@venn.agency>
> Date: Monday, November 5, 2018 at 9:15 PM
> To: Joe Andrieu <joe@legreq.com>
> Cc: W3C Credentials CG <public-credentials@w3.org>, "
> public-digital-verification@w3.org" <public-digital-verification@w3.org>,
> "ChristopherA@lifewithalacrity.com" <ChristopherA@lifewithalacrity.com>,
> kim <kim@learningmachine.com>, "joe@joeandrieu.com" <joe@joeandrieu.com>
> Subject: Re: [AGENDA] W3C Credentials CG Call Tue, November 6th, 12 noon
> EST, 9 AM PST
> Resent-From: <public-credentials@w3.org>
> Resent-Date: Monday, November 5, 2018 at 9:14 PM
>
> Hi everyone,
>
> I've been invited to speak at the VR, Privacy & Identity Summit taking
> place at Stanford this Thursday. A specific brief was not forthcoming until
> this evening, and I've just learned that in my 5 minutes I need to explain
> to a non-technical audience "that there is a way to store identity in a
> blockchain that several big companies are already committed to working on."
>
> This means what I've prepared about SSI is too technical, and too
> far-ranging conceptually, and I need some 11th hour help! If you can, I'd
> really appreciate any succinct ways the group has of summarizing SSI/DID
> that I could inject into my presentation.
>
> I currently have Drummond's slides from the SSI meetup and have been
> slicing it all down. The argument I was trying to make in my previous
> slides was "Understanding identity in context is key to solving privacy
> issues in virtual spaces." Here are my slides<
> https://docs.google.com/presentation/d/1OeZmP7-1tvhAyTF2gQItle1lKxlxvh3kk56k82KsMS0/edit?usp=sharing>.
> Because there are only 5 minutes I may have to lose some of my privacy
> stuff and focus on getting the attention of the big fish towards SSI as
> it's currently developing and how it can assist a post GDPR landscape and
> evolve and solve identity management problems.
>
>
> If there is time on the call maybe we can have an explain off and see who
> can word SSI the best in under two minutes! 😛 I'll buy beers for best 🍺
>
>
>
> Sam Chase
> -------------------------------------------------------
> Co-Founder & CEO, Venn.Agency
> The Intelligent Edge
> Phone: 323-740-9425  Linkedin
> -------------------------------------------------------
> samantha@venn.agency<mailto:samantha@venn.agency>
>
>
> On Mon, Nov 5, 2018 at 4:13 PM Joe Andrieu <joe@legreq.com<mailto:
> joe@legreq.com>> wrote:
>
> TL;DR: What’s after TPAC/IIW
>
>
> NEXT MEETING:
>
>
> Tuesday, November 6th, 2018
>
> Time: 12pm Boston, 9am Pacific, 17:00 GMT (Double check due to DST)
>
> Text Chat: http://irc.w3.org/?channels=ccg
>
>          irc://irc.w3.org:6665/#ccg<http://irc.w3.org:6665/#ccg>
>
> Voice: See updated instructions:
> https://github.com/w3c-ccg/w3c-ccg.github.io/blob/master/connecting.md
>
>   VoIP: sip:ccg@96.89.14.196<mailto:sip%3Accg@96.89.14.196>
>
>   US phone: tel:+1.540.274.1034;6306
>
>   EU phone: tel:+33.9.74.59.31.06;6306
>
> We prefer people to dial in via SIP when possible.
>
>
> Duration: 60 minutes
>
>
> Minutes from last meeting (to be posted):
>
> https://w3c-ccg.github.io/meetings/2018-10-16/
>
>
> MEETING MODERATOR: Joe Andrieu <joe@joeandrieu.com<mailto:
> joe@joeandrieu.com>>
>
>
>
> PROPOSED AGENDA:
>
>   1.  IP Note: Anyone can participate in these calls. However, if you have
> not agreed to the groups IP policy, we cannot consider substantive
> contributions. (1 minute)
>   2.  Queuing in IRC (2 minute)
>
>      *   We use IRC to queue speakers during the call as well as to take
> minutes
>      *   q+ to add yourself to queue (with optional reminder, e.g., “q+
> DID spec needs better SEO”
>      *   If you’re not on IRC, simply ask to be put on the queue.
>      *   Please be brief so the rest of the queue get a chance to chime
> in. You can always q+ again.
>      *   All attendees should type “present+” to get on the attendee role
>
>   1.  Connections Check & Scribe Selection (3 minutes)
>
> .   Scribe List:
>
>
> https://docs.google.com/document/d/1LkqZ10z7FeV3EgMIQEJ9achEYMzy1d_2S90Q_lQ0y8M/edit?usp=sharing
> )
>
> 4.   Agenda Review (2 minutes)
>
> 5.   Introductions & Reintroductions (4 minutes) (see scribe doc for
> reintroduce column)
>
> 6.   Announcements & Reminders (5 minutes)
> https://w3c-ccg.github.io/announcements/
>
> a.   W3C Workshop on Strong Authentication & Identity -- December
> 10th-11th, Redmond, WA
> https://www.w3.org/Security/strong-authentication-and-identity-workshop/
>
> b.   RWOT VII -- Feb 27-Mar 1 2019, Location TBD
>
> http://weboftrust.info
>
> 7.   Progress on Current Action Items (5 min)
>
>
> https://github.com/w3c-ccg/community/issues?q=is%3Aissue+is%3Aopen+label%3A%22action+item%22
>
> 8.   Status of Work Items (5 min)
>
> https://github.com/w3c-ccg/community/blob/master/work_items.md
>
> 9.   TPAC Report Out (10 min)
>
> 10.  IIW Report Out (10 min)
>
> 11.  DIDs Unique Selling Proposition (10 min)
>
>
> — W3C-CCG Co-Chairs: Christopher Allen, Kim Hamilton Duffy & Joe Andrieu
>
> --
> Joe Andrieu, PMP
>                     joe@legreq.com<mailto:joe@legreq.com>
> LEGENDARY REQUIREMENTS
>     +1(805)705-8651
> Do what matters.
>                   http://legreq.com<http://www.legendaryrequirements.com>
>
>
>

-- 
Heather Vescent <http://www.heathervescent.com/>
President, The Purple Tornado, Inc <https://thepurpletornado.com/>
Author, A Comprehensive Guide to Self Sovereign Identity
<https://ssiscoop.com/>
Author, The Cyber Attack Survival Manual <http://amzn.to/2i2Jz5K>

@heathervescent <https://twitter.com/heathervescent> | Film Futures
<https://vimeo.com/heathervescent> | Medium
<https://medium.com/@heathervescent/> | LinkedIn
<https://www.linkedin.com/in/heathervescent/> | Future of Security Updates
<https://app.convertkit.com/landing_pages/325779/>
Received on Tuesday, 6 November 2018 14:53:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 November 2018 14:53:47 UTC