February 2, 2016 UXC Meeting Page

From IDESG Wiki
Revision as of 03:58, 28 June 2018 by Omaerz (talk | contribs) (22 revisions imported: Initial Upload of old pages from IDESG Wiki)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

USER EXPERIENCE COMMITTEE MEETING NOTES


Attendees:

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


Meeting Notes

  • Mary Hodder led the call. Notes taken by Linda Braun
  • Meeting was called to order at 11:59 a.m. EDT
  • Meeting Notes: Minutes from January 14 and January 19, 2016 minutes approved.
  • IPR policy reminder:

http://www.idesg.org/portals/0/documents/governance/IDESG%20IPR-Policy.pdf

  • Recording policy:

https://workspace.idesg.org/kws/groups/idesg_members/download.php/475/Recording_Policy_Conduct_at_IDESG_Meetings[1].pdf

  • Roll call.


Minutes

  • Design Pattern Changes
    • Ellen had a few concerns with the text of the Design Pattern pages so they were not sent out as previously discussed at last week’s meeting. Ellen took the group through the sections where she would like to make some changes and the group discussed. Definitions/glossary – we haven’t done the work yet to normalize the terms. Other groups may have a definition for relying party and we know that we are not in sync. UXC has not yet added a definition for relying party. Suggestion was to add it with the glossary attached. Paul Knight thought that made a lot of sense; definitions associated with UXC use. Paul has added a page on the wiki titled Glossary https://wiki.idesg.org/wiki/index.php?title=Glossary and said he would like to additionally point to the UXC work done.
  • Chat from mary hodder to Everyone:
    • Relying Party: **An entity that relies on an identity representation or claim by a requesting/asserting entity within some request context. An entity that authenticates a claimant and provides some service or value. (Wallace) An entity that requests and/or receives information about the identity of an individual or authentication assertions from another party such as an Identity Provider, Credential Service Provider (CSP), or Trusted Broker. (Sal/Krum)
    • An organization that accepts assertions of identity or attributes. (Garcia)
    • Mary talked about rethinking our terms – what would it mean to IDESG in general if the glossary was consistent across the board. What if they see a different definition for relying party in our group versus another group? Too many variations in the definitions may make it difficult for people.
    • ID ecosystem definition discussed as well. The group decided to include UXC definition of the ID ecosystem in our glossary with a disclaimer since they didn’t want to assume the definition for the whole IDESG.
    • Next section discussed was Mitigation. This definition was probably added 18 months earlier so some is probably inconsistent.
    • Don’t use whitehouse.gov as an untrustworthy website.
    • Action: Ellen will go through the design patterns to align definitions with IDEF glossary. She’ll send it to the UXC and then Mary will forward along to TFTM, Privacy and Management Council stating it is a draft.
    • When to use this Pattern section discussed – write it based on current work.
    • Chat from Paul Knight to Everyone:

https://wiki.idesg.org/wiki/index.php?title=Baseline_Functional_Requirements_v1.0

  • ISO Standards
    • Mary received a copy of the standards adoption form for submission. The form has been posted to the IDESG website. Action:Mary will fill out the form for the standards that UXC is recommending. ISO 29115 has already been submitted by the Security Committee as confirmed by Mary Ellen Condon.
  • Upcoming work
    • Dictionary: Not much progress from a group IDESG perspective. Mary may bring this up at today’s Management Council meeting.
  • SALS review
    • Action:Mary will send out the transcript from her review of the SALS. She asked the UXC to look at the transcript and point them to areas that might not have been clear. Good feedback received on the session and UXC’s work.
  • Ongoing action items
    • 1. Insert “Transparency” into Supplemental Guidance – consider for V2.
    • 2. Create another page for UXC review of other committees’ requirements
    • 3. Waiting on Jamie Clark’s write-up on SME request.
    • 5. Citations needed – language for DPs.
  • Virtual Plenary, February 4, 2016, 1-4pm ET.
  • Next regular meeting, February 9, 2016.
  • Action: See above.


Adjourn

  • Adjourn: Meeting was adjourned at 12:59 p.m. ET