Michael,
We could consider sending out a Draft 6 with these changes as part of the vote
solicitation email one week before the OF meeting on the 27th, and I could
simply note that the minor editorial changes are captured on the Editorial
email reflector archive.
Randy
From: Mirmak, Michael <michael.mirmak@xxxxxxxxx>
Sent: Friday, January 6, 2023 1:03 PM
To: Randy Wolff <rrwolff@xxxxxxxxxx>; arpad.muranyi@xxxxxxxxxxx;
ibis-editorial@xxxxxxxxxxxxx
Subject: RE: [ibis-editorial] Re: [EXT] Re: IBIS 7.2 Draft 5 Editorial Updates
CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
recognize the sender and were expecting this message.
Will all these changes be clearly understood if we need to raise and dispose of
them in an IBIS Open Forum approval meeting? Even in a separate document, they
may be a bit overwhelming for a single motion.
* MM
From:
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>
<ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>>
On Behalf Of Randy Wolff
Sent: Wednesday, January 4, 2023 4:15 PM
To: arpad.muranyi@xxxxxxxxxxx<mailto:arpad.muranyi@xxxxxxxxxxx>;
ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] Re: [EXT] Re: IBIS 7.2 Draft 5 Editorial Updates
Bob also caught that the Examples for Modulation_Levels (pg. 286-287),
PAM_Thresholds (pg. 287), and PAM_Offsets (pg. 288) need to be changed to
Courier New font.
Randy
From:
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>
<ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>>
On Behalf Of Muranyi, Arpad
Sent: Tuesday, January 3, 2023 4:12 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [EXT] [ibis-editorial] Re: IBIS 7.2 Draft 5 Editorial Updates
CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
recognize the sender and were expecting this message.
Randy,
All good catches. I agree to correct each one of them
as you suggest.
Arpad
=============================================
From:
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>
<ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>>
On Behalf Of Randy Wolff
Sent: Tuesday, January 3, 2023 12:26 PM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] IBIS 7.2 Draft 5 Editorial Updates
Editorial,
In reviewing the parser contract for IBIS 7.2, we found the following editorial
changes needed in IBIS 7.2 Draft 5:
This should be "string_literal" (lowercase) on page 248:
Parameter: Tx_Impulse_Input
Required: No, and illegal before AMI_Version 7.2
Direction: Tx
Descriptors:
Usage: Info
Type: String
Format: Value
Default: <String_literal>
Description: <string>
On page 286, the highlighted text has an extra ".":
Modulation_Levels Common Name
2 NRZ, PAM2
3 PAM3, Duobinary
4 PAM4
5 PAM5
....
8 PAM8
...
Required statement should be updated to suggested text in highlight on page 287:
Parameter: PAM_Thresholds
Required: Yes, illegal if Modulation_Levels is not specified.
Required: Yes, if Modulation_Levels is specified, illegal if
Modulation_Levels is not specified
On page 376 under [Designator Pin List] the highlighted text should be changed
to "may optionally be":
Usage Rules: The [Designator Pin List] keyword shall be followed by the
subparameter names "signal_name", "signal_type", and "bus_label", serving as
column headings. The keyword and the list of its subparameters shall be
followed by rows of information containing all designator pins references by
terminal lines found in all the EMD models contained by EMD Sets and referenced
by all EMD Groups found in the .emd file. Designator pin names which are not
referenced by any terminal line Qualifer_entry in any of the EMD models may be
optionally be listed under the [Designator Pin List] keyword.
Thanks,
Randy