ISO/IEC 14863:1996

Information technology — System-Independent Data Format (SIDF)

Technologies de l'information — Format de données indépendantes du système (SIDF)

General Information

• Status: Published
• Publication Date: 17-Jul-1996
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9093 - International Standard confirmed
• Start Date: 29-Jul-2008
• Completion Date: 12-Feb-2026

Overview

ISO/IEC 14863:1996 - Information technology - System‑Independent Data Format (SIDF) specifies a logical, system‑independent format for information interchange and secondary data storage. The standard defines how primary file system information (data, attributes, characteristics) is organized on target media and the requirements for both originating and receiving systems to ensure reliable interchange of file sets and volume sets.

Key topics and technical requirements

• Format scope: Organization of information on media, field and structure definitions, and conformance requirements for media volumes and systems.
• Field and Field Identifier (FID): Data is grouped into named Fields; each Field is uniquely identified by a byte sequence (FID). Field Tables group related Fields and are normatively defined in annexes.
• Recording conventions: Byte/bit order and numeric representation are specified - e.g., the standard records the least significant byte first and gives explicit bit recording rules for each byte. Negative values use two’s complement.
• Character sets (CHAR SPEC): Character encoding defaults to the CS4 character set (IRV of ISO/IEC 646) unless another CHAR SPEC is specified. The standard accommodates multiple character set types and provides mechanism to specify them.
• Timestamps and precision: Standardized timestamp fields (year, month, day, hour, minute, second, centiseconds, microseconds, etc.) are defined for consistent time metadata.
• Media and file organization: Defines Sectors, Buffers, Files, File Sets, Volume and Volume Sets, sector numbering, interleaving and spanning of file sets across volumes.
• Integrity checks: Use of Cyclic Redundancy Check (CRC) for data integrity and detailed recording rules for CRC bits.
• Structure description schema: A formal grammar for describing structures, repetition operators and nesting used throughout the standard.
• Conformance levels: Rules for conformance of media volumes, originating systems, and receiving systems; requirements for access, recording and handling.

Practical applications and users

ISO/IEC 14863 (SIDF) is useful for:

• System integrators and software vendors building cross‑platform file interchange and archival tools.
• Backup, archival and digital preservation solutions that need a stable, system‑independent representation of file systems.
• Hardware and media vendors (optical, removable media) that must support standardized volume and file structures.
• Enterprises and government archives requiring long‑term, platform‑agnostic secondary storage formats.
• Developers implementing tools to convert or migrate file system data between heterogeneous environments.

Related standards

ISO/IEC 14863 references and is intended to work alongside other standards such as:

• ISO/IEC 13346 (Volume and file structure for write‑once/rewritable media)
• ISO 9660 (CD‑ROM volume and file structure)
• ISO/IEC 646, ISO/IEC 2022, ISO/IEC 10646 (character set standards)
• POSIX (ISO/IEC 9945‑1) and related registration procedures

Keywords: ISO/IEC 14863, SIDF, System-Independent Data Format, data interchange, secondary storage, file set, volume set, Field Identifier, CHAR SPEC, CRC, ISO/IEC standards.

Standards Content (Sample)

