Re: DIDComm work

Hey everyone,

I've seen that a few people signed up to attend these meetings, but there
was a bit of a snag that I haven't been able to resolve. If this work is
done outside of an organization it runs afoul of IPR protections and could
allow someone to patent this work. On top of this, I haven't found a
suitable place or time (most I could get were 5/12 respondents at one time)
to host this call. However, I want this work to continue and plan to show
up where ever needed if discussion is happening on the subject. If others
who responded would like to keep track of the different places where the
work is occurring as well, please reach out and I can provide more details.

Thanks,
*Kyle Den Hartog*
Personal Blog <https://kyledenhartog.com>


On Wed, May 15, 2019 at 4:13 PM Kyle Den Hartog <kdenhar@gmail.com> wrote:

> Hey various CCG members,
>
> At IIW I noticed that there was quite a bit of interest in discussing how
> a DIDComm protocol might work. I've been discussing this work in many
> places to help evangelize and find early consensus on what we would like to
> see in a common messaging protocol that's based on DID work that has been
> baking in various communities. Given that this work would likely need to
> cross cutting through (hopefully) the entire DID space, I wanted to reach
> out to various people in many different orgs to get discussion going on
> this subject.
>
> My hope is that we can start with a call to discuss things and move
> forward in an agile way as needed. Right now I'm looking to find a good
> time for this call and have setup a scheduler here:
>
> http://whenisgood.net/DIDComms/
>
> If you would like to join the calls please provide times that would work
> best for you weekly.
>
> Also, if you aren't able to make the calls, but would like to follow the
> discussion will be taking notes in a google doc here.
>
>
> https://docs.google.com/document/d/1k5USBTdQP9RbcImbnC61cjyxRI3FtbTq8IRHlK-_7cw/edit#
>
> Thanks!
> *Kyle Den Hartog*
>

Received on Tuesday, 4 June 2019 08:14:40 UTC