- From: Alan Karp <alanhkarp@gmail.com>
- Date: Tue, 31 Dec 2024 08:17:25 -0800
- To: Merul Dhiman <me@merul.org>
- Cc: "Michael Herman (Trusted Digital Web)" <mwherman@parallelspace.net>, Kishore Rajasekharuni <kishore.rajasekharuni@jukshio.com>, "public-credentials (public-credentials@w3.org)" <public-credentials@w3.org>
- Message-ID: <CANpA1Z1smPRyFuLnRxPgU3F5bik=SjPwEF_UUMLyfXP8g66_sw@mail.gmail.com>
On Tue, Dec 31, 2024 at 3:41 AM Merul Dhiman <me@merul.org> wrote: > This is a very interesting question which often gets asked to me. We have > always thought of DIDs and VCs as low level architecture details, and that > is where they shall belong its just a technology which allows us to issue > and digitally verify data. > > I think we never even need to tell the user about the technology which > lies underneath, as it is, for them totally not relevant. However we tell > them what we solve for them and address their pain points and empathise > with them. > That's the right approach, a lesson we learned from one of our projects. We built a file sharing application that used opaque identifiers (not DIDs) under the covers. The user only saw petnames except in one place. Wouldn't you know it? Almost every user complained about it. -------------- Alan Karp On Tue, Dec 31, 2024 at 3:41 AM Merul Dhiman <me@merul.org> wrote: > This is a very interesting question which often gets asked to me. We have > always thought of DIDs and VCs as low level architecture details, and that > is where they shall belong its just a technology which allows us to issue > and digitally verify data. > > I think we never even need to tell the user about the technology which > lies underneath, as it is, for them totally not relevant. However we tell > them what we solve for them and address their pain points and empathise > with them. > > > Best Wishes, > > Merul Dhiman > CTO > AuvoDigital OÜ > > https://auvo.io > > > > > On Sun, Dec 29, 2024 at 15:57 Michael Herman (Trusted Digital Web) < > mwherman@parallelspace.net> wrote: > >> An interesting related question for a UX expert is: If DIDs are low-level >> technology artifacts, what are the best/most appropriate UX metaphors to >> surface in real apps? >> >> Get Outlook for Android <https://aka.ms/AAb9ysg> >> ------------------------------ >> *From:* Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net> >> *Sent:* Sunday, December 29, 2024 8:13:29 AM >> *To:* Kishore Rajasekharuni <kishore.rajasekharuni@jukshio.com> >> >> *Cc:* public-credentials (public-credentials@w3.org) < >> public-credentials@w3.org> >> *Subject:* Re: [External] Pop Quiz: Where do DIDs belong from an >> Enterprise Architecture perspective? >> >> Thank you for your analysis Kishore.When I say "DIDs", I'm being very >> literal: >> A DID = decentralized identifier = "did:wxyz:1234" character string. >> >> The answer to the question gets into the subtleties of decentralized >> identifiers (e.g. did:wxyz:1234).. They are not intended to be >> human-friendly or comprehensible (like a checksum or a GUID); hence in my >> mind, they are low-level technical/infrastructure concepts/elements - at >> the very most, the lowest levels of your application architecture >> (admitting this is actually going too far IMO). >> >> It would be interesting to revisit how a platform like .NET abstracts an >> identifier up the chain into higher level application objects like an >> Identity or Principal (.NET terminology). >> >> Michael Herman >> CEO and First Principles Thinker >> Web 7.0 Foundation / Trusted Digital Web (TDW) >> >> Get Outlook for Android <https://aka.ms/AAb9ysg> >> ------------------------------ >> *From:* Kishore Rajasekharuni <kishore.rajasekharuni@jukshio.com> >> *Sent:* Friday, December 27, 2024 8:34:31 AM >> *To:* Michael Herman (Trusted Digital Web) <mwherman@parallelspace.net> >> *Cc:* public-credentials (public-credentials@w3.org) < >> public-credentials@w3.org> >> *Subject:* Re: [External] Pop Quiz: Where do DIDs belong from an >> Enterprise Architecture perspective? >> >> My understanding - DiD can be part of Party Management in the Business >> architecture layer. At the application architecture layer, it can be the >> Digital Identity module exposing APIs for Onboarding, Identity Proofing and >> Fraud Detection. The underlying Digital Identity Apps / Portals can be part >> of the Technology / Infrastructure architecture. >> >> regards >> Kishore >> >> On 27 Dec 2024, at 12:07 PM, Michael Herman (Trusted Digital Web) < >> mwherman@parallelspace.net> wrote: >> >> Are DIDs part of the: >> - Business architecture/layer/domain >> - Application architecture/layer/domain >> - Technology/Infrastructure architecture/layer/domain? >> >> Get Outlook for Android >> <https://www.google.com/url?q=https://aka.ms/AAb9ysg&source=gmail-imap&ust=1735886469000000&usg=AOvVaw3dZOsMm5uX8vKzgHgmZY6E> >> >> >>
Received on Tuesday, 31 December 2024 16:17:43 UTC