Potential error in Telco specification #634
Assignees
Labels
Non-breaking change
A change that is not expected to result in a new endpoint version.
Proposal made
The DSB has proposed a specific change to the standards to address the change request
Telco
Milestone
Comments
nils-work
added a commit
to ConsumerDataStandardsAustralia/standards-staging
that referenced
this issue
Mar 26, 2024
|
A change to address this issue has been staged for review here: ConsumerDataStandardsAustralia/standards-staging@release/1.30.0...maintenance/634
|
CDR-API-Stream
moved this from Full Backlog
to Iteration Candidates
in Data Standards Maintenance
CDR-API-Stream
moved this from Iteration Candidates
to Full Backlog
in Data Standards Maintenance
CDR-API-Stream
moved this from Full Backlog
to Iteration Candidates
in Data Standards Maintenance
nils-work
moved this from Iteration Candidates
to In Progress: Staging
in Data Standards Maintenance
nils-work
added
the
Proposal made
nils-work
moved this from In Progress: Staging
to Awaiting Chair Approval
in Data Standards Maintenance
nils-work
added
the
Non-breaking change
nils-work
moved this from Awaiting Chair Approval
to In Progress: Staging
in Data Standards Maintenance
|
A decision on this change was made with other items in Maintenance Iteration 18, but this issue was not included in version 1.30.0. |
CDR-API-Stream
added a commit
to ConsumerDataStandardsAustralia/standards
that referenced
this issue
Jul 3, 2024
* 1.30.0 branch * Updates to base build * Update releasenotes.1.30.0.html.md * Updated release notes templates * Removed repeated object * Removed duplicate TelcoAccount schema Addresses: ConsumerDataStandardsAustralia/standards-maintenance#634 * Create clean 1.31.0 branch * Expanded nested array structure for previousDays Addresses: ConsumerDataStandardsAustralia/standards-staging#396 * Remove redundant TelcoAccount object * Update releasenotes.1.31.0.html.md * Enable generic links to schemas Addresses: ConsumerDataStandardsAustralia/standards-staging#400 * Updated Consumer Data Right link Addresses: ConsumerDataStandardsAustralia/standards-staging#402 * Updated Obligation Date Schedule Addresses: ConsumerDataStandardsAustralia/standards-maintenance#615 * Removed title text * Standards Maintenance Issue #640: Changed retirement date of Get Generic Plan Detail v2 and Get Energy Account Detail v3 to March 3rd 2025 * Standards Maintenance Issue #415: Clarified that a Token Introspection End Point response must include specific fields only for currently active tokens * Standards Maintenance Issue #415: Corrected release notes change description * Standards Maintenance Issue #415: Updated link to change in release notes * Standards Maintenance Issue #415: Fixed spelling mistake in release notes * Standards Maintenance Issue #633: Changes to CX and Security standards to clarify cdr_arrangement_id is requried for consent amendments * Standards Maintenance Issue #633: minor presentation fixes * Updated FDO table Addresses: ConsumerDataStandardsAustralia/standards-staging#377 * Presentational styling of Banking documentation Addresses: ConsumerDataStandardsAustralia/standards-staging#395 * Moved the March 2025 FDO to the 17th * Standards Maintenance Issue #640: Moved release notes entry to Introduction section * Standards Maintenance Issue #643: Allow data holders to depricate use of vulnerable TLS ciphers * Standards Maintenance Issue #415: Made the word SHALL bold * Fixed typo (#399) Addresses: ConsumerDataStandardsAustralia/standards-staging#394 * Standards Maintenance Issue #643: Fixed typo in release notes * Added MI19 DP link change log, re-ordered CRs in releasenotes * In release notes, changed link to obligation date schedule for CR 615 * Build standards version 1.31.0 for staging * Added change date in Change Log. Added None to release notes sections where there are no changes * Rebuild version 1.31.0 in preparation of publishing --------- Co-authored-by: Nils Berge <[email protected]> Co-authored-by: Hemang Rathod <[email protected]>
github-project-automation
bot
moved this from In Progress: Staging
to Done
in Data Standards Maintenance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the Telco specification.
The 'TelcoAccountDetailResponseData' Schema is a combination of the three schemas
"#/components/schemas/TelcoAccountBase"
"#/components/schemas/TelcoAccount"
"#/components/schemas/TelcoAccountDetail"
This leads to multiple 'properties' called 'plans'.
Nils Berge mentioned that this may be an error.
In the case this is intentional, should a particular property take precedence ?
Thanks
DSB Proposed Solution
The proposed solution can be found through the staging link provided in this comment.
The text was updated successfully, but these errors were encountered: