Child pages
  • UMA telecon 2020-12-03
Skip to end of metadata
Go to start of metadata

UMA telecon 2020-12-03

Date and Time

Agenda

  • Approve minutes of UMA telecon 2020-11-19
  • New Pensions Dashboard profile
    • Expecting a new profile contribution and proposal imminently
    • Closely related to our Pensions Dashboard use case from business-legal work (see slides 22-23)
  • AOB

Minutes

This meeting was recorded.

Roll call

Quorum was reached.

Approve minutes

MOTION: Approved.

New Pensions Dashboard profile

What's a "pension" in this context? In the US, think 401k. In the UK, it's an investment account to save for retirement.

Background

The problem that emerged about five years ago was that people were collecting a lot of "pension pots" as they moved jobs. Getting an overview and managing assets got unwieldy, and assets went unclaimed and accounts went dormant. Consumers started to want more control. The concept of a pensions dashboard emerged. It needed to exemplify choice, control, and inclusion. The government is backing this. It needs to be secure and private by design.

Origo's role as a not-for-profit has been significant. The profile they have worked on is valuable as an open standard to underlie a quite ambitious government effort. 15M UK consumers and the whole UK population can benefit.

While Ken and Ian aren't OAuth or UMA experts, Mike Pegman was involved and he is.

They believe this is a fantastic UMA use case. There are 44,000 schemes in the market and there are about 300 RS's serving them, which would each need to integrate to a dashboard. This could be a market maker for UMA. Origo is interested to become an RS supplier at some point, but it is not a pension provider itself. Interoperability between pension providers and the consent/authorization service would be important.

They believe there will be a proving phase and then wider industry rollout. There's a three-year timeline for everything. The Money and Pensions Service (MaPS) is an entity that's similar to the Open Banking Implementation Entity.

Timing and urgency

The date driver, it's believed, is that early-phase procurement documents will be published where they'd like to reference the profile documents from a neutral venue. The contribution made to the WG today could satisfy this imminent requirement.

Profiling work

The usual process would be to develop an editor's draft as we develop the profile's elements, then one or more voted WG drafts, then go through Kantara approval(s). It's interesting to consider broadening the profiling work already done to apply to other sectors or jurisdictions. The profile also seems to connect to existing profiling work, such as resource registration patterns. Finally, the discovery service and two-step pattern seems to apply in a number of other circumstances.

Testing conformance

Would conformity testing against such a profile be necessary? It could be. That might be a role for Kantara.

Show, not tell

Can we demonstrate this vs. just talk about it? That's most effective. Demonstrating connectivity will be key. A prototype does exist already. Nancy points out how FHIR has moved forward with sandboxes and so on.

Next steps

MOTION: Nancy moves: Accept the Origo profile contributions for consideration. APPROVED by acclamation.

AI: Eve:

  • Put the contribution documents in PDF form on the wiki.
  • Add them to the third-party profiles page if they're not already there.

AI: Origo folks:

  • Decide if we need to add something new to the Implementations page.
  • Let the MaPS program know about the results of today.
  • Advertise joining Kantara and the UMA WG as appropriate.

Attendees

As of October 26, 2020, quorum is 5 of 9.  (Michael, Karim, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve)

  1. Michael
  2. Domenico
  3. Peter
  4. Sal
  5. Alec
  6. Eve

Non-voting participants:

  1. Kenneth May - Origo - chief architect - not-for-profit for financial services - now also joining Kantara
  2. Ian Muir - Origo - strategy and architecture consultant - Pensions Dashboard
  3. Nancy
  4. Colin
  5. Tim
  6. Lisa
  7. Lars
  8. Kate
  9. Anik


  • No labels