ISO/IEC
INTERNATIONAL
STANDARD
First edition
1996-07-15
Information technology -
System-Independent Data Format (SIDF)
Format de don&es indgpendantes du
Technologies de /‘information -
s yt&me (SIDF)
Reference number
&O/l EC 14863: 1996(E)
ISO/IEC 14863: 1996 (E)
Page
Contents
Section 1 - General
1 Scope
2 Conformance
2.1 Conformance of Media Volumes
2.2 Conformance of an originating system
2.3 Conformance of a receiving system
3 Normative references
4 Definitions
5 General conventions and notations
5.1 Representation of numbers
5.2 Names
5.3 Structures
5.4 Fields
5.5 Field Identifiers (FIB)
5.6 Field Tables
5.7 Headers
5.8 Indices
5.9 Structure description schema
Section 2 - Requirements for the media
6 Specific conventions and notations for the recorded format
6.1 Recording of numbers
6.2 Character sets and coding
6.3 Character set specification (CHAR SPEC)
6.3.1 Character Set Type
6.3.2 Character Set Information
6.4 CSO character set
6.5 CSl character set
6.6 CS2 character set
0 ISO/IEC 1996
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized
in any form or by any means, electronic or mechanical, including photocopying and microfilm,
without permission in writing from the publisher.
ISO/IEC Copyright Office * Case Postale 56 * CH-1211 Geneve 20 * Switzerland
Printed in Switzerland
ii
ISO/IEC 14863r1996 (E)
0 ISO/IEC
6.7 CS3 character set
6.8 CS4 character set
6.9 CSS character set
6.10 CS6 character set
6.11 CS7 character set
6.11.1 Code extension characters
6.12 CS8 character set
6.13 Source Name Space specification
6.13.1 Name Space
6.14 NSO Name Space
6.15 NSl Name Space
6.16 NS2 Name Space
6.17 NS3 Name Space
6.18 NS4 Name Space
6.19 NS5 Name Space
6.20 NSFC Name Space
6.21 NSFE Name Space
6.22 Strings
6.23 Resynchronization Pattern
7 Timestamp
7.1 Type and Time Zone (RBP 0)
7.2 Year (RBP 2)
7.3 Month (RBP 4)
7.4 Day (RBP 5)
7.5 Hour (RBP6)
7.6 Minute (RI3P 7)
7.7 Second (RBP 8)
7.8 Centiseconds (RBP 9)
7.9 Hundreds of microseconds (RBP 10)
7.10 Microseconds (RBP 11)
8 Requirements for a standard for recording
9 Cyclic Redundancy Check (CRC)
10 Organization of Information on a Volume
10.1 Recording of Sectors
10.2 Organization of a Volume
10.3 Volume Sets
10.4 Recording of Fields
10.4.1 NULL Field
10.5 Recording of Field Tables
10.6 Recording of Buffers
10.7 Recording of file marks
11 Organization of Information within a File Set
11.1 Organization of a File Set
11.2 File Sets spanning multiple Volumes
11.3 Interleaving
12 Organization of information within a File
. . .
0 ISO/IEC
13 Field Table description
13.1 Volume Header Field Table
13.2 Volume Trailer Field Table
13.3 Blank Space Field Table
13.4 Buffer Header Field Table
13.5 Volume Index Field Table
13.6 Volume Subindex Field Table
13.7 File Set Header Field Table
13.8 File Set Continuation Header Field Table
13.9 File Set Trailer Field Table
13.10 File Set Index Field Table
13.11 File Set Subindex Field Table
13.12 File Header Field Table
13.13 File Continuation Header Field Table
13.14 File Information Field Table
13.15 File Data
13.15.1 Path Field Table
13.15.2 Characteristics Field Table
13.15.3 Source volume File Data
13.15.4 Source directory File Data
13.15.5 Source file File data
13.15.6 Transaction Set File data
13.15.7 Streams
13.16 Levels of partition interchange
13.16.1 Level 1 of partition interchange
13.16.2 Level 2 of partition interchange
14 Requirements for systems
14.1 Requirements for the description of systems
14.2 Requirements for an originating system
14.2.1 General
14.2.2 Mandatory access by user
14.2.3 Optional access by user
14.2.4 Volume characteristics
14.2.5 File Set characteristics
14.2.6 Recording of Bit Data
14.2.7 Cyclic Redundancy Check (CRC)
14.3 Requirements for a receiving system
14.3.1 General
14.3.2 Levels of conformance
Annexes
A - Structure of the Field Identifier
I3 - Specification of the length of data in Fields
C - Field specification
D - Numerical list of the Field Identifiers specified by this International Standard
E - Numerical list of Field Identifiers which are obsolete (0) or not specified by this International Standard
iv
0 ISO/IEC
ISOIIEC 14863: 1996 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees established by the respective organization to deal with
particular fields of technical activity. IS0 and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft
International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 14863 was prepared by ECMA (as Standard ECMA-208) and was adopted, under a special
“fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval
by national bodies of IS0 and IEC.
Annexes A to C form an integral part of this International Standard. Annexes D and E are for information only.

0 ISO/IEC
ISO/IEC ~14863:1996 (E)
Introduction
The System Independent Data Format Association (SIDF) was formed in early 1993 by a consortium of industries.
ECMA TC15 adopted the work of this committee in early 1994 and developed Standard ECMA-208 on the basis of the SIDF
specification.
vi
INTERNATIONAL STANDARD OISO/IEC /IEC 14863:1996 (E)
Information technology - System-Independent Data Format (SIDF)
Section 1 - General
1 Scope
This International Standard specifies a logical format for information interchange and secondary data storage. The format
provides a System-Independent Data Format (SIDF) for the representation of primary file system information. This
information includes, among other things, data, attributes and characteristics. This International Standard specifies
-
the organization of the information on target media,
-
requirements for originating and receiving systems for the processing of the information.
2 Conformance
Conformance of Media Volumes
21 .
A Volume shall be in conformance with this International Standard if all information recorded on it meets the relevant
requirements of sections 2 and 3 for the level of partition claimed.
22 . Conformance of an originating system
An originating system shall be in conformance with this International Standard if it meets the requirements of 14.2.
23 . Conformance of a receiving system
A receiving system shall be in conformance with this International Standard if it meets the requirements of 14.3 for the
Level of conformance claimed.
3 Normative references
The following standards contain provisions which, through reference in this text, constitute provisions of this International
Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to
agreements based on this International Standard are encouraged to investigate the possibility of applying the most recent
editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International
Standards.
ISO/IEC 646: 199 1, Information technology -- IS0 7-bit coded character set for information interchange.
ISO/IEC 2022: 1994, Information technology -- Character code structure and extension techniques.
Information processing -- &bit single-byte coded graphic character sets -- Part 1: Latin
IS0 8859~1:1987,
alphabet No. 1.
IS0 8859-2: 1987, Information processing -- &bit single-byte coded graphic character sets -- Part 2: Latin
alphabet No. 2.
-- &bit single-byte coded graphic character sets -- Part 3: Latin
IS0 8859-3: 1988, Information processing
alphabet No. 3.
Information processing -- &bit single-byte coded graphic character sets -- Part 4: Latin
IS0 8859-4: 1988,
alphabet No. 4.
of CD-ROM for information interchange
IS0 9660: 1988, Information processing -- Volume and file structure
ISO/IEC 13346-1:1995, Information technology -- Volume and file structure of write-once and rewritable media using
non-sequential recording for information interchange -- Part I: General.
ISOIIEC 13346-2: 1995, Information technology -- Volume and file structure of write-once and rewritable media using
non-sequential recording for information interchange -- Part 2: Volume and boot block
recognition.
Information technology -- Volume andfile structure of write-once and rewritable media using
ISO/IEC 13346-3: 1995,
non-sequential recording for information interchange -- Part 3: Volume structure.

0 ISO/IEC
Information technology -- Volume andfile structure of write-once and rewritable media using
ISO/IEC 13346-4: 1995,
non-sequential recording for information interchange -- Part 4: File structure.
ISO/IEC 13346-5: 1995, Information technology -- Volume and file structure of write-once and rewritable media using
non-sequential recording for information interchange -- Part 5: Record structure.
Information technology -- Portable Operating System Interface (POSIX) -- Part 1: System
ISO/IEC 9945 1: 1996,
Application Program Inter$ace (API) [C Language].
ISO/IEC 10646-1:1993, Information technology -- Universal Multiple-Octet Coded Character Set (UC’S) -- Part 1:
Architecture and Basic Multilingual Plane.
Procedure for the Registration of identifiers and attributes for
ISO/IEC 13800:1996, Information technology --
volume and file structure.
ITU Rec. X.25 (1993), Interface between data terminal equipment (DTE) and data circuit-terminating equipment
(DCE) for terminals operating in the packet mode and connected to public data networks by
dedicated circuit.
4 Definitions
For the purposes of this International Standard, the following definitions apply.
41 l Blank Space: Either one or more NULL Fields, or a BLANK SPACE Field Table.
42 Buffer: A set of adjacent sectors, which are logically related A common use of buffers is to encapsulate subsets of
fiie set data so that it can be treated as a whole.
43 . byte: A string of eight binary digits operated upon as a unit.
44 . Byte Sequence: An ordered set of bytes.
. Field: The basic logical grouping of data.
46 a Field Identifier (FID): A Byte Sequence which identifies a Field.
47 Field Table: A set of logically associated Fields.
representation of a single primary file
48 . File: A collection of data that is stored as a single unit. A File contains a
system entity, such as a Source directory, file, data base object, or data base.
49 0 file mark: A sector containing a control block used as a delimiter to facilitate positioning, as defined by the
relevant standard for recording.
Note 1 - Some media may not support file marks.
4.10 File Set: A set of associated Files, sourced from a single Source, recorded within a Volume Set.
4.11 Interleaved File Sets: Two or more File Sets are interleaved if any part of at least one is recorded between any
parts of another.
4.12 Iterated Field Set: A sequence of one or more Fields, which may be repeated within a Field Table.
4.13 operating system: The software which controls the file system of the Source.
4.14 originating system: An information processing system which can create a File Set in a Volume Set for the
purpose of data interchange with another system.
4.15 Relative Byte Position: Indicates the byte position in a number.
4.16 receiving system: An information processing system which can process a File Set of a Volume Set which has
been created by another system for the purpose of data interchange.
0 ISO/IEC ISO/IEC 14863: 1996 (E)
4.17 Sector: The data field of the smallest addressable part of the medium that can be accessed independently of other
addressable parts of the medium.
Note 2 - This Sector is different from the physical sectors of a physical track.
4.18 Sector Number: The ordinal sequence number of a Sector within a Volume, starting with 0 (0, 1, 2, 3, . . . . n).
4.19 Source: The primary system (e.g. file system, data base) which is the source of the Files that are recorded as a File
Set for secondary storage. The name of the Source is specified for the File Set, and is not included in the Source path
information of the individual Files.
4.20 standard for recording: A standard that specifies the recording method and the addressing method for the
information recorded on a medium.
4.21 Volume: A set of Sectors which resides within one physical partition on a secondary storage medium.
4.22 Volume Set: One Volume, or multiple logically related Volumes.
4.23 Volume Set Sequence Number: The ordinal sequence number of each Volume within a Volume Set, starting
with 1 (1, 2, 3, . . . . n).
5 General conventions and notations
51 . Representation of numbers
-
Numbers in decimal notation are shown as decimal digits.
-
Numbers in hexadecimal notation are shown as a sequence of hexadecimal digits preceded by #.
- The setting of bits is denoted by ZERO or ONE.
- Numbers in binary notation and bit combinations are represented by sequences of ZEROS or ONES.
- Bit combinations are shown with the most significant bit to the left.
- Bits are indicated with the small letter b.
- Bytes are indicated with the capital letter B.
52 . Names
The names of formally defined entities, such as a Volume, are shown with a capital initial.
The name of Fields, such as VOLUME HEADER, are written in capitals.
53 . Structures
Data structures are shown in tables indicating the Relative Byte Position (RBP), purpose and size of the entities that
comprise the structure.
Fields
54 .
Fields are denoted by names shown in capital letters.
55 . Field Identifiers (FIDs)
A Byte Sequence in hexadecimal notation uniquely identifying a Field.
56 . Field Tables
The name of a Field Table is that of its first Field, it is shown with capital initials. Field Tables list each Field with its name,
its FID and a brief description of the data. The normative definition of each Field is specified in annex C. The Data
Description reads “empty” if no Data part is included in the Field. Iterated Field Sets within a Field Table are shown
indented, with a bar alongside. Nested Iterated Field Sets are shown with each inner level of nesting further indented than
the outer level(s).
57 l Headers
The term “File Set (Continuation) Header” is used to express: File Set Header and/or File Set Continuation Header. The term
“File Record (Continuation) Header” is used to express: File Record Header and/or File Record Continuation Header.
0 ISO/IEC
ISO/IECl4863:1996 (E)
58 . Indices
The term “Volume (Sub)Index” is used to express: Volume Index and/or Volume Subindex. The term “File Set (Sub)Index”
is used to express: File Set Index and/or File Set Subindex.
59 . Structure description schema
Requirements for recording the different elements of the format are summarized by means of a structure description.
A structure shall be a sequence of terms. A term shall be either:
-
a name, enclosed by [I, followed by a definition enclosed by { } , or
-
a name, enclosed by <>, of a term defined in the structure or of a descriptor defined elsewhere in this International
Standard in the text associated with the structure.
Within a definition enclosed by { }, the Or Operator and Repetition Operators may be applied to the terms therein.
The Or Operator is represented by the character VERTICAL LINE: I. It is placed between the terms to which it applies and
indicates that either term, but not both simultaneously, is valid at that point in the definition.
There are three Repetition Operators, which shall be interpreted as shown in figure 1, where n and m are decimal digits.
Repetition Operator Interpretation
I I I
n n occurrences of the preceding term
n+
n or more occurrences of the preceding term
n+m n to m occurrences of the preceding term
Figure 1 - Repetition Operators
The Repetition Operators shall apply only to the preceding term.
The operators are listed in increasing order of precedence:
I repetition operator
[I 0
Higher precedence operators shall be applied before lower precedence operators.
As an example, the schema shown in figure 2 specifies that the entity “Concert” shall be organized as zero or one
Introduction, followed by one or more Pieces, an Intermission, one or more Pieces, and zero or more Encores. A Piece
consists either of one Song or three to five Movements.
[Concert] 1
O+l
[Piece] {

1 3+5
1 1+

1+
0+
Figure 2 - Example of the syntaxof the structure description schema
Sectidn 2 - Requirements for the media
6 Specific conventions and notations for the recorded format
61 . Recording of numbers
-
In each Field the field data is recorded so that the least significant byte (denoted byte BO) is recorded first. Within each
byte the least significant bit is denoted bit b0, the most significant bit is denoted b7, and is recorded first. This order of
recording also applies to the data of the cyclic redundancy code (CRC) and to its output (CRC bits).
ISWIEC 14863:1996 (E)
0 ISO/IEC
- Negative values are recorded in WO’s complement notation.
62 . Character sets and coding
Except as specified in this clause and in 6.13, the characters used in the Fields specified by this International Standard shall
be coded according to the International Reference Version (IRV) of ISO/IEC 646. The CS4 character set described in 6.8
shall be the default character set, and shall be used if no other is explicitly specified. The specification of the characters
allowed in these Fields and the method of recording shall be recorded as a CHAR SPEC Field (see 6.3).
Note 3 - Support for a variety of character ses is a requirement of this International Standard. Ideally, there should be only one character standard used. In
practice, several standards, including ISO/IEC 646, ISO/IEC 2022, IS0 8859 and ISO/IEC 10646-l are used. This International Standard accommodates
current practice by specifying several character sets and providing a mechanism for specifying other character sets.
As an example, CS2 (see 6.6) uses the IRV of ISO/IEC 646 as the basic character set but restricts Fields containing
characters to a widely usable subset of this character set.
63 . Character set specification (CHAR SPEC)
The data part of the CHAR SBEC Field consists of two parts, Character Set Type and Character Set Information, recorded as
a sequence of bytes. The Character Set Type shall be recorded as the first byte of the sequence; the Character Set
Information shall consist of any remaining bytes.
The set of characters allowed in certain Fields and/or Field Tables shall be specified by a one-byte Character Set Type, and
additional Character Set Information appended immediately after as needed.
6.3.1 Character Set Type
The Character Set TvPe identifies the allowed set of characters as shown in figure 3.
Allowed characters
The CSO coded character set (see 6.4).
The CSl coded character set (see 6.5).
The CS2 coded character set (see 6.6).
The CS3 coded character set (see 6.7).
The CS4 coded character set (see 6.8).
The CS5 coded character set (see 6.9).
The CS6 coded character set (see 6.10).
The CS7 coded character set (see 6.11).
The CS8 coded character set (see 6.12).
9 to 255 Reserved for future standardization
Figure 3 - Sets of allowed characters
6.3.2 Character Set Information
The interpretation of the contents of this field, if any, is specified by the value of the Character Set Type as described in 6.4
to 6.12.
64 . CSO character set
The CSO character set shall be subject to agreement between the originator and recipient of the medium.
The character set is undefined for interchange. However, the agreed character set can be identified in the Character Set
Information, if so desired.
65 . CSl character set
The CSl character set shall be the graphic characters of the character sets specified by the Character Set Information Field.

0 ISO/IEC
ISO/IEC 14863: 1996 (E)
The Character Set Information Field shall specify one or more escape sequences, to be used in an 8-bit environment
according to ISO/IEC 2022 that designate and implicitly invoke graphic character sets specified in ISO/IEC 10646-l. These
sequences shall be recorded contiguously from the start of the Field.
66 . CS2 character set
The CS2 character set shall be the 38 characters in positions 02114, 03/00 to 03/09, 04/01 to 05/10, and 05/15 of the IRV of
ISO/IEC 646.
Note 4 - These characters are: FULL STOP, DIGITS, LATIN CAPITAL LETTERS and LOW LINE.
67 . CS3 character set
The CS3 character set shall be the 65 characters in positions 02/13 to 02/14, 03/00 to 03/09, 04/01 to 05/10, 05/15, and 06/01
to 07/10 of the IRV of ISO/IEC 646.
Note 5 - These characters are: HYPHEN-MINUS, FULL STOP, DIGITS, LATIN CAPITAL LETTERS, LATIN SMALL LETTERS and LOW LINE.
68 . CS4 character set
The CS4 character set shall be the 95 characters in positions 02/00 to 07/14 of the IRV of ISO/IEC 646.
69 . CS5 character set
The CS5 character set shall be the 191 characters in positions 02/00 to 07/14 and lO/OO to 15/15 of Latin Alphabet No. 1 in
IS0 8859- 1.
6.10 CS6 character set
The CS6 character set shall be the graphic characters of the character sets specified by the Character Set Information Field.
The Character Set Information field shall specify one or more escape sequences according to ISO/IEC 2022 that designate
and implicitly invoke the graphic character sets to be used in an 8-bit environment according to ISO/IEC 2022 or ISO/IEC
10646-l. These sequences shall be recorded contiguously from the start of the Field.
6.11 CS7 character set
The CS7 character set shall be the graphic characters of the character sets specified by the Character Set Information Field
and code extension characters (see 6.11.1).
The Character Set Information field shall specify one or more escape sequences according to ISO/IEC 2022 that designate
and implicitly invoke the graphic character sets to be used in an 8-bit environment according to ISO/IEC 2022 or ISO/IEC
10646- 1. These sequences shall be recorded contiguously from the start of the field.
Code extension characters
6.11.1
Characters specified by the CS7 Character Set may include one or more of the following, referred to as code extension
characters, to allow alternative character sets to be recorded.
- Escape sequences according to ISO/IEC 2022 or ISO/IEC 10646-l
- Shift functions according to ISO/IEC 2022
6.12 CS8 character set
The CS8 character set shall be the 53 characters in positions 02101, 02103 to 02109, 02113 to 02/14, 03100 to 03109, 04100 to
05/10,05/14 to 06/00, 07/11 and 07/13 to 07/14 of the IRV of ISO/IEC 646.
Note 6 - These characters are: EXCLAMATION MARK, NUMBER SIGN, DOLLAR SIGN, PERCENT SIGN, AMPERSAND, APOSTROPHE, LEFT
PARENTHESIS, RIGHT PARENTHESIS, HYPHEN-MINUS, FULL STOP, DIGITS, LATIN CAPITAL LETTERS, CIRCUMFLEX ACCENT, LOW LINE,
GRAVE ACCENT, LEFT CURLY BRACKET, RIGHT CURLY BRACKET, TILDE.
6.13 Source Name Space specificabn
The Source or originating system shall indicate the properties of path name information that is associated with a Source file
or similar entity by the Field NAME SPACE. In some contexts other Fields may also use the same Name Space information,
for example RESOURCE NAME SPACE in the File Set Header. The Name Space specifies the following characteristics of
the file name:
0 ISO/IEC ISO/IEC 14863:1996 (E)
- Path element character set restrictions: The characters used in the Source file path name shall be contained within this
set.
- Path element length restrictions: Each element of the path name shall consist of at least one character, and shall not be
longer than the number of characters specified.
- Total path length restriction: The entire path shall not be longer than the number of characters specified.
- Path ordering (parent-first or child-first): For complete paths in hierarchical file systems, if the parent-first path
ordering is used, the parent node closest to the root shall be listed first, followed by its immediate child, and proceeding
so forth to the path element furthest from the root. If the child-first path ordering is used, the node furthest from the root
shall be listed first, followed by its immediate parent, and proceeding so forth to the path element nearest to the root.
- Case-sensitive: A CAPITAL LETTER is considered different from the corresponding SMALL LETTER.
- Case retention: A CAPITAL LETTER and the corresponding SMALL LETTER are stored and displayed distinctly.
- Separators: In the full path name, the separator(s) between any two elements of the path name.
- Special requirements: Any other characteristics not reflected above. For example, whether restrictions apply to the
character FULL STOP (#2E), regarding its position or frequency of use in a path element name.
6.13.1 Name Space
Name Spaces shall be identified by an unsigned hexadecimal number. The Name Spaces specified by this International
Standard are shown in figure 4.
Identifier Name Space
#OO The NSO Name Space (see 6.14).
#Ol The NS 1 Name Space (see 6.15).
#02 The NS2 Name Space (see 6.16).
#03 The NS3 Name Space (see 6.17).
#04 The NS4 Name Space (see 6.18).
#05 The NS5 Name Space (see 6.19).
#FFFFFFFC The NSFC Name Space (see 6.20).
#FFFFFFFE The NSFE Name Space (see 6.21).
-.
rigure 4 - Defined Name Spaces
6.14 NSO Name Space
be members of the CS8
Path element character set restrictions: Characters of the NSO Name Space path elements shall
Character Set.
Path element length restrictions: A path element shall contain at most 12 characters. A path element shall not contain
more than one FULL STOP. A path element shall contain at most 8 characters before a FULL STOP and at most 3
characters after a FULL STOP. If a path element does not contain a FULL STOP, that path element shall contain at most 8
characters.
Total path length restriction: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete (i.e. not relative) path shall be recorded before the child element.
Case-sensitive: FALSE.
Case retention: FALSE.
Separators: The separator between the first two elements of a complete path shall be COLON. The separator between all
subsequent elements of the path shall be SOLIDUS.
Special requirements: A path element shall not contain more than one FULL STOP character. The first element of a
complete path shall be a Source volume Name.

0 ISO/IEC
ISO/IEC 14863: 1996 (E)
Note 7 - This Name Space may be associated with file systems of many personal computers. In some implementations the total path length is restricted to 256
characters, and the use of longer paths may yield unpredictable results. In some implementation the characters represented by #21, #23 to 29, #2D, #2E, #7D
and #7E may not be supported, and their use may yield unpredictable results.
6.15 NSl Name Space
Path element character set restrictions: Bytes #OO and #3A are not allowed for the NSl Name Space path elements.
Path element length restriction: Each path element shall contain at most 32 characters.
Total path length restrictions: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete path shall be recorded before the child element.
Case-sensitive: TRUE.
Case retention: TRUE.
Separators: The separator between the first two elements of a complete path shall be two adjacent COLONS. The separator
between all subsequent elements of the path shall be COLON.
Special requirements: The first element of a complete path shall be a Source volume Name.
6.16 NS2 Name Space
Path element character set restrictions: Characters of the NS2 Name Space path elements shall be represented by any
single byte, except #OO, #2F, #3A.
Path element length restriction: Each path element shall contain at most 300 characters.
Total path length restrictions: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete path shall be recorded before the child element.
Case-sensitive: TRUE.
Case retention: TRUE.
Separators: The separator between the first two elements of a fully qualified path shall be COLON. The separator between
all subsequent elements of the path shall be SOLIDUS.
Special requirements: The first element of a complete path shall be a Source volume Name.
6.17 NS3 Name Space
Path element character set restrictions: Characters of the NS3 Name Space path elements shall be represented by any
single byte within one of the following ranges: #Ol to #2E, #30 to #39, #3B to #7E.
Path element length restriction: Each path element shall contain at most 255 characters.
Total path length restrictions: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete path shall be recorded before the child element.
Case-sensitive: TRUE.
Case retention: TRUE.
Separators: The separator between the first two elements of a complete path shall be COLON. The separator between all
subsequent elements of the path shall be SOLIDUS.
Special requirements: The first element of a complete path shall be a Source volume Name.
NS4 Name Space
6.18
Path element character set restrictions: Characters of the NS4 Name Space path elements shall be represented by any
single byte within one of the following ranges: #21 to #2E, #30 to #5B, #5D to #FF.
Path element length restriction: Each path element shall contain at most 300 characters.
Total path length restrictions: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete path shall be recorded before the child element.
0 ISO/IEC %SO/IEC 14863:1996 (E)
Case-sensitive: FALSE.
Case retention: TRUE.
Separators: The separator between the first two elements of a complete path shall be COLON. The separator between all
subsequent elements of the path shall be SOLIDUS.
Special requirements: The first element of a complete path shall be a Source volume Name.
6.19
NS5 Name Space
Path element character set restrictions: Characters of the NS5 Name Space path elements shall be represented by any
single byte within one of the following ranges: #30 to #39, #40 to #5A, #5E to #60, #7B, #7D to #FF.
Path element length restriction: Each path element shall contain at most 256 characters.
Total path length restrictions: No total path length restrictions shall apply.
Path ordering: The parent path element(s) of a complete path shall be recorded before the child element.
Case-sensitive: FALSE.
Case retention: TRUE.
Separators: The separator between the first two elements of a complete path shall be COLON. The separator between all
subsequent elements of the path shall be SOLIDUS.
Special requirements: The first element of a complete path shall be a Source volume Name.
Note 8. - In so,me implementations the total path length is restricted to 256 characters, and use of longer paths may yield unpredictable results.
6.20 NSFC Name Space
Path element character set restrictions: Characters of the NSFC Name Space path elements shall be represented by any
single byte within one of the following ranges: #O to #2A, #2C to #2D, #2F to #3C, #3E to #5B, #5D to #FF.
Path element length restriction: Each path element shall contain at most 256 characters.
Total path length restrictions: The total path shall contain at most 256 characters.
Path ordering: The child element of a complete path shall be recorded before the parent path element(s).
Case-sensitive: FALSE.
Case retention: TRUE.
Separators: The separator between all path elements shall be FULL STOP.
6.21 NSFE Name Space
Name Space NSFE shall be used to indicate that the characteristics associated with the Name Space shall be determined by
the Source, and are not specified by this International Standard.
6.22 Strings
A string shall be recorded as a sequence of zero or more non-NULL characters, followed by a NULL character.
6.23 Resynchronization Pattern
The Resynchronization Pattern shall be the two-byte Byte Sequence #A55A.
z
7 Timestamp
A Timestamp specifies a date and time recorded in the format shown in figure 5. If the Year field has the value 0 the
Timestamp shall be ignored; all other Fields in Timestamp shall be set to all ZEROS. Timestamps are established by the
originating system and/or the Source. The accuracy of Timestamps is not specified by this International Standard. If a
Timestamp is recorded in a Field the Data part of which is longer than I2 bytes, the Timestamp shall be recorded first, and
all subsequent bytes shall be recorded as NULL(s).

0 ISO/IEC
Name Representation
RBP
Timestamp type and time zone 16-bit integer
16-bit integer
2 Year
8-bit integer
4 Month
8-bit integer
Day
8-bit integer
6 Hour
8-bit integer
7 Minute
8-bit integer
8 Second
Centisecond 8-bit integer
Hundreds of microseconds 8-bit integer
Microseconds 8-bit integer
Figure 5 - Timestamp format
Type and Time Zone (RBP 0)
71 .
The most significant 4 bits of this integer, interpreted as a 4-bit number, shall specify the interpretation of the Timestamp.
-
the value 0 shall indicate that the Timestamp specifies Coordinated Universal Time, timezone shall be all ZEROS.
-
the value 1 shall indicate that the Timestamp specifies local time.
-
the value 2 shall indicate that the interpretation of the Timestamp is subject to agreement between the originator and
recipient of the medium.
-
no other value shall be recorded.
The least significant 12 bits of this field, interpreted as a signed 12-bit number in TWO’s complement form, shall be
interpreted as follows:
-
if the value is in the range -1440 to 1440, then the value specifies the offset, in minutes, of the date and time from
Coordinated Universal Time.
-
if the value is -2047, this shall mean that no such offset is specified.
-
no other values shall be recorded.
72 a Year (RBP 2)
This field shall specify the year as a number in the range 1 to 9999.
73 l Month (RBP 4)
This field shall specify the month of the year as a number in the range 1 to 12.
.
Day (RBP 5)
74 .
This field shall specify the day of the month as a number in the range 1 to 3 1.
75 . Hour (RBP6)
This field shall specify the hour of the day as a number in the range 0 to 23.
76 . Minute (RBP 7)
This field shall specify the minute of the hour as a number in the range 0 to 59.
77 Second (RBP 8)
l
If the value of the Type field is 2, then this field shall specify the second of the minute as a number in the range 0 to 60.
Otherwise, this field shall specify the second of the minute as a number in the range 0 to 59.
Centiseconds (RBP 9)
78 .
This field shall specify the hundredths of the second as a number in the range 0 to 99.
0 ISO/IEC ISO/IEC 14863:1996 (E)
79 0 Hundreds of microseconds (RBP 10)
This field shall specify the hundreds of microseconds as a number in the range 0 to 99.
7.10 Microseconds (RBP 11)
This field shall specify the microseconds as a number in the range 0 to 99.
8 Requirements for a standard for recording
The media for recording shall meet the following requirements of a standard for recording.
standard recording shall specify:
The for
a unique address for each sector;
-
the length of each sector;
-
the means for determining whether a sector is rewritable or not;
-
for media where sectors may only be recorded once, a means for detecting whether a sector has not yet been recorded;
whether sectors or groups of sectors may require pre-processing prior to recording;
-
a method for recording and detecting file marks, if file marks are supported.
The standard for recording used in conjunction with this International Standard is subject to agreement between the
originator and recipient of the medium.
9 Cyclic Redundancy Check (CRC)
A Cyclic Redundancy Check (CRC) as specified in this standard, where implemented, shall be computed in accordance with
ITU Rec. X.25. CRC shall use the generating polynomial .32 + x26 + ,23 + .22 + xl6 + xl2 + .I1 + xl0 + x8 + x7 + x5 + x4 +
x2 + x + 1. CRC shall use the seed value -1. CRC generates a 32-bit output.
10 Organization of Information on a Volume
10.1 Recording of Sectors
The physical sectors of a Volume shall be organized into logical Sectors of equal length. Sectors shall have a length of 2n+8
bytes, where n is an positive integer (i.e. Sector lengths of 512, 1024, 2048, 4096, . .). Each Sector of a Volume shall be
identified by a unique Sector Number. Sector Number 0 shall be assigned to the Sector at the start of the Volume Header.
This is not necessarily the sector with the lowest physical address of the partition.
10.2 Organization of a Volume
A Volume is a set of Sectors. The lowest numbered Sectors of the Volume, referred to as the Volume Preamble, shall
contain only a Volume Header and zero or more File Set Continuation Headers. The remaining Sectors of the Volume, up to,
but not including, the Volume Postamble, shall be referred to as the Volume Data Space of the Volume. Volume Data Space
shall consist of File Sets (see clause 11) and, optionally, Volume Indices (see 13.5).
The Volume Postamble may contain one File Set Subindex and/or one Volume Set Subindex. If it contains both, the File Set
Subindex shall precede the Volume Set Subindex. The Volume Postamble shall end with the Volume Terminator. The
Volume Terminator shall be either a Volume Trailer, the physical end-of-partition, or the end of recorded data, which ever
occurs at the lower numbered Sector. No more than one Volume shall be recorded in one physical partition.
Note 9 - Because a Volume, as specified by this International Standard, need not be located at the physical start of the partition, a Volume may be preceded by
other information. The presence of such prefixed information is restricted to media at Level 2 of medium interchange (see 14.3.2).
Figure 6 summarizes the requirements for recording Volumes.
0 ISO/IEC
[Volume] {
[Volume Preamble] {

0+

[Volume Postamble] {
O+l
0-d
[Volume Terminator] {



>
>
>
Figure 6 - Schema for Volumes
10.3 Volume Sets
A Volume Set shall consist of one or more Volumes having a Volume Set Label common to all Volumes.
n), their numbers constitute their Volume Set
The Volumes in a Volume Set shall be numbered ordinally (1, 2, 3, . . . .
Sequence Numbers. All occurrences of Volume Set Time within a Volume Set shall be equivalent. The ordered
concatenation of the Volume Data Spaces of the Volumes of a Volumes Set constitutes the Volume Set Data Space.
Note 10 - Volumes within a Volume Set may be of different physical media types.
File Set(s) shall be recorded within the Volume Set Data Space of a Volume Set. A Volume Index is optional, but if present
shall be recorded within the Volume Set Data Space, immediately following a File Set.
Figure 7 summarizes the requirements for recording Volume Set Data Space.
[Volume Set Data Space] { {

O+l
1 o+
Figure 7 - Schema for Volume Set Data Space
Figure 8 to figure 10 show examples of the layout of the Volume organization.
Volume Header Volume Header
First File Set First File Set
Second File Set
Second File Set
Volume Index (optional)
Volume Trailer
(space unavailable to Volume)
(physical end of partition)
Figure 8 - Simplified view of a Volume Figure 9 - Simplified view of a Volume
Two File Sets are recorded on the Volume, Two File Sets are recorded on the Volume,
further File Sets can be appended. no further File Sets can be appended without
overwriting the Volume Trailer.
ISOIIEC 14863:1996 (E)
0 ISO/IEC
Volume Header
I
Volume Header
File Set Cont. Header
First File Set
for Third File Set
Third File Set (part 2)
Second File Set
Fourth File Set
Third File Set (part 1)
(physical end of partition)
(sectors not yet recorded)
(physical end of partition)
L
YS-0028-A
Figure 10 - Simplified view of a Volume Set, the Third File Set of which spans from one Volume to the next.
10.4 Recording of Fields
All data in the Volume, except for Streams (see 13.15.6), shall be expressed in Fields. A Field shall consist of a Field
Identifier (FID) (see annex. A), and may contain a Data Length part and a Data part.
Certain FIDs specify the: length of the data implicitly, in which case the Data Length part shall be omitted. For all other
FIDs, the Data Length part shall be present immediately after the FID. If data is present in the Field, the Data part of the
Field shall immediately follow the Data Length part if present, or shall follow the FID if the Data Length part is omitted.
The formal definition of each type of Field is specified in annex C.
FID Data length Data
Figure 11 - Parts of a Field
Fields contained in Buffer(s) shall have both their FID and Data length part recorded entirely within a single Buffer.
10.4.1 NULL Field
The NULL Field shall consist only of its FID which consists of the single byte #OO. It has no meaning, and functions merely
as a placeholder.
Recording of Field Tables
10.5
A Field Table is a sequence of Fields. All Fields shall be recorded in Field Tables, except when the Null Field is used as
Blank Space (see 13.3). A Field Table shall start and end with Fields identified by the same FID. The Data part of the first
Field shall consist of the Resynchronization Pattern. The Data part of the last Field shall either contain CRC bits or be
empty, as indicated by the Data Length part of this last Field. This Field shall not appear elsewhere in the Field Table. Each
Field Table is given the name of its first Field. If the OFFSET TO END Field is included in a Field Table, it shall be the
?
second Field.
Any set of Fields specified as an Iterated Field Set may be repeated within the Field Table. Each iteration is identified by the
first Field listed in the Iterated Field Set.
Except for the first and last Field, OFFSET TO END, and any restrictions on Iterated Field Sets, or otherwise specified,
Fields may be in any order within the Field Table; they need not be in the order shown in examples.
If the CRC bits are computed, they shall be calculated over the whole Field Table, except the last Field.
0 ISO/IEC
10.6 Recording of Buffers
All information recorded in a Volume, except
Volume Header
File Set Continuation Hea
...