================================================================================ 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 December 12, 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* Mike LaBonte convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of minutes from the December 11 meeting: Bob Ross moved to approve. Mike LaBonte seconded. Minutes were approved without objection. Review of ARs: - Michael Mirmak to check the other instances of "Example:" for spacing issues. - Mike reported this was done by Michael. - Michael to send the document and checklist to Mike. - Mike reported this is done and the documents were posted and sent out. Opens: - Mike made a few changes in the document, which he would like to review. - Bob has comments that he would like to review and discuss. Mike stated we can get to these, and we can decide if we want to make the changes or defer more discussion. - Mike asked if we should discuss the IBIS 7.0 Draft Known Issues. Bob suggested to defer this until we have more people. Mike agreed and suggested we should also defer discussion of the formatting rules until we have more participation. Review of ver7_0_181211.docx: Mike showed a comparison document highlighting the changes he made. Many of the changes were line spacing issues where some of the lines were 10 point rather than 12 point Times New Roman. He eliminated lines above the figure captions. The heading for Section 10.5 was separated from the text. Bob suggested every first-level and second-level section headings should start on a new page. Mike noted there is an exception to this if the text of the second-level section is very short. Bob stated he found some major sections which do not start on a new page. Bob asked if we need two spaces between each keyword or parameter. Mike suggested to defer this question until Michael can participate. Arpad asked if Figure 50 should be centered. Bob noted Figure 49 has the same issue. Mike checked the figures in the Interconnect Modeling section to ensure they are centered and set to "In Line with Text". Bob thought the Figure 49 caption is too close to the picture. Mike increased the spacing for Figure 49. Arpad suggested to remove the blank lines at the beginning of Example 2 on page 314. Bob asked if there should be extra space after the bullet list on page 8. Mike replied there is typically one line after bullet lists. Bob asked if there should a blank line at the beginning of the bullet list. Mike replied this should be 4 point spacing, same as the new paragraph spacing. He commented we would need to add this to the rules. Bob noted a spacing issue on page 10 between the "Version" sections which are not consistent with page 9. Mike commented all of the bold titles could have some set spacing such as a fourth-level heading. Bob commented that Section 3 (page 15) has it own page. There is another bullet list issue on page 16. On page 26, Bob suggested we could reduce the amount space between the keywords. Mike agreed this might look better. On page 28, Bob noted we have one word. Mike stated we have a checklist item for pagination, and these can be fixed with the "Keep with next" setting. On page 30, Bob commented the first paragraph has no new paragraph spacing. On page 32, there is an extra line above "Usage Rules:". On page 33, there is another list spacing issue. Mike corrected these issues. Arpad asked if the items in the list should have 4 point spacing separating them. Mike stated this is an open question. On pages 36, 39, and 41, Bob noted there are bullet lists without spaces afterwards. Mike fixed these. Bob suggested to go through the entire document to deal with the list spacing, as there are many lists with inconsistent spacing. Mike stated he would like to discuss this and decide formal list spacing of rules. Bob suggested Section 7.2 and Section 7.3 need to be on new pages. Mike stated, according the Michael's formatting rules, second-level headings shorter than a page may not start on a new page, which applies to Section 7.2. Bob suggested Section 7.3 should start on a new page. Arpad stated Section 7.3 does not need a new page. Mike noted Section 6.2 is on a new page. Bob stated that "major" second-level sections such as Section 7.3 and Section 10.2 should begin on new pages. Arpad suggested only the first-level sections such as Section 6 and Section 10 to start on a new page. Summary of spacing rule comments/questions: 1. Should lists be followed by a blank line? 2. Should items in a list have 4 point spacing? 3. Are two blank lines necessary to separate keywords and Reserved Parameters? 4. When do second-level headings require a page break? Mike will send out the latest draft and checklist [AR]. Mike noted there was no change to the checklist. Bob suggested to keep the checklist and document file names in sync. We tentatively agreed to meet on Friday. Mike will check if Michael Mirmak can make host. Arpad moved to adjourn. Bob seconded. The meeting adjourned without objection. The next meeting will take place Friday, December 14, at 8 AM Pacific. 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?