-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Uplift for Data Recipient Multi-Sector support #425
Comments
Please refer to #424 to address multi-sector support for Data Holders Introduction:Data recipients utilise CDR Register APIs to obtain information about data holders in the ecosystem. With the introduction of the energy sector to the CDR, there is a need to redefine the APIs to simplify alignment to multi-sector support. Along with these changes, there is an opportunity to address outstanding work to align CDR Register APIs to the conventions defined in the Consumer Data Standards. These changes are to allow for the APIs to be more usable and align their usage across multiple sectors. Proposed Changes:Please refer to issue #424 for details on the proposed changes This issue will be used to collate feedback specific to data recipient impact. |
This change has been documented via issue #424 and was incorporated into release v1.15.0. Refer to Decision 212 for further details. |
Description
Data recipients may need to determine how registrations with data holder brands supporting single or multiple sectors are to occur. The introduction of energy raises the question on whether SSA requirements need to be updated to cater for multiple sectors.
Area Affected
Register APIs will need be structured to expose single or sector agnostic discovery and status
Dynamic client registration specification will need to define how the registration process will support single and multi-sector scenarios
Change Proposed
Provide requirements to data recipients on how registration against data holder brands will cater to both single and multi-sector scenarios
The text was updated successfully, but these errors were encountered: