Bob,
Draft 3 removes the 128 “full path name” rule, and advises the user about
this.
Walter
3. “file name” shall mean the name of the file, including the path
relative to the directory containing the file that references the “file
name”. A “file name” may not be a directory. The “file name” has three
sections, “path name” (optional), “base name” and “extension name”
(characters following the last “.” in “file name”). The number of character
in the combined “base name” and “extension name” shall not exceed sixty-four
(64) characters. The number of characters in “path name” shall not exceed
sixty-four (64) characters.
Definitions:
“path name” The path of a “file name” in any file reference in a parent file
relative to the location of the parent file.
“full path name” The path of a file in any file reference in a parent file
which itself is referenced by a file referenced by an IBIS file, relative to
the location of the IBIS file. There can be many levels of referenced files.
“absolute path name” The path of a file relative to the root of the file
system directory.
The model maker should be aware that excessive nesting of file paths may
result in “absolute path names” that are longer than a 260 character hard
limit on Windows file systems.
Walter Katz
wkatz@xxxxxxxxxx <mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308
Mobile 303.335-6156
From: Bob Ross [mailto:bob@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 19, 2017 2:50 PM
To: dmarc-noreply@xxxxxxxxxxxxx; 'Walter Katz' <wkatz@xxxxxxxxxx>
Cc: 'Muranyi, Arpad' <Arpad_Muranyi@xxxxxxxxxx>; 'IBIS-ATM'
<ibis-macro@xxxxxxxxxxxxx>
Subject: RE: [ibis-macro] Re: Bird 186.3_Draft_2 (character length
restrictions on file naming rules.
Walter,
I agree, this helps. However, I think that the full path name limit of 128
should not be a requirement.
This requires parser checking for each referenced file name that could
ripple throughout all subsequent references.
I would rather make this an advisory statement (similar to using lower case
file names for operating system differences).
To avoid exceeding some operating system character limitations (such as 256
characters) that might be created by full path names or absolute path
names, the IBIS file developer is advised to use shorter file names and
directory names if several levels of directory calls are used.
Bob
From: ibis-macro-bounce@xxxxxxxxxxxxx
<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Miller ;(Redacted
sender "bob.miller" for DMARC)
Sent: Wednesday, April 19, 2017 10:00 AM
To: Walter Katz
Cc: Muranyi, Arpad; IBIS-ATM
Subject: [ibis-macro] Re: Bird 186.3_Draft_2 (character length restrictions
on file naming rules.
[chiming in]:
I think this helps, Walter.
Regards,
Bob
On Wed, Apr 19, 2017 at 10:53 AM, Walter Katz <wkatz@xxxxxxxxxx
<mailto:wkatz@xxxxxxxxxx> > wrote:
Arpad,
I tried to clean up the definitions distinguishing “path name”, “full Path
name” and “absolute path name”. Does this help make things clearer. The
update draft 2 of 183.3 is included. The following is the changed section
without the markups:
3. “file name” shall mean the name of the file, including the path
relative to the directory containing the file that references the “file
name”. A “file name” may not be a directory. The “file name” has three
sections, “path name” (optional), “base name” and “extension name”
(characters following the last “.” in “file name”). The number of character
in the combined “base name” and “extension name” shall not exceed sixty-four
(64) characters. The number of characters in “path name” shall not exceed
sixty-four (64) characters.
Definitions:
“path name” The path of a “file name” in any file reference in a parent file
relative to the location of the parent file.
“full path name” The path of a file in any file reference in a parent file
which itself is referenced by a file referenced by an IBIS file, relative to
the location of the IBIS file. There can be many levels of referenced files.
“absolute path name” The path of a file relative to the root of the file
system directory.
If there are “file names” specified in files referenced by the IBIS file,
then the “full path name” relative to the directory containing the IBIS file
shall not exceed one hundred and twenty eight (128) characters.
The file name must use characters from the following set (space, “ ”, 0x20
is not included):
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ‘ ` . /
Walter
Walter Katz
wkatz@xxxxxxxxxx <mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308 <tel:(303)%20449-2308>
Mobile 303.335-6156 <tel:(303)%20335-6156>
From: ibis-macro-bounce@xxxxxxxxxxxxx
<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx ;
<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> ] On Behalf Of Muranyi, Arpad
Sent: Wednesday, April 19, 2017 1:27 AM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx <mailto:ibis-macro@xxxxxxxxxxxxx> >
Subject: [ibis-macro] Re: Bird 186.3_Draft_1 (character length restrictions
on file naming rules.
Walter,
I see a language problem. The first and third sentences define “file name”
as
” The “file name” has three sections, “path name” (optional), “base name”
and “extension name””.
The last sentence talks about “full path name” with the same meaning as the
previously defined “file name”. However, if “path name” is a subset (or
part)
of the “file name” then what is the meaning of “full path name”? In other
words, is “full path name” = “file name”? I know what you are trying to
say,
I am just picking on how you say it because it is confusing and/or
inconsistent.
I think you should find a better way to say it.
Thanks,
Arpad
=================================================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx
<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz
Sent: Tuesday, April 18, 2017 3:17 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx <mailto:ibis-macro@xxxxxxxxxxxxx> >
Subject: [ibis-macro] Bird 186.3_Draft_1 (character length restrictions on
file naming rules.
All,
The new paragraph below in red was added to 186.3. Two other lines were
deleted as a result.
3. “file name” shall mean the name of the file, including the path
relative to the directory containing the file that references the “file
name”. A “file name” may not be a directory. The “file name” has three
sections, “path name” (optional), “base name” and “extension name”
(characters following the last “.” In “file name”). The number of character
in the combined “base name” and “extension name” shall not exceed sixty-four
(64) characters. The number of characters in “path name” shall not exceed
sixty-four (64) characters. If there are “file names” specified in files
referenced by the IBIS file, then the full path name relative to the
directory containing the IBIS file shall not exceed one hundred and twenty
eight (128) characters.
The file name must use characters from the following set (space, “ ”, 0x20
is not included):
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ‘ ` . /
Note that files names in the Windows operating system are case insensitive
and case preserving, while file names in Linux operating systems are case
sensitive. When a <https://en.wikipedia.org/wiki/Computer> computer
<https://en.wikipedia.org/wiki/File_system> file system stores file names,
the computer may keep or discard
<https://en.wikipedia.org/wiki/Letter_case> case information. When the case
is stored, it is called case preservation. File names in IBIS files should
be case sensitive so that the IBIS file and the files it references will
work properly on both Windows and Linux operating systems. The “/” character
is used to delineate directories in a file name. The character sequence
“../” is not permitted, except that it is permitted if generated by the EDA
tool. Absolute or relative paths can be generated by the EDA tool in
applications as needed. The EDA tool is responsible for making any operating
system-specific adjustments (for example, replacing forward slashes "/" with
backslashes "\") if necessary.
The characters after the last “.” are considered the file name extension,
where the extension shall not contain a “/”. There are places in this
document that specify the file name extension for specific files types (e.g.
.ibs, .pkg, and .ami). These extensions are case sensitive.
A “file name” may not be a directory.
Directory (path) names follow the same rules as file names, except that they
shall be the name of a directory.
Walter Katz
wkatz@xxxxxxxxxx <mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308 <tel:(303)%20449-2308>
Mobile 303.335-6156 <tel:(303)%20335-6156>
Attachment:
bird186.3_Draft_3.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
