Closed cre8 closed 1 month ago
EBSI has different resources defined in the spec
They are using different did methods for natrual persons and legal persons because of GDPR. So they have did:ebsi and did:key
did:ebsi
did:key
so we have two cases: holder: did:key, issuer: did:ebsi holder: did:ebsi, issuer: did:ebsi
According to this https://api-conformance.ebsi.eu/docs/specs/api-guidelines/tir-v4#invite-a-legal-entity only a legal entity can become a trusted issuer so we don't have the case that a natural person is an issuer.
Then we have also to consider different status approaches like:
Closing this for now since we do not know if there different profiles are actively used out there.
EBSI has different resources defined in the spec
They are using different did methods for natrual persons and legal persons because of GDPR. So they have
did:ebsi
anddid:key
so we have two cases: holder: did:key, issuer: did:ebsi holder: did:ebsi, issuer: did:ebsi
According to this https://api-conformance.ebsi.eu/docs/specs/api-guidelines/tir-v4#invite-a-legal-entity only a legal entity can become a trusted issuer so we don't have the case that a natural person is an issuer.
Then we have also to consider different status approaches like: