XTCE13 — CustomAlarmType has wrong parent

The CustomAlarmType appears to extend BaseAlarmType, where as it should just be an extension of InputAlgorithmType (or similar). The result is there are three name attributes to fill in if you want to do so.

In fact because the AlarmType is the base for all the various DefaultAlarms, the CustomAlarm should probably extend a stubby version of InputAlgorithm without a name or description attribute.

it's right, but ugly

The issue is what appears to be duplication of attributes. But the way to read it is the Alarm has an optional name, the custom alarm HAS A inputAlgorthm – and this could have it's own name.

this all came about because the alarms now have a common base ... which includes an optional name.

So while a little ugly or even confusing ... it's right.