Neura Market
Back to .md Directory
SPEC.md

Product Managers' Community of Practice Running Agenda & Notes

[![hackmd-github-sync-badge](https://hackmd.io/NX9nH53nTk6u03pz6Hd7tA/badge)](https://hackmd.io/NX9nH53nTk6u03pz6Hd7tA)

decentralized-identity
May 2, 2026
0 downloads
0 views
ai
View source

Product Managers' Community of Practice Running Agenda & Notes

hackmd-github-sync-badge

Group Resources: (keep at top)

Parking lot for future/proposed topics

January 13th, 2021

Trinsic?

Dec 30th, 2021

No agenda-- social mixer? cancel meeting?

Dec 15th, 2021

Guest: Evin McMullen (ConsenSys) - Serto Schemas

Nov 17th, 2021

Spitballing agenda items or open-discussion topics

  • Nima K (over email): I also have limited resources, but am interested in starting a few discussions around Personas, User concepts/tools/artifacts, Problems, etc. Let me know if anyone is interested.
  • what to do when there is no agenda?
    • Nate: Even just comparing stacks or giving technical-roadmap updates and where interop or protocols fit on those roadmaps
      • i.e. We're looking for interop partners for Q1/Q2, for example...
    • Analyze together recent demos or launches?
    • Chris (+Phil): CoP, spitballing space, IIW-session-style talk-around or bate-papa
    • Customer and business "questions"
    • Chris: Follow Finance model, with a guest/presi every OTHER meeting and looser chats the in-between meetings
      • Alex (Affinidi) spoke at Identity Week Asia on future IAM, mostly about design challenges
    • Barriers to attending?
      • New meeting time? too often, wrong time zone?
      • Content focus?
      • Justifying time to our respective bosses :D (Would "content calendar" and pre-scheduled speakers help?)

June 30th, 2021

  • New member intros
  • Ecosystem updates
    • DIF at large
      • Wallet security charter defined. WG ist startin now.
    • Events & Conferences
    • Legal/Regulatory
      • Specification of eIDAS Toolbox still early. Definition of where this toolbox will be specified seems unclear.
    • Other
  • Co-chairs for this group
  • Presentation by https://digit.ink *

June 16th, 2021

June 2nd, 2021

  • New member intros
  • Ecosystem updates
    • DIF at large
    • Events & Conferences
    • Legal/Regulatory
    • Other
  • Credential payloads discussion
  • Wrap-up / next session

May 26th, 2021

  • Group discussion about common challenges, proposed discussions for upcoming weeks

What is the credential payload? (Keith can format presentation)

  • Lack of common payload / schemas - a human problem!
  • Ask for and receive credentials in a standardized way
  • Gaps with schema.org — > required vs. optional fields
  • Presentations requests etc.
  • Who is qualified to issue this? Who is the issuer

Usability demos + conversations

  • Demo day - potential ideas
  • E-status wallet
  • Microsoft Authenticator
  • Workday wallet

How do we make wallets accessible to everyone?

  • Edge agents, wallets on phones driving solutions
  • Identity for everybody: may not have a smart phone
  • How authenticate into a service
  • Discussion of web wallets - mention of secure wallet working group, connection to European security standards (German identity requirements, for example)

How do I trust the issuer?

  • Trust frameworks across entities
  • Which types of issuers - Nations and global corporates
  • Different types of credentials with variety of trust needs
  • Liability question: who do I go after if this is not the company that I think it is?

What do interoperable ecosystems look like?

  • DIF interoperability working group
  • Thinking about breaking into pieces
  • Consider connections to privacy conversations - Holder DIDs on BC, GDPR
    • Cloud Act (Europe) -- implications for banking sector but not only( data sharing)
    • Approved cryptographic curves

Business Models for Respective Markets

  • Who pays and who plays?

  • Presentations/ discussions for upcoming sessions

    • June 2nd - Payloads/ schemas
    • June 16th - Wallet demos & accessibility discussion
    • June 30th - Wallets pt. 2 or Trusted Issuers

May 5th, 2021

Topic: Open Badges and Verifiable Credentials: how to build the ecosystem.

Nate Otto, Kerri Lemoie, Simone Ravaioli, Kim Hamilton Duffy

Nate Otto @ottonomy notto@concentricsky.com Kerri Lemoie @kayaelle klemoie@concentricsky.com Simone Ravaioli @psykoreactor simone.ravaioli@digitary.net Kim Hamilton Duffy @kimdhamilton kimhd@mit.edu

Slides: https://docs.google.com/presentation/d/1Cy2hpQ78EqoF00QWPV_RDAH4A5mh9gMyiV2AZJKKlIM/edit?usp=sharing

April 7th, 2021

  • Recording
  • New member intros
  • Ecosystem updates
    • DIF
      • Wallet security group finding co-chairs
      • DIF Steering committee nominations coming up
      • Industry-specific working groups
        • Healthcare (Spherity - dormant temporarily)
        • Banking / Finance (Bloom and Onespan
        • Travel and Hospitality (industry groups - coming soon)
        • Business use cases - non IRP protected
    • IIW
  • Housekeeping: Next session cancelled
  • Demo/ discussion: Workday

March 24th, 2021

March 10th, 2021

February 24th, 2021

February 10th, 2021

  • Recording
  • Ecosystem Updates
  • Round robin intros, perspective/interest in key management
  • Key management discussion

    • (Build a list of questions together)

      • What is the "State of the art" in terms of key management?

        • For end users
        • What are enterprise best practices for key management today? "tactical use"
          • Decades-old solutions already in place - HSM
            • Enterprise intergrations with webKMS and hardware solutions
            • In some ways this is simpler than end user case, lower education delta

      • What are alternatives to single points of failure for key backup and use?

      • What is the relationship to existing patterns...

        • End users: Digital literacy and access
        • Business: Digital transformation

      • What are the foundational design principles for an effective "SSI" solution?

    • E.g.

      • Why are we talking about keys?
      • What options exist today for key management?
      • What are the different business and technical considerations of each approach?
      • ...

Notes: * Uganda, concerns about auditability ... how do I know that this person is in this organization? * Designated signing parties, double signers

  • Discussion of key core principles (Rouven)

    • Key management across various devices
    • Complexity of key management
    • Defining rules for updating keys
    • What are the combination of techniques we can leverage?
    • Levers/ questions:
      • Where is private key material stored?
      • Who is responsible for storing it?
      • What is the "job" of the key and how much do we invest in securing / recovering it as a result?

  • Save last 10 mins for picking our next discussion topic - > Key management for Individuals

January 27th, 2021

  • Member intros and re-intros

  • Ecosystem Updates

      * DID usage for traditional login: [https://docs.magic.link/decentralized-id](https://docs.magic.link/decentralized-id)
  * IDunion applies for funding for the next three years. [www.idunion.org](www.idunion.org)
  * Finema: New projects in Thailand, recommendation of VCs in Thai langauge, use-cases from the public administration.

  • Main topic today: Product Manager Meetings 2021

    • Why are we here? (objectives/reason for gathering)
    • Proposed topics for upcoming meetings
    • Find the topics below as mindmap here: https://mm.tt/1762189321?t=Tm5NG5A0mY
      • Credentials management in wallets
        • Proof request -> use doesn't have suitable credential -> how to continue? Discovering where to get the credential in questions
        • Proof request UI: optional and required attributes; Multiple credenitals as answer -> How to illustrate this proof request UI?
      • How to recognize / discover SSI-enabled services -> use case overview!
      • Consent management from holders and businesses point of view.
      • How to communicate trust (of credentials, issuers) to users; Initial trust;
      • SSI and regulations
      • Multi-language interpretation for schema attributes, applications and concepts.
      • Visualising our ecosystem: Networks, Business agents, end-user agents,
      • Building a roadmap for decentralized Identity, where are we now? and where will we be in 2 or 5 years?
      • Key management and Backup-strategies: end-user and enterprise perspective
    • Facilitators & Presenters

January 13th, 2021 - NEW TIME 5pm Wednesdays (same time as biweekly)

Next session: Goals setting & Planning

  • Determine topics and their importance & urgency.
  • Define aims and goals of the product manager call.
  • More practical presentations - tangable UI & implementation challanges.

Synthetic Summary of 2020 Meetings (Adrian Doerk, 23/12/20):

  • User experience (cryptographic trust)
  • Wallets - what is a wallet - enterprise wallet vs. End user wallet, how will it look like in five years
  • Decentralised identity adoption
  • Consent: (Implied - informed - progressive; sharing policies/decision framework - with risk of sharing XYZ, Framing: actual vs. Relative privacy; responsibilization,)
  • Open source: product strategy, existing repositories (e.g. BC gov issuer kit)
  • Legal frameworks & Government topics: (eIDAS, DHS Wallet challenge, ETDA from Thailand, Korean Data standardization conference, EU digital governance act + My Data response)
  • Personas and their specific needs
  • Onboarding: challenges, What is working well, SSO,
  • Language barriers & Localization/cultural context

December 23th, 2020 - Recording

  • Agenda items:

  • Ecosystem updates:

  • Conferences/workshops

  • User experience (cryptographic trust)

    • Language
    • Personas and their specific needs
    • Onboarding: challenges, What is working well, SSO,
    • Consent: (Implied - informed - progressiv; sharing policies/decision framework - with risk of sharing XYZ, Framing: actual vs. Relative privacy; responsibilization,) \

  • Other topics:

    • Wallets - what is a wallet - enterprise wallet vs. End user wallet, how will it look like in five years
    • adoption & use-cases
    • Open source: product strategy, existing repositories (e.g. BC gov issuer kit)
    • Legal frameworks & Government topics: (eIDAS, DHS Wallet challenge, ETDA from Thailand, Korean Data standardization conference, EU digital governance act + My Data response)

How to move forward and structure the topics?
Idea: Determine importance & urgency of the topics!
Mentimeter session to get feedback -> For Topic, structures etc.

How to move forward and structure the topics?
Idea: Determine importance & urgency of the topics!

December 9th, 2020 - Recording

Agenda Items:

November 11th, 2020 - Recording

Agenda Items:

  • New member intros (5 mins)
  • Ecosystem updates (5 mins)
    • Working groups
      • Starting CCG APAC calls
      • Go to DIF governance call friday if you want to talk about technical steering committee split (8am PST)
    • Conferences/workshops
    • Legal/regulatory
      • EU folks - a draft of the Digital Governance Act leaked and MyData wrote a cool open letter in response. Huge consequences for consent and product design :D
    • Other cool resources & finds *
    • Asks *
  • Scheduling
    • Current meeting schedule:
      • November 25 (Thanksgiving in US, many off) - will cancel
      • December 9th
      • December 23rd
        • A few folks can make it.
      • January 6th
  • Consent Part 2 (Jonny Howle gave last week) - continued discussion
    • Where does “responsibilization” come into play with decentralized tech?
      • Transfer of responsibility onto new participant in system
      • Users are responsible for their privacy/ decisions
      • DIDs/VCs to reduce corporate liability - “blame the user!” :)
      • “Irresponsible responsibilization” when still not great ways for everyday humans to store/recover keys
      • Key issues
        • Privacy of keys (management/security)
        • Disclosure of credentials (consent/ privacy… aware of what sharing)
    • Where are the common security vs. convenience trade-offs in our space?
      • How can contextual integrity help?
        • How can control/consent be managed progressively over time?
          • Temporary sharing, conditional revocation
          • Technical solutions to anchor reference to verifiable presentations, use similar method of checking against revocation list
          • Progresive consent is complemented by selective disclosure of claims/credentials as a feature
        • Building up a consent decision framework over time, makes it easier to use a product over time … preferences over time, set a **policy **(related to data model(s))
          • Design term for product getting easier to use over time
          • Low risk
            • Sharing already public info (a la Open Badges)
          • Mid Risk
            • No statement of purpose provided by requester of info (+ contextual integrity requirements)
          • High risk
            • Sharing my private key
            • Sharing my DNA
            • Sharing with an insecure site / unknown party
          • Progressive consent is not “point and click”
            • May share 5 pillars of contextual integrity
            • Standard, defined data model
            • Small scope of consent decision
            • “Re-negotiation”
    • How can relative understanding of actual privacy be incorporated into consent actions? (relative vs. objective framing)
      • Example: does this grow or shrink my privacy footprint, and what does that mean for me?
    • How can sharing/consenting actions vary across the spectrum depending on who you are sharing with
    • What are user experience paths related to improved consent and control over time? (maybe Finema example?)
  • Related consent work:
  • Topics for upcoming sessions:
    • Accessibility and language for end users of this technology (Lucas & Nader to co-facilitate on December 9th)
      • Words and flows for those not deeply involved in this space
      • Relationship to consent, full understanding of actions
        • Talk about:
          • Data model(s) for consent policies
          • UI <> Data Model relationship
          • Defaults/policies
            • Personal assistant privacy protector
          • Keep it human!
    • Adrian Doerk (couldn’t make it today) share this list of ideas...
        • Credential images
        • Proof requests
      •  - Consent (Who asks, why asks, right to ask)

      •  - Type of information requested and their illustration (e.g. self-attested, verified)

      •  - Informed user consent (when and how does the user requires additional information)
        • Execution of GDPR rights (right to be forgotten, right of information stored etc.)
        • Syntax of attributes (e.g. DD.MM.YYYY)

October 28th, 2020 - Recording

Agenda Items:

  • New member intros (5 mins)
  • Ecosystem updates (5 mins)
  • Consent Presentation (Jonny Howle)
    • (Watch this recording if you missed it! Great presentation)
      • Privacy Paradox
      • Contextual Integrity
      • Hypothetical vs. Actual Scenarios, Relative vs. Objective costs
        • Power of framing actual privacy relative to past experiences or like groups
      • Implied → Informed → Progressive Consent
    • Discussion
      • Trust Agents (algorithmic consent support bot)
        • Deeper question: “How do we allow users to build preferences.”
      • What “head space” am I in when I make privacy decisions?
      • Cognitive dissonance
      • Privacy is misleading… much better to talk about control and consent
        • Selective disclosure, starting from most restrictive settings and reduce restrictions from there. (similar to principle of least privilege :) )
      • Users creating bumpers for themselves to not accidentally do something that is not in their best interest
      • Balancing friction with small actions in the UX for selective disclosure
  • Next session(s)...
    • Questions: (we will jump back in here next session)
      • Where does “responsibilization” come into play with decentralized tech?
      • Where are the common security vs. convenience trade-offs in our space?
        • How can contextual integrity help?
        • How can control/consent be managed progressively over time?
      • How can relative understanding of actual privacy be incorporated into consent actions?
      • How can sharing/consenting actions vary across the spectrum depending on who you are sharing with
      • What are user experience paths related to improved consent and control over time? (maybe Finema example?)
    • Maybe naturally goes next?...
      • Accessibility and language for end users of this technology (Lucas)
        • Words and flows for those not deeply involved in this space
        • Relationship to consent, full understanding of actions

October 14th, 2020 - Recording

Agenda Items:

  • New member intros (5 mins)
  • Ecosystem updates (5 mins)
    • Working groups *
    • Conferences/workshops
    • Legal/regulatory *
    • Other cool resources & funds *
    • Asks *
  • IIW presentations and topics (see above)
  • Next topics for product meetings
    • Privacy and Consent at the UX and UI level (Jonny) ← plan for the next session
      • (Johnny may show sneak peek of beta product, or just mention)
      • Mick Lockwood (sp?) possible presenter to group
      • Possibly two meetings
      • Wayne: Offered to invite CCG as well
    • Wallet Interfaces
      • Different modalities: Mobile, Browser, etc.
      • Well known interactions with each type
      • When should they be used, how interchangeable, how much context given to the user, etc.
    • Accessibility and language for end users of this technology (Lucas)
      • Words and flows for those not deeply involved in this space
      • Relationship to consent, full understanding of actions
    • Key management and recovery (Jonny)
      • What is “best in class” today
    • What does it mean to be “production ready” with emergent technology (Margo)
      • Wayne: Satisfy expectations while mitigating risks
    • To what extent should credentials be visual? (Lucas)
      • Mapping old and new expectations (design patterns)
    • “Progressive Decentralization” for the end user (Jonny, Jacob +1)
      • Mapping out the steps along the way…
        • Example: Managed (maybe child) to self-held keys etc.
      • Responsibilities, protections, of key management
  • Product meeting cadence & facilitation
    • Bi-weekly still good
  • Upcoming possible presentations:
    • Catherine checking on work with Thai government
    • Jonny wallet
    • Margo issuance stepper
  • Design meetup: https://www.meetup.com/TuesdayDesign/

Notes:

  • Starting DIF Africa, launching after IIW (Finema)

Sept 30th, 2020 - Recording

Agenda Items:

  • New member intros (5 mins)
  • Ecosystem updates (5 mins)
    • Working groups *
    • Conferences/workshops
      • IIW is coming again…Oct 20-22nd (info)
    • Legal/regulatory *
    • Other cool resources & funds *
    • Asks (take a penny, leave a penny) *
  • Wallet Competition Q&A (~30 mins)
  • Next topics for product meetings
    • Continue onboard flows or mix in other discussions?

September 16th, 2020 - Recording

Agenda Items:

  • New member intros (5 mins)
  • Ecosystem updates (5 mins)
  • Onboarding discussion continued:
    • What are some of the common characteristics and flows of good onboarding experiences today? (existing design patterns, not SSI-specific)
      • What is working well?
        • Don’t overwhelm with questions/ filling out info at the beginning … instead start taking actions
        • Can just use it without having to learn it! (self-explanatory)
        • SSO elephant in room!
          • Rapidly becoming the norm to “Sign in with (Google/Facebook/etc.)” = “Math of Convenience”
        • When install app, verify secondary info (phone, email, DL, etc.)
          • Treating onboarding as opportunity to create value
        • In-app integrations to other applications “magic”
        • No prior knowledge required
          • Make as simple as possible COME BACK HERE
        • For the privacy nerds :)
          • Email receipt of actions in your account
            • Example: Github sends “freak out if this isn’t you” email
          • 2FA security factors, pros and cons
          • EU law allows to access information from a third party system, but have to put in bank sign in details
      • **Where are the common pain points? **
        • Need to have minimum technical understanding to get through
          • Test: “Can I give it to a person with less technical understanding and will they be successful?”
        • System impersonation
        • Single use codes, how make sure data is synced across devices and secured? Delegate to third party system and accept risks.
        • Only option is to use single sign on instead of disconnected account (+1)
        • Different preferences for security vs. usability
        • SSO provides ease of not having to manage multiple passwordsBalancing security vs. number of clicks
        • Examples of showing security in the UI
          • Visible security twitter check vs. actual verification
    • What is different about onboarding when decentralized technology is involved? (DID/ VC/ etc. -- B2C or B2B)
    • Similarities / differences to existing flows
      • Conceptual difference in approach, much more work up front
      • Onboarding a wallet
      • Onboarding credentials
      • Connecting to an existing identity
    • Example flow 1:
      • Create wallet
      • Create self-issued assertions (VCs)
        • Ability to do things with those credentials right away
      • Jump… bringing in third party trusted credentials
    • Example flow 2 (more b2b + government)
      • Start with basic education about SSI, start with government appreciation
        • Understand what VCs and other countries are implementing
        • (Translation of w3c to Thai language)
      • Provide wallets to businesses first
    • Example flow 3: (b2b working with issuers)
      • Issuer wants to provide credential
      • A business has to quickly get a wallet to receive the credential, and present it to others in the future
    • Example flow 4:
      • Go where users are to
      • start… start using locked-down enterprise grade application
      • Other examples of workflows: Torus and Fortmatic (now Magic)
      • Starting with more managed experiences, then move towards more self-managed
      • Why would these enterprises let your data go?
        • Apple example: we won’t farm your data… but we will capture you inside our systems
        • Privacy regulations (GDPA, CCPA, + Brazil)
          • What is less expensive? The fine, or the compliance implementation?
    • Example flow 5:
      • Melbourne wallets paper, have for a regional target audience
    • Notes:
      • How do you go from someone who doesn’t have a wallet to someone who does?
        • Note: “their is a “competing project” launching next week claiming it has figured out on boarding to give everyone a decentralized ID in their centralized network http://www.didalliance.org”
      • Kaliya proposed idea: “maybe the product managers could collaborate on a “common on-boarding flow” for people going from no wallet to having a wallet with a credential.”
    • New opportunities? (discuss sample flows)
    • New pain points? (relate back to above personas)
    • Questions raised, pros and cons of different approaches
  • Example 6: A wallet for Melbournian - a regional target audience:
    https://www.swinburne.edu.au/media/swinburneeduau/research-institutes/smart-cities/200820-Digital-Wallet-Interview-findings-report.pdf
  • Next meeting… lets go specifically into best practices around the following two workflows:
    • Consumer-oriented flow
      • Create Wallet → Create self-certified credential → Receive third party credential
    • Business-oriented flow
      • Issuer creates credential → Business goes to claim → Creates wallets → Receives Credential
    • (Connect to CCG/ competition efforts)

Other points:

  • How big is the delta between what experts understand as the risks and what end users understand

September 2nd, 2020 - Recording

Call in details:

https://us02web.zoom.us/j/81023290545?pwd=M3VpSWRsMXZYUk4yN1R5NXM3Qm8xQT09

Meeting ID: 810 2329 0545

Passcode: 323392

Product group link: https://dif.groups.io/g/id-productmanagers

Agenda Items:

Differentiation between B2C (Student using the wallet) and B2B (e.g. University Staff - “Registrar” - using the software to offer services, works at the university, has access to student data).

Define:
Name, Description, needs, problems, photo, preferences,

Persona 1:
Name: Luisa
Description: Schwedisch, 14 years old, goes to 8 grade, speaks english,
Needs: Use online services, connect to friends, access school/learning materials
Problems: has too many passwords, doesn’t know who to trust on the internet.
preferences: Dancing, Doing videos, is worried about exposing too much about herself.

**Persona 2: **
Name: Paul
Description: Paul is a truck driver picking up a load of car parts from the Port of Houston. (Yes, I know this is sort of B2B :) )

