Check and update JSON schemas
Following changes to the drafts over recent months the JSON schema files should be reviewed and updated if necessary.
Comments (5)
-
reporter -
reporter Need to look at what should be removed from the JSON Schema based on the split out of components from the IDA spec. Things to check are the changes introduced relating to:
It feels like the current JSON Schema should be modified to focus on the OpenIDConnect 4 IDA spec and it’s use of the OpenID IDA Verified Claims schema definition. It might also be possible to split out the definition of the
verified_claims
element so that it can bve used independantly. -
At Dec 7 call we talked a bit about whether a JSON Schema can cover the language tag (ex:
name#ja
) as defined in the Section 5.2 of the Core spec.
https://openid.net/specs/openid-connect-core-1_0.html#ClaimsLanguagesAndScripts -
JSON Schema reconciliation & improvement
renametxn
tocheck_id
remove any attachments related elements
consider removing distributed claims elements
checkutility_bill
anddocument
do comparison of openid4IDA from 19th Aug 2022 with both current OIDC4IDA and OID4verified_claims docs to spot schema affecting change- produce change report
- attend to chages
- write list of features that we wish to test
- Create set of negative tests for JSON schema
and…
Split the JSON schema as follows
current
- claims
- OIDC4IDA response (referring to claims)
- OIDC4IDA request
becomes
- claims
- OID4IDA (referring to claims)
- OIDC4IDA respose (referring to OID4IDA)
- OIDC4IDA request (referring to claims)
-
reporter Write some fail cases
write json examples that demonstrate that the JSON schema files do actually fail when normative errors exist in the examples tested
Split the JSON schema as follows
claims
OIDC4IDA response (referring to claims)
OIDC4IDA requestbecomes
claims
OID4IDA (referring to claims)
OIDC4IDA respose (referring to OID4IDA)
OIDC4IDA request (referring to claims) - Log in to comment
being addressed by PR #188