Arpad, I also agree that there should be no rules on Model Specific parameters. Unfotunately, (Type Tap) parameters must now be of the form tap(-2, tap(-1, tap(0, tap(1, tap(2, . . So the only thing that this BIRD does is allow the user to enter (Type Tap) parameters as tap(M2, tap(M1, tap(C0, tap(P1, tap(P2, . . Walter From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Tuesday, February 14, 2012 2:43 PM To: IBIS-ATM Subject: [ibis-macro] Re: Parameter Naming Rules BIRD Walter, I think this is a good idea. For reserved parameters I think we will need to do something you are suggesting, but for Model Specific parameters I am not sure we can or should. The name of the parameter in that case should be left to the model maker, not the spec. The best we can or should do for Model Specific parameter names is a general rule on what characters are prohibited, for example "-", and what characters can't be used in the first position of the parameter name. I don't think we should get into the business of defining naming conventions, such as what you are suggesting for the tap names. Thanks, Arpad ============================================================== From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz Sent: Monday, February 13, 2012 1:16 PM To: IBIS-ATM; Todd Westerhoff; Adge Hawes Subject: [ibis-macro] Parameter Naming Rules BIRD Importance: High All, I plan to submit the enclosed BIRD to the Open Forum. Please read and be prepared to decide in this Tuesday's ATM meeting whether this BIRD should be considered for 5.1 or be deferred to 5.2. Walter Walter Katz wkatz@xxxxxxxxxx Phone 303.449-2308 Mobile 720.333-1107