Issue 7981: initialValue attribute only exists for a ParameterType or ArgumentType (xtce-ftf) Source: Integral Systems (Mr. Charles Gerry Simon, gsimon(at)integ.com) Nature: Uncategorized Issue Severity: Summary: . In version 1.11 of the schema there was an initialValue attribute for a Parameter in the ParameterSet but this was removed in 1.12. Now the initialValue attribute only exists for a ParameterType or ArgumentType. I think it would make more sense if the initialValue was a Parameter attribute and not a ParameterType attribute since there could be multiple instances of the same ParameterType. Right now each of these instances would have the same initialValue but I think what you really want is for each instance to be able to define its own intialValue if it has one. Right now if you have a Type but you want to have different initalValues for it you have to create multiple Types and I think this makes more work than is really necessary. Noted. I think this is going to be an ongoing debate amoung XTCE enthusiasts. Right now the Parameter in ParameterSet is very simple; it is not 'type' aware. One of the problems we'd have in giving it an initial value is that we couldn't type check it by the XML validator. Because ParameterType in ParameterTypeSet knows it's type it can type check (i.e., the initialValue for an IntegerParameterType will only accept an integer, the initialValue for a StringParameterType accepts a string ...). 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: 2. 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.