Re: Decentralized Identity and Product Design/UX Q&A Session, Next Wednesday at 12 PM ET

I came up with some wireframes before SSI was a thing due to my involvement
with the semantic web and linked data lists. I used to do shameless self
promotion there. It is mostly stuff from KMI, DIG, and a few other places
remixed with my understanding at the time. I've been going to the math side
as of late. See you soon as I seem to fall into reclusion.

"I will talk about E.I.S.P.P. (a self directed research project) at
@idworkshop (with an entire playlist for the wire frame "storyboards"
https://bit.ly/2FVI2hm ). I expect the highest interest will be for the
video ch_1_2_VRM https://bit.ly/3j8xcCF . Needs DIDs. Prepare here."

-Brent Shambaugh

GitHub: https://github.com/bshambaugh
Website: http://bshambaugh.org/
LinkedIN: https://www.linkedin.com/in/brent-shambaugh-9b91259
Skype: brent.shambaugh
Twitter: https://twitter.com/Brent_Shambaugh
WebID: http://bshambaugh.org/foaf.rdf#me


On Mon, Sep 28, 2020 at 7:05 PM John, Anil <anil.john@hq.dhs.gov> wrote:

> During the community events portion of the CCG call tomorrow, let me bring
> up what SVIP is planning on doing at the cohort level when it comes to
> Interop and we can go from there ..
>
>
>
> While there are many communities that continue to have **conversations**
> about the nature and aspects of interoperability, the SVIP cohort has, as
> of May of earlier this year,  (
> https://lists.w3.org/Archives/Public/public-credentials/2020Jun/0100.html
> ) demonstrated a great start to multi-platform interoperability across the
> following technical infrastructures …
>
>
>
>    - Factom
>    - Hyperledger Fabric
>    - Hyperledger Indy
>    - Mavennet Neoflow
>    - Transmute for Trade
>    - Universal Issuer/Verifier
>    - Veres One
>
>
>
> … so I am less interested in a conversation about interop and more
> interested in building on top of work that has been done to date:
>
>    1. Increase the rigor and surface area of the aspects under test by in
>    a manner that benefits both SVIP and the community at large by working
>    together to expand the common interop test suite under the W3C CCG umbrella
>    2. Increase the types of tests that are done e.g. verifiable
>    presentation of multiple credentials, ledger independent selective
>    disclosure, and occasionally connected wallets were not in scope during the
>    first  plugfest
>    3. Increase the set of infrastructures under test to ensure true,
>    broad, global interop – step on up and walk the talk! : -)
>
>
>
> Best Regards,
>
>
>
> Anil
>
>
>
>
>
> *From:* Taylor Kendal <taylor@learningeconomy.io>
> *Sent:* Monday, September 28, 2020 6:48 PM
> *To:* John, Anil <anil.john@hq.dhs.gov>
> *Cc:* Phillip Long <pdlong2@asu.edu>; W3C Credentials CG <
> public-credentials@w3.org>; Wayne Chang <wyc@fastmail.fm>; Heather
> Vescent <heathervescent@gmail.com>; Kim Hamilton Duffy <
> kimdhamilton@gmail.com>
> *Subject:* Re: Decentralized Identity and Product Design/UX Q&A Session,
> Next Wednesday at 12 PM ET
>
>
>
> *CAUTION: *This email originated from outside of DHS. DO NOT click links
> or open attachments unless you recognize and/or trust the sender. Contact
> your component SOC with questions or concerns.
>
>
>
> Phil, glad to hear of your interest/support. I imagine we could help to
> facilitate the convos needed between the other groups mentioned. I'm also
> keeping tabs on other interested parties that fall beyond the bounds of
> CCG/SVIP/DIF.
>
>
>
> Anil, what would be an appropriate next step to explore broadening the Q1
> '21 event? At LEF, we would also be open to supporting the evolution of #3
> (expectations of engagement). Open to thoughts from CCG leadership, but if
> it's not overcooking the kitchen, I would be excited to join the 30 Oct.
> cohort meeting to better understand what might be possible among a
> broader network.
>
>
>
> *~ If you want to go fast, go alone. If you want to go far, go together.*
>
>
>
> TK
>
>
>
> On Mon, Sep 28, 2020 at 3:57 PM John, Anil <anil.john@hq.dhs.gov> wrote:
>
> >There's a fairly clear need among aligned groups (e.g. T3 Network
> <https://urldefense.us/v2/url?u=https-3A__urldefense.proofpoint.com_v2_url-3Fu-3Dhttps-2D3A-5F-5Fwww.uschamberfoundation.org-5Ft3-2D2Dinnovation-26d-3DDwMFaQ-26c-3Dl45AxH-2DkUV29SRQusp9vYR0n1GycN4-5F2jInuKy6zbqQ-26r-3DwhPMCrJJokni4GTPDANC6Fj-2D-2DrQ5itrFskRlh4e4wJo-26m-3DSoxUnMD2Ywo7W-5FOwE2XXAKrLrj7LYZ6my6r0VTTvH88-26s-3DuNjLD3xYtTYcPKF63FkguMJMHx4VudnD-5FqENM-5FL6OlM-26e-3D&d=DwMGaQ&c=2plI3hXH8ww3j2g8pV19QHIf4SmK_I-Eol_p9P0CttE&r=FUgYmx6LTIaPqn7QR6TBfzml-fqCTpab-djgqlCFtgU&m=MqDfRACBX-9xLHckpsDSZ_cIJqObUb3Q1otYCRKabv4&s=iiqatsCY4vTO40so1jmEMMpbrUz0LefI9TE0gkBzzNY&e=>
> , OET
> <https://urldefense.us/v2/url?u=https-3A__urldefense.proofpoint.com_v2_url-3Fu-3Dhttps-2D3A-5F-5Ftech.ed.gov-5F-26d-3DDwMFaQ-26c-3Dl45AxH-2DkUV29SRQusp9vYR0n1GycN4-5F2jInuKy6zbqQ-26r-3DwhPMCrJJokni4GTPDANC6Fj-2D-2DrQ5itrFskRlh4e4wJo-26m-3DSoxUnMD2Ywo7W-5FOwE2XXAKrLrj7LYZ6my6r0VTTvH88-26s-3DweWKqPNyp1CmIvcvvgByhHV-2DAjvKkFu7LGx8daIOwEY-26e-3D&d=DwMGaQ&c=2plI3hXH8ww3j2g8pV19QHIf4SmK_I-Eol_p9P0CttE&r=FUgYmx6LTIaPqn7QR6TBfzml-fqCTpab-djgqlCFtgU&m=MqDfRACBX-9xLHckpsDSZ_cIJqObUb3Q1otYCRKabv4&s=H1KHMlEXUqjRhwm2KElr236r7fjZU7bsq9thyP_nQPw&e=>,
> etc.) for open, public infrastructure that enables rapid/iterative
> prototyping and informed resource allocation.
>
>
>
> So, let us have that conversation!
>
>
>
> I also have a concrete suggestion on where/how best to have that
> conversation …
>
>
>
> As a bit of background, SVIP just finished the contract awards for all the
> existing companies who moved forward to the next phase of their work w/in
> SVIP and the new companies who are joining our portfolio to work a variety
> of problem sets all leveraging the DID/VC ecosystem  (Not going to share
> those names right now, as you will know them soon enough, as we like to
> highlight each company individually via a press release).
>
>
>
> We will be meeting with them as a Group in late October, to discuss a
> variety of items including:
>
>    1. To begin the scenario planning needed for the SVIP hosted follow-on
>    multi-vendor, multi-platform interoperability plug-fest for around the 1Q
>    of 2021 (Building on top of what was accomplished earlier this year)
>    2. Expectations regarding contributions to the community
>    infrastructure needed to move the work forward on the interop front
>    (Contribution/Expansion of the Test Suites, Credential Samples, APIs,
>    Common data elements and more)
>    3. Expectations of engagement in the global technical community (W3C,
>    DIF etc.) to work on the interoperability of VC/DID/SSI Systems
>
>
>
> On a separate, but parallel track, I’ve also had multiple one-on-one
> conversations with both companies and organizations globally about how best
> we can work together on technical interop.
>
>
>
> An idea that I’ve socialized with many of them, to which there has been
> active and positive feedback, has been to host an event to bring together
> the companies in the SVIP portfolio with other companies/organizations with
> products to discuss and plan an “expanded” interop plug-fest with
> additional scenarios. i.e. We would use that day to define additional
> interop scenarios that will be part of a future “expanded” plug-fest in the
> future.
>
>
>
> SVIP plans to host and set the table for this discussion for the folks
> I’ve spoken with already on Friday, October 30, 2020 as part of our Cohort
> meeting i.e. with the folks w/ real products who are ready and willing to
> test their products via a real multi-party, multi-vendor interoperability
> using both test suites and n X n testing.
>
>
>
> However, if there is broader interest, I am happy to work with the W3C CCG
> leadership (if they see value to something like this) and others to see how
> best we could expand the scope of the discussions to include more
> implementers.
>
>
>
> Happy to discuss, if appropriate, on a future CCG call as well.
>
>
>
> Best Regards,
>
>
>
> Anil
>
>
>
> Anil John
>
> Technical Director, Silicon Valley Innovation Program
>
> Science and Technology Directorate
>
> US Department of Homeland Security
>
> Washington, DC, USA
>
>
>
> Email Response Time – 24 Hours
>
>
>
> [image: https://www.dhs.gov/science-and-technology/svip]
>
>
>
>
>
>