All,
Per the discussion on November 26, 2019, here is an updated draft3 for
discussion at the next meeting.
Bob
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Monday, November 25, 2019 11:11 AM
To: bob@xxxxxxxxxxxxxxxxx; 'IBIS-ATM'
Subject: [ibis-macro] Re: IBIS BIRD197.6_draft3 Editorial Suggestions
Bob,
For the sentence improvement, I would submit that may, shall and
should are the preferred choices for standards work, depending on whether
we are conveying a flexible option, a requirement or a recommendation,
respectively. Must should shall is to be avoided.
* MM
From: ibis-macro-bounce@xxxxxxxxxxxxx <ibis-macro-bounce@xxxxxxxxxxxxx> On
Behalf Of Bob Ross
Sent: Monday, November 25, 2019 11:07 AM
To: 'IBIS-ATM' <ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Re: IBIS BIRD197.6_draft2 Editorial Suggestions
All,
Attached is draft2. I moved the Application Scenarios to the directly under
the related bullets in User Notes and forward referenced the Example.
The User Notes include Michael Mirmaks suggested improvement.
The waveform range is stated from A to B to include the endpoints.
---
I think this sentence can be improved:
From
The Rx AMI_GetWave output waveform returned by the AMI model must be
nominally centered around zero Volts.
To:
The Rx AMI_GetWave output waveform returned by the AMI model must be
nominally centered at zero Volts. ß
Or
The Rx AMI_GetWave output waveform returned by the AMI model must be
centered around zero Volts.
Should must be replaced with should?
------
There should be a default value statement such as
If DC_Offset is not specified, the executable model shall assume 0.0 V
------
Also, a statement about reporting DC_Offset value should be added to avoid
ambiguity about the range:
The EDA tool may report the actual DC_Offset value used.
Bob
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Friday, November 22, 2019 8:15 PM
To: 'IBIS-ATM'
Subject: [ibis-macro] Re: IBIS BIRD197.6_draft1 Editorial Suggestions
Michael,
I am still working on this, but I added your suggested change.
Bob
From: Mirmak, Michael [mailto:michael.mirmak@xxxxxxxxx] ;
Sent: Friday, November 22, 2019 2:32 PM
To: bob@xxxxxxxxxxxxxxxxx; IBIS-ATM
Subject: RE: [ibis-macro] IBIS BIRD197.6_draft1 Editorial Suggestions
I would like to suggest a minor alteration to the Other Notes section,
specifically:
Other Notes:
1. It is the responsibility of the EDA tool to determine the input value
of DC_Offset. This shall include, but is not limited to, channel effects as
well as the impact of any equalization imposed by the transmitter. The EDA
tool may use any method to do this.
Thank you.
* MM
From: ibis-macro-bounce@xxxxxxxxxxxxx <ibis-macro-bounce@xxxxxxxxxxxxx> On
Behalf Of Bob Ross
Sent: Monday, November 18, 2019 1:40 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] IBIS BIRD197.6_draft1 Editorial Suggestions
All,
Per some discussion and AR at the October 18, 2019 teleconference, a
suggested revision is attached along with the original BIRD197.5. The main
change is to add titles to 1. And 2. I do not know if I got this exactly
right.
There are also some other minor cleanup changes.
This is for ATM discussion.
Bob
--
Bob Ross
Teraspeed Labs
www.teraspeedlabs.com <http://www.teraspeedlabs.com/>
bob@xxxxxxxxxxxxxxxxx
Direct: 503-246-8048
Office: 971-279-5325
Attachment:
bird197.6_draft3.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
