Merge pull request #173 from ConsumerDataStandardsAustralia/maintenan…

…ce/465

Standards Maintenance Issue #465

slate/source/includes/_intro.md.erb

@@ -3,5 +3,6 @@
 
 <%= partial "includes/introduction/intro.md" %>
 <%= partial "includes/introduction/fdo.md" %>
+<%= partial "includes/introduction/dependencies_schedule.md" %>
 <%= partial "includes/introduction/endpoint_version_schedule.md" %>
 <%= partial "includes/security/references.md" %>

slate/source/includes/endpoint-version-schedule/includes/_register.md

@@ -10,19 +10,15 @@
 | CDR Register APIs    | Get OpenId Provider Config                | ``/.well-known/openid-configuration``                        | <span class="method get">GET</span>    | None    | 2021-10-29&dagger;    | N/A             | 2021-10-29, V1.14.0&dagger; | N/A                 |
 | CDR Register APIs    | Get JWKS                                  | ``/jwks``                                                    | <span class="method get">GET</span>    | None    | 2021-10-29&dagger;    | N/A             | 2021-10-29, V1.14.0&dagger; | N/A                 |
 | CDR Register APIs    | Get Data Holder Brands                    | ``/{industry}/data-holders/brands``                          | <span class="method get">GET</span>    | V1      | 2021-10-29&dagger;    | N/A             | 2021-10-29, V1.14.0&dagger; | 2021-12-23, V1.15.0 |
-| CDR Register APIs    | Get Data Holder Brands                    | ``/{industry}/data-holders/brands``                          | <span class="method get">GET</span>    | V2      | 2022-08-30&Dagger;    | N/A              | 2021-12-23, V1.15.0* | N/A |
+| CDR Register APIs    | Get Data Holder Brands                    | ``/{industry}/data-holders/brands``                          | <span class="method get">GET</span>    | V2      | 2022-11-15    | N/A              | 2021-12-23, V1.15.0* | N/A |
 | CDR Register APIs    | Get Software Statement Assertion (SSA) | ``/{industry}/data-recipients/``<br/>``brands/{dataRecipientBrandId}/``<br/>``software-products/{softwareProductId}/ssa`` | <span class="method get">GET</span>    | V2    | 2021-10-29&dagger;  | N/A             | 2021-10-29, V1.14.0&dagger; | 2021-12-23, V1.15.0 |
-| CDR Register APIs    | Get Software Statement Assertion (SSA) | ``/{industry}/data-recipients/``<br/>``brands/{dataRecipientBrandId}/``<br/>``software-products/{softwareProductId}/ssa`` | <span class="method get">GET</span>    | V3    | 2022-08-30&Dagger;  | N/A             | 2021-12-23, V1.15.0 | N/A                 |
+| CDR Register APIs    | Get Software Statement Assertion (SSA) | ``/{industry}/data-recipients/``<br/>``brands/{dataRecipientBrandId}/``<br/>``software-products/{softwareProductId}/ssa`` | <span class="method get">GET</span>    | V3    | 2022-11-15  | N/A             | 2021-12-23, V1.15.0 | N/A                 |
 | CDR Register APIs    | Get Software Products Statuses | ``/{industry}/data-recipients/``<br/>``brands/software-products/status`` | <span class="method get">GET</span>  | V1  | 2021-10-29&dagger; | N/A          | 2021-10-29, V1.14.0&dagger; | 2021-12-23, V1.15.0 |
-| CDR Register APIs    | Get Software Products Statuses | ``/{industry}/data-recipients/``<br/>``brands/software-products/status`` | <span class="method get">GET</span>  | V2  | 2022-08-30&Dagger; | N/A          | 2021-12-23, V1.15.0 | N/A                 |
+| CDR Register APIs    | Get Software Products Statuses | ``/{industry}/data-recipients/``<br/>``brands/software-products/status`` | <span class="method get">GET</span>  | V2  | 2022-11-15 | N/A          | 2021-12-23, V1.15.0 | N/A                 |
 | CDR Register APIs    | Get Data Recipient Statuses | ``/{industry}/data-recipients/status``                                     | <span class="method get">GET</span>    | V1     | 2021-10-29&dagger;    | N/A              | 2021-10-29, V1.14.0&dagger; | 2021-12-23, V1.15.0 |
-| CDR Register APIs    | Get Data Recipient Statuses | ``/{industry}/data-recipients/status``                                     | <span class="method get">GET</span>    | V2     | 2022-08-30&Dagger;    | N/A              | 2021-12-23, V1.15.0 | N/A                 |
+| CDR Register APIs    | Get Data Recipient Statuses | ``/{industry}/data-recipients/status``                                     | <span class="method get">GET</span>    | V2     | 2022-11-15    | N/A              | 2021-12-23, V1.15.0 | N/A                 |
 | CDR Register APIs    | Get Data Recipients                       | ``/{industry}/data-recipients``                              | <span class="method get">GET</span>    | V2     | 2021-10-29&dagger;    | N/A              | 2021-10-29, V1.14.0&dagger; | 2021-12-23, V1.15.0 |
