/
paths:
diff --git a/docs/includes/swagger/cds_telco.json b/docs/includes/swagger/cds_telco.json
index b0e1358c..636c88ca 100644
--- a/docs/includes/swagger/cds_telco.json
+++ b/docs/includes/swagger/cds_telco.json
@@ -12,7 +12,7 @@
"url" : "https://opensource.org/licenses/MIT"
},
"title" : "CDR Telco API",
- "version" : "1.22.1"
+ "version" : "1.23.0"
},
"servers" : [ {
"url" : "https://data.holder.com.au/cds-au/v1"
diff --git a/docs/includes/swagger/cds_telco.yaml b/docs/includes/swagger/cds_telco.yaml
index 71983504..94e2f703 100644
--- a/docs/includes/swagger/cds_telco.yaml
+++ b/docs/includes/swagger/cds_telco.yaml
@@ -11,7 +11,7 @@ info:
name: MIT License
url: https://opensource.org/licenses/MIT
title: CDR Telco API
- version: 1.22.1
+ version: 1.23.0
servers:
- url: https://data.holder.com.au/cds-au/v1
paths:
diff --git a/docs/index.html b/docs/index.html
index e469d934..fea60a7e 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -1757,7 +1757,6 @@ Introduction
This text is an example of text removed from the standards:
- Old text removed
Note: changes to request and response payloads are listed at the beginning of the relevant API section due to the documentation being auto generated from OpenAPI specification files.
-Additional note for v1.22.0: For this version only the delta statements from v1.21.0 have been retained in v1.22.0 as the release dates between the two versions were close together. The affected delta statements will be noted as being associated with v1.21.0
These standards have been developed as part of the Australian Government's introduction of the Consumer Data Right legislation to give Australians greater control over their data.
@@ -1773,14 +1772,11 @@ Introduction
where the standards are specified as binding standards as required by the Consumer Data Right rules for the purposes of s56FA of the legislation, they apply as under contract between a data holder and an accredited data recipient. The legal effect of binding standards as between data holders and accredited data recipients is fully set out in s56FD and s56FE of the legislation.
-+ Added binding statement in response to legal advice
-
-
Some of these standards will be binding data standards under the Competition and Consumer (Consumer Data Right) Data Standards (No. 1) 2023. See that instrument here. In summary, provisions of these standards (as they exist from time to time) that impose obligations or prohibitions on CDR entities are binding data standards. Provisions included in these standards merely by way of guidance are not binding data standards.
Version
-These standards represent version 1.22.1 of the high level standards. See the versioning section for more information on how versions are managed in the standard.
+These standards represent version 1.23.0 of the high level standards. See the versioning section for more information on how versions are managed in the standard.
Interpretation
@@ -1792,13 +1788,6 @@ Future Dated Obligations
The table below highlights these areas of the standards.
-Removed obligations more than six months in the past
-
-Reordered FDO entries by applicable date
-
-Corrected some typos
-
-
| Section |
@@ -1965,18 +1954,8 @@ Register Dependency Schedule
The actual release dates for the Register APIs are expected to occur prior to these dates and are not defined by the Standards.
-Endpoint Version Schedule
Updated the obligation dates schedule to have correct
-numbers for each date
-
-Removed entries in the obligation dates schedule older
-than six months
-
-Corrected the year of the obligation date for Get
-Energy Account Detail V2
+Endpoint Version Schedule
-Corrected link to go directly to the end point version
-schedule
-
A table-view of all endpoint versioning is available here.
Normative References
@@ -2355,15 +2334,14 @@ End Point Versioning
Each end point will have multiple versions independent of other end points. A specific end point version will be requested by a client using a HTTP header. This header will be supported by all end points under the API standards. See the section on HTTP Headers for more information on how versions are requested and supplied under the standards.
-Corrected link to go directly to the end point version
-schedule
-
A table-view of all endpoint versioning is available here.
URI Structure
+
Some example URIs that meet this standard are:
+
1. https://www.bank.com.au/api/cds-au/v1/banking/accounts
2. https://www.bank.com.au/api/cds-au/v1/banking/accounts/abc123/transactions/?x=y#bar
3. https://www.bank.com.au/complex/uri/taxonomy/cds-au/v1/banking/products?page=2
@@ -5309,7 +5287,9 @@ SSA Definition
Get Software Statement Assertion API v1 & v2 has the scope claim explicitly defined.
-Registration Request using JWT
+Registration Request using JWT
Removed following requirement from id_token_encrypted_response_alg and id_token_encrypted_response_enc fields:
+- Must be ignored for Authorization Code Flow
+
Example Request
Client registration with OpenID Hybrid Flow
@@ -5479,13 +5459,13 @@ Registration Request using JWT
+ 
+