Skip to content

Commit

Permalink
- Added v1.0.0 archive files
Browse files Browse the repository at this point in the history
  • Loading branch information
@JamesMBligh
JamesMBligh committed Dec 8, 2019
1 parent 2352819 commit 8959534
Show file tree
Hide file tree
Showing 363 changed files with 422,282 additions and 1 deletion.
9 changes: 9 additions & 0 deletions docs/archive/standards-1.0.0/LICENCE
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
<p>Unless otherwise stated, all specifications and downloadable reference applications are subject to this MIT Open Licence.</p>
<h1 id='mit-licence'>MIT Licence</h1>
<p>Copyright 2018 Data61</p>

<p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the &quot;Software&quot;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>

<p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>

<p>THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
30 changes: 30 additions & 0 deletions docs/archive/standards-1.0.0/README
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
<h1 id='consumer-data-right-standards'>Consumer Data Right Standards</h1>
<p>This repository contains the binding API Standards and Information Security profile created in response to the <a href="https://treasury.gov.au/consumer-data-right" title="Treasury's Consumer Data Right webpage">Consumer Data Right</a> legislation and the subsequent regulatory rules. The purpose of the Consumer Data Right regime is to give Australians greater control over their data and is intended to apply sector by sector across the whole Australian economy.</p>

<p>These standards are maintained by the Data Standards Body (DSB) with final decisions on standards being taken by the Data Standards Chair. The Data Standards Body is currently <a href="https://www.data61.csiro.au/en/Who-we-are/Our-programs/Consumer-Data-Standards" title="CSIRO's Data61 Consumer Data Standard webpage">CSIRO&#39;s Data61</a>. The work of standards development is conducted in close consultation with the <a href="https://www.accc.gov.au/focus-areas/consumer-data-right-cdr-0" title="ACCC's CDR webpage">Australian Competition and Consumer Commission (ACCC)</a> as lead regulator of the Consumer Data Right, supported by the <a href="https://www.oaic.gov.au/consumer-data-right/about-the-consumer-data-right/" title="OAIC CDR webpage">Office of the Australian Information Commissioner (OAIC)</a>.</p>
<h2 id='additional-information'>Additional Information</h2>
<ul>
<li><a href="https://consumerdatastandards.org.au/">Data Standards Body Web Site</a> - Contains additional informaiton on the CDR and the DSB as well as notifications of the latest developments in the regime.</li>
<li><a href="https://consumerdatastandardsaustralia.github.io/standards/">Formal Standards Site</a> - The published contents of the standards in this repository. This is the formal documentation of the binding standards.</li>
<li><a href="https://cdr-register.github.io/register/#introduction">CDR Register Design Documentation</a> - The documentation for the CDR Register which is a core piece of infrastructure that facilitates the operation of the CDR regime.</li>
</ul>
<h2 id='contributing-to-the-standards'>Contributing To The Standards</h2>
<p>Consultation on the standards as they evolve is performed transparently with any interested contributor invited to participate in accordance with the rules of engagement described below.</p>

<p>There are a number ofways to contribute to these standards:</p>

<ul>
<li><p><strong><a href="https://github.com/ConsumerDataStandardsAustralia/standards/issues">Issues posted on this repository</a></strong> - The issues posted on this repository are used for formal consultation of specific decision proposals that are to be considered by the Data Standards Chair. These decisions constitute significant changes to the standards and are raised as required. These issues constitute an audit trail of the decisions taken by the Data Standards Chair. As this is the case it is requested that contributors do not raise new issues and instead contribute comments to the issues created by the DSB.</p></li>
<li><p><strong><a href="https://github.com/ConsumerDataStandardsAustralia/standards-maintenance">The standards maintenance repository</a></strong> - This repository is used to manage minor changes to established aspects of the standards. Contributors are encouraged to raise new issues in this repository that will then be prioritised for resolution in a series of multi-week iterations. Outcomes of these iterations will then be submitted to the Data Standards Chair for approval on this repository as a decision. The issues on the maintenance repository are also a good way to raise questions and request clarification of the standards.</p></li>
<li><p><strong><a href="mailto:[email protected]">Via Email</a></strong> - If you would like to submit a confidential question or item of feedback, or if GitHub feels unfamiliar, the DSB welcome email correspondence related to the standards and the standards development process.</p></li>
</ul>
<h2 id='rules-of-engagement-for-this-repository'>Rules of engagement for this repository</h2>
<p>We&#39;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.</p>

<p>We ask that all contributors to the Consumer Data Standards repositories comply with the <a href="https://help.github.com/articles/github-community-forum-code-of-conduct/">GitHub Community Forum Code of Conduct</a>.</p>

