Post Issue Peer-to-Patent

Subsequent directory entries hold portion of long filename

[Note: The original Claim 9 was canceled in the Reexamination Certificate issued October 10, 2006.]

Relevance

4.1.4 Flag position 0 - CONTINUE Alternate Name continues in next "NM" field

Claim Chart

All

Directory holds only a portion of long filename

In a data processing system having a processor running an operating system and a memory means having memory locations wherein the operating system is stored in the memory means, a method, comprising the steps of: (a) storing in a first of the memory locations of the memory means a first directory entry for a file wherein the first directory entry holds a short filename for the file, said short filename including at most a maximum number of characters that is permissible by an application program; (b) storing in a second of the memory locations of the memory means that is adjacent to the first of the memory locations a second directory entry for the file wherein the second directory entry holds at least a first portion of a long filename for the file, said long filename including a greater number of characters than the maximum number of characters that is permissible by the application program; (c) storing at least one additional directory entry holding a next portion of the long filename in the memory means; and (d) accessing one of the directory entries to locate the file.

Relevance

(a) ISO 9660 file identifier (ISO 9660:1988 alone provides inadequate support for delivery of POSIX file system information. The Rock Ridge Group was formed to generate a proposed standard for utilizing the System Use Areas provided by the ISO 9660 standard to record complete POSIX file system semantics.) (b) 4.1.4 The purpose of the "NM" System Use Field is to store the content of an Alternate Name to support POSIX-style or other names. (c) 4.1.4 If more than one "NM" System Use Field appears in (all) the System Use Area(s) for a single directory record, the contents ([5] below) of each should be concatenated together, in the order in which they were recorded, until a CONTINUE flag with value zero is encountered (see [4] below), to obtain the entire Alternate Name. (d) 3.3 Reader Makes Right Receiving systems which are capable of interpreting the System Use Fields defined herein, but which cannot handle the full extent of the file naming convention utilized by this specification may have to restrict themselves to the use of the ISO 9660 compliant file names stored in the File Identifier field of the ISO 9660 directory structure.

Claim Chart

All

Long filename associated with short filename

In a data processing system having a processor running an operating system and a memory means with memory locations, wherein said memory means stores the operating system, a computer-readable medium holding computer-executable instructions for performing a method comprising the steps of: (a) storing in a first of the memory locations of the memory means a first directory entry for a file wherein the first directory entry holds a short filename for the file, said short filename including at most a maximum number of characters that is permissible by an application program; (b) storing in a second of the memory locations of the memory means that is adjacent to the first of the memory locations a second directory entry for the file wherein the second directory entry holds at least a first portion of a long filename for the file, said long filename including a greater number of characters than the maximum number of characters that is permissible by the application program; (c) storing at least one additional directory entry in at least one other of the memory locations that is adjacent to the second of the memory locations of the memory means wherein the at least one additional directory entry holds a next portion of the long filename; and (d) accessing one of the directory entries to locate the file.

Relevance

(a) ISO 9660 file identifier (ISO 9660:1988 alone provides inadequate support for delivery of POSIX file system information. The Rock Ridge Group was formed to generate a proposed standard for utilizing the System Use Areas provided by the ISO 9660 standard to record complete POSIX file system semantics.) (b) 4.1.4 The purpose of the "NM" System Use Field is to store the content of an Alternate Name to support POSIX-style or other names. (c) 4.1.4 If more than one "NM" System Use Field appears in (all) the System Use Area(s) for a single directory record, the contents ([5] below) of each should be concatenated together, in the order in which they were recorded, until a CONTINUE flag with value zero is encountered (see [4] below), to obtain the entire Alternate Name. (d) 3.3 Reader Makes Right Receiving systems which are capable of interpreting the System Use Fields defined herein, but which cannot handle the full extent of the file naming convention utilized by this specification may have to restrict themselves to the use of the ISO 9660 compliant file names stored in the File Identifier field of the ISO 9660 directory structure.

Claim Chart

All

Long file name with signature

In a computer system having a storage, a directory service for accessing directory entries and a file system that uses the directory entries to access files, a method, comprising the computer-implemented steps of: (a) creating a first directory entry for a file wherein the first directory entry holds a short filename for the file and the location of the file; (b) creating a second directory entry for the file wherein the second directory entry holds at least one portion of a long filename having a fixed number of characters and a signature that identifies that the second directory entry holds a first portion of the long filename; (c) storing the first directory entry and the second directory entry on the storage among the directory entries used by the directory service; (d) accessing the second directory entry by the directory service to access the file; and (e) creating and storing in the storage a sequence of at least one additional directory entry for holding a next sequential portion of the long filename.

Relevance

(a) First directory entry = ISO 9660 entry (b) Second directory entry = (first) NM record (c) Receiving systems which are capable of interpreting the System Use Fields defined herein, but which cannot handle the full extent of the file naming convention utilized by this specification may have to restrict themselves to the use of the ISO 9660 compliant file names stored in the File Identifier field of the ISO 9660 directory structure. (d) The purpose of the "NM" System Use Field is to store the content of an Alternate Name to support POSIX-style or other names. (e) CONTINUE flag in NM record indicates whether name is continued in additional NM records.

Claim Chart

All

Comingled directory entries

In a computer system having a storage, a directory service for accessing directory entries and a file system that uses the directory entries to access files, a comnputer-readable medium holding computer-executable instructions for performing a method comprising computer-implementented steps of: (a) creating a first direct0ry entry for a file wherein the first directory holds a short filename for the file and the location of the file; (b) creating a second directory entry for the file wherein the second directory entry holds at least one portion of a long filename having a fixed number of characters; (c) creating a sequence of at least one additional directory entry for holding a next sequential portion of the long filename; (d) storing the first directory entry the second directory entry and the at least one additional directory entry on the storage among the directory entries used by the directory service; and (e) accessing the second directory entry and the at least one additional directory entry by the directory service to access the file.

Relevance

(a) ISO 9660 directory entry (b) 4.1.4 NM record (c) 4.1.4 Additional NM records as needed. See CONTINUE flag (d) NM records stored according to SUSP protocol (e) 4.1.4 If more than one "NM" System Use Field appears in (all) the System Use Area(s) for a single directory record, the contents ([5] below) of each should be concatenated together, in the order in which they were recorded, until a CONTINUE flag with value zero is encountered

Claim Chart

All

Type of Prior Art	Online Publication

URL	http://www.programmersheaven.co...

Author/Creator	Rock Ridge Group

Title	ROCK RIDGE INTERCHANGE PROTOCOL VERSION 1

Publication Date	July 24, 1991

Publisher	Rock Ridge Group

Directions to Document Location	Unzip above URL and read RRIP109 as plain text. added .txt suffix to permit submission here.

Additional Information	Basis of what was eventually adopted as IEEE P1282.

(b) Common name space for long and short filenames

Sponsors:

Notes	Covers all independent claims. Will add details once I get upload to work