Dave Longley

We may have decided that using `@protected` with `@vocab` was a non-starter years back and failed to document it. Notably users of `@vocab` and users of `@protected` tend to run...

If you have consumers from the JSON world (vs. only the RDF world), it is much better to use idiomatic JSON and avoid CURIEs, etc.

@cwebber, > I understand the push for a URI type that represents something that can't change, that makes sense to me. But... a new URN subscheme? That just encodes the...

TL;DR - Remove lots of optionality to make ZCAPs easier to implement and interoperate.

> Or is desired not to reintroduce loading additional resources (even hash-identified ones that could be provided alongside the payload)? This. We want to keep it really simple -- everything...

We want to be able to distinguish `invoker` from `delegator`, so if we change the name, we should change both, perhaps to: `authorizedInvoker` and `authorizedDelegator`. I'm also not sure how...

We are likely going to change `invoker` to `authorizedInvoker` and `delegator` to `authorizedDelegator` to avoid confusion. The reason for moving forward with the change is that specifying who delegated a...

We're going to experiment a bit more with our implementation per the last comment -- it may turn out to be more confusing in some ways to use `authorizedDelegator` than...

Just sharing another link with some comparisons between zcaps and macaroons: https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/draft-documents/lds-ocap/lds-ocap.md#macaroons

> The context is an Array not a string? Hmm, it's a JSON-LD-ism that an array with a single value and a string with that same value are technically considered...