Comments (5)
I note the publication of ConsumerDataStandardsAustralia/standards#50 (comment) and observe that it doesn't answer some of the above questions; in particular there is no description of how the actual text in the standard is changed and whether or not this would follow the expected model of having one pull request created that contains changes to the standard for one decision, linked to the issue and with the opportunity for the actual new text in the standard to be reviewed and potentially clarified/improved before being submitted for final approval.
from standards-maintenance.
As the approval process for the standards is via the Data Standards Chair the model of using decision proposals for changes has been adopted.
Following the approval of a change a branch and pull request is created but this is managed using a private staging repository.
Once the DSB team has reviewed the changes and confirmed that they align with the approved Decision the PR is merged and then the changes are pushed to the public repository.
As a result, while the public repository does not contain the PR and Branch used to create the changes, the commit history still contains all of the changes and can be used for comparison purposes.
from standards-maintenance.
Thanks for the response!
Following the approval of a change a branch and pull request is created but this is managed using a private staging repository.
Once the DSB team has reviewed the changes and confirmed that they align with the approved Decision the PR is merged and then the changes are pushed to the public repository.
I'm not sure I understand the rational for:
-
Why the review of whether the actual text changes reflects the agreed decision is being done in private
-
Why there is no public opportunity for review of the text prior to it being finalised
Whilst I understand that the legal need for review by the Data Standards Chair causes some deviation from the processes you'd expect open standards to follow (e.g. the processes used to agree the FAPI, OpenID Connect and OAuth 2 specs that the Australian standards built on top of), these deviations don't seem to relate to that requirement. Can you expand on the rational for the above lack of transparency please?
from standards-maintenance.
The only activity that is performed internally is the iterative development of the changes. The consultation process and resulting output are all fully transparent and are open to critique. There have been a number of occasions where the text incorporated to adopt a decision was ambiguous or in error and needed to be corrected and this was highlighted by the community. These changes are also transparent.
The actual process for developing the standards artefacts is a choice for the DSB team.
It should be noted that the standards, while openly and transparently consulted upon, are not openly developed. They are explicitly a centrally endorsed and managed set of artefacts.
from standards-maintenance.
@CDR-API-Stream Perhaps @jogu's point could be addressed by putting in a summary of changes into the description of a release, and tagging all our releases in Git? The details would then be visible in: https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/releases
from standards-maintenance.
Related Issues (20)
- Energy plan details - tariffPeriod has limited types - include more values
- Authorization Response Algs should be conditional in RegistrationProperties HOT 1
- Add maxLength field sizes to field descriptions for Register APIs and SSA HOT 1
- Add fields to Get Product Details to indicate the availability of data attributes
- Add new pricing models to EnergyPlanContractV2 HOT 11
- Improved structure for Solar Time Varying Tariffs HOT 15
- Additional field to support Step Tariff calculations HOT 18
- AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide HOT 14
- EnergyPlanTariffPeriod - Change to daily supply charge HOT 13
- Addition of a DH-side endpoint for querying the status of a consent establishment flow HOT 13
- Maintenance Iteration 18 Holistic Feedback HOT 14
- Commercial Credit Card Structure under Get Account Details call
- Updates to 'Revoking consent' Standards HOT 4
- Concurrent consent support and cdr_arrangement_id HOT 4
- Collection Consents - Authorisation Amendment HOT 8
- Potential error in Telco specification HOT 2
- Include "Provider number" in GetDataHolderBrands Response HOT 1
- Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction HOT 19
- Review Register API descriptions HOT 3
- Maintenance Iteration 19 Holistic Feedback 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.