Arpad,
I meant BIRD189.4 since BIRD189.3 is already uploaded,
http://www.ibis.org/birds/
Bob
From: Muranyi, Arpad [mailto:Arpad_Muranyi@xxxxxxxxxx] ;
Sent: Monday, June 12, 2017 12:14 PM
To: bob@xxxxxxxxxxxxxxxxx; ibis-editorial@xxxxxxxxxxxxx; 'IBIS-Interconnect'
Cc: Michael Mirmak
Subject: RE: [ibis-editorial] Draft2 - RE: [ibis-interconn] BIRD189.4 Draft
1
Bob,
I am confused about "The next version will be BIRD189.3", since the attached
file was "BIRD189.4 Draft 2".
Thanks,
Arpad
==============================================================
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Saturday, June 10, 2017 2:35 PM
To: ibis-editorial@xxxxxxxxxxxxx; 'IBIS-Interconnect'
<ibis-interconn@xxxxxxxxxxxxx>
Cc: Michael Mirmak <michael.mirmak@xxxxxxxxx>; bob@xxxxxxxxxxxxxxxxx
Subject: [ibis-editorial] 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
