[OASIS Issue Tracker] Created: (ENERGYINTEROP-588) Add Elements to match each of the enumerated types

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

Add Elements to match each of the enumerated types
--------------------------------------------------

                 Key: ENERGYINTEROP-588
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-588
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
    Affects Versions: wd32
         Environment: Toby Considine
            Reporter: Toby Considine
            Assignee: William Cox
             Fix For: WD33


In the existing Schemas, almost are enumeration are extensible. They follow the general form

	<xs:element name="optReason" type="eitc:OptReasonType"/>
	<xs:simpleType name="OptReasonType">
		<xs:annotation>
			<xs:documentation>Reason for Opting.</xs:documentation>
		</xs:annotation>
		<xs:union memberTypes="eitc:OptReasonEnumeratedType eitc:EiExtensionTokenType"/>
	</xs:simpleType>
	<xs:simpleType name="OptReasonEnumeratedType">
		<xs:annotation>
			<xs:documentation>Enumerated Reasons for Opting.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:token">
			<xs:enumeration value="economic"/>
			<xs:enumeration value="emergency"/>
			<xs:enumeration value="mustRun"/>
			<xs:enumeration value="notParticipating"/>
			<xs:enumeration value="outageRunStatus"/>
			<xs:enumeration value="overrideStatus"/>
			<xs:enumeration value="participating"/>
		</xs:restriction>
	</xs:simpleType>

In using the most common tool sets (which seem based on either SAX or MSXML), this requires extra work to get to the enumerated values and increases not only the difficulty of code, but the complexity of code. Add an element instantiating each to make coding simpler.

In the example above, this would be:

	<xs:element name="optReasonEnumerated" type="eitc:OptReasonEnumeratedType"/>

This does not change the messages or the information content, but makes coding easier. It is also consistent with NIEM expectations, perhaps for the same reason.

-- 
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