Verifiable Credentials: Mapping to a Generic Policy Terminology

Note: This post is the sole opinion and perspective of the author.

Over the past several months I have been diligently attempting to map the dynamically evolving world of trust frameworks and verifiable credentials into a straightforward and hopefully timeless terminology that can be used for policymaking. The storyboard diagram above is what I’ve come up with so far.

  • Counterparty — for every consequential relationship or transaction there are at a minimum of two parties involved. Regardless of whether the interaction is collaborative, competitive, zero positive sum, they can be considered as counterparties to one another.
  • Claim — is the something that is the matter of concern between the counterparties — it can be financial, tangible, intangible; something in the present, or a promise of something in the future.
  • Offer — a counterparty offers something that usually relates to a Claim.
  • Commit — a counterparty can commit to its Offer.
  • Present — a counterparty can present an Offer (or a Claim).
  • Accept — on the other side, the other counterparty accepts an Offer.
  • Issue — An Offer, once formed, can be issued in whatever form — usually a document or credential that is signed by the counterparty.
  • Hold — An offer can be held. How it is held depends on its embodiment (e.g.., digital, paper, verbal, etc.)
  • Verify — An offer, or more specifically its embodiment can be verified for its origin and integrity.

All of the above is made possible by:

  • Business Trust — how the counterparties decide to trust one another. This is the non-technical aspect of agreements, rules, treaties, legislation, etc.

And underpinned by:

  • Technical Trust: how the counterparties prove to another that their trust has not been compromised. This the technical aspect that includes, cryptographic protocols, data formats, etc.

Why is this useful? When writing policy, you need a succinct model which is clear enough for subsequent interpretation. To do this, you need conceptual buckets to drop things into. Yes, this model is likely to change, but it’s my best and latest crack at it to synthesize the complex world of digital credentials with an abstraction that might be useful to help us align existing solutions while adopting exciting new capabilities.

As always, I am open for comment and constructive feedback. You know where to find me.




Based in Ottawa. Does identity stuff. My tweets are my opinion but they can be yours too!

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

1.6 Million WordPress Sites Have Been Attacked

Linux Honeypot Deployed

{UPDATE} City Pickups Driver Delivery Hack Free Resources Generator

Identity & Access Management: Beyond usernames and passwords

How To Block / Blacklist a Number on vivo NEX 3 5G

How To Block / Blacklist a Number on vivo NEX 3 5G

Using OpenID Connect with Decentralized Identifiers

MetaFabric Community Reward Airdrop — What You Should Know About It?

Ransomware Protection: How would NetApp provide protection after ransomware being detected

Ransomware Protection

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tim Bouma

Tim Bouma

Based in Ottawa. Does identity stuff. My tweets are my opinion but they can be yours too!

More from Medium

One-way Transfer of Rights

What Sports Can Teach Medicine about Central Fatigue and Recovery

Why Youths Must Engage With Government: Taaooma’s Tale

Hinsdale students isolated over mask refusal, infuriating parents

Photo byWGN TV Chicago