Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission)
ids 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) so seems like a no-brainer to make this a normative requirement in v3. didn't in 442 so as to remain within errata scope.
ids 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) so seems like a no-brainer to make this a normative requirement in v3. didn't in 442 so as to remain within errata scope.