August 25, 2015 UXC Meeting Page

From IDESG Wiki
Revision as of 16:53, 17 September 2015 by Mary Hodder (talk | contribs) (→‎USER EXPERIENCE COMMITTEE MEETING NOTES - draft: removed draft as meeting approved 09082015)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

USER EXPERIENCE COMMITTEE MEETING NOTES


Attendees:

  • Mary Hodder
  • Suzanne Lightman
  • Ellen Nadeau
  • Noreen Whysel
  • Jim Zok
  • Paul Knight
  • Linda Braun, Global Inventures


Meeting Notes

  • Mary Hodder led the call. Notes taken by Linda Braun
  • Meeting was called to order at 12:12 p.m. EDT


Agenda Review


Minutes

  • Redress discussion and supplemental
    • UXC was asked to look at Privacy supplemental for redress. Mary reviewed the text with the team.
    • From Privacy:
    • Entities shall provide users the source of any verification or information that leads to an eligibility, authentication, or authorization decision. If users seek redress, they must be provided with a mechanism to dispute or change erroneous information at the source of the information.
    • If credentialing is denied or a credential is revoked from a user, justification for that decision should be presented along with the source of any information that contributed to that decision.
    • Note: Intermediaries may not have a direct relationship with users who move through their systems, but should facilitate endpoints’ ability to conform to this requirement. See Interop 8.
    • From UXC:
    • 7) HL Requirement, INTEROP-9: Entities MUST provide effective mechanisms for redress of complaints or problems arising from identity transactions or the failure of the entity to comply with the IDESG Baseline Requirements. These mechanisms MUST be easy for USERS to find and access.
    • All IDESG members should provide a mechanism for redress and include the ability to correct or otherwise address any issues an USERS may have.
    • Pathways for redress should be clear and available to the USER throughout the process.
    • Redress mechanism should be considered must-see-this-first information in a first encounter and then provided as appropriate to the USER in a consistent manner thereafter.
    • Consult USABLE-4 supplemental guidance for additional consideration that applies to Redress.
    • Consult the UXC Resources page located here for examples: https://www.idecosystem.org/wiki/UXC_resources
    • No changes proposed for the redress wording.
  • Portability best practices text reviewed from Privacy Committee work. Discussion followed that it might make sense to keep portability as a best practice for now. UXC does not think standardization in this topic is mature enough at this time for portability to be an IDESG requirement.
  • Mary went through the UXC requirements to change the MUST wording in the supplemental guidance and changed where appropriate to SHOULD.


Wrap up and actions for next week

  • Mary is traveling next week. If anything urge comes up regarding portability meeting Noreen will chair call. Mary will let Linda know the status as to whether or not she should cancel the call for September 1.
  • Next meeting, September 1 or 8, 2015.


Adjourn

  • Meeting was adjourned at 12:59 p.m. EDT


Quick Links: Security Committee | Functional Model | Security Committee Meeting Notes | Security Committee Content