Arpad, Since Supporting_Files will be a reserved parameter, it can have a clarification that all of the elements of the list are supporting files/directories. If it were a table then I would have one row for each supporting file or directory, e.g.: (Supporting_Files (Usage Info)(Type String) (Description "Additional files that support this model") (Table ( "my_stuff_dir" ) ( "m1.s4p" ) ( "m2.s4p" ) ( "m3.s4p" ) ) ) Walter From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Tuesday, September 18, 2012 7:15 PM To: 'IBIS-ATM' Subject: [ibis-macro] Another comment on BIRD 121 (Data Management) Walter, I discovered a logical problem in BIRD 121. The "Supporting_Files" is a "List", but the definition of "List" on pg. 177 of v5.1 says this: List <default value> <value> <value> <value> ... <value> This defines a discrete set of values from which the user may select one value In the context of BIRD 121, the EDA tool supposed to read the entire list and take the actions described in the definition of this parameter in BIRD 121. Using the example in the BIRD: (Supporting_Files (Usage Info)(Type String) (List "my_stuff_dir" "m1.s4p" "m2.s4p" "m3.s4p") (Description "Additional files that support this model") ) "my_stuff_dir" is not a default value in case the user doesn't make a selection in a tool GUI dialog. The entire list is to be used by the EDA tool for locating the supporting files. I think this would work better if we used Table instead of List. A table can have only one row, but each column in that row is valid data which is to be used simultaneously. Using List this way introduces inconsistencies in the spec and is very confusing. Thanks, Arpad ==================================================================