Ayra Business Card
The Ayra Business Card is the first of the Ayra Cards family of credentials.
It is intended to mimic how physical business cards are used today.
Business Cards are created (issued) by an Employee or perhaps by an Organization.
A Business Card, issued by an Organization that is registered in an ecosystem will likely have a higher assurance level.
A self-issued Business Card won't have a publicly registered Issuer DID, so will likely be considered lower assurance. However, the boostrapped connection, data, and payloads that it provides may still be very valuable.
The information on a business card varies but there are consistencies (names, contact points).
The bearer of the card presents it - on request or unsolicited - to the receiver.
The receiver decides what to do with the card
A business card is often used to formalize a relationship - to attach fixed details to a person.
In the Ayra Business Card concept we have the following Interactions:
INTERACTIONS: Ayra Business Card
Connect - creates a TrustedRelationship between Bearer (Holder) and Receiver (Verifier)
RequestForCard (optional)
OfferCard (may follow Request for Card or be Unsolicited)
ExchangeCard
ProcessCard - locally process the information from the Card, and optionally:
ProcessPayloads
Subsequently, after a relationship is established, we may have ongoing digital communication and information exchange. That is out-of-scope for the Ayra Card concept at time of writing.
Trust Registry & Type Catalogue Impacts
Ayra Trust Network Trust Registry
REQ: The Issuer of an Ayra Business Card MUST be registered if the Issuer is an Organization. If an individual self-issues, they do not have to be registered.
REQ: The Issuer of an Ayra Business Card MUST be registered in at least one of:
A trust registry run by an ecosystem that is registered in the Ayra Trust Network.
The Ayra Trust Network directly when running in pre-production. NOTE: This is a temporary approach
For use in the First Person context, the issuer MUST be registered to fulfil the needs of a PHC and VRC.
CREDENTIAL: Schema
name
DOB (optional)
Company
Payloads[]
telephone (with type)
email (type)
social links
government ID (attribute -> presentation request)
etc.
Last updated