Needs: He needs to be able to present his Commercial Drivers License to enter the port and pick up the materials. He also needs to be able to scan and digitally sign for custody of the materials.
Problems: Paul needs to be able to do everything on his smart phone. Sometimes he doesn’t have internet/ cellular signal at the Port.
Preferences: Paul doesn’t want to sign up for another darn account. He doesn’t want to download an app unless he uses it regularly and it makes his job easier.

Persona 3:
Name: Jane
Description: 20, landed immigrant to a new country
needs: to receive her new government-issued documents, and keep them up-to-date (e.g.: driver’s license, passport renewal). She also needs to be able to produce those documents when completing transactions: new bank account, rental agreement, etc.
problems: language barriers, lack of time to work through bureaucracy (busy studying and working), limited tech budget (not the latest phone/computer) and knowledge.
preferences:

Persona 4:
Name: Alexandra
Description: Alumni, 25, she does not live anymore in the city where the university is located.
needs: Wants to get her Diploma to get a job
problems: She lives +2h from the University
preferences: Loves chocolate

Persona 5:
Name: Simon
Description: Is an exchange student from Stanford University
Needs: To get his course descriptions so that he can transfer some of the credits
problems: He needs to be physically on ground at Stanford so as to contact each Course Department
preferences: To be emailed over

