- Daniel Hardman·Last edited by Daniel Hardman on Feb 21, 2022Linked with GitHubContributed by
There is no commentSelect some text and then click Comment, or simply add a comment to this page from below to start a discussion.This file has been moved to a PR agains the DIDComm User Group repo
Read more
DIDComm UG Meeting, 24 Oct 2022
Agenda Karim - report from RWOT Snorre's question about whether we want endpoints Rodolfo - mediator demo
Oct 24, 2022Proposed Resolutions for Issues in DIDComm v2 Spec
368 - move tracing?: Suggest we merge PR #372 and then close the issue. 351 - didcomm:// scheme: got proposal from Timo; added comments to ticket; added PR #373 326 - apu and apv in ECDH-ES: awaiting PR from Baha 321 - Yolan's big review: resolved by PR #377 315 - Crystals-Kyber ex: defer 311 - multiple presentations: defer 298 - P521: PR #374 from Daniel 285 - terminology section: suggest we defer. TOIP has tooling that can generate glossaries, and we can publish one as a separate artifact. Having it in the spec is a nice-to-have that we can skip. 269 - refactor kid/skid: defer or "won't fix" (we have wordsmithed this section to some extent already): PR #375 from Daniel 263 - media type rewords: suggest close as "wont fix"
Apr 23, 2022Peer DIDs with KERI
Peer DIDs were invented before KERI was formally described. Once KERI came along, it became clear that KERI is a more sweeping generalization of the same principles that informed most of the peer DID design. Peer DIDs embody the main principles that KERI advocates, but use just a subset of KERI's features. This means that we can redefine peer DIDs in terms of KERI. The benefits of doing so are: The peer DID spec can be much, much simpler. Peer DIDs get an upgrade path. KERI gets added momentum. Communities can come together. The DID method landscape can consolidate. This document is a first cut at redefining peer DIDs this way.
Mar 2, 2022UnSync Meetings
thanks to Sam Curren for suggesting this Meetings are expensive, especially if we are only interested or needed for a small slice of them. Async interactions are cheaper and more flexible. We love the way we can tolerate remote work and different timezones. However, they lack the focus and rhythm of traditional get-togethers. They're easy to ignore or procrastinate. We have scheduling conflicts. Sometimes, these are big disadvantages. An UnSync Meeting is a hybrid that delivers most of the benefits of both. The name is intended to suggest something that's NOT a traditional synchronous interaction, but that DOES sync people up. :-) How They Work
Feb 22, 2022
HackMD