[Openid-specs-ab] Issue #1439: PE Schema Validation Problems (openid/connect)

[David Chadwick]

New issue 1439: PE Schema Validation Problems
https://bitbucket.org/openid/connect/issues/1439/pe-schema-validation-problems

David Chadwick:

Currently some non-trivial examples of presentation definitions from the DIF PE specification are causing OIDC schema validation to fail. One example is if a VC contains a set of values, and the PD tries to choose one of the set by using “oneOf” or “anyOf”. This issue has been raised in the DIF PE group \(see [https://github.com/decentralized-identity/presentation-exchange/issues/280](https://github.com/decentralized-identity/presentation-exchange/issues/280) and [https://github.com/decentralized-identity/presentation-exchange/issues/303](https://github.com/decentralized-identity/presentation-exchange/issues/303) \)

DIF say they are using the JSON schema defined in [https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-02](https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-02) which allows more complex constructs such “oneOf” and “anyOf”.

The current workaround for OIDC has been to use simpler examples in the OIDC specifications.

This issue is a placeholder to ensure that any problems with schema validation are resolved before the final specification is published