Editorial updates

The concept of this specification is that the OP can provide all identity data along with metadata about the identity assurance process. It is the responsibility of the RP to assess this data and map it into its own legal context.

Dima Postnikov

1 hour ago

Why “all” identity data?

‌

This specification uses the [!@IDA-verified-claims] document as the definition of the schema for representation of assured digital identity attributes and identity assurance metadata. The basic idea is to use a container element, called `verified_claims`, to provide the RP with a set of Claims along with the respective metadata and verification evidence related to the verification of these Claims. This way, it is explicit which Claims are verified and which are not, reducing the risk of RPs accidentally processing unverified Claims as Verified Claims.

Dima Postnikov

1 hour ago

regular claims may contain the same verified data, it’s just not guaranteed and no verification metadata available for it. Not sure if we can definitively say these are “unverified“?

Comments (3)