Persona 6:
Name: Lucy
Description: She is a first-year international student.
Needs: relies on a mobile app to navigate on/off campus
problems: not sure if regular path searching day after day, will release too much personal information (privacy related)
preferences: pre-set a home location.

Persona 7:

Name: 65 year old

Description: Lawyer in Canada

Needs

Preferences: Less familiar with novel technologies

Other personas

-Person with challenges with eyesight

-Limited access to internet-enabled devices and/or internet connection

-Language

-Fearful to use technology due to surveillance, loss of privacy

-Someone who cannot read or write

Mutual:

**Problems: **Determining trust, Physical contact required, financial resources, Internet access, Capabilities (eyesight, literacy etc.) losing control of data/Information,
**Needs: **Access to information, services and documents, proving legitimacy, verification of contacts, user friendly \

Other Important Complexity

  • Risking loss if delete app, understanding consequences
  • Having to pick a ledger/ site to use a credential
  • Kaliya:
    • “If a user ever has to see a DID, we failed”
    • “From a human perspective, is what we are building interoperable?”
      • Car dash metaphor - we can drive different cars!
      • How do we make the car dash look the same? -> e.g. common for symbols
    • What are some of the common characteristics and flows of good onboarding experiences today? (existing design patterns, not SSI-specific)
      • What is working well?
        • Don’t overwhelm with questions/ filling out info at the beginning … instead start taking actions
        • Can just use it without having to learn it! (self-explanatory)
        • SSO elephant in room!
          • Rapidly becoming the norm to “Sign in with (Google/Facebook/etc.)” = “Math of Convenience”
        • When install app, verify secondary info (phone, email, DL, etc.)
          • Treating onboarding as opportunity to create value
        • In-app integrations to other applications “magic”
        • No prior knowledge required
          • Make as simple as possible COME BACK HERE
        • For the privacy nerds :)
          • Email receipt of actions in your account
            • Example: Github sends “freak out if this isn’t you” email
      • **Where are the common pain points? **
        • Need to have minimum technical understanding to get through
          • Test: “Can I give it to a person with less technical understanding and will they be successful?”
    • What is different about onboarding when decentralized technology is involved? (DID/ VC/ etc. -- B2C or B2B)
    • Notes:
      • How do you go from someone who doesn’t have a wallet to someone who does?
        • Note: “their is a “competing project” launching next week claiming it has figured out on boarding to give everyone a decentralized ID in their centralized network http://www.didalliance.org”
    • New opportunities? (discuss sample flows)
    • New pain points? (relate back to above personas)
    • Questions raised, pros and cons of different approaches

August 19th, 2020 - No Recording?

Call in details:

https://us02web.zoom.us/j/81023290545?pwd=M3VpSWRsMXZYUk4yN1R5NXM3Qm8xQT09

Meeting ID: 810 2329 0545

Passcode: 323392

Product group link: https://dif.groups.io/g/id-productmanagers

Agenda Items:

July 22nd 9 am PST/6pm CET - No Recording?

Agenda Items:

|<strong>Group</strong>|Participants|Notes| |---|---|---|---| |1|<ul><li>Margo Johnson</li><li>Jonny Howle</li><li>David Kelts</li></ul>|<ul><li>Simple audit past experiences</li><li>Presentation requests from past</li><li>Bringing physical wallet experience online… do we envision convergence into single experience including payment + identity</li><li>Multiple devices, shared view (multi-modal)</li><li>Take cognitive load off consumers in making more complex consent/permissions decisions (solve for consent fatigue) by creating a more accepted list over time… built a robust set of permissions</li><li>look at physical wallet “I don’t want to have a wallet of stuff” - physical things can go away and become a request</li><li>rapid rewards selective disclosure request via QR codes (Colorado touchless QR codes in Covid times)</li></ul>| |2|<ul><li>Michael Boyd (Trinsic)</li><li>Emiliano Sune (BC Gov)</li><li>Catherine (Finema)</li></ul>|<ul><li>First we need to have cross ledger support?</li><li>It’s hard to figure out which credential belongs to which ledger… ledger mismatches are hard to figure out. Some companies might have an internal ledger for their internal stuff…</li><li>We need to be able to use credentials with any platform. We need just one wallet for each individual. Need to have groupings of credentials within the wallet</li><li>What do enterprise wallets look like? How do they apply in this context?</li></ul>| |<strong>3</strong>|<ul><li>Adrian Doerk (lissi)</li><li>Balazs Nemethi</li><li>Xavier (Validated ID)</li></ul>|<ul><li><strong>5 years from now:</strong></li><li>Mostly smartphones, but also augmented by other devices (glasses, Rings, Watches etc.)</li><li>Decentralized login will be another option to social login -> SSI wallets probably won’t be able to enable “all” use-cases.</li><li>What is our USP against Password managers - how do we communicate that to the end-user? </li></ul>|

  • The Future of Wallets
    • Breakout Questions (15 mins)
      • Gather in groups of 3 to 4 to discuss
    • Group Discussion (10 mins)
      • Share what you learned from the discussion
  • Brainstorm future topics

*Wallet examples from most recent CCG call:

Meeting notes:

June 10th 9 am PST/6pm CET - No Recording?

Agenda Items:

  • Intro new group members, round robin
  • Ecosystem updates
    • DIF working groups, CCG, other new projects, etc.
      • DIF F2F June 16th
        • Slot 1: Balazs DIF F2F what to expect
    • Internet Identity Workshop reflections
      • Full notes here
      • Any session to go back and review notes on?
        • “Is consent broken? If yes, what can we do?” (notes)
        • “Open Source Product Strategy” (notes)
        • “Verifiable Credentials for Global Supply Chains” (notes)
        • Mattr ZKP talk(s)(there were three, not counting the ZKP crash course)
        • COVID talks and what could go wrong?
      • The next IIW is October 27-29
    • Conferences
    • Regulatory or policy changes in our space?
      • Possible legislation emerging in California re: COVID 19 credentials * EFF opposes * Recommended to read responses here
    • Other cool resources
  • Project sharing/ demos (5-10 minute slots, share what you are working on/thinking about, discuss reactions and questions
    • Slot 2: Michael Boyd (Trinsic ID) SSI Cloud Platform
    • Slot 3: Margo Johnson (Transmute) Universal Wallet
    • Slot 4: Juan Caballero (Spherity) What happened to the rubrics? Show-n-tell of Carsten’s variant, possible work item for this group?
      • Juan will condense and share

Notes:

  • Meet every two months … with co-chair we will try monthly!
  • Talk about co-chairing on the mailing list as well
    • Michael Boyd interested
    • Ask if others want to contribute
  • Desire for more user experience conversations
    • Checking on status of Sovrin DID UX efforts

April 15th 2020 9 am PST/6pm CET - No Recording?

Product Group Invitation & Talking Points (Draft)

  • Current groups.io description: “An open discussion group hosted under DIF for Identity professionals to discuss and evolve decentralized Identity product-related work.”
  • Updated description:
    • The DIF Product community group is an open discussion space for anyone interested in connecting the dots between real-world needs and the technology discussed in other DIF groups. Recurring topics include user experience, design patterns, terminology, business value, and cross-company interoperability.
    • Group members can join monthly calls with the following format:
      • **Ecosystem update **(10 min) - Keep tabs on DIF related standards progress, conferences, legal/regulatory, and helpful resources
      • Topic discussion (20min) - Discuss a community driven topic that relates to the shared challenges of building and distributing decentralized identity products.
      • Product demos (20-30 min)- Ranging from polished app demos to early ideation, group members can share a 5 minute demo and get detailed feedback from the group
    • Members can also initiate asynchronous discussions in the groups.io chat to solicit feedback or organize around work items.

Potential Topic Ideas:

  • How do we express <span style="text-decoration:underline;">cryptographic trust i</span>n a user experience?
  • How do we drive decentralized identity adoption with current web infrastructure in a modular approach?
  • How will digital identity wallets look in 5 years for individuals? for organizations?

Related Documents

SPEC.md

GPU Selection Guide for Large Language Models (LLMs)

This guide helps you choose the right GPU for running Large Language Models, whether you're using them for inference, fine-tuning, or training.

aillm
0
11
mshojaei77
SPEC.md

Community AI Agent Skills Discovery Sources

**Research Date:** 2026-03-26

aiagentprompt
0
9
liqiongyu
SPEC.md

ReleaseKit - Technical Requirements Document

ReleaseKit provides **two interfaces** to the same underlying functionality:

aiagentllm
0
8
grokify
SPEC.md

api_llm Specification

Provide direct, transparent HTTP API bindings for major LLM providers without abstraction layers or automatic behaviors.

aillmrag
0
6
iron-cage