================================================================================ IBIS EDITORIAL TASK GROUP http://www.ibis.org/editorial_wip/ Mailing list: ibis-editorial@freelists.org Archives at http://www.freelists.org/archive/ibis-editorial/ ================================================================================ Attendees from October 3, 2018 Meeting (* means attended at least using audio) ANSYS Curtis Clark Cadence Design Systems Bradley Brim Intel Corp. Michael Mirmak* Keysight Technologies Radek Biernacki Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield*, Randy Wolff SiSoft Walter Katz, Mike LaBonte* Teraspeed Labs Bob Ross* Michael Mirmak convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of minutes from the September 28 meeting: Mike LaBonte moved to approve with this change. Bob Ross seconded. Minutes were approved without objection. Review of ARs: - Michael to send out the latest IBIS 7.0 draft and checklist to the group. - Michael reported this was done and thanked Mike LaBonte for posting. Opens: - Michael asked Arpad Muranyi if there has been any feedback on BIRD196. Arpad replied he has not received any. Michael asked if the plan is still to vote on this BIRD at the October 12th IBIS Open Forum meeting. Arpad replied that is his understanding. Mike commented it will be on the agenda. Editorial review of ver7_0_181003.docx and the task checklist: Michael stated the next checklist item is number 36, which is BIRD189.7 on Interconnect Modeling. He noted that we may need to go through and check some of notes in the background items of this BIRD. Michael stated the first change in BIRD189.7 is the A_gnd description to the simulator global reference node. In the Component section, we add the [Interconnect Model Group] keyword after the [Alternate Package Models] keyword. Bob commented we make reference to the Syntax Rules section and asked if this is the correct section number. Michael agreed this is an issue. Justin commented that this is an issue here and in other locations such as the Back-Channel section. Bob asked if we want to reference the Syntax Rules or the General Syntax Rules and Guidelines section. Michael replied when we are referring to the complete section of General Syntax Rules and Guidelines this is different from specific item references in the Syntax Rules section. Bob stated we will need to go through these in detail. Michael suggested to add a checklist item for this. Bob agreed. Michael added a checklist item for checking references to Section 3.2 Syntax Rules vs. Section 3 General Syntax Rules and Guidelines. Michael stated the [Interconnect Model Group] keyword, the examples, and the [End Interconnect Model Group] keyword are added to the Component section. Bob asked about [Pin Mapping] following the [Interconnect Model Group] text. Michael replied this is correct per the BIRD and noted the [Pin Mapping] text has some small changes. The [Bus Label] and [Die Supply Pads] keyword definitions are inserted after [Pin Mapping] and before [Diff Pin]. Bob asked about [Die Supply Pads] and the summary text about bus_label. Michael noted we may need some additional text about this. Mike noted an extra space after the word "designate" in the [Die Supply Pads] text. Bob commented we also have a problem with making plurals of reserved words which can distort the meaning. In Section 7 Package Modeling, Michael noted BIRD189.7 adds a new introduction and a new Rules of Precedence section. Bob asked about the reference to Chapter 12 and if this should be "chapter" or "section". Mike asked if we have a checklist item about this. Michael stated we do not and added a new item for this global change. Bob commented these are brought in by the BIRD. Michael asked if we want to change this now. He noted 3 of the 5 instances of the word "chapter" are in the BIRD189.7 changes. The other instances are in the Multi-Lingual section. Michael changed all these instances but left the checklist item open. Bob commented he prefers "chapter" over "section" for the top-level headings, but he doesn't want to make this change now. Michael stated the [Description] keyword has the line length restriction removed. He noted we did refer to Section 12 as Chapter 12 in the actual BIRD. He stated it is a simple text add for all of the Section 12 text. This includes all of the examples and figures. The new text is inserted as written in the BIRD after Section 11 all the way to the end of the IBIS document. Bob stated we often put the [End] keyword as the last keyword. Michael noted the [End] keyword is currently the last keyword of Section 9. Bob asked about the Package Model and the EBD sections which require the [End] keyword. Michael asked if the [End] keyword is defined in the wrong place and if it is required for .ims files. Bob replied it is required for .ims files. He commented that it is a question of where we define the [End] keyword and if it should be defined in multiple places. Mike said he would be in favor of moving the [End] keyword to after the Interconnect Model section. Arpad stated he was not sure about moving it, but we should add .ims to the [End] keyword description. Michael asked if we want a note referencing the [End] keyword in each of the sections requiring it. Bob stated he prefers to add the [End] keyword definition to each of the sections. Mike asked how this is done for the [File Name] keyword. Bob replied that we reference [File Name] but only define it once. Michael asked where we would want to move the [End] keyword to. Arpad suggested to move it to the end of Section 5. Bob was concerned that if we do this the order of the keywords is not preserved. Arpad noted that we use the [End] keyword in other file formats which are not defined in order. Michael agreed that we do have the problem that we typically put keywords in the order they should appear in the file. Arpad asked if we are going by the scoping or by the order of the keywords. Bob noted that Section 5 also contains [Component] definitions, and it is not the header and base [Model] keywords. Arpad stated the problem with adding the definition to each section is that it is only required for separate files. Bob noted EBDs cannot be embedded in a .ibs file, while Package and Interconnect Model Sets can be in the .ibs file. Michael suggested to add the [End] keyword to Section 4 and rename Section 4. Mike suggested to rename Section 4 to File Header and Footer Information. Bob noted that the Section 4 keywords including [IBIS Ver] are required for other formats such as .ebd, .pkg and .ims. Michael added a checklist item for renaming section 4 and adding the [End] keyword to it. Mike suggested to add all the required file formats to the [IBIS Ver] keyword. Bob stated we might want to get more specific with which versions support which formats. We marked checklist item 36 as verified. Michael noted he will not be able to attend on Friday. Mike volunteered to be the document editor and host the meeting on Friday. Michael will send out the latest draft and checklist [AR]. Arpad moved to adjourn. Bob seconded. The meeting adjourned without objection. The next meeting will take place Friday, October 5. Open Technical Questions: 1. BIRD182: POWER and GND [Pin] signal_name as [Pin Mapping] bus_label a. Is a bus_label created even if we don't have [Pin Mapping], [Bus Label], or [Die Supply Pads] through the [Pin]? b. Is a bus_label short created for legacy package models based on the second column of [Pin] when we do not have a [Pin Mapping] entry?