recipient_schema_1.5.md

Requirements

• Support multiple types of identity documents, e.g student id, national id, distributed id, passport, etc
• Supports multiple instances of identity documents
• Supports identity documents from various countries
• Parser should be able to determine the highest scope of identity without knowing all the formats
• Identity profiles should be maskable to reduce unnecessary disclosure

Ways of solving this

• Array of recipient identities
• Blockcerts uses recipient + recipientProfile

Thoughts

Identity profiles can be very specific to the relationships they're representing e.g a student id does not mean anything to anyone else outside of the student and the school

It can also have meaning through scope even if the consumer does not specifically recognise the identity e.g a national id is a national id, if you trust that it is a national id then it does not really matter which country it is

e.g myInfo might want to be able to pin a cert to a national id, specifically nric or fin

ID profiles can mutate over a person's lifetime

examples of identity scopes:

personal - name

organisation - student id

nation - nric

global - passport number

universal - ethereum addresses, DIDs