[OASIS Issue Tracker] Commented: (ENERGYINTEROP-333) Patterns forstrings and extension needs to be applied to EI

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24876#action_24876 ] 

Toby Considine commented on ENERGYINTEROP-333:
----------------------------------------------

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.

> Patterns for strings and extension needs to be applied to EI
> ------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-333
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-333
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>         Environment: William Cox
>            Reporter: William Cox
>            Assignee: Toby Considine
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira