Walter: The rule wording in BIRD154.1 is too rigid and limiting. I would accept: "All entries in List_Typ shall be unique." Example: (List_Type "case1" "case2" "case3" "case4") (Type Boolean) (List True False False True) This should be legal because you might want to correlate this parameter with another parameter that describes the same cases. This is not confusing. Some vendors may want to do this. The rule in BIRD154.1 requires too many checks. This delays the parser development for an optional convenience at the expense of other technical features that the user community really needs. So I strongly advocate the relaxation of the rule to the above rule, which is easy to check. Bob From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz Sent: Wednesday, May 22, 2013 12:48 PM To: 'Bob Ross'; 'IBIS-ATM' Subject: [ibis-macro] Re: BIRD 154.1 Bob, I want to keep my wording. It is important that if two values in List are the same they have the same List_Tip value and if two values in List_Tip are the same they have the same List value. Anything else would be totally confusing to a user. Walter From: Bob Ross [mailto:bob@xxxxxxxxxxxxx] Sent: Wednesday, May 22, 2013 1:00 PM To: wkatz@xxxxxxxxxx; 'IBIS-ATM' Subject: RE: [ibis-macro] BIRD 154.1 Subject BIRD Number Correction from 151.1 to 154.1 I would like this rule relaxed to a suggestion: From All entries in List_Tip shall be unique, except that if two entries in List are the same, then the corresponding List_Tip entries must also be the same. To All entries in List_Tip should be unique, but if two entries in List are the same, then the corresponding List_Tip entries can be the same. That way, we do not have to check this in the parser and we can allow (List 2 1 2 3 4 5) (List_Typ "default_val" "val1" "val2" "val3" "val4" "val5") or other equalities where the List_Typ entries might be different for the same values. I want to simplify parser checking and especially comparison checking within the List for all Types. By making this rule a suggestion, we do not have to check it. In practice, this will not be a problem for developers who use List_Type. Bob From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz Sent: Wednesday, May 22, 2013 8:23 AM To: IBIS-ATM Subject: [ibis-macro] BIRD 151.1 All, Enclosed is IBIS 151.1 for review. The major change is changing Labels in List parameters to List_Tip. I plan on formally submitting this on Thrusday. Walter Walter Katz wkatz@xxxxxxxxxx Phone 303.449-2308 Mobile 303.335-6156