Versions Compared

Key

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

 (1) WG NAME: (and any acronym or abbreviation of the name): The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate.

...

  • 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

  • To promote interoperability of independent implementations of UMA

...

The following technical specifications may be developed in 2021:

  • One or more extension and/or profile specifications

    • A Relationship and Policy Management Extension, defining the “out of scope” interfaces of the UMA Federated Authorization specification

    • A Resource Definitions Extension, enabling resource discovery through through AS-first client interactions

  • Updates to the UMA 2.0 specifications as warranted

(5) OTHER DRAFT RECOMMENDATIONS: Other Draft Recommendations and projected completion dates for submission for All Member Ballot.

The following reports are anticipated to be developed in 2021 (final titles and document boundaries to be determined):

  • 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
  • Analysis of UMA deployments or deployment profiles

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

At the time of this charter’s revision, following are the members of the leadership team:

  • Chair: Eve MalerAlec Laws, ForgeRockIDENTOS

  • Vice-chair: Maciej MachulakSteve Venema, HSBCForgerock

  • Graphics and User Experience Editor: Domenico Catalano, Oracle

  • Implementations Coordinator: Maciej Machulak, HSBC

(7) AUDIENCE: Anticipated audience or users of the work.

...

This Work Group has a number of dependencies on, and shared goals with, the output of other efforts. The Kantara groups and external efforts with which this Work Group intends to liaise informally include (but are not limited limited to):

  • 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 Alliance