...
- Alternate Thursdays 6:30am PT
- Screenshare and dial-in: https://global.gotomeeting.com/join/485071053
United States: +1 (224) 501-3316, Access Code: 485-071-053
- See UMA calendar for additional details: http://kantarainitiativekantara.atlassian.orgnet/confluencewiki/display/uma/Calendar
Agenda
- Approve minutes of UMA telecon 2020-03-12, 2020-03-26, 2020-04-02, 2020-04-23, 2020-04-30
- Profiling (and turning it into projects)
- Conformance testing project update
- AOB
...
- Approve minutes of UMA telecon 2020-03-12, 2020-03-26, 2020-04-02, 2020-04-23, 2020-04-30
tbsDeferred.
Profiling (and turning it into projects)
...
It would be valuable for us to produce additional specs that may contain non-normative text as well. While this is broader than profiling, it would expose existing valuable content in a form that would widen its audience. Examples include the resource description profile use cases we discussed last week, the UMA Implementer's Guide material (which is akin to OIDC implementer's guide material though not identical), and even our voluminous UMA use case and case study material on our wiki.
With regards to the consent management work currently going on, there is a GDPR receipt profile that is underway on the consent receipt in the consent and notice project group, Andrew is also working on a framework for ISO. And at OpenConsent Joss is on the Advisory Board and they are tracking MyData. On the SSI front Mark L is working with others on a distributed ledger consent specification, which came out of the Hyperledger effort.
...