XTCE12 — CommandContainer issue

Another question involving the CommandContainer. In the CommandMetaData
there are two ways to create a CommandContainer: inside a MetaCommand or
inside the CommandContainerSet. For some reason the CommandContainer inside
the MetaCommand has an ArgumentRefEntry and a FixedValueEntry but the
CommandContainer inside the CommandContainerSet does not. The reason they
are different is that the CommandContainer inside the MetaCommand is of
CommandContainerType, but the CommandContainer inside the
CommandContainerSet is of SequenceContainerType. Is this an error in the
schema or is there a reason that these CommandContainers are of different
types?

The reason why there's a CommandContainer inside the CommandContainerSet is
so containers that are used/re-used by many commands could be defined there.
Since these Containers are not associated with any particular MetaCommand
and arguments are local to a MetaCommand, it would be a mistake to allow
them to contain arguments - we wouldn't know which argument to use.

Agree with the description

It is correct that the CommandContainerSet has "CommandContainer" elements that are simply SequenceContainers in nature. It cannot have Arguments because arguments are local to a MetaCommand. They are of somewhat limited value because they can only contain parameters, but they can be used as base containers in many MetaCommands, to provide parameter entries for "system generated fields", such as header items for the command that would not be part of the operator driven set of Arguments to provide. The author of the comment was able to determine the utility of the CommandContainerSet from the existing specification and schema. Since we agree with the author of the question, we close without change.