Dave Longley

JFYI, we're using this library to generate JWEs with our edv work: https://github.com/digitalbazaar/minimal-cipher

It's clear to me that suffixes make sense to express sub-syntaxes (of increasing specificity) of a super syntax. I tend to offer this sub-class analogy for how I think of...

Also -- the stream portion of the spec is quite out of date/out of sync with implementations. Please take a look at https://github.com/digitalbazaar/edv-client when comparing your implementation. We expect to...

@jernst, > The value of this spec diminishes very rapidly the more restrictions are being made on which URLs are supported. Is that true? How do you know / why...

> > I think we should specify the did v1 @context as the default context. Other contexts possible, but not required. > > I'm sorta fine with that if most...

> +1. I think the proposal so far is to add KERI-like mechanisms (a chain of backwards hashlinks, plus outside observers). We need to be careful here. This is insufficient...

@kdenhartog, > Isn't that true of any DID Method that's based on a blockchain as well? For example by producing a longer chain on BTC that invalidates a BTCR update...

@dmitrizagidulin, > would that not be addressed by outside observers? Yes, but we can't just hand wave. We need to build into did:web's protocol how that observing is done/how observers...

The DID spec expects key rotation (without revocation) to be a private / confidential activity and the DID document expresses public key material (via verification methods). To rotate keys, stop...

> As this is an HTTP-based API, I would expect this to work for any arbitrary clients and not be restricted to browsers (and service workers) only. So far, implementations...