Issue 7979: CommandContainer under the MetaCommand (xtce-ftf) Source: Integral Systems (Mr. Charles Gerry Simon, gsimon(at)integ.com) Nature: Uncategorized Issue Severity: Summary: In the CommandContainer under the MetaCommand, inside the EntryList, there is a division between groupings of the Parameter/ContainerRefEntries and the FixedValue/ArgumentRefEntries. The problem is what this does is make you have to define ALL your ParameterRefEntries and ContainerRefEntries BEFORE defining any FixedValues or ArgumentRefs inside a CommandContainer. For example, the following sequence of entries would be illegal for a CommandContainer: FixedValueEntry-ContainerRefEntry-ParameterRefEntry-ArgumentRefEntry. Unless there is a legitimate reason for the separation, I think the FixedValueEntry and the ArgumentRefEntry needs to be added to the same grouping that the ParameterRefEntry/ContainerRefEntry is in. You're probably right. We simply extended the EntryListType to create a CommandEntryList type. While this keeps the schema simpler, it does make the XML documents messier. We usually opt for better XML over better Schema. Resolution: Revised Text: Actions taken: December 15, 2004: received issue Discussion: End of Annotations:===== m: Simon C Gerry Contr Det 12/VOC To: "'Smyth, Justin'" Cc: "Vickers, Victoria" , "Wetmiller, Eric" , "Falk, Nathan" , "Graves, Eric" , "'xtce-ftf@omg.org'" Subject: RE: more problems with the XTCE schema Date: Wed, 15 Dec 2004 17:36:10 -0700 X-MS-TNEF-Correlator: X-Mailer: Internet Mail Service (5.5.2657.72) -----Original Message----- From: Smyth, Justin [mailto:jsmyth01@harris.com] Sent: Wednesday, December 15, 2004 12:27 PM To: Simon C Gerry Contr Det 12/VOC Cc: Vickers, Victoria; Wetmiller, Eric; Falk, Nathan; Graves, Eric Subject: more problems with the XTCE schema Hi Gerry, I've identified some more problems/issues with the XTCE schema that I'd like to bring to your attention: 1. In the CommandContainer under the MetaCommand, inside the EntryList, there is a division between groupings of the Parameter/ContainerRefEntries and the FixedValue/ArgumentRefEntries. The problem is what this does is make you have to define ALL your ParameterRefEntries and ContainerRefEntries BEFORE defining any FixedValues or ArgumentRefs inside a CommandContainer. For example, the following sequence of entries would be illegal for a CommandContainer: FixedValueEntry-ContainerRefEntry-ParameterRefEntry-ArgumentRefEntry. Unless there is a legitimate reason for the separation, I think the FixedValueEntry and the ArgumentRefEntry needs to be added to the same grouping that the ParameterRefEntry/ContainerRefEntry is in. You're probably right. We simply extended the EntryListType to create a CommandEntryList type. While this keeps the schema simpler, it does make the XML documents messier. We usually opt for better XML over better