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 GuideFor example, but demonstrating interoperability of UMA with other standardization efforts (HEART/FAPI..) *needs work

  • To promote interoperability of independent implementations of UMA

...

  • 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 AS-first client interactions

  • Updates to the UMA 2.0 specifications as warranted

...

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

  • Business model-related reportsAn evaluation of UMA with the new

  • A horizontal UMA security profile, considering other profiles including HEART, FAPI, and OAuth 2.1 specificationReview of deployment profiles accepted by the group (did we want to keep this?)
  • 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 Maler, ForgeRock

  • Vice-chair: Maciej Machulak, HSBC

  • Graphics and User Experience Editor: Domenico Catalano, Oracle

  • Implementations Coordinator: Maciej Machulak, HSBC

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

...

  • Kantara Advanced Notice & Consent Receipt

  • OpenID Foundation HEART Work Group

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

  • IETF OAuth Working GroupOthers???

  • IETF GNAP Working Group
  • Decentralized Identity Foundation? Trust over IP Foundation?
  • Me2B Alliance