W3C home > Mailing lists > Public > public-credentials@w3.org > February 2020

[MINUTES] W3C Credentials CG Call - 2020-02-10 12pm ET

From: W3C CCG Chairs <w3c.ccg@gmail.com>
Date: Mon, 17 Feb 2020 14:48:17 -0800 (PST)
Message-ID: <5e4b1831.1c69fb81.bf702.6bc0@mx.google.com>
Thanks to James Chartrand for scribing this week! The minutes
for this week's Credentials CG telecon are now available:


Full text of the discussion follows for W3C archival purposes.
Audio from the meeting is available as well (link provided below).

Credentials CG Telecon Minutes for 2020-02-10

  1. Introductions and Re-introductions
  2. Survey of emerging standards
  Christopher Allen and Joe Andrieu and Kim Hamilton Duffy
  James Chartrand
  Kim Hamilton Duffy, Dmitri Zagidulin, James Chartrand, Kerri 
  Lemoie, Stuart Sutton, Steven Pattison, Juan Caballero, David 
  Mason, David Chadwick, Chris Winczewski, James Anderson, Durga 
  Prasad, Tzviya Siegman

Dmitri Zagidulin: Kimhd — I have did:web related slides, if time 
Dmitri Zagidulin: 
Kim Hamilton Duffy: 
Kim Hamilton Duffy: https://www.w3.org/accounts/request
Kim Hamilton Duffy: https://www.w3.org/community/credentials/join
Kim Hamilton Duffy: https://w3c-ccg.github.io/meetings/
Juan Caballero: If there's an alias that's hard to spell or 
  remember, you can type 2 or 3 letters and hit tab
Juan Caballero: It'll even put the colon after it for you.  try 
Juan Caballero: I think safari doesn't show that panel
Juan Caballero: By default
Juan Caballero: Names
James Chartrand is scribing.

Topic: Introductions and Re-introductions

David Mason:  Work for Government of Canada
Juan Caballero: David Mason! we met at IIW, glad to cross paths 
David Chadwick:  Introduces himself, member of VC working group
Kim Hamilton Duffy: DavidC is David Chadwick
David Chadwick:  Implementation ready.  back to participating in 
Kerri Lemoie:   Works with OpenBadges, technology researcher

Topic: Survey of emerging standards

Kim Hamilton Duffy:  Will be working on draft of data standards, 
  e.g., openbadges as VC, work with credential engine registry, 
Kim Hamilton Duffy:  Start with emerging standards, today some 
  from credentials community group
Kim Hamilton Duffy: 
Kim Hamilton Duffy:  Also talk about future work from DID group.  
  would like to incorporate european work
Kim Hamilton Duffy:  First of series talking about emerging 
Kim Hamilton Duffy:  Will talk about credential apis.
Kim Hamilton Duffy:   Will help to share notes about related 
Kim Hamilton Duffy:  Greg Nadeau could talk about broward
Want to hear about european work.
Kim Hamilton Duffy:  Start with slide 3
Kim Hamilton Duffy:  DID:  uri from which DID doc can be 
Kim Hamilton Duffy:  Explaining DID identifier and what it looks 
Kim Hamilton Duffy:  DID string can be resolved to verify key 
Kim Hamilton Duffy:  Like issuer id in openbadges, or email for 
Kim Hamilton Duffy:   OpenBadges 2.1 will support DIDs
Kim Hamilton Duffy:  Go to slide 4
Kim Hamilton Duffy:  Did:web uses domain name for verification
Kim Hamilton Duffy: Did:web slides: 
Dimitriz: author of did:web
Dimitriz: motivation for did:method, context, where it fits in, 
Dimitiz: DIDs uniquely identify issuer and the entity being 
  issued to
Kim Hamilton Duffy: Slide 4 is super helpful
Dimitriz: helps disambiguate
Dmitri Zagidulin:  Did can be reused
Dmitri Zagidulin:  Go to slide 5
James Anderson:  During the slides, feel free to be very brief in 
  scribing. The slide link is part of the minutes [scribe assist by 
  Kim Hamilton Duffy]
Dmitri Zagidulin:  Govs don't want to be responsible for managing 
Dmitri Zagidulin:  Explains slide 6
Dmitri Zagidulin:  Identifiers should be reusable across contexts
Dmitri Zagidulin:  Identifiers should provide info about entity
Dmitri Zagidulin:  Skip to slide 16
Dmitri Zagidulin:  Some dids are ephemeral
Dmitri Zagidulin:  Explains different implementations of dids
Dmitri Zagidulin:  Blockchain based: coin based, non-coin based, 
  ledgers internal like hyperledger
Dmitri Zagidulin:  Jump to slide 19
Dmitri Zagidulin:  Key management and building wallets is hard
Dmitri Zagidulin:  Same problems with all dids, how to manage 
  private keys
Dmitri Zagidulin:  Problem with DIDs, how do we know issuer key 
  belongs to issuer
Dmitri Zagidulin:  Go to slide 20
Dmitri Zagidulin:  Trying to solve problem of trust anchors
Dmitri Zagidulin:  So why not reuse infrastructure around domain 
Dmitri Zagidulin:  Slide 21
Dmitri Zagidulin:  Stick did:web in front of url and you get a 
Dmitri Zagidulin:  Did document you get back is same as any other
Dmitri Zagidulin:  Explains how to bind did to domain
Dmitri Zagidulin:  Slide 23 - benefits of did:web
Dmitri Zagidulin:  Did:web provides bridge step until dids 
Dmitri Zagidulin:  How do we protect integrity - blockchain 
  provides some
Dmitri Zagidulin:  How do we make sure document doesn't change
Dmitri Zagidulin: Hashlinks can lock down contents of did 
  document so it can't be changed
Dmitri Zagidulin: Hashlinks also allows specifying backup links
Dmitri Zagidulin:  Certificate authorities can get hijacked - ca 
  transparency can help - fairly robust
Dmitri Zagidulin:  Ledger solutions will look like ca 
Kim Hamilton Duffy: Some certificate transparency references: 
Kim Hamilton Duffy: https://www.certificate-transparency.org/
Dmitri Zagidulin:  Did:web with hashlinks - how to add key, 
  revoke or rotate - breaks hashlink - confident of solution 
  because precedents like keybase
Juan Caballero: Keybase.io
Juan Caballero: Ipfs and ipld
Juan Caballero: KERI
Juan Caballero: You mean?
Kim Hamilton Duffy: KERI yes
Juan Caballero: Or the SCIDs piece?
Juan Caballero: (Two different way of certifying through rotation 
Juan Caballero: (Both by sam smith - hard day to be the scribe!)
Kim Hamilton Duffy: Good point. Here's a link to KERI info: 
Dmitri Zagidulin:  Did working group is working on ability to 
  reuse service enpoints to chain dids
Kim Hamilton Duffy:  Push credential issuer discussion to next 
Chris Winczewski:  Slide 21,22 - is key material separate from 
  domain structure?
James Chartrand is scribing.
Dmitri Zagidulin:  Could reuse public key in ca, but don't have 
Durga Prasad: Durgaprasad814 call me Durga
Durga Prasad: https://docs.opencerts.io/dns_verification.html
Durga Prasad:  Using openattestation - similar to did:web?
Durga Prasad:  Explains how text field of dns record is used
Durga Prasad:  How do we deal with lesser known domains?
Dimitriz:  answer: partner with better known institution
Kerri Lemoie:   What happens if domain changes hands
Juan Caballero: Or if all .org TLD management changes hands :_(
Dimitriz: hashlinks prevent changes to past dids with hashlinks
Dimitriz:  but is a problem in general - cert transparency may 
Tzviya Siegman: https://credweb.org/
Tzviya Siegman:  Mentions credible web - considering using VC.  
  and are talking about domain names changing hands
Tzviya Siegman:  Credweb is addressing question of what is a 
  credible web site
Dmitri Zagidulin: https://www.w3.org/community/credibility/
Kim Hamilton Duffy:  Thanks dmitri
Dmitri Zagidulin: (Thank you tzviya, I definitely think the CCG 
  should collaborate with the Credible Web CG
Received on Monday, 17 February 2020 22:48:31 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:57 UTC