Mike, I tend to agree with Walter. On pg. 144 of the PDF document "Description" is on the same scope as "Reserved_Parameters" or "Model_Specific". Here it is optional. On the other hand, I see a lot of "must be in the following format" statements when the spec describes the format of the parameters (pg. 144, 145, 146, 149): <<Picture (Enhanced Metafile)>> <<Picture (Enhanced Metafile)>> <<Picture (Enhanced Metafile)>> <<Picture (Enhanced Metafile)>> In these sections the specification doesn't seem to make "Description" optional. On the other hand, on pg 146 I see this for Tx_Jitter: <<Picture (Enhanced Metafile)>> which is in direct contradiction with what the previous page said about what the format of Tx_Jitter and Tx_DCD should be if specified. Similarly, on pg. 147, the Rx_Clock_PDF section has this: <<Picture (Enhanced Metafile)>> which is also in direct contradiction with what the previous page said about what the Rx_Clock_PDF and Rx_Receiver_Sensitivity format should be if specified. In addition to the contradicting format examples for Rx_Clock_Sensitivity I also found a cut and paste error on pg. 147: <<Picture (Enhanced Metafile)>> where the last sentence should not talk about Rx_Clock_PDF but Rx_Clock_Sensitivity... So what was the intent? It seems that for the reserved parameters, none of the parameter description sections use the "Description" and the example on pg. 150 seems to follow that rule. Also, it seems that the example on pg. 150 does make use of the "Description" and the format for the model specific on pg. 149 describes that the "Description" is required. If I could blame all this on cut and paste errors, than I could see that Walter's comments may have already been around in the mind of people who wrote these sections in the spec, and the intention may have been that the reserved parameters wouldn't require (or use) "Description" but the model specific parameters would require it. In this case we would only have to remove the "Description" from the format descriptions on pg. 144, 145, 146 but not from pg. 149. If we agree on this, the only question would be to figure out how to fix the spec and what to tell the parser developer. To me it sounds like fixing this would require a BIRD, which raises the usual questions about time line for finishing the parser, vs. getting the BIRD written and approved, etc... Questions, comments? Thanks, Arpad ============================================================== -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz Sent: Wednesday, September 09, 2009 12:01 PM To: michael.mirmak@xxxxxxxxx; IBIS-ATM Subject: [ibis-macro] Re: Description required for Reserved Parameters in AMI files? MM, It can apply to the model where it is optional (page 144 of IBIS 5.0 pdf) | ) | End of Model_Specific section | (Description <string>) | description of the model | | (optional) In all other places it is required, or it is implied that it is required. I personally think that it should not be required for Reserved Parameters (the standard describes what they are and what they do), and should berequired for all Model Specific parameters (to at least force the model maker to document what he is exposing to the user intelligently). But the spec says it is always required (except for the model itself). Bonus question: " " is a valid string. Walter Walter Katz 303.449-2308 Mobile 720.333-1107 wkatz@xxxxxxxxxx www.sisoft.com -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of Mirmak, Michael Sent: Wednesday, September 09, 2009 12:37 PM To: IBIS-ATM Subject: [ibis-macro] Description required for Reserved Parameters in AMI files? A simple question for AMI experts: is "Description" required for Reserved Parameters in AMI files? On page 144 of IBIS 5.0 (PDF version), the following text appears: | ... All reserved | parameters must be in the following format: | | (parameter_name (Usage <usage>)(Type <data_type>) | (Default <values>) (Description <string>)) However, few of the given examples actually follow this usage of Description. Which is correct? Thanks in advance... - MM PS Bonus question: is a null or empty string permissible in "Description?" --------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe --------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe