Dave Longley

@melvincarvalho, Yeah, that looks right to me too.

Since this topic comes up in a number of places I figured I'd write a bit more here: The general security requirement here is that any application, such as a...

I believe that the core of the issue highlighted above is in a lack of validation on the information that is to be verified. Any protected information or data must...

There's a typo in the controller document v1 context and it should instead use the activitystreams vocab for `alsoKnownAs`. A bug fix will address this particular case. That being said,...

@trwnh, Apologies, I would have written a shorter response if I had more time. > If I'm reading this correctly, are you saying that two context authors are required to...

> In particular, using a protected context in a JSON-LD document significantly constrains the semantics and processing of that document beyond the constraints of generic JSON-LD. I don't think this...

Simpler advice might be to not mix unexpected inline contexts with protected contexts. You don't have to do anything with `@propagate` if you use another non-inline context to define `https://generic-property.example`...

-1, I disagree that this will result in intuitive media type naming, rather I expect it to create more confusion overall in the market. VCs are already a thing, were...

I think we should do all of the following: 1. Remove `@vocab` from the core context. 2. For the "Getting Started" section, create a "development context", which might just be...

I'm happy for us to use text from the CID spec to help resolve issues here. I generally don't think it's a good idea to add statements about the DID...