<p>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.
* Please refrain from initiating new issues or pull requests in this repository due to the need for formal approval of all aspects of the standards</p>
82 changes: 82 additions & 0 deletions docs/archive/standards-1.0.0/docs/archive/infosec-0.1/CHANGELOG
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
<h1 id='changelog'>Changelog</h1>
<p>All notable changes to this project will be documented in this file.</p>

<p>The format is based on <a href="https://keepachangelog.com/en/1.0.0/">Keep a Changelog</a>,
and this project adheres to <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p>
<h2 id='unreleased'>[Unreleased]</h2><h2 id='0-0-1-1-2018-11-23'>[0.0.1+1] - 2018-11-23</h2><h3 id='added'>Added</h3>
<ul>
<li>First draft of CDR Info Sec Profile</li>
</ul>
<h2 id='0-0-1-2-2018-11-24'>[0.0.1+2] - 2018-11-24</h2><h3 id='added-2'>Added</h3>
<ul>
<li>Change log <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/5">#5</a></li>
</ul>
<h3 id='fixed'>Fixed</h3>
<ul>
<li>Bug <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/3">#3</a></li>
</ul>
<h2 id='0-0-2-1-2018-11-30'>[0.0.2+1] - 2018-11-30</h2><h3 id='added-3'>Added</h3>
<ul>
<li>Published 0.0.2 build 1.</li>
</ul>
<h3 id='fixed-2'>Fixed</h3>
<ul>
<li>Bug <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/16">#16</a></li>
</ul>
<h2 id='0-0-2-2-2018-12-08'>[0.0.2+2] - 2018-12-08</h2><h3 id='added-4'>Added</h3>
<ul>
<li>Todos for linking directly to relevant part(s) of specifications.</li>
</ul>
<h3 id='fixed-3'>Fixed</h3>
<ul>
<li>Various typographical errors.</li>
<li>Padding of time values in date times per ISO8601.</li>
<li>Made it clearer which values are being referred to in <em>Hashing value for state and authorisation code</em>.</li>
</ul>
<h2 id='0-0-3-1-2018-12-11'>[0.0.3+1] - 2018-12-11</h2><h3 id='added-5'>Added</h3>
<ul>
<li>Define Normative and Non-Normative elements - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/24">#24</a>.</li>
<li>Clarify Request Object Content - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/13">#13</a>.</li>
<li>Consent and Authorisation - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/12">#12</a></li>
<li>Refine Introspection Endpoint section - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/11">#11</a></li>
<li>Add Vectors of Trust - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/10">#10</a></li>
<li>Update LoAs with LoA 2 <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/4">#4</a></li>
</ul>
<h2 id='0-0-3-2-2018-12-14'>[0.0.3+2] - 2018-12-14</h2><h3 id='fixed-4'>Fixed</h3>
<ul>
<li>Typographic errors.</li>
</ul>
<h2 id='0-0-3-3-2018-12-14'>[0.0.3+3] - 2018-12-14</h2><h3 id='changed'>Changed</h3>
<ul>
<li>X1254 is now an informative reference - Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/37">#37</a>.</li>
</ul>
<h3 id='added-6'>Added</h3>
<ul>
<li>12.2 might imply vectors of trust is required. Feature <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/30">#30</a></li>
</ul>
<h3 id='fixed-5'>Fixed</h3>
<ul>
<li>Add <code>essential</code> field in examples of essential claims - Bug <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/29">#29</a></li>
</ul>
<h2 id='0-0-3-4-2018-12-18'>[0.0.3+4] - 2018-12-18</h2><h3 id='fixed-6'>Fixed</h3>
<ul>
<li>Improved clarity of document.</li>
<li>Simplified introduction.</li>
<li>CIBA is now FAPI-CIBA</li>
<li>Fixed some typographic errors.</li>
<li>Replaced customer with consumer.</li>
<li>Removed references to accreditation of Data Holder.</li>
<li>Holder and Recipient are now Data Holder and Data Recipient.</li>
<li><code>iss</code> claim is not supported on request object.</li>
<li><code>iat</code> claim in not mandatory as part of private key client authentication JWT.</li>
<li><code>bc-authorize</code> is now <code>backchannel_authentication_endpoint</code> on OIDD.</li>
<li><em>user</em> is now <em>end-user</em> in appendix.</li>
</ul>
<h2 id='0-0-3-5-2018-12-19'>[0.0.3+5] - 2018-12-19</h2><h3 id='fixed-7'>Fixed</h3>
<ul>
<li>Bug with consent id outside of claims <a href="https://github.com/ConsumerDataStandardsAustralia/infosec/issues/42">#42</a></li>
</ul>
<h2 id='0-1-0-1-2018-12-20'>[0.1.0+1] - 2018-12-20</h2><h3 id='added-7'>Added</h3>
<ul>
<li>Published 0.1.0 build 1.</li>
</ul>
21 changes: 21 additions & 0 deletions docs/archive/standards-1.0.0/docs/archive/infosec-0.1/LICENSE
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
<p>MIT License</p>

