[OpenID-Specs-eKYC-IDA] Issue #1311: Unclear definitions for requests (openid/ekyc-ida)

Daniel Fett issues-reply at bitbucket.org
Tue Jun 28 13:27:00 UTC 2022


New issue 1311: Unclear definitions for requests
https://bitbucket.org/openid/ekyc-ida/issues/1311/unclear-definitions-for-requests

Daniel Fett:

Sometimes we seem to forget that the same text in the spec describes not only responses, but also requests. Different rules apply to both and this is not always reflected properly.

In `assurance_details`, the spec says:

* `txn`: REQUIRED. Identifier referring to the `txn` used in the `check_details`. The OP MUST ensure that `txn` is present in the `check_details` when `evidence_ref` element is used.

This should probably say `assurance_details` instead of `check_details`, and I guess the ‘REQUIRED’ only applies to responses?

---

The spec also says:

* `evidence_ref`: OPTIONAL. JSON array of the evidence being referred to. When present this array MUST have at least one member.

I guess this also only applies to responses?

---

Does it make sense to use `assurance_details` at all in requests?



More information about the Openid-specs-ekyc-ida mailing list