Merge pull request #263 from ConsumerDataStandardsAustralia/staging/193

Issue 193 - Update end point version schedule links
ConsumerDataStandardsAustralia · Mar 20, 2023 · 773bf33 · 773bf33
2 parents 58d264f + 40b351f
commit 773bf33
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 3 deletions.
diff --git a/slate/source/includes/introduction/_endpoint_version_schedule.md b/slate/source/includes/introduction/_endpoint_version_schedule.md
@@ -10,6 +10,9 @@ than six months
 
 Corrected the year of the obligation date for Get
 Energy Account Detail V2
+
+Corrected link to go directly to the end point version
+schedule
 ```
 
-A table-view of all endpoint versioning is available <a href='includes/endpoint-version-schedule/'>here</a>.
+A table-view of all endpoint versioning is available <a href='includes/endpoint-version-schedule/#endpoint-version-schedule'>here</a>.
diff --git a/slate/source/includes/releasenotes/releasenotes.1.22.1.html.md b/slate/source/includes/releasenotes/releasenotes.1.22.1.html.md
@@ -21,6 +21,7 @@ This release addresses the following minor defects raised on [Standards Staging]
 - Issue [255](https://github.com/ConsumerDataStandardsAustralia/standards-staging/issues/255): Maintenance of obligation date tables
 - Issue [254](https://github.com/ConsumerDataStandardsAustralia/standards-staging/issues/254): Get Energy Account Detail V2 - Fix binding date
 - Issue [245](https://github.com/ConsumerDataStandardsAustralia/standards-staging/issues/254): Get Energy APIs: meta object should not be mandatory
+- Issue [193](https://github.com/ConsumerDataStandardsAustralia/standards-staging/issues/193): Incorrect link to Endpoint Version Schedule in Standards
 - Issue [152](https://github.com/ConsumerDataStandardsAustralia/standards-staging/issues/152): Get Meta objects to be optional in energy requests
 
 
@@ -35,7 +36,8 @@ This release is a patch release and does not include any changes arising from a
 | Binding Statement | Added binding statement to the Introduction section | [Introduction](../../#introduction) |
 | Align Obligation Dates | Corrections to the future dated obligations table | [FDOs](../../#future-dated-obligations) |
 | Align Obligation Dates | Corrections to the obligation dates table | [Obligations Table](../endpoint-version-schedule/#obligation-dates-schedule) |
-| Fix Binding Date | Correct the binding date for Get Energy Account Detail V2 in the end point schedule | [FDOs](../endpoint-version-schedule/#endpoint-version-schedule) |
+| Fix Binding Date | Correct the binding date for Get Energy Account Detail V2 in the end point schedule | [End Point Version Schedule](../endpoint-version-schedule/#endpoint-version-schedule) |
+| Fix End Point Schedule Link | Correct the link for the end point version schedule | [End Point Version Section](../../#endpoint-version-schedule) |
 
 ## High Level Standards
 

diff --git a/slate/source/includes/standards/_versioning.md b/slate/source/includes/standards/_versioning.md
@@ -26,4 +26,9 @@ The high level standard will be versioned as described above.  The major compone
 ###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](#http-headers) for more information on how versions are requested and supplied under the standards.
 
-A table-view of all endpoint versioning is available <a href='includes/endpoint-version-schedule/'>here</a>.
+```diff
+Corrected link to go directly to the end point version
+schedule
+```
+
+A table-view of all endpoint versioning is available <a href='includes/endpoint-version-schedule/#endpoint-version-schedule'>here</a>.