Torsten Lodderstedt

I think constraints related to picking a credential and what is disclosed from this credential are different aspects. I therefore feel those aspects should be represented in different elements of...

I'm not sure what direction you want to go. Do you suggest to remove the "limit_disclosure" element underneath "constraints" and use "frame" instead?

I took a look at the frame definition. I don't think this is a suitable solution as it does not remove the ambiguity of the current construct and it is...

Here is my proposal: Introduce a new contain element `selective_disclosure` and use it to list the fields that shall be selectively disclosed and use `constraints` for selecting the credentials, only....

We should consider to make support for refresh tokens a MUST on the client side. This would allow ASs to issue RTs if needed (either always or based on policy)....

Have you be able to run this construct with any other parser than AJV? We use https://python-jsonschema.readthedocs.io/en/stable/ and I also tried to use the schema with https://www.jsonschemavalidator.net/. It did not...

Is there any appetite to fix this problem?

Externally hosted schemas work if the "consuming" schema refers to a certain element in that schema, like "http://example.org/schema#someelement" (see https://json-schema.org/understanding-json-schema/structuring.html#ref). The way you refer to the external schema is different....

What would be the semantics of such a reference? The "ref" elements is part of the definition of a schema element, i.e. it defines that element using kind of an...

And how does AJV interpret that construct? What is the allowed value range for the `filter` element?