Mike Prorock

options should be actually optional or defined as a required parameter of a call if required

> 2\. No examples of traditional scope based OAuth, such as those supported by Auth0 / Okta. big +1 to getting scopes in there - this is the industry default...

definitely still seeing an issue. note as a workaround, I was able to specify a single column as a concat of the two values being grouped on and get things...

Is this possibly a better topic for the Implementation Guide or [VC-JWT](https://github.com/w3c/vc-jwt)?

> In this model: > > 1. IANA maintains all registries > 2. A registry can contain vocabularies > 3. A vocabulary can be controlled by a WG at IETF...

> The proof value here could be the binary octets of `root`+`signature`+`0x1`+`path`+`nonce`+`0x3`+`path`+`nonce`... since each of those values is a known fixed size (the `0x1` etc bytes indicate which index the...

-0.5 to derive for potential confusion with other operations +1 to "issue" or "create" to create a presentation prior to presenting

> 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 feels like a data integrity issue, not something to be addressed in core data model

If coming back over an API as a response it is helpful to get the JSON serialization compared to compact