Re: Selective Disclosure for W3C Data Integrity

Hey everyone,

I wanted to suggest that it might be useful to discuss simplifying the 
functionality of selective disclosure. What I'm wondering is if it's 
possible to simply use three generalized three states, something like this:

  * State 1 - The viewer is everybody, only an abstract
  * State 2 - The viewer provides a DID to authenticate, which could
    allow for more data to be revealed
  * State 3 - The viewer provides some sort of signature or marker or
    credential that signifies as them as more trusted, and can view all
    the data within the DID

Basically, it's one step from all or nothing. Also, what would be more 
useful than proposing complex mechanisms to solve special cases with 
perfect fidelity, is to generate a dozen use cases that span the range 
of potential uses?

For example, for the oft mentioned "drivers license at a club" example 
use case, the following info would be provided:

  * State 1 - everyone  = offers name, has a valid license is TRUE, age
    is over 18/21
  * State 2 - viewer presents a DID = offers name, has a valid license
    is TRUE, age is over 18/21, relay email for mediated contact
  * State 3 - for access by authorized governmental agency, financial
    institution or UNOS (United Network for Organ Sharing) with a DID
    and a special VC = offers name, has a valid license is TRUE,
    birthdate, address, organ donor status

I am reminded of a funny story. I once designed an app for a large bank. 
and the EVP said, /"too complicated, make it more simple"/. Then I made 
it really simple, and he said, /"Still too complicated."/ So I replied, 
/"If I make it any more simple, it's gonna hurt."/ So he says, /"Okay, 
now we're getting somewhere."/

How can we make this so simple that most of the CTOs on this list would 
say it's too simple?

Moses


-- 
*Moses Ma | Managing Partner*
moses.ma@futurelabconsulting.com