Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • To maintain the UMA specifications and consider developing enhancements to and any future versions of them

    • For example, to consider whether extension and profile proposals contributed to the Work Group should result in Work Group deliverables

  • To develop Business Model reports and/or specifications that support the enablement of a license-based model for controlling access rights to personal digital assets, in liaison with other relevant bodies

    • For example, working with Kantara and external consent-oriented work groups. Such as the Kantara Advanced Notice & Consent Receipt work group

  • To promote UMA adoption

    • For example, by offering support for profiling and extension creation and creating educational materials

    • For example, by maintaining the UMA Implementer's Guide

    • For example, by producing UMA feature and value documents
  • To promote interoperability of independent implementations of UMA

...

  • Business model-related reports

  • A horizontal UMA security profile, considering other profiles including HEART, FAPI, and OAuth 2.1
  • Analysis of new authorization profiles, such as GNAP in comparison to UMA
  • Analysis of UMA deployments or deployment profiles

  • UMA Marketing/promotion document or Business Value Reports

(6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants.

...

  • Kantara Advanced Notice & Consent Receipt

  • OpenID Foundation HEART Work Group

  • OpenID Foundation FAPI Work Group
  • Financial Data Exchange
  • Open Identity Exchange

  • IETF OAuth Working Group

  • IETF GNAP Working Group
  • Decentralized Identity Foundation
  • Trust over IP Foundation
  • Me2B Alliancepp2pi
  • Shift (formerly PP2PI)

(11) CONTRIBUTIONS (optional): A list of contributions that the proposers anticipate will be made to the WG.

...