Re: Bikeshed: Wallet or Credential Repository (was: Re: Verifiable Credential Notarization Protocol (VCNP))

Here's a fairly complex example of the TDW model for a UBL Invoice FDO...
I’ve finished modeling the UBL Invoice-2 example (including all of the required CBCs and CACs) using something called the Trinity Specification Language that then feeds into an automatic C# code generator.

Here’s a link to the TSL specification for a UBL Invoice: https<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRACommon/UBL21Credentials.tsl#L312>://github.com/mwherman2000/<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRACommon/UBL21Credentials.tsl#L312>TrustedDigitalWeb<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRACommon/UBL21Credentials.tsl#L312>/blob/master/TDW.Servers/TDW.TRACommon/UBL21Credentials.tsl#L312<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRACommon/UBL21Credentials.tsl#L312>

Here’s an example of the UBL-TSL-C# binding that is auto generated (I think its pretty cool 😊): https<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRATester/Program.cs#L42>://github.com/mwherman2000/<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRATester/Program.cs#L42>TrustedDigitalWeb<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRATester/Program.cs#L42>/blob/master/TDW.Servers/TDW.TRATester/Program.cs#<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRATester/Program.cs#L42>L42<https://github.com/mwherman2000/TrustedDigitalWeb/blob/master/TDW.Servers/TDW.TRATester/Program.cs#L42>

Every TDW Credential has a distinct, easily understabdable set of 4 layers:
- List of Claims
- Content (List of Claims plus a UDID and a Context)
- Envelope (Content plus an Envelope Label)
- Cell (Envelope plus an Envelope Seal)

I'm trying to remove as much mystery as possible for developers.

Michael

P.s. For interop, it's a relatively straightforward mapping from a TDW Credential to a VC (including DID Docs, which, for example, are a specialized form of a Credential).


Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net>
Sent: Saturday, July 17, 2021 12:00:50 PM
To: public-credentials@w3.org <public-credentials@w3.org>; Manu Sporny <msporny@digitalbazaar.com>
Subject: Re: Bikeshed: Wallet or Credential Repository (was: Re: Verifiable Credential Notarization Protocol (VCNP))

Yes. I prefer the following 3 terms for backing stores for a Trusted Digital Agent:
- Smart Wallet (workflow-enabled credential ledgers (subledgers))
- Key Ring
- Master Secrets Store
Reference: https://hyperonomy.com/2021/06/28/trusted-digital-web-8-layer-architecture-reference-model-tdw-arm/


Wrt Linked Data Structures, I prefer concepts that people (developers especially) can readily identify with e.g Credential Ledgers, Hashes, Signed Hashes, Notarization, a simple and easy-to-understand and code against Credential data model, Credential modeling and Agent modeling language, auto code generation ...assuming your goals are to be the first fully decentralized object platform with more than a million app developers.

Bold? ...a bit. The above is how the Trusted Digital Web platform works (almost). 🙂

Michael



Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Manu Sporny <msporny@digitalbazaar.com>
Sent: Saturday, July 17, 2021 9:04:22 AM
To: public-credentials@w3.org <public-credentials@w3.org>
Subject: Bikeshed: Wallet or Credential Repository (was: Re: Verifiable Credential Notarization Protocol (VCNP))

On 7/17/21 10:52 AM, Michael Herman (Trusted Digital Web) wrote:
> Alice’s Personal Wallet

Thanks for the diagram, Michael, it's very helpful.

I'm not seeing much in there that hasn't been contemplated by the VC data
model with Linked Data Signatures (which support chained signatures -- which
you're demonstrating one use of here). That said, having the use case
diagrammed is quite useful.

My suggestion is to get away from the "Wallet" language when talking about the
general ecosystem in the same way that we got away from blockchain/DLT when
talking about the Verifiable Data Registry.

Where entities store their Verifiable Credentials isn't always going to be a
wallet. I suggest the more general term should be:

Verifiable Credential Repository

OR just

Credential Repository

I'm sure folks may want to bike shed that term. I suggest that "Wallet" or
"Holder" is already confusing people (the most recent perma-thread is a great
example) and we should get our terminology straight before launching into the
next standardization cycle.

-- manu

--
Manu Sporny - https://www.linkedin.com/in/manusporny/

Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
https://www.digitalbazaar.com/