================================================================================ 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 14, 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 12 meeting: Bob Ross moved to approve. Mike LaBonte seconded. Minutes were approved without objection. Review of ARs: - Mike to send out the latest draft and checklist. - Mike reported this was done. Opens: - Mike asked if Bob would like to continue discussing his comments. Bob replied he would like to, but his comments revolve around the vertical spacing rules. We did not come to a decision last time on some of the issues including how to space lists. Mike preferred to wait until Michael Mirmak can attend to discuss the vertical spacing. Michael has sent out a list of rules related to vertical spacing, but these need to be approved. Bob stated we still need to discuss the second-level headings. Review of ver7_0_181212.docx: Arpad suggested to change the other examples in the Interconnect section to be consistent with Example 2 which has an additional comment character in the header. Mike changed this in the other examples. Mike stated, on pages 233 and 234, there were some line spacing issues. On page 299, there was an orphaned keyword line. Mike had corrected these issues. Mike noted Sections 6.1 and 6.2 do not begin on new pages. However, Section 10.2 does start on a new page. Arpad suggested that only the first-level headings should start on new pages. Bob disagreed, stating that some second-level sections are major sections that should start on new pages. Mike noted that Section 10.3 has a page break, while Sections 7.1 and 7.2 are very short and do not make sense to put on a new pages. Bob stated Section 7.3 is a major section that should start on a new page. He suggested that we may need to apply this on a section by section basis. Mike noted that there is a rule proposed by Michael about this. Mike thought the only sections that do not currently follow Michael's rules are the Section 7 second-level headings. Bob stated section 7 looks okay. Justin suggested to put Section 3 and Section 3.1 on the same page. Bob agreed this looks good. Mike asked if we can mark checklist item 79 regarding table alignment as complete as of last meeting. Bob and Arpad agreed. We marked this as verified. For checklist item 83 on the vertical spacing, Mike did a search on new paragraphs. And, he can reliably find instances of too many spaces. The size and fonts of any blank lines can also be determined from the paragraph symbols. Mike asked if we can mark this item as done, with the exception of the two lines between keywords. Arpad suggested to wait until we settle the spacing between the keywords topic. Mike suggested to mark checklist item 83 as complete and add a new checklist item for replacing the paragraph spacing above keyword/parameter/function with styles. Mike asked where we stand on plurals and possessives checklist item 81. Bob stated he wasn't sure on the status, as Michael had added this item. Arpad stated, when we discussed previously, it was noted there is industry disagreement on how to handle this. For checklist item 82 on "Reserved Parameters" as lower case, Mike found four instances of "Reserved parameters" and made them upper case. Mike commented the other issue was for submodel. Bob stated that submodel and Reserved Parameters are different concepts. He preferred to make no changes to submodel or model, as we would have to review each one of these changes. Mike agreed. We marked checklist item 82 as verified. Mike asked for checklist item 72 if we have no new BIRDs. Bob stated this is correct, but we have already done BIRD196. Mike commented that to fix the plurals and possessives properly would require more involved effort. Bob suggested to leave this open until Michael can discuss it. Mike stated we do have four instances of keywords followed directly by an apostrophe 's', and he had suggested to insert the word "keyword" before the apostrophe 's'. Bob thought this is okay. Mike made this change, but he left checklist item 81 open for feedback from Michael. We agreed to tentatively meet Tuesday and Wednesday next week. Bob stated we still need to resolve the line spacing for keywords. Mike stated he could prototype adding the style to the keywords and parameters. Bob thought this would be good to see how it looks. Mike will send out the latest draft and checklist [AR]. Mike will send out a prototype document with the styles for keywords and parameters [AR]. Arpad moved to adjourn. Bob seconded. The meeting adjourned without objection. The next meeting will take place Tuesday, December 18, at Noon 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?