Comments (2)
V1.1.0 was released and appears to have inconsistently approached breaking changes as evidenced by #60 #66 #61
from standards-maintenance.
Rather than being prescriptive and embedding details such as you've proposed into the Standards themselves, the approach of the DSB has been to assess endpoint versioning in the context of change on a case-by-case basis. This is intended to allow for consultation and flexibility as needed. Although it depends on the circumstances, the decision to increment may generally be favoured to provide certainty to participants.
With that in mind though, two new labels - 'Breaking change' and 'Non-breaking change' have been created to apply to Change Requests in this repository to encourage consultation on that particular aspect through the Maintenance Iteration process.
Issues with the labels currently applied can be found in the following views -
- Breaking changes (list view | board view)
- Non-breaking changes (list view | board view)
The utility of these labels can be reviewed in the current and future iterations.
As there is no change to the Standards expected as an outcome of this Change Request, it will be considered as acknowledged but scheduled to be closed on 25 August 2023.
Thanks
from standards-maintenance.
Related Issues (20)
- EnergyBillingDemandTransaction - Measure Unit
- Add structured fields for rate applicability HOT 6
- No link for mailing addresses to accounts when there are multiple mailing addresses HOT 1
- Remove FAPI 1.0 draft references HOT 4
- Energy 'Get Agreed Payment Schedule' - BSB and Account Number Tokenisation/non-Tokenisation HOT 4
- EnergyBillingDemandTransaction - timeOfUseType - New Value HOT 5
- Interest paid at maturity guidance for applicationFrequency in BankingProductDepositRate HOT 9
- Schemas missing currency field HOT 1
- Use of additionalValue field in Product Eligibility Types HOT 2
- Add Swift BIC Code to Get Payees and Get Scheduled Payments API HOT 8
- Multiple missing values from mandatory fields served by AEMO APIs HOT 9
- Extend status and outages APIs to secondary data holders HOT 2
- Maintenance Iteration 16 Holistic Feedback HOT 27
- Government Environment Certificate Schemes
- Energy - Cancelled Invoices in Invoice APIs
- NFR: Secondary Data Holder unable to determine Customer Present HOT 1
- NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds HOT 1
- NFR: Arrangements with large numbers (500+) of accounts HOT 1
- Metrics: Performance threshold including SDH HOT 3
- Update Get Metrics Endpoint Schedule HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standards-maintenance.