-| CDR Register APIs    | Get Data Recipients                       | ``/{industry}/data-recipients``                              | <span class="method get">GET</span>    | V3     | 2022-08-30&Dagger;    | N/A              | 2021-12-23, V1.15.0 | N/A |
-| CDR Register APIs    | Get Data Holder Statuses                       | ``/{industry}/data-holders/status``                      | <span class="method get">GET</span>    | V1     | 2022-08-30&Dagger;    | N/A              | 2021-12-23, V1.15.0 | N/A |
+| CDR Register APIs    | Get Data Recipients                       | ``/{industry}/data-recipients``                              | <span class="method get">GET</span>    | V3     | 2022-11-15    | N/A              | 2021-12-23, V1.15.0 | N/A |
+| CDR Register APIs    | Get Data Holder Statuses                       | ``/{industry}/data-holders/status``                      | <span class="method get">GET</span>    | V1     | 2022-11-15    | N/A              | 2021-12-23, V1.15.0 | N/A |
 
 **&dagger;NOTE:** The CDR Register standards were introduced into the Consumer Data Standards in v1.14.0. Prior to this the CDR Register specifications were hosted by the ACCC.
-
-**&Dagger;NOTE:** This date has been defined to give certainty to Data Recipient and Data Holder participants but it is yet to be confirmed by the ACCC.
-
-**\*NOTE:** Data Holder Brands V2 definition is still subject to change

slate/source/includes/introduction/_dependencies_schedule.md

@@ -0,0 +1,27 @@
+## Register Dependency Schedule
+
+```diff
++ Added Register dependency schedule table to differentiate Register delivery from Participant future dated obligations
++ Added Get Data Holder Brands Summary API to the dependency schedule
+```
+
+The Register APIs dependency schedule specifies the latest dates the CDR Register can release API versions. Delivery past these dates may impact the ability for data holders and data recipients to meet their future dated obligations.
+
+
+
+The table below highlights these dependency dates.
+
+|Section|Description|Dependency Date|
+|-------|-----------|---------------|
+|[Get Data Holder Brands V2](#get-data-holder-brands)|CDR Register must introduce version 2 of this end point by November 15th 2022|November 15th 2022|
+|[Get Software Statement Assertion (SSA) V3](#get-software-statement-assertion-ssa)|CDR Register must introduce version 3 of this end point by November 15th 2022|November 15th 2022|
+|[Get Software Products Statuses V2](#get-software-products-statuses)|CDR Register must introduce version 2 of this end point by November 15th 2022|November 15th 2022|
+|[Get Data Recipient Statuses V2](#get-data-recipients-statuses)|CDR Register must introduce version 2 of this end point by November 15th 2022|November 15th 2022|
+|[Get Data Recipients V3](#get-data-recipients)|CDR Register must introduce version 3 of this end point by November 15th 2022|November 15th 2022|
+|[Get Data Holder Statuses V1](#get-data-holder-statuses)|CDR Register must introduce version 1 of this end point by November 15th 2022|November 15th 2022|
+|[Get Data Holder Brands Summary V1](#get-data-holder-brands-summary)|CDR Register must introduce version 1 of this end point by October 1st 2022|October 1st 2022|
+
+
+The actual release dates for the Register APIs are expected to occur prior to these dates and are not defined by the Standards.
+
+The Register API release schedule will be made available in the future.

slate/source/includes/introduction/_fdo.md

@@ -1,5 +1,10 @@
 ## Future Dated Obligations
 
+```diff
+- Moved Register FDOs to the Register dependency schedule to differentiate Register delivery from Participant future dated obligations
+```
+
+
 The standards, as published from time to time, may include specific statements indicating that a specific section of the standards will not take effect until a future date or may cease to have effect on some future date.
 
 The table below highlights these areas of the standards.
@@ -23,12 +28,6 @@ The table below highlights these areas of the standards.
 |[Self-Signed JWT Client Authentication](#self-signed-jwt-client-authentication) | Until July 31st 2022, Data Recipients MUST accept the [Resource Path](#uri-resource-path) for the endpoint and the ``<RecipientBaseURI>`` as a valid audience value. From July 31st 2022, Data Holders MUST use an audience value matching the Resource Path for the endpoint and the Data Recipient MUST verify the audience matches the Resource Path for the endpoint. | July 31st 2022 |
 |[Get Payees V1](#get-payees)|Data holders may obsolete version 1 of this end point from August 31st 2022.  Data recipients must upgrade their implementations to use version 2 by this time|August 31st 2022|
 |[Get Payee Detail V1](#get-payee-detail)|Data holders may obsolete version 1 of this end point from August 31st 2022.  Data recipients must upgrade their implementations to use version 2 by this time|August 31st 2022|
-|[Get Data Holder Brands V2](#get-data-holder-brands)&Dagger;|CDR Register must introduce version 2 of this end point by August 30th 2022&dagger;.  Data recipients may upgrade their implementations to use this version from this time|August 30th 2022&dagger;|
-|[Get Software Statement Assertion (SSA) V3](#get-software-statement-assertion-ssa)|CDR Register must introduce version 3 of this end point by August 30th 2022&dagger;.  Data recipients may upgrade their implementations to use this version from this time|August 30th 2022&dagger;|
-|[Get Software Products Statuses V2](#get-software-products-statuses)|CDR Register must introduce version 2 of this end point by August 30th 2022&dagger;.  Data holders may upgrade their implementations to use this version from this time|August 30th 2022&dagger;|
-|[Get Data Recipient Statuses V2](#get-data-recipients-statuses)|CDR Register must introduce version 2 of this end point by August 30th 2022&dagger;.  Data holders may upgrade their implementations to use this version from this time|August 30th 2022&dagger;|
-|[Get Data Recipients V3](#get-data-recipients)|CDR Register must introduce version 3 of this end point by August 30th 2022&dagger;.  Data holders may upgrade their implementations to use this version from this time|August 30th 2022&dagger;|
-|[Get Data Holder Statuses V1](#get-data-holder-statuses)|CDR Register must introduce version 3 of this end point by August 30th 2022&dagger;|August 30th 2022&dagger;|
 |[Information Security profile](#security-profile) | FAPI 1.0 adoption is introduced across three phases.<br/><strong>Phase 2: FAPI 1.0 Final (Baseline & Advanced)</strong> includes, amongst other changes:<ul><li>Enforces additional requirements for authorisation code, token and request object use</li><li>Enforces PAR-only authorisation request data submission</li><li>Refresh token cycling is not permitted</li><li>Data Holders and Data Recipients MUST support FAPI 1.0 Final including **[[RFC9126]](#nref-RFC9126)**, **[[RFC7636]](#nref-RFC7636)** and **[[JARM]](#nref-JARM)**</li><li>Data Holders SHOULD support of Authorization Code Flow in conjunction with Hybrid Flow</li></ul> | September 16th 2022 |
 |[Get Metrics V3](#get-metrics)|Version 3 of this end point must be made available by affected data holders by October 1st 2022|October 1st 2022|
 |[Standard Error Codes](#error-codes) | Data Holders MAY retire application-specific error codes in favour of standard error codes from November 1st 2022 | November 1st 2022 |
@@ -41,6 +40,3 @@ The table below highlights these areas of the standards.
 |[Get Customer Detail V1](#get-customer-detail)|Data holders may obsolete version 1 of this end point from February 28th 2023.  Data recipients must upgrade their implementations to use version 2 by this time|February 28th 2023|
 |[Information Security profile](#security-profile) | FAPI 1.0 adoption is introduced across three phases.<br/><strong>Phase 3: Retire Hybrid Flow</strong> includes, amongst other changes:<ul><li>Data Holders MUST support Authorization Code Flow</li><li>Data Holders MAY retire Hybrid Flow</li></ul> | April 7th 2023 |
 
-**&dagger;NOTE:** Further consultation required with the ACCC to confirm this obligation date
-
-**&Dagger;NOTE:** Get Data Holder Brands V2 definition is still subject to change

slate/source/includes/releasenotes/releasenotes.1.17.0.html.md

@@ -23,6 +23,7 @@ This release addresses the following change requests raised on [Standards Mainte
 - [Standards Maintenance Issue 438: Representing adjustment transactions within the Billing Payload for C&I customers](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/438)
 - [Standards Maintenance Issue 457: Energy - Get Service Point Detail register suffix should be optional](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/457)
 - [Standards Maintenance Issue 482: JWT signing non-normative examples use unsupported signing algorithm)](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/482)
+- [Standards Maintenance Issue 465: Confirm Register API 2022 release dates](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/465)
 
 ### Decision Proposals
 
@@ -39,6 +40,7 @@ This release addresses the following Decision Proposals published on [Standards]
 | Obligation date highlighting | Highlighting based on a date pickers has been added for the Endpoint versioning schedule to enhance documentation functionality. This feature allows users to select a target date and determine what obligations apply at that date. | [Endpoint versioning schedule](../../includes/endpoint-version-schedule/)
 | Obligation Dates Table | A series of fixed obligation milestones were agreed in Maintenance Iteration 10. This set of milestones will be used to pin breaking changes to a deterministic series of possible obligation dates. | [Obligation Dates]() |
 | Scrollable diffs and examples | Added previous and next buttons to support easy scrolling between all diffs and non-normative examples. This feature is context dependent on the tab being viewed | N/A |
+| Introduction | [**Standards Maintenance #465**](https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/465) Moved Register FDOs to the Register dependency schedule to differentiate Register delivery from Participant future dated obligations. </br> Register API versions now have dependency dates of **15th November 2022**, aligned to Energy | [Register Dependencies Schedule](../../#register-dependencies-schedule) |
 
 ## API End Points