《ISO-13346-1-1995.pdf》由会员分享，可在线阅读，更多相关《ISO-13346-1-1995.pdf（18页珍藏版）》请在三一文库上搜索。
1、INTERNATIONAL STANDARD ISO/IEC 13346-I First edition 1995-l 2-l 5 Information technology - Volume and file structure of write-once and rewritable media using non-sequential recording for information interchange - Part 1: General Technologies de /information - Structure de volume et de fichier de moy
2、ens dkriture unique et de r the type of medium may be either write once, or read only, or rewitable, or a combination of these types. ISO/IEC 13346 consists of the following five Parts: Part 1: General Part 2: Volume and Boot Block Recognition Part 3: Volume Structure Part 4: File Structure Part 5:
3、Record Structure Annex A - ICB Strategies, is part of Part 4. Part 1 specifies references, definitions, notation and basic structures that apply to the other four Parts. 2 Parts references The first digit of a reference within ISO/IEC 13346 identifies the Part, e.g. 2/5 refers to clause 5 in Part 2,
4、 and figure 4/3 refers to figure 3 in Part 4. 3 Conformance 3.1 Conformance of a medium A medium shall be in conformance with ISO/IEC 13346 when it conforms to a standard for recording (see l/5.10) and information recorded on sectors of the medium conform to the specifications of Part 1 and one or m
5、ore of Parts 2, 3,4 and 5. A statement of conformance shall identify the sectors of the medium on which information is recorded according to the specifications of ISO/IEC 13346, and the Parts and the levels of medium interchange (see 2/10, 3/10.10, and 4/15) to which the contents of those sectors of
6、 the medium conform. 3.2 Conformance of an information processing system An information processing system shall be in conformance with ISO/IEC 13346 if it meets the requirements specified in Part 1 and one or more of Parts 2, 3,4 and 5 either for an originating system (see 2/12, 3/13,4/17 and 5/l 1)
7、 or for a receiving system (see 2/13, 3/14, 4/18 and 5/12) or for both types of system. A statement of conformance shall identify the Parts, and the levels of the requirements for each of those Parts, which can be met by the system. 4 Normative references The following International Standards contai
8、n provisions which, through reference in this text, constitute provisions of this part of ISODX 13346. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this part of ISO/IEC 13346 are encouraged to investigate the
9、 possibility of applying the most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards. 1 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standard
10、s 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISOLIK 13346-1:1995(E) OISO/IEC ISO/IEC 646: 1991, Information technology - IS0 7-bit code character setfor information interchange. ISO/IEC 2022: 1994, Information technology
11、 - Character code structure and extension techniques. ISO/lEC 6429: 1992, Information technology - Control functions for coded character sets, IS0 8859-l: 1987, Information processing - g-bit single-byte codedgraphic character sets - Part I: Latin alphabet No. 1. ISOIIEC 9293; 1994, Information tech
12、nology - Volume andfile structure of disk cartridges for information interchange. IS0 9660: 1988, Information processing - Volume andJile structure of CD-ROMfor information interchange. ISOIIEC 9945-1: 1990, Information technology - Portable Operating System Interface (POSUI) - Part 1: System Applic
13、ation Program Interface (API) C Language. ISO/IEC 10646-111993, Information technology - Universal Multiple Octet Coded Character Set (UC - Part 1: Architecture and Basic Multilingual Plane. ISOIIEX 13490-l: 1995, Information technology - Volume andfile structure of read-only and write-once compact
14、disk media for information interchange - Part 1: General. ISOIIEC 13490-2: 1995, Information technology - Volume andJle structure of read-only and write-once compact disk media for information interchange - Part 2: Volume andfile structure. ISO/IEX 13800”, Information technology - Procedure for the
15、registration of identifiers and attributes for volume and file structure ITU-T Recommendation V.4 1, Code-Independent Error-Control System. 5 Definitions For the purposes of ISO/IEC 13346, the following definitions apply. 5.1 application: A program that processes the contents of a file, and may also
16、 process selected attribute data relating to the file or to the volume(s) on which the tile is recorded. 5.2 byte: A string of eight binary digits operated upon as a unit. If the standard for recording (see l/5.10) specifies that the container for the recording of a byte has more than eight bits, in
17、 ISO/lEC 13346 a byte shall be recorded in the least sign - the length of each sector; - the means for determining whether a sector is read-only, write-once, or rewritable; - for media where sectors may only be recorded once, a means for detecting whether each sector has not yet been recorded; - whe
18、ther sectors may require preprocessing prior to recording. The standard for recording used in conjunction with ISO/IEC 13346 is subject to agreement between the originator and recipient of the medium. 5.11 user: A person or other entity (for example, an application) that causes the invocation of the
19、 services provided by an implementation. 5.12 volume: A sector address space as specified in the relevant standard for recording. NOTE 2 - A medium usually has a single set of sector addresses, and is therefore a single volume. A medium may have a sepamte set of addresses for each side of the medium
20、, and is therefore two volumes. 5.13 volume set: A collection of one or more volumes with identical volume set identification. 6 Notation The following notation is used in ISO/IEC 13346: 6.1 Numerical notation 6.1.1 Decimal notation Numbers in decimal notation are represented by decimal digits. 6.1.
21、2 Hexadecimal notation Numbers in hexadecimal notation are represented as a sequence of one or more hexadecimal digits prefixed by %“: hexadecimal digit 0123456789ABCDEF decimal value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 6.2 Bit fields Certain fields containing an integral value, or parts of fields
22、 containing an integral value, are intended to be interpreted as an array of bits. This array of bits shall be referred to as a bit field. Bit positions within an n bit field are numbered such that the least significant bit is numbered 0 and the most significant bit is numbered n- 1. 6.3 Descriptor
23、formats Descriptor formats shah be specified by a figure specifying the location, length, name and contents of each field. The interpretation of each field shall be given in the prose associated with the figure. 3 Copyright International Organization for Standardization Provided by IHS under license
24、 with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitted without license from IHS -,-,- BO/IEC 13346-1:1995(E) 01s0/lEc The descriptor spec Byte position Length in bytes Name Contents 0 4 Data Length (=D-L) Uint32 (l/7.1.
25、5) 4 32 Application Identifier regid (l/7.4) 36 4 Reserved #OO bytes 40 2 Type Int16 (l/7.1.4)=57 42 D-L Implementation Use bytes p-L+421 * Padding #OO bytes Figure 1 - Example descriptor format ied by figure l/l has six fields: - The Data Length field shall be a 32-bit unsigned integer recorded acc
26、ording to l/7.1.5 in byte positions 0 to 3 of the descriptor. The value of this field may be referred to as D-L. - The Application Identifier field shall be a 32 byte field specifying an identification of an application recorded according to l/7.4 in byte positions 4 to 35 of the descriptor. - The R
27、eserved field shall be 4 bytes, each with the value #OO, recorded in byte positions 36 to 39 of the descriptor. - The Type field shall be the number 57 as a 16-bit signed integer recorded according to l/7.1.4 in byte positions 40 to 41 of the descriptor. - The Implementation Use field shah be D-L by
28、tes recorded in byte positions 42 to (D-L+41), where D L is the value recorded in the Data Length field of this descriptor. A symbolic length referred to in a descriptor shall either be defined within that descriptor or be described in the interpretation of the field it is used in. The specification
29、 of the interpretation for this field might state that the interpretation of those bytes is not specified by ISO/IEC 13346, or could specify some specific interpretation for those bytes. - The Padding field shall be a variable length field, as indicated by the asterisk “*“, of bytes, each with a val
30、ue of #OO. The specification of the interpretation for the field shall specify the length of the field. 6.4 Character strings A value for a sequence of bytes may be specified by a quoted sequence of characters, encoded according to the International Reference Version of ISO/IEC 646. For example, “Sh
31、eep” shah represent the bytes #53, #/68, #65, #65, #70. 6.5 Arithmetic notation The notation ip(x) shall mean the integer part of x. The notation rem(a, b) shall mean a-bxip(a /b), where a and b are integers. 6.6 Schema The notation specified by this clause, hereafter referred to as schema, specifie
32、s the format of a structure, or sequence of structures, by construction. White space is unimportant. A structure shall be a sequence of terms. A term shall be either a name enclosed by l+ 1 1+ I o+ Figure 3 - Example schema 6.7 Other notations Various other notations used in ISO/IEC 13346 are specif
33、kd in figure l/4. Notation BP RBP ZERO ONE Interpretation Byte position within a descriptor, starting with 0 Relative byte position within a descriptor, starting with 0 A single bit with the value 0 A single bit with the value 1 Figure 4 - Other notations 7 Basic types The following basic types are
34、used in ISO/IEC 13346. 7.1 Numerical values The recording format of a numerical value represented in binary notation by an n-bit number shall be denoted by a type name of Intn or Uintn where 5 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NA
35、SA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitted without license from IHS -,-,- ISOlIEC 13346-1:1995(E) OISO/IEC - n denotes the number of bits used in the binary number - Uint denotes an unsigned integer x, in the range 0 I x 2”, rep
36、resented as a binary number - n-l Int denotes a signed integer x, in the range -2 x 2”-, represented by a twos complement number A numerical value shall be recorded in a field of a structure specified by ISOLEC 13346 in one of the following formats. The applicable format shall be specified in the de
37、scription of the structure. 7.1.1 8-bit unsigned numerical values A Uint8 value shah be recorded as an S-bit unsigned number in a one-byte field. 7.1.2 this information shall be called the scope of the regid. The scope of a regid consists of the field in which the regid is recorded and any informati
38、on specified by the description of that field to be part of the scope the regid. BBP Length 0 1 1 23 24 8 Name Contents Flags Uint8 (l/7.1.1) Identifier bytes Identifier Suffix bytes Figure 9 - regid format 7.4.1 Flags (BBP 0) This field shall specify certain characteristics of the regid as shown in
39、 figure l/10. Bit Interpretation 0 Dirty: Ifan implementation modifies the information on the medium within the scope of this regid such that the identification specified by this regid might not be valid, then this bit shall be set to ONE, otherwise it shall be set to ZERO. 1 Protected: If this bit
40、is ONE, then the contents of this regid shall not be modified; if this bit is ZERO, then the contents of this regid may be modified (see 3113.1 and 4/17.2.3). 2-7 shall be reserved for future standard these octets shall be recorded in ascending order as the least significant 8 bits of bytes 0 throug
41、h 22 of this field respectively. Any unused bytes shall be set to #OO. 11 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitted with
42、out license from IHS -,-,- ISo/IEC 13346-1:1995(E) 01s0/lEc The interpretation of the content of the Identifier field shall be specified in the description of the descriptor field in which the regid is recorded. If this field contains all #/OO bytes, then this field does not specify an identifier. N
43、OTE 14 - The values #2B and #2D do not represent characters. However, for most coded character sets using the value recorded in one byte to represent a character, such as ISO/IEC 646, the value #2B corresponds to “+” and the value #2D corresponds to “-“. 7.4.3 Identifier Suffix BP 24) This field sha
44、ll specify further identification in a manner not specified by ISOiDX 13346. 12 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitte
45、d without license from IHS -,-,- ISO/IEC 1334&1:1995(E) 0 ISO/IEC ICS 35.220 Descriptors: data processing, data storage, information interchange, data recording devices, read-only memories, read-write memories, specifications, logical structure, generalities. Price based on 12 pages Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 06:39:34 MDTNo reproduction or networking permitted without license from IHS -,-,-