- From: Snorre Lothar von Gohren Edwin <snorre@diwala.io>
- Date: Thu, 22 Jul 2021 08:47:34 +0200
- To: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>
- Cc: "public-credentials@w3.org" <public-credentials@w3.org>, David Chadwick <d.w.chadwick@verifiablecredentials.info>
- Message-ID: <CAE8zwO3Lj_ENo+ZAeT_dD9riQS3WUEe6STBQQwJSmsoFUM6z2Q@mail.gmail.com>
Just replying directly to the part of the email I wanted to reply to. But linking in alot of the other answers. I also dont feel a notary is able to work as an expert witness in verifying that something is correct. I too have felt that notaries just make sure that the current document they see, is the document that is delivered, and nothing else. But why are noone talking about the machine itself being able to issue a VC? It is produced with a DID, under anchoring of a trusted company. The machine can issue VCs. Which are verified back to the company who is a trusted company? This way alice presents its DID to the machine, gets the reading, and is able to receive the DID? Which can be directly passed onto the doctor? On Fri, Jul 16, 2021 at 8:37 PM Michael Herman (Trusted Digital Web) < mwherman@parallelspace.net> wrote: > In scenario A, Alice wants to report an actual blood pressure reading to > Dr. Bob's Clinic. ...something like "120/80" ... really the pair of > individual numbers. Alice wants the reading to be signed by her and > notarized by SOVRONA as trusted notary ...that is, SOVRONA acts as a > witness to Alice's signature of her own self-issued blood pressure home > reading. > > Wrt to your question about scenario B, the Sovronia driver's license > should appear to be signed by the Province of Sovronia whose signature is > witnessed by SOVRONA, the mutually trusted credential notary. > > A and B are actually different examples of the same more generic > credential notarization scenario/problem. > > Get Outlook for Android <https://aka.ms/AAb9ysg> > > ------------------------------ > *From:* David Chadwick <d.w.chadwick@verifiablecredentials.info> > *Sent:* Friday, July 16, 2021 11:05:33 AM > *To:* public-credentials@w3.org <public-credentials@w3.org> > *Subject:* Re: Verifiable Credential Notarization and Third-Party Notary > Services Providers: User Scenarios > > > Hi Michael > > can you please explain these scenarios a bit more for me. > > A. The user creates any blood pressure reading they like, true or false, > and gets a notary to certify this? Is this what you intended? > > B. What is the difference between a Sovronia DL signed with Sovronia's key > or with Soveronia's notariser's key if the verifier knows and trusts the > right public key? > > Kind regards > > David > On 15/07/2021 20:45, Michael Herman (Trusted Digital Web) wrote: > > I believe there are a large number of scenarios where individual Persons > as well as Organizations are going to want to (self) issue Verifiable > Credentials using the credential notarization services of a third-party > notary service provider. > > Here’s 2 user scenarios as examples: > > > > - User Scenario A: (steps A1…A8) > Alice self-issues a blood pressure home reading (BPHR) credential to > Dr. Bob’s Clinic using SOVRONA’s credential notarization services. SOVRONA > is a third-party notary services provider/network. > > - User Scenario B: (steps B1…B8) > The Province of Sovronia issues a Sovronia Driver’s License to Alice > using SOVRONA’s credential notarization services. SOVRONA is a third-party > notary services provider/network. > > > > I have a some drill-down questions (e.g. protocol detail questions) but > first, let me ask what general questions/comments have about the validity > of the 2 user scenarios depicted below. > > > > > > Best regards, > > Michael Herman > > Far Left Self-Sovereignist > > > > Self-Sovereign Blockchain Architect > > Trusted Digital Web > > Hyperonomy Digital Identity Lab > > Parallelspace Corporation > > > > > > -- *Snorre Lothar von Gohren Edwin* Co-Founder & CTO, Diwala +47 411 611 94 www.diwala.io
Attachments
- image/jpeg attachment: image003.jpg
- image/jpeg attachment: image006.jpg
Received on Thursday, 22 July 2021 06:49:00 UTC