Matt Peterson

Simple text/typo correction @ https://consumerdatastandardsaustralia.github.io/standards/#cdr-energy-api_schemas_tocSenergyplancontrolledloadv2 Change: `controlloed` to `controlled` 

Array delimiters (`[]`) are missing from several array properties of [Energy Plan Contract v3](https://consumerdatastandardsaustralia.github.io/standards/#cdr-energy-api_schemas_tocSenergyplancontractv3): 

**Description clarification** The current description for [EnergyPlanTariffPeriodV2](https://consumerdatastandardsaustralia.github.io/standards/#cdr-energy-api_schemas_tocSenergyplantariffperiodv2) is: > Array of tariff periods. Sometimes this schema is used by DHs to describe intra-day time-of-use tariff periods, rather than the presumably...

For `EnergyPlanTariffPeriodV2`, the description for time of use `rates` erroneously refers explicitly to _controlled load_: | Name | Type | Required | Description | |---|---|---|---| | » rates | [object]...

I am proposing some minor improvements to descriptions of some `timeOfUseRates` properties for the purpose of clarity leading to more consistent implementation and interpretation. Specifically, an explicit reference to the...

Unless I've missed something, this redundant `timeZone` property should have been removed when the types for TOU rate boundaries were changed to ISO8601 (#613). If that's the case, this is...

Descriptions for TOU rate boundaries already reference the `electricityContract`'s `timeZone` property, rather than the `tariffPeriod`'s `timeZone` property. > If the time is provided without a UTC offset, the time zone...

> The tariff level timeZone fields were added based on previous CR- https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/439 Ahha! Thanks for that context, @HemangCDR. That makes a whole heap more sense now. And it highlights...

There are some fields that are not covered by list in referenced comment https://github.com/ConsumerDataStandardsAustralia/standards/issues/190#issuecomment-922643873 - Value of [billing transaction](https://consumerdatastandardsaustralia.github.io/standards/#cdr-energy-api_schemas_tocSenergybillingtransactionv3) amounts are ambiguous but should seemingly be described as **exclusive** of...

@AGL-ENERGY-CDR The former; clarify one way or the other if GST is included or not in the values. I don't have a preference if it is or is not, so...