-
Key: XTCE13-189
-
Status: open
-
Source: Boeing ( Mr. David Overeem)
-
Summary:
It appears that when several base alarm types were made (BooleanAlarmType, BinaryAlarmType, EnumerationAlarmType, NumericAlarmType, etc) that the BinaryAlarmType did not get completely applied. This only affects the class hierarchy when using a code generator and does not affect user documents.
This "BinaryContextAlarmType" should have called out xtce:BinaryAlarmType as the extension instead of xtce:AlarmType:
<complexType name="BinaryContextAlarmType">
<complexContent>
<extension base="xtce:AlarmType">
<sequence>
<element name="ContextMatch" type="xtce:ContextMatchType"/>
</sequence>
</extension>
</complexContent>
</complexType> -
Reported: XTCE 1.2 — Mon, 10 Feb 2025 16:45 GMT
-
Updated: Fri, 14 Feb 2025 21:37 GMT
XTCE13 — Mistake in AlarmType refactoring
- Key: XTCE13-189
- OMG Task Force: XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF