-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review date format conventions #310
Comments
This change has been staged for review: 8ec8fd9 |
JamesMBligh
added a commit
to ConsumerDataStandardsAustralia/standards
that referenced
this issue
Apr 24, 2024
* 1.30.0 branch * Updates to base build * Update releasenotes.1.30.0.html.md * Updated release notes templates * Corrected typo in Description Addresses: ConsumerDataStandardsAustralia/standards-staging#361 * Updated links Addresses: ConsumerDataStandardsAustralia/standards-staging#362 * Updated Principles text for CX Addresses: ConsumerDataStandardsAustralia/standards-staging#370 * Improved wrapping for long lines Addresses: ConsumerDataStandardsAustralia/standards-staging#371 * Adding version delta and release notes * Updates to 'Revoking consent' Standards Addresses: ConsumerDataStandardsAustralia/standards-maintenance#631 * Removed two outdated statements Addresses: ConsumerDataStandardsAustralia/standards-maintenance#632 * Corrected typo in `cdr_arragement_id` Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Changed 'Software Package' to 'Software Product' Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Updated documentation to include link Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Clarified documentation Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Updated Non-normative Example Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Clarified Register endpoint responses Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Applied change to Register API in NBL Candidate Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment) * Template code change Change log and version delta details TBC. Addresses: ConsumerDataStandardsAustralia/standards-staging#376 * Removed unused Format column * Updated template and schema mapping Addresses: ConsumerDataStandardsAustralia/standards-staging#376 * Removed outdated statements and examples Addresses: ConsumerDataStandardsAustralia/standards-maintenance#543 * Fixed typo Addresses: ConsumerDataStandardsAustralia/standards-staging#388 * Updated date format Addresses: ConsumerDataStandardsAustralia/standards-staging#310 * Updated based on feedback in MI18 Addresses: ConsumerDataStandardsAustralia/standards-maintenance#543 (comment) * Standards Maintenance Issue #624: Converted solarFeedInTariff.timeVaryingTariffs into an array. Added new mandatory displayName field to solarFeedInTariff.timeVaryingTariffs * Standards Maintenance Issue #625: Added optional period field to various energy rate objects to help support stepped tariff calculation * Standards Maintenance Issue #627: Made changes to EnergyPlanTariffPeriod to allow sharing of banded daily supply charges * Standards Maintenance Issue #627: Corrected bandedDailySupplyCharges to an array. Fixed typos in FDO table * Standards Maintenance Issue #627: Fixed typos in field descriptions * Standards Maintenance Issue #625: Fixed typos in FDO table * Standards Maintenance Issue #624: Fixed typos in FDO table * Standards Maintenance Issue #624: Added new ENUM values CURRENT and VARIABLE to solarFeedInTariff.scheme * Standards Maintenance Issue #625: Corrected diff and release notes including as part of the change * Remove spaces causing extra lines when wrapping * Moving the typo correction to a separate issue * Final updates to 1.30.0 --------- Co-authored-by: Nils Berge <[email protected]> Co-authored-by: Hemang Rathod <[email protected]> Co-authored-by: Mark Verstege <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Define consistent date formats to apply through the Standards documentation.
e.g. Milestone Date and Binding Date are currently different on the Obligation Dates Schedule page.
Keeping the same format would help with searching for corresponding obligations on the page.
Also consider whether breaking down the current '# Obligations Assigned' column, or adding a column for each sector in the Obligation Milestone table would be helpful for participants.
The text was updated successfully, but these errors were encountered: