Insight for DID spec: proofs, not keys about vc-data-model

[kimdhamilton]

From @ChristopherA on July 14, 2017 22:29

I started this at https://github.com/opencreds/did-spec/issues/4#issuecomment-315449659

I'd like to see a paragraph or so from each of us of top lessons learned, and important links to code, text, or issues contributed to.

[kimdhamilton]

From @msporny on July 17, 2017 0:59

I suggest we start moving a lot of these issues to the DID spec issue repository. @talltree, @dlongley, and I met in DC this past week to go through a revision of the DID spec that Digital Bazaar needs so it can align it w/ our implementation and thinking. I expect this will be an area of focus at the next RWoT.

Specifically, a capabilities based security model for DDOs and what you can do w/ keys associated w/ DIDs.

[kimdhamilton]

From @ChristopherA on July 17, 2017 1:21

Moving these issues is in progress — many of the issues from this hackathon have already been moved there. @kimdhamilton found a useful tool that moves them intact.

[kimdhamilton]

From @talltree on July 17, 2017 5:20

Christopher and Kim,

I'm glad to see these issues move to the DID spec issue repository. Are you
planning for these to start being discussed on the weekly calls, or should
we start planning a dedicated weekly or bi-weekly called on the DID spec.
There is a lot of work to do here and implementations are already underway,
which creates pressure to do it quickly.

Thanks,

=Drummond

On Sun, Jul 16, 2017 at 9:21 PM, Christopher Allen <[email protected]

wrote:

Moving these issues is in progress — many of the issues from this
hackathon have already been moved there. @kimdhamilton
https://github.com/kimdhamilton found a useful tool that moves them
intact.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
WebOfTrustInfo/btcr-hackathon-2017#39 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLkTRPzv5-i1LImiRTdzrqxanrul4Nvks5sOrcXgaJpZM4OX7HS
.

[agropper]

Sorry, I've lost the thread... Is this an open call tomorrow? Where? Adrian On Sat, Jul 22, 2017 at 12:46 PM, Kim (Hamilton) Duffy < [email protected]> wrote:

…

*From @talltree <https://github.com/talltree> on July 18, 2017 5:0* Kim, thanks. Evernym has a company summit this week so my time on the call tomorrow will be limited. I'll try to get on the chat and watch for it on the agenda so I can be sure to join for that segment at least. =Drummond On Mon, Jul 17, 2017 at 3:34 PM, Kim (Hamilton) Duffy < ***@***.***> wrote: I'm open to both. Btw, tomorrow we have about 15 minutes that you (and/or Manu) can spend on DID topics as you see fit. Given the priority of this spec, I imagine we could carve out a large amount of time for the weekly meeting on an ongoing basis. As the year proceeds, we could juggle the weekly meeting focus. It's possible that even this won't be enough, so we could have either dedicated recurring or off-by-one meetings as well. @ChristopherA <https://github.com/christophera> https://github.com/ christophera what do you think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub WebOfTrustInfo/btcr-hackathon-2017#39 (comment) <WebOfTrustInfo/btcr-hackathon-2017#39 (comment)> , or mute the thread https://github.com/notifications/unsubscribe-auth/ADLkTTM7rU_ eap54qVLp3Q9fBp990mVxks5sO7dWgaJpZM4OX7HS . — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIeYY2_DUN1ghU9jooe6EqqnLrGMc3oks5sQidggaJpZM4OgOKA> .

-- Adrian Gropper MD PROTECT YOUR FUTURE - RESTORE Health Privacy! HELP us fight for the right to control personal health data.

[kimdhamilton]

Sorry @agropper -- this was an issue that I ported using an automated tool, and it pulled in some confusing comments. I deleted those. No call tomorrow

[kimdhamilton]

This issue was moved to opencreds/did-spec#15

[kimdhamilton]

In fact, this was supposed to be in DID spec; moved