-
Notifications
You must be signed in to change notification settings - Fork 9
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
Representation of time within EnergyPlanDetail Schema #505
Comments
This CR is now included in MI11. This is a result of re-prioritisation work the DSB carried out as per action raised in MI11 session on 25th May. BackgroundThe following fields describing time within EnergyPlanTariffPeriod are currently defined as type “string”, the description stating that time would be in HHMM format using 24 hour clock format:
This was done in collaboration with the EME/AER team followed by several energy sector consultations conducted last year. During consultation of issue #472 in MI11, participants indicated the desire to have all time attributes type defined as TimeString to ensure consistent representation of time within EnergyPlan schema. Proposed changeThe DSB has discussed this with EME/AER and proposes to make the above change. The change would also be applied to time fields in the proposed controlledLoad changes being discussed in #472. |
We support the change of these fields to |
The proposal doesn't seek to specify a time offset to UTC but rather an RFC3339 formatted time in alignment with the rest of the Standard which includes the ability to specify any offset an implementer likes (allowing the receiver to do any time math they like to suit their use case). I believe the suggestion above is based on a desire to specify no timezone, there's actually an allowance for this in RFC3339:
Further the issues with
The schema for
Put another way leaving it as |
Just a footnote here, the driver for the request here is less about RFC3339 time (although that's what is available in |
This change request was incorporated thorough ConsumerDataStandardsAustralia/standards#249 (comment). A new CR can be raised if the issue needs to be re-assessed |
Description
As part of feedback on issue #472, request was made to align how time is represented within EnergyPlanDetail Schema.
This issue has been raised to consult on the request.
Area Affected
EnergyPlanDetail Schema
Change Proposed
This decision proposal is currently a placeholder. The DSB will publish recommended changes to be consulted on within the Maintenance Iteration it gets prioritised for.
The text was updated successfully, but these errors were encountered: