Payloads - sub-detail

Payloads - sub-detail

EARLY DOCUMENT - NEEDS WORK

ACTION ITEMS:

• Consider DIDComm Attachments for the Payloads structure.

Transparent/Opaque Payloads

The Verifier may not understand what a payload is. That is okay - i.e. it is a feature, not a bug.

Well Known Payloads

Technical Detail

A payload is a simple JSON Object with a known structure (Github TODO).

key-value pair (TECH QUESTION: is it more than that - a tuple?) that provides data for use. The Ayra Card has no opinion about what these payloads are right now.

TODO:

• create PAYLOAD JSON Schema and update examples below.

• link to EARLY JSON Schema and example

• create "known payloads" task in GH repo to capture the general concept.

SIDENOTE: Trust Distribution - helps me carry trust (reputation?)

Examples may be (all are notional now):

• an email address {"emailaddress":"[email protected]"}

• an LEI can be shared in several ways:

  • Attribute (e.g. {"LEI":"TBZG00RXXONEZBA52B44"}) in that the bearer is simply asserting that they have the LEI as provided. It is completely up to the verifier to determine what to do with that information. They can take the information at face value or do their own research, but the data provided doesn't provide any more assurance than "I shared the following data with you."

  • a vLEI, which is a pointer to authenticated data (e.g. {"vLEI":"vlei:TBZG00RXXONEZBA52B44"}) that allows a "vLEI Dance" to follow). GLEIF's vLEI system can be used to automatically test the assertion that the bearer is who they say they are and a signing officer for that entity.

What do Payloads Enable?

• Advertising Capabilities - Verifiers cannot discover what services or functions are available without making specific requests. However, before they can make these requests, they first need to understand what options are even possible. The payload concept solves this by creating a standardized way to broadcast an inventory of available interactions, making them discoverable to all potential users.

• Rapid Discovery - When a verifier is introduced to somebody via an Ayra Card, they receive a list of the available payloads that an entity is providing. From that "get capabilities" check they can decide the next steps in the dance.

EXAMPLES

• SingPass - just an attribute

• OPAQUE: age proof shared as Presentation...

• Data or Pointer