Orie Steele

cc @selfissued @csuwildcat this is also related to "DID / JOSE interoperability"... and the very poor usability of the "VC-JWT" format... since VC-JWT does not have "documentLoader" but also does...

@peacekeeper yes, its related... ` "sameAs": "did:example:123?version=0",` This would imply you can merge the graphs, which if you rotated compromised keys out... that would be bad... also semantically, did subject...

@dhh1128 consider, a JWS or a linked data proof using `kid` or verificationMethod `did:example:12#key-0` ### Valid ``` { "id": "did:example:123", "verificationMethod": [ { "id": "#key-0", "type": "JsonWebKey2020", "controller": "did:example:123", "publicKeyJwk":...

@TallTed thanks for commenting on this! I think I agree with your proposal. consider the verificationMethod in a proof, with value: `did:example:123?version=53#key-0` This must be de-referencable to: ``` { "id":...

You can secure JSON-LD claim sets (the W3C VC Data Model 2.0) with securing formats that are not based on RDF canonicalization, see: - https://w3c.github.io/vc-jose-cose/#with-sd-jwt I've tested different selective disclosure...

You may request changes of this file: https://github.com/w3c/did-spec-registries/blob/main/tooling/did-method-registry-entry.yml#L27 Its type is string, to account for Organization Names, or multiple folks. I don't like the idea of changing the range of...

@iherman can you rephrase this as a directive for me or @msporny ? happy to take a stab at a PR, if I can figure out what to do.

@iherman I have tried to address some of your concerns here. https://github.com/w3c/did-spec-registries/pull/115/files

I fully support a normative requirement on JSON-LD only core data model, and to eliminate the JSON and abstract data models from the next version of the technical recommendation. We've...

It could be that given the security security issues with complex contexts, the base context should be reduced to only the terms and key words necessary for the "claims data...