Consumer Data Right Standards - Maintenance

This repository is used to contain discussions and contributions from the community of participants and other interested parties in the Australian Consumer Data Right regime. Please refer to the Main Standards Repository for more information.

See the Consumer Data Standards support portal article Standards Maintenance for details of the maintenance cycle. The details for the next maintenance iteration are below.

Getting Involved

If you would like to participate in the Standards Maintenance fortnightly meetings and contribute to the discussion, send a request via email to [email protected]

You can also sign up to our mailing list to stay up to date on DSB News.

The Agenda, Minutes and Actions for Maintenance Iterations are available on the Meetings page.

Raising Issues

If you would like to propose an enhancement, fix or change to the Data Standards you can raise an issue on this repository.

If you would like to suggest a documentation fix, you can post a comment on the holistic feedback issue created for each Maintenance Iteration. See Getting Involved above.

If you would like to request clarification or ask a question you can search the CDR Support Portal for existing guidance or raise a query if you're unable to find an answer.

Rules of engagement for this repository

We're committed to undertaking conversations relating to the technical standards in the open. Questions or comments that participants might ask us via email or private message are likely to be questions or comments other participants have as well. Our answers will be of interest to everyone. There are likely to be experiences and lessons everybody working in this ecosystem can learn from. Having these conversations transparently helps us reduce duplication, resolve issues faster and keep everyone up to date with the conversation.

We ask that all contributors to the Consumer Data Standards repositories comply with the GitHub Community Forum Code of Conduct and DSB’s Community Guidelines.

In addition, it would be appreciated if the following rules are adhered to when commenting or contributing:

• Please provide a single, considered response to each proposal covering all feedback concerning the proposal.
• For transparency, if you work at or are associated with an organisation with an interest in the standards, please indicate this in your response.
• Please ensure you are aware of and compliant with any social media guidelines or internal processes for response set by your organisation before providing feedback.
• The creation of new issues by contributors is encouraged in this repository.