XTCE13 — Add an optional attribute to ComparisonList to make it all ORs

For some reason this idea flew into my funnel this morning. I was looking at the ComparisonList and noticed the annotation to it said there's an implied 'and' between all the comparisons in the list.
I then thought: Why not add an attribute to override that to set to it all ORs? Why would that be a bad thing?
Unable to come up with any reason that this would be a bad thing, I decided it must be a good thing and that a good thing should be an issue.
The main reason to support the OR case is that it's simply a little easier to build out the comparisonlist than the booleanexpression. And one assumes that if it's a good thing to have an ANDed ComparisonList for convenience, that it seems like symmetrically speaking it would be a good thing to have ORed ComparisonList for conveniences as well. Basically this is just a suggested small change for the convenience purposes.

An OR Based Comparison List is Possible

It is reasonable to create an "or"-based ComparisonList element optional attribute. This has a specific use case that is commonly seen where a telemetered container comes from more than one onboard computer and that computer is annotated in the header.

At present, it has been agreed to leave this to a future revision as it for sure introduces another implementation detail that is otherwise covered by a different part of the comparison logic already within the specification.