Over on the ParameterSegmentRefEntry element, the "order" attribute appears to require a positive integer. The annotation suggests that 0 is an allowable and useful value. We should clarify for the users.

After examination:

I believe you are correct in that somewhere in all the refactoring, someone missed (completely) updating the annotation on AlarmType. I will add an issue against it for you and we will correct it in the 1.4 release sometime in the next year or two, depending on if there is anything else pressing.

Original Note:

subject: REQUEST INFORMATION

textarea: Hi! I'm working with the XTCE 1.3 standard and I noticed a discrepancy in the schema. I wasn't sure how to reach out to let y'all know about this small issue.

In the schema definition for "AlarmType", the documentation mentions, amongst others, the following XTCE types: CustomAlgorithmType, BinaryAlarmConditionType, and TimeAlarmConditionType. None of those three types actually exist in the schema (although, the others mentioned in that documentation block do exist).

Let me know if there's another channel I should use for this in the future or if you need any additional information from me.

Thanks!