Shane Doolan

Introduce explicit language to prevent unwarranted friction in the dynamic client registration (DCR) process by data holders

1

# Description Adatree has experienced four prominent data holders on two separate occasions performing ADR domain allowed-listing on dynamic client registration (DCR) attempts. This has resulted in product testing and...

Optionality of critical fields is facilitating data quality issues across Data Holder implementations

7

# Description The below is taken from the Payload Conventions section of the Standards: https://consumerdatastandardsaustralia.github.io/standards/#payload-conventions > Note that optional fields are not considered optionally implementable by a Data Holder. For...

Extend status and outages APIs to secondary data holders

4

# Description Recent issues with AEMO, specifically metering data, has further highlighted the need for ADRs to have at least some visibility into the state of secondary data holder systems...

# Description Some data holders are creating resource identifiers (e.g. account_id, transaction_id, client_id) in the hundreds of characters. We have seen resource IDs of well over a thousand characters and...