Bumblefudge
Bumblefudge
- colby pointed out today that the recommended kotlin lib removes "in-path functions" - + is that a problem? will that make holders throw when interacting with an eval-happy verifier?...
Don't let me be the bottleneck! I'll add more if no one else does
Initial Thoughts: - test harness? jest type harness versus docker-based? is what's in there now JUST for JSONSchema? - could pair with, e.g., a VC-JWT and did-method-set profile for people...
`id`s being unique NEED to be unique for OIDC4VP implementations to use scopes/RARs as desired, and it feels like this requirement was implicit (at least judging by the UUID examples)...
On today's call, we discussed that some of the PRs we're merging should be reconsidered when there's an Imp Guide to move some of this text to. See: #325 #334...
A list of JSONPath issues in the past point to the possibility that requiring implementers to support/allow "all of" JSONPath without constraints or guidance is a blocker to adoption: -...
[Spec-up#34](https://github.com/decentralized-identity/spec-up/issues/34) opened to help feature/core more readable with a better feature-boxing.
[Discussed last week at VC-API WG](https://github.com/w3c-ccg/vc-api/issues/174#issuecomment-1089314082)
Might/should this spec have opinions about or include an optional behavior for historical query? As @rhiaro cheekily suggested, you can always query https://web.archive.org/web/20220731132838/https://www.spruceid.com/.well-known/did.json if you want to read [in human-readable,...