-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: wd25
-
Component/s: None
-
Labels:None
-
Environment:
William Cox
-
Resolution:
The pattern of defined strings for a particular status attribute should be consistently described.
See ENERGYINTEROP-201 for application to optInOut reason string.
This is consistent with the approach agreed by the TC, and used in EMIX and WS-Calendar.
How we solved this in EMIX:
<xs:element name="contractType" type="power:ContractTypeType"/>
<xs:simpleType name="ContractTypeType">
<xs:union memberTypes="power:ContractTypeEnumeratedType emix:EmixExtensionType"/>
</xs:simpleType>
<xs:simpleType name="ContractTypeEnumeratedType">
<xs:restriction base="xs:string">
<xs:enumeration value="FullRequirementsPower"/>
<xs:enumeration value="FullRequirementsPowerWithDemandCharge"/>
<xs:enumeration value="FullRequirementsPowerWithMaximumAndMinimum"/>
<xs:enumeration value="HourlyDayAheadEx-AnteRealTimePrice"/>
<xs:enumeration value="TimeOfUsePricing"/>
<xs:enumeration value="TransportService"/>
<xs:enumeration value="CongestionRevenueRights"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="EmixExtensionType">
<xs:annotation>
<xs:documentation>Pattern used for extending string enumeration, where allowed</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:pattern value="x-\S.*"/>
</xs:restriction>
</xs:simpleType>
This defines a general extension pattern (x-*), and a known list, and defines the valid enumerations as the union of the two. It also restricts the extensions to strings only, and not a rational for tunnelling.
Following NIEM Naming and Design rules for extensibility. Make reference to NIEM document. Include section on how this works (viz. EMIX section with similar goals).
As voted in meeting
This is in part editorial and in part schema and model related. Please comment.