Jurisdiction Code of ISO

[perlboy]

Description

The payloads returned by AEMO for Service Points jurisdictionCode sometimes contain ISO which is a violation of the schema. While we've attempted to escalate through Holder and AEMO we have been informed that there is no immediate solution available.

This has the effect of denying List Service Points and related calls for impacted NMI.

Intention and Value of Change

Allow schema valid responses through by adding ISO as a recognised jurisdiction code. We suspect this code is representative of "isolated" but have not received specific direction on this.

Area Affected

EnergyServicePoint.jurisdictionCode

Change Proposed

Add ISO as a valid enum value to EnergyServicePoint.jurisdictionCode with a description defined by AEMO/DSB as to what it actually means. Given AEMO is already outputting this as an enum value an incrementing of the endpoint version would be of no real use (either the Holder stops it and errors or the Recipients receives it and errors - either way it's broken now).

[mattyp]

As part of the working group's action items for MI22 (ConsumerDataStandardsAustralia/standards#364), I would urge considering this proposed change to formally document the use of ISO as non-breaking. As stated in the original proposal, the value is already being used in practice. This change is simply documenting that fact, not actually changing any behaviour or mechanics.