All,
The attached BIRDs were updated with editorial changes by the Quality Task
Group (with MM, ML, Lance Wangy, Bob R.). These BIRDS are distributed for
discussion at the Editorial Task Group Meeting on Wednesday, June 14, 2017.
A major editorial change: All must à shall.
Bob
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Monday, June 12, 2017 12:55 PM
To: ibis-editorial@xxxxxxxxxxxxx; 'IBIS-Interconnect'
Subject: [ibis-editorial] Re: [ibis-interconn] Re: Draft2 - RE: BIRD189.4
Draft 1
Mike,
Are you asking about pending BIRD189.4 or BIRD158.6 or both?
I believe we intended to have relative paths in all cases (Ts4file parameter
for .ami, .ibs files for the NA choice for the [Interconnect Model Set]
below, and sets relative to the .ims under the .ibs location).
The [Interconnect Model] is contained within the same-level [Interconnect
Model Set]. Each [Interconnect Model] subparameter File_TS or File_IBIS-ISS
can reference .ts or .iss file relative the location of the [Interconnect
Model Set] location according to the example syntax (without relative
paths):
[Interconnect Model Set Selector]
All_pins_iss NA | An [Interconnect Model Set]
is
| present in the .ibs file
All_pins_touchstone 8_pin_s16p.ims | The [Interconnect Model Set]
is
| stored in a separate .ims
file
[End Interconnect Model Set Selector]
Bob
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Monday, June 12, 2017 11:28 AM
To: Bob Ross; ibis-editorial@xxxxxxxxxxxxx; 'IBIS-Interconnect'
Subject: [ibis-interconn] Re: Draft2 - RE: BIRD189.4 Draft 1
Bob,
Thanks! Key question: did we *intend* to support relative paths (below the
.ibs location) for files such as TS4File? If so, we certainly need to make
the text clear. If not, we will need to ensure clear instructions
differentiating between where relative paths are supported and where they
are not across the specification for all IBIS formats.
- MM
From: Bob Ross [mailto:bob@xxxxxxxxxxxxxxxxx] ;
Sent: Saturday, June 10, 2017 12:35 PM
To: ibis-editorial@xxxxxxxxxxxxx; 'IBIS-Interconnect'
<ibis-interconn@xxxxxxxxxxxxx>
Cc: Mirmak, Michael <michael.mirmak@xxxxxxxxx>; bob@xxxxxxxxxxxxxxxxx
Subject: Draft2 - RE: [ibis-interconn] BIRD189.4 Draft 1
Michael,
I made a few more changes as Draft2 (attached) and by adding a few more
file reference names in place of file name and clarifying that the
File_TS or File_IBIS-ISS files are relative to either the referencing .ibs
or ims files .
The next version will be BIRD189.3, and its date is TBD. These changes and
some other changes can be seen with the final markup selection.
There could be some other language to make this BIRD align with pending
BIRD186.3.
--------
Also, pending BIRD158.6 is impacted because the parameter Ts4file now can be
defined as a file reference relative to the directory location of the .ami
file.
Bob
From: ibis-interconn-bounce@xxxxxxxxxxxxx
[mailto:ibis-interconn-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Friday, June 9, 2017 1:52 PM
To: ibis-editorial@xxxxxxxxxxxxx; IBIS-Interconnect
(ibis-interconn@xxxxxxxxxxxxx)
Subject: [ibis-interconn] BIRD189.4 Draft 1
Please find enclosed Draft 1 of BIRD189.4. This draft makes a number of
minor changes to maintain compatibility with the rules defined in BIRD186.3,
Draft 9:
1) Used stem instead of base name.
2) Added the word specified to ensure the actual directory location
(relative path) is stated, where needed, in file references.
3) Used the phrase (i.e., a file reference containing a relative path
to a directory below that of the referencing .ibs file is permitted) in
several locations.
4) Specified that the .ims file named under [Interconnect Model
Selector] is really a file reference, which must correspond to the rules in
Section 3.
5) Updated Background Information/History to reflect the changes
above.
The key question for (2) above is whether we intend to allow relative paths
(below the directory containing the calling .ibs file) in the entries for
File_IBIS-ISS, File_TS, etc. Do we? If so, we should probably show at
least one example containing a relative path.
Comments and questions are, of course, welcome. Thanks in advance.
- MM
Attachment:
bird186.3_draft10b.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Attachment:
bird189.4-draft2.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