<p>Copyright (c) 2018 Data61</p>

<p>Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the &quot;Software&quot;), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:</p>

<p>The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.</p>

<p>THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.</p>
29 changes: 29 additions & 0 deletions docs/archive/standards-1.0.0/docs/archive/infosec-0.1/README
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
<h1 id='consumer-data-right-information-security-profile'>Consumer Data Right Information Security Profile</h1><h3 id='the-latest-information-security-profile-draft-is-published-at-https-consumerdatastandardsaustralia-github-io-infosec'>The latest Information Security Profile Draft is published at: https://consumerdatastandardsaustralia.github.io/infosec/</h3>
<p>The Information Security Profile draft is evolving as decisions are made.</p>
<h2 id='data61-and-the-standards'>Data61 and the standards</h2>
<p>Data61 has been appointed as technical advisor to the interim data standards body by the Australian federal government, as part of the introduction of <a href="https://www.accc.gov.au/focus-areas/consumer-data-right" title="ACCC Consumer Data Right webpage">Consumer Data Right</a> legislation to give Australians greater control over their data.</p>
<h3 id='please-visit-the-consumer-data-standards-web-site-at-https-consumerdatastandards-org-au'>Please visit the Consumer Data Standards Web Site at: https://consumerdatastandards.org.au/</h3><h2 id='newsletters'>Newsletters</h2><h4 id='you-can-subscribe-to-and-view-cdr-information-security-newsletters-here'>You can subscribe to and view CDR Information Security newsletters <a href="https://us18.campaign-archive.com/home/?u=fb3bcb1ec5662d9767ab3c414&amp;id=d59b5d73bc">here</a></h4><h2 id='change-log'>Change Log</h2><h4 id='the-change-log-can-be-found-here'>The change log can be found <a href="CHANGELOG.md">here</a></h4><h2 id='workshop-material'>Workshop Material</h2><h4 id='presentation-slides-16th-november-2018-workshop'>Presentation Slides <a href="workshops/InfoSecWorkshop16112018.pdf">16th November 2018 Workshop</a></h4><h4 id='presentation-slides-6th-december-2018-workshop'>Presentation Slides <a href="workshops/InfoSecWorkshop06122018.pdf">6th December 2018 Workshop</a></h4><h2 id='cdr-overview'>CDR Overview</h2>
<p>The Consumer Data Right is intended to apply sector by sector across the whole economy, beginning in the banking sector. The energy and telecommunications sectors will follow. In the first instance Australia’s four major banks have been tasked with implementing an open banking standard by 1 July 2019, and so developing an open banking standard - building on existing open banking and financial API standards - is Data61’s immediate focus. All other banks will need to comply with these standards by 1 July 2020.</p>

<p>This work is being delivered by a newly formed team within Data61 - the Consumer Data Standards team - acting as the interim standards body. The work of the team will be overseen by Mr. Andrew Stevens as interim Chair, with industry and consumer advice provided by an Advisory Committee. Data61 will be working closely with the Australian Competition and Consumer Commission (ACCC) as lead regulator of the Consumer Data Right, supported by the Office of the Australian Information Commissioner (OAIC).</p>

<p>A number of working groups are being established to support Data61 designing and testing the open standards it develops. Input provided by the Advisory Committee and working groups, alongside draft guidance materials, API specifications and implementation materials will be shared openly. At present, three work streams are being proposed:</p>

<ul>
<li>API Standards</li>
<li>Information Security</li>
<li>Consumer Experience</li>
</ul>

<p>This repository will be used to seek feedback from working groups, share drafts and proposals and review standards as they develop. Feedback on proposed decisions by the Data Standards Body will be collated and presented to the Chair, who has decision-making authority in relation to the Standards. </p>

<p>For more information, contact [email protected]. Further updates will be added to this page as the Consumer Data InfoSec Profile work gets underway.</p>
<h2 id='rules-of-engagement'>Rules of engagement</h2>
<p>We&#39;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.</p>

<p>We ask that all contributors to the Consumer Data Standards repositories comply with the <a href="https://help.github.com/articles/github-community-forum-code-of-conduct/">GitHub Community Forum Code of Conduct</a>.</p>

<p>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.</p>
Binary file added docs/archive/standards-1.0.0/docs/archive/infosec-0.1/docs/fonts/slate.eot
View file
Binary file not shown.
Loading

0 comments on commit 8959534

Please sign in to comment.