Orie Steele
Orie Steele
Thanks for reporting this... this is bad. The reason is for this bug is confusion over trying to match the behavior of JWS.verify in `jose`, which returns the verified payload...
See https://w3c-ccg.github.io/vp-request-spec/#did-authentication We need to relate DID Auth to Evidence, by example... Then encourage or discourage its use in that manner. Can't be ignored though, because we see guidance emerging...
https://github.com/w3c/vc-data-model/pull/1181
Suggest closing, this has been addressed in both securing specs.
I'd suggest we use "create" to refer to the assembling... And "issue" to refer to the securing.
related issue: https://github.com/w3c/vc-data-model/issues/990#issuecomment-1342312804
Can someone propose a complete JSON-LD example, and where it would be inserted into the specification?
Seems blocked by the working group having not accepted a solution that supports selective disclosure. I suggest closing until such an item exits, or leaving open until this item can...
I don't like any of those options : ( It feels like this should be put on hold until we make progress on crypto suites. I suspect a concrete example...
I still wonder about this... When is a URL enough? When is an `@id` like `sha256:0123ABC` enough? Why is multibase a requirement? Do VCs need a RDF type to explain...