XTCE12 — Clear Up Calibrated/Uncalibrated Values in Schema

Description Kevin Rice 2007-10-22 20:56:01 BST
XTCE has several locations within it where values need to be supplied, in many
cases they may be calibrated or uncalibrated values and an associated attribute
is supplied which determines whether the value should be treated as such.
However in some cases, no attribute is supplied and the default is to treat the
value as calibrated. The problem is that this is inconsistent and may not
cover the common industry use cases, especially as related to alarms (limits).
This bug report lists all the areas that use such a value in XTCE where an
attribute is not supplied along with it to set whether the value should be
calibrated or not. These areas need to be considered and an attribute supplied
if appropriate.
The following list may not be exhaustive (although it needs to be) and some may
make more sense than others in terms of supplying calibrated or uncalibrated
values; that needs to be determined (through use cases) and schema changes
applied consistently to all these areas in the next revision.
ParameterSet/parameter@initialValue
Verifiers/ParameterValueChange/Change@value
StringParameterType/SizeRangeInCharacters@min,max
StringParameterType/

Alarm/EnumerationAlarmList/EnumerationAlarm@enumerationValue

• (attributes is a string, is it the enum value, or is it label?)
  IntegerParameterType/toString/RangeEnumeration
  IntegerParameterType/StaticRangeAlarm
  IntegerParameterType/ChangeAlarms
  FloatParameterType/StaticRangeAlarm
  FloatParameterType/ChangeAlarms
  RelativeTimeType/ChangePerSecondAlarms
  ArgumentList/Argument@initialValue
  ParameterToSetList/../NewValue

Add Clarifying Annotation

This will be clarified by annotating the associated elements in the schema.