Page Comparison

• Propose alternating so that 1 call / month in USA timezones, 1 call / month in APAC - Agreed
• Phil: Keep momentum to achieve deliverables
• Nicky / Drummond: Use TF model
• Already a Yoma Ecosystem TF
• Bentley: What are the key research questions - HX input.  Feedback - having a focus to group. 

Here is the script for the video:

Include examples?  Could include Yoma

Jan:

• 1) Notice presented: Privacy & consent notices include the consequences / potential risks
• 2) Following consent, creation of consent receipts (aligned w/ISO standard)
• 3) revoking consent

Kalin:  Love this as a project idea and picks up on various strands,  e.g. using Yoma Persona

What is the HX aspect of consent process?

Bentley:  Another area of focus? Jan to give demo and presentation at next session on 18th.

Phil: message on script seems to be targeting other ToIP groups, but should it go more widely into the ecosystem.?

Kalin: Certainly want to open up more widely than just ToIP - script to be updated.

Are there core deliverables that the HXWG should create separately from other x-pollination projects like Yoma

e.g. Role of HX in ToIP Stack, in building trust and contributing to the ToIP mission?

• Phil: Two things are going on: Identity and ToIP industry design and user research are understaffed and underfunded. And nearly all the best funded work is happening behind corporate closed doors. So this group might encourage sharing of research, cooperation on research initiatives, and host open resources for designers, developers, and product people, that foster HX innovation, speed up design work, and de-risk product design. Like...
  • collections of UI screenshots/vids of wallets, dashboards, and other HCI (pinterest? twitter?). to help identify the state of the market (and evolution). 
  • WG host wiki of HX patterns (abstractions of what works) and antipatterns
  • WG host list of normative HX capabilities, interactions that should X.  
• Phil: Research to describe human constraints in trust and identity that must propagate back to those who architect ToIP. For example, human cognitive overload limits the volume of meaningful consents people can deal with. 
• Nicky: examples of other work, best practice; Phil - use pinterest? ; +1 from Kalin
• Jan: Wallets are key - design elements - easier and more consistent user experience
• Bentley: Align w/ Hyperledger Aries BiFold https://github.com/hyperledger/aries-mobile-agent-react-native
  for open-source components - part of design patterns 
• Andrew: To be Continued!....
• Kalin: Iterate on it, let's continue to develop.