Broken reference in schema file

[Mark Haine]

there is a reference to the file “verified_claims_request-12.json“ but that file does not exist

[Torsten Lodderstedt]

What reference are you referring to?

This one works: "$id": "https://openid.net/schemas/verified_claims_request-12.json"

I also just run the tests and the work (on the master branch).

[Takahiko Kawasaki]

$id of verified_claims.json was changed from https://openid.net/schemas/verified_claims-12.json to https://openid.net/schemas/ekyc-ida/12/verified_claims.json by the commit a04bbb8 on Jan 25, 2022. The same commit changed the value of a $ref from verified_claims_request-12.json#/definitions/verified_claims_def to verified_claims_request.json#/definitions/verified_claims_def.

However, openid-connect-4-identity-assurance.md still says as follows. See the value of the target attribute of the reference tag.

<reference anchor="verified_claims.json" target="https://openid.net/schemas/verified_claims-12.json">
  <front>
    <title>JSON Schema for assertions using verified_claims</title>
    <author>
        <organization>OpenID Foundation</organization>
      </author>
   <date year="2020"/>
  </front>
</reference>

The URL of https://openid.net/schemas/verified_claims-12.json is actually accessible. On the other hand, https://openid.net/schemas/ekyc-ida/12/{verified_claims.json|verified_claims_request.json|claims_schema.json} are not accessible. Therefore, if a JSON validator tries to fetch https://openid.net/schemas/ekyc-ida/12/verified_claims_request.json to resolve verified_claims_request.json#/definitions/verified_claims_def (instead of using a pre-cached local copy of verified_claims_request.json), an error will occur.

That is, inconsistencies among JSON files and MD files exist. So, the files must be modified to align with each other.

BTW, the magic number 12 doesn’t look cool. Is there a plan to remove 12 or replace 12 with final (or something else) toward the finalization of the IDA specification?

[Torsten Lodderstedt]

filed PR #120

[Joseph Heenan]

This will effectively be resolved when we change the spec to reference the json schema indirectly via a webpage on openid.net as per https://bitbucket.org/openid/ekyc-ida/issues/1228/determine-best-way-of-managing-identifiers#comment-63953758

Probably we can close this issue & the related PR.

[Mark Haine]

Resolved by PR#130