Re: Materials from 2020-01-09 DID Resolution Spec meeting

Yes. Of course who decides what's a "normal" time zone?
You should probably retaliate by announcing your own calls in YOUR time
zone and date, and confuse every one else! :)

Seriously, if the time for the DID Resolution calls is bad for you (or
anyone else?), we could talk about moving it.

Markus

On 1/14/20 12:00 AM, Kyle Den Hartog wrote:
> Ahh shoot you're right it's the 16th for everyone in normal timezones!
> Just caught my mistake.
> *Kyle Den Hartog*
> Personal Blog <https://kyledenhartog.com>
>
>
> On Tue, Jan 14, 2020 at 11:59 AM Kyle Den Hartog <kdenhar@gmail.com
> <mailto:kdenhar@gmail.com>> wrote:
>
>     I've got on my calendar the next call will be the 17th. Did we
>     move it this week and I didn't catch that? I definitely want to be
>     apart of the matrix parameter discussion and it's impact on the
>     resolver.
>
>     *Kyle Den Hartog*
>
>
>     On Fri, Jan 10, 2020 at 9:15 PM Markus Sabadello
>     <markus@danubetech.com <mailto:markus@danubetech.com>> wrote:
>
>         Recording, logs, and slides for the 2020-01-09 DID Resolution
>         Spec meeting are here:
>         https://github.com/w3c-ccg/meetings/tree/gh-pages/2020-01-09-did-resolution
>
>         The meeting page is here:
>         https://docs.google.com/document/d/1qYBaXQMUoB86Alquu7WBtWOxsS8SMhp1fioYKEGCabE/
>
>         We discussed DID resolver architectures, client-side
>         dereferencing, and different "bindings" or "transports" (e.g.
>         local vs. HTTP vs. DIDComm) for invoking a DID resolver.
>         We ran out of time talking about matrix parameters vs. query
>         parameters, and we will cover this topic next week.
>
>         Thanks to Sumita for scribing!
>
>         *Next call will be on January 16th.*
>
>         Markus
>
>