-
Notifications
You must be signed in to change notification settings - Fork 72
General Nomenclature
This page is about TokenScript concepts, Mobile-wallet-specific stuff goes to Mobile Wallet Nomenclature
If a web service supports multiple tokens, or that it only supports one token, and a user has multiple instances of it, Token Negotiation is the process of finding the match. Token here is a broad word. It also covers the matching of attestations.
Example 1. On 1st Jan 2018, BWS, a website, requires the buyer to be over 18 years old. It request an identity attestation:
(&(|(objectClass=DriverLicence))(objectClass=Passport))(valid>=2018101)(birthDate<20000101))
Meaning one of Driver's licence, NSW Photo Card and Passport will do, as long as it isn't expired on that day, and has a birthDate earlier than 18 years ago.
Another example would be the same BWS website allowing the user to check out with either store credit, cash-equivalent (DAI) or crypto. Such negotiation is more complicated than the identity case because it needs to specify the required balance in multiple ways and might have different transaction rules for each. For example, if you use an American Express credit card, the price is $10 off for $100 minimum spent.