Rules for drafting STANDARDs--Part 3:Information classifying and coding
Some standard content:
GB/T20001 "Rules for the Preparation of Standards" is divided into the following parts: Part 1: Terminology;
Part 2: Symbols;
Part 3: Information Classification and Coding;
Part 4: Chemical Analysis Methods.
GB/T20001.3—2001
This part is Part 3 of GB/T20001, replacing GB/T7026—1986 "Rules for the Preparation of Information Classification and Coding Standards for Standardization Work Guidelines". This revision readjusted the original standard in accordance with GB/T1.1-2000 and added some specific content. The main changes are as follows:
- The Chinese and English names of the standard have been modified. The name of the standard was changed to "Standard Writing Rules Part 3: Information Classification and Coding"; - The overall arrangement and structure of the standard were modified according to GB/T1.1-2000; - The table of contents, preface and Chapter 3 "Terms and Definitions" were added, and the structure of the original standard was modified. The original Chapter 4 "Composition of Information Classification and Coding Standards" was changed to Chapter 5 "Structure", and the original Chapters 3, 5, 6, 7 and 8 were changed to Chapter 6 "Drafting", Chapter 7 "Format, Requirements and Details of Classification and Code Table Writing" and Chapter 8 "Format of Arrangement"
- In addition to adding and modifying the corresponding content according to the requirements of GB/T1.1-2000 for the standard, the corresponding items were appropriately added and modified according to the needs of the development of information classification and coding standardization; - Appendix A was modified;
- References were added.
GB/T20001 is one of the series of national standards such as guidelines, guidelines and writing rules for standardization work. The following lists the expected structure of these national standards and their corresponding international standards, guidelines, and national standards that will be replaced: a) GB/T1 "Guidelines for Standardization Work"
-Part 1: Structure and writing rules for standards (ISO/IEC Guide Part 3, replacing GB/T1.1-1993, GB/T1.2-1996);
-Part 2: Methods for formulating standards (ISO/IEC Guide Part 2, replacing GB/T1.3-1997, GB/T 1.7-—1988);
-Part 3: Technical work procedures (ISO/IEC Guide Part 1, replacing GB/T16733-1997). b) GB/T 20000 "Guidelines for Standardization Work" Part 1: Common vocabulary for standardization and related activities (ISO/IEC Guide 2, replacing GB/T 3935.1-1996); - Part 2: Rules for the adoption of international standards (ISO/IEC Guide 21); Part 3: Rules for referenced documents (ISO/IEC Guide 15, replacing GB/T 1.22-1993); - Part 4: Preparation of safety-related content in standards (ISO/IEC Guide 51); Part 5: Preparation of environmental content in product standards (ISO/IEC Guide 64). c) GB/T20001 "Rules for Writing Standards" Part 1: Terminology (ISO10241, replacing GB/T1.6-1997); Part 2: Symbols (replacing GB/T1.5-1988); Part 3: Information Classification and Coding (replacing GB/T7026-1986); Part 4: Chemical Analysis Methods (ISO78-2, replacing GB/T1.4-1988). Appendix A of this part is an informative appendix.
GB/T20001.3-2001
This part was proposed and managed by the China Standards Research Center. The main drafting unit of this part: China Standards Research Center. The main drafters of this part: Feng Wei, Li Xiaolin, Hu Jiazhang. GB/T7026 was first issued in November 1986, and was revised for the first time in 2001 and the standard number was re-determined as GB/T20001.3. 1 Scope
Standard Writing Rules
Part 3: Information Classification and Coding
This part of GBT20001 specifies the structure and writing rules of the information classification and coding standard. GB/T20001.3—2001
This part is applicable to the writing of national standards, industry standards and local standards for information classification and coding. It can be used as a reference for the writing of enterprise standards. Chapters and articles containing information classification and coding content in non-information classification and coding standards can also be used as a reference. 2 Normative References
The clauses in the following documents become clauses of this part through reference in this part of GB/T20001. For all dated referenced documents, all subsequent amendments (excluding errata) or revisions are not applicable to this part. However, parties to an agreement based on this part are encouraged to study whether the latest versions of these documents can be used. For any undated referenced document, the latest version shall apply to this part. GB/T 1.1-2000 Guidelines for standardization work Part 1: Structure and drafting rules of standards (ISO/IEC Directives, Part 3, 1997, Rules for the structure and drafting of International Standards, NEQ) GB/T 7027 Basic principles and methods for information classification and coding standards GB/T 10113 General terms for classification and coding
3 Terms and definitions
The terms and definitions established in Chapter 3 of GB/T 1.1-2000 and GB/T 10113 apply to this part of GB/T 20001. 4 General
4.1 Basic requirements
The preparation of information classification and coding standards shall comply with the provisions of GB/T 1.1-2000, and the classification principles and coding methods in the standards shall also comply with the provisions of GB/T 7027.
4.2 Coordination of standards
When formulating information classification and coding standards, they should be coordinated with relevant information classification and coding standards and other relevant standards. 5 Structure
The content and hierarchical division of information classification and coding standards should comply with the provisions of Chapter 5 of GB/T1.1--2000. Table 1 gives a typical arrangement example of elements in information classification and coding standards, and lists the allowed content of each element. When writing standards, the relevant elements in Table 1 can be selected according to the specific characteristics of the standardization object and the purpose of formulating the standard, and other normative technical elements outside Table 1 can also be included.
GB/T20001.3—2001
Element type
Informative overview element
Normative general elements
Table 1 Arrangement of elements in the information classification and coding standard "Arrangement of elements
Normative reference documents
Terms and definitions
Classification principles and methods
Normative technical elements
Informative supplementary elements
Coding method
Classification and code table
Normative appendix
Informative appendix
References
Contents allowed by elements"
Other contents of the identification standard (see 6.1.1 in GB/T1.1—2000) (Arrangement of contents see GB/T 1.1-2000, 6.1.2) Article
Text of name
Introduction
Cited documents
Grade note
Cited documents
(For the arrangement of contents, see 6.4.3 of GB/T 1.1 and 6.4.3 of this part)
Bold indicates "essential elements", regular indicates "normative elements" and italics indicates "informative elements". Informative appendices may not contain normative elementsb
6 Drafting
6.1 Informative overview elements
GB/T 20001.3-2001
The writing of the cover, table of contents, foreword and introduction of the information classification and coding standard shall comply with the provisions of 6.1 of GB/T 1.1-2000. 6.2 Normative general elements
6.2.1 The name, scope and normative reference documents of the information classification and coding standard shall comply with the provisions of 6.2 in GB/T1.1-2000.
6.2.2 The name of the information classification and coding standard shall briefly and clearly reflect the standardization object or subject of the information classification and coding. In addition to the basic general standards and regulations for information classification and coding, the name of the information classification and coding standard is generally in the form of "×X× Classification", "X× Code" or "×X× Classification and Code".
6.3 Normative technical elements
6.3.1 Terms and definitions
Terms and definitions are optional elements, which should provide definitions necessary for understanding certain terms in the standard. When writing, they should comply with the provisions of 6.3.1 in GB/T1.1-2000. 6.3.2 Classification principles and methods
The classification principles of the information classification coding standard shall comply with the provisions of GB/T7027, and explain the classification basis and classification method adopted by the standard. When the content of the standard is relatively simple or does not require classification, this element can be omitted. 6.3.3 Coding method
The coding method of the information classification coding standard shall comply with the provisions of GB/T7027, and explain the code type, code structure and coding method adopted by the standard. The code structure of the hierarchical code can also be represented by a schematic diagram, for example: XXXXX XXX
Name of the third layer code
Name of the second layer code
Name of the first layer code
When the code structure is more complex, examples can be used for explanation. If the code is long and needs to be verified, the verification method of the code should be explained, and GB/T17710 can also be referred to.
6.3.4 Classification and code table
6.3.4.1 The classification and code table (or code table) should be listed in the form of a table. The table generally consists of a code column, a coding object name column (which can be referred to as the "name column" in the code table), and a description column. The columns can be appropriately increased or decreased according to actual needs, as shown below: Example:
Tables A.1 and A.2 in Appendix A give specific examples of code tables. Description
6.3.4.2 When the content of the table is relatively simple, two or more columns can be arranged on one page to reduce the length. 6.3.4.3 When the content of the description column is a lot, two tables can be listed for the same coding object: one table only lists the code and the coding object name, so as to intuitively understand the classification of the coding object; the other table adds the description of the coding object name. 6.3.5 Normative Appendix
Normative Appendix is an optional element, which gives additional provisions to the standard text. The compilation of normative appendices shall comply with the provisions of 5.2.6 and 6.3.8 in GB/T1.1-2000.
6.4 Informative supplementary elements
GB/T20001.3-2001
6.4.1 The compilation of informative supplementary elements of information classification and coding standards shall comply with the provisions of 5.2.6 and 6.4 in GB/T1.1-2000. 6.4.2 When the classification objects of one standard are similar to those of another standard, but the classification principles or methods are different, a code comparison table of the two standards can be given in the informative appendix for ease of use. 6.4.3 When there are many classification and coding objects, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the coding object name; b)
in the order of the English corresponding words of the coding object name; c) in order of other related relationships.
6.5 Other rules
6.5.1 When the standard being formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard being formulated.
6.5.2 When the standard being formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard being formulated. 7 Format, requirements and details for the compilation of classification and code tables 7.1 Code column
7.1.1 Format
The code is generally written from the top left in the code column. When there are many levels of codes, the code column can be divided further according to the levels (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code should comply with the provisions of GB/T7027. 7.1.2.1 The code characters should be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: - Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
- Characters with similar pronunciations and shapes in a standard should not appear at the same time, such as: letter "I" and number "1", letter "O" and number "0\, etc.
7.1.2.2 Codes are best represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20013 Coding method
The coding method of the information classification coding standard shall comply with the provisions of GB/T7027, and shall clarify the code type, code structure and coding method adopted by the standard. The code structure of the hierarchical code can also be represented by a schematic diagram, for example: XXXXX XXX
Name of the third layer code
Name of the second layer code
Name of the first layer code
When the code structure is more complex, an example can be used for explanation. If the code is long and needs to be verified, the verification method of the code should be explained, and GB/T17710 can also be referred to.
6.3.4 Classification and code table
6.3.4.1 The classification and code table (or code table) shall be listed in the form of a table. The table generally consists of a code column, a coding object name column (which can be referred to as the "name column" in the code table), and a description column. The columns can be appropriately increased or decreased according to actual needs, as shown below: Example:
Tables A.1 and A.2 in Appendix A give specific examples of code tables. Explanation
6.3.4.2 When the content of the table is relatively simple, two or more columns of the table can be arranged on one page to reduce the length. 6.3.4.3 When the content of the description column is large, two tables can be listed for the same coding object: one table only lists the code and the name of the coding object, so as to intuitively understand the classification of the coding object; the other table adds the description of the name of the coding object. 6.3.5 Normative Appendix
Normative Appendix is an optional element, which gives additional clauses to the standard text. The preparation of normative appendix shall comply with the provisions of 5.2.6 and 6.3.8 in GB/T1.1-2000.
6.4 Informative Supplementary Elements
GB/T20001.3-2001
6.4.1 The preparation of informative supplementary elements of the information classification coding standard shall comply with the provisions of 5.2.6 and 6.4 in GB/T1.1-2000. 6.4.2 When the classification objects of one standard are similar to those of another standard, but the classification principles or methods are different, a code comparison table of the two standards can be given in the informative appendix for ease of use. 6.4.3 When there are many classification and coding objects, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the coding object name; b)
in the order of the English corresponding words of the coding object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details for the compilation of classification and code tables 7.1 Code column
7.1.1 Format
Codes are generally written in the code column from the top left. When there are many code levels, the code column can be divided according to the levels (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code should comply with the provisions of GB/T7027. 7.1.2.1 Code characters should be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: 1. Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
In a standard, characters with similar pronunciation and shape should not appear at the same time, such as the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is best represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20013 Coding method
The coding method of the information classification coding standard shall comply with the provisions of GB/T7027, and shall clarify the code type, code structure and coding method adopted by the standard. The code structure of the hierarchical code can also be represented by a schematic diagram, for example: XXXXX XXX
Name of the third layer code
Name of the second layer code
Name of the first layer code
When the code structure is more complex, an example can be used for explanation. If the code is long and needs to be verified, the verification method of the code should be explained, and GB/T17710 can also be referred to.
6.3.4 Classification and code table
6.3.4.1 The classification and code table (or code table) shall be listed in the form of a table. The table generally consists of a code column, a coding object name column (which can be referred to as the "name column" in the code table), and a description column. The columns can be appropriately increased or decreased according to actual needs, as shown below: Example:
Tables A.1 and A.2 in Appendix A give specific examples of code tables. Explanation
6.3.4.2 When the content of the table is relatively simple, two or more columns of the table can be arranged on one page to reduce the length. 6.3.4.3 When the content of the description column is large, two tables can be listed for the same coding object: one table only lists the code and the name of the coding object, so as to intuitively understand the classification of the coding object; the other table adds the description of the name of the coding object. 6.3.5 Normative Appendix
Normative Appendix is an optional element, which gives additional clauses to the standard text. The preparation of normative appendix shall comply with the provisions of 5.2.6 and 6.3.8 in GB/T1.1-2000.
6.4 Informative Supplementary Elements
GB/T20001.3-2001
6.4.1 The preparation of informative supplementary elements of the information classification coding standard shall comply with the provisions of 5.2.6 and 6.4 in GB/T1.1-2000. 6.4.2 When the classification objects of one standard are similar to those of another standard, but the classification principles or methods are different, a code comparison table of the two standards can be given in the informative appendix for ease of use. 6.4.3 When there are many classification and coding objects, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the coding object name; b)
in the order of the English corresponding words of the coding object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details for the compilation of classification and code tables 7.1 Code column
7.1.1 Format
Codes are generally written in the code column from the top left. When there are many code levels, the code column can be divided according to the levels (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code should comply with the provisions of GB/T7027. 7.1.2.1 Code characters should be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: 1. Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
In a standard, characters with similar pronunciation and shape should not appear at the same time, such as the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is best represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—2001March—2001March—20012 gives a specific example of the code table. Explanation
6.3.4.2 When the content of the table is relatively simple, two or more columns can be arranged on one page to reduce the length of the text. 6.3.4.3 When the content of the description column is large, two tables can be listed for the same coding object: one table only lists the code and the name of the coding object, so as to intuitively understand the classification of the coding object; the other table adds the description of the name of the coding object. 6.3.5 Normative Appendix
Normative Appendix is an optional element, which gives additional clauses to the standard text. The preparation of normative appendix shall comply with the provisions of 5.2.6 and 6.3.8 in GB/T1.1-2000.
6.4 Informative Supplementary Elements
GB/T20001.3-2001
6.4.1 The preparation of informative supplementary elements of the information classification coding standard shall comply with the provisions of 5.2.6 and 6.4 in GB/T1.1-2000. 6.4.2 When the classification objects of one standard are similar to those of another standard, but the classification principles or methods are different, a code comparison table of the two standards can be given in the informative appendix for ease of use. 6.4.3 When there are many classification and coding objects, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the coding object name; b)
in the order of the English corresponding words of the coding object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details for the compilation of classification and code tables 7.1 Code column
7.1.1 Format
Codes are generally written in the code column from the top left. When there are many code levels, the code column can be divided according to the levels (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code should comply with the provisions of GB/T7027. 7.1.2.1 Code characters should be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: 1. Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
In a standard, characters with similar pronunciation and shape should not appear at the same time, such as the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is best represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20012 gives a specific example of the code table. Explanation
6.3.4.2 When the content of the table is relatively simple, two or more columns can be arranged on one page to reduce the length of the text. 6.3.4.3 When the content of the description column is large, two tables can be listed for the same coding object: one table only lists the code and the name of the coding object, so as to intuitively understand the classification of the coding object; the other table adds the description of the name of the coding object. 6.3.5 Normative Appendix
Normative Appendix is an optional element, which gives additional clauses to the standard text. The preparation of normative appendix shall comply with the provisions of 5.2.6 and 6.3.8 in GB/T1.1-2000.
6.4 Informative Supplementary Elements
GB/T20001.3-2001
6.4.1 The preparation of informative supplementary elements of the information classification coding standard shall comply with the provisions of 5.2.6 and 6.4 in GB/T1.1-2000. 6.4.2 When the classification objects of one standard are similar to those of another standard, but the classification principles or methods are different, a code comparison table of the two standards can be given in the informative appendix for ease of use. 6.4.3 When there are many classification and coding objects, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the coding object name; b)
in the order of the English corresponding words of the coding object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details for the compilation of classification and code tables 7.1 Code column
7.1.1 Format
Codes are generally written in the code column from the top left. When there are many code levels, the code column can be divided according to the levels (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code should comply with the provisions of GB/T7027. 7.1.2.1 Code characters should be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: 1. Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
In a standard, characters with similar pronunciation and shape should not appear at the same time, such as the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is best represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects. bzxZ.net
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20013 When there are many objects in the classification code, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the code object name; b)
in the order of the English corresponding words of the code object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details of the compilation of classification and code tables 7.1 Code column
7.1.1 Format
The code is generally written from the left to the top of the code column. When there are many code levels, the code column can be divided according to the level (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code shall comply with the provisions of GB/T7027. 7.1.2.1 The code characters shall be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: - Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
- Characters with similar pronunciations and shapes in a standard should avoid appearing at the same time, such as: the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is preferably represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20013 When there are many objects in the classification code, a code index can be compiled. The code index should be located after the appendix. The index can be arranged in the following forms:
a) in the order of the Chinese phonetic alphabet of the code object name; b)
in the order of the English corresponding words of the code object name; c) sorted by other related relationships.
6.5 Other rules
6.5.1 When the standard to be formulated is an extension and refinement of a certain standard that has been published, the entire code of the published standard can be used as part of the code of the standard to be formulated.
6.5.2 When the standard to be formulated needs to use the code of a certain standard that has been published as part of its code, the entire code or part of the code of the published standard can be used as part of the code of the standard to be formulated. 7 Format, requirements and details of the compilation of classification and code tables 7.1 Code column
7.1.1 Format
The code is generally written from the left to the top of the code column. When there are many code levels, the code column can be divided according to the level (see Table A.2 in Appendix A). 7.1.2 Requirements
The design of the code shall comply with the provisions of GB/T7027. 7.1.2.1 The code characters shall be correct, easy to recognize and read. Avoid using characters that are easily confused and misunderstood, such as the following characters: - Characters that may be used in the syntactic structure of data exchange, such as: question mark (?), colon (:), addition symbol (+), abbreviation (\), etc.
- Characters with similar pronunciations and shapes in a standard should avoid appearing at the same time, such as: the letter "I" and the number "1", the letter "O" and the number "0\, etc.
7.1.2.2 The code is preferably represented by all numbers or all letters. The mixed form of letters and numbers is generally used in special positions (such as the first position or the last position), and should not be used in random positions. 7.1.2.3 When using sequential codes, the codes are generally of equal length. For example: use 001~999 instead of 1~ 999. 7.1.2.4 When using hierarchical codes, codes at the same level should be of equal length. 7.1.2.5 In a standard, the code writing format should be consistent. For example: when using letter codes, they should all be in uppercase (or lowercase), and uppercase and lowercase should not be mixed. Codes at the same level should have consistent font sizes. 7.1.2.6 When using digital codes, if there are containment categories, the code usually uses a code with the last digit being "9". 7.1.2.7 For ease of reading and writing, the code can be divided into small segments. The separator can be "_\\." \\Space" etc. For example: 754623 can be written as 754-623 or 754·623.
7.2 Name column
7.2.1 Format
7.2.1.1 The code object name is written in the name column from the left to the top. Each code object name occupies one line. When the code object name is long, it can be continued to the next line, and the continued part should be aligned with the previous line.7.2.1.2 When the line classification method is used, the code object name of the first level is written from the left to the top. When writing, leave one space on the second layer, and leave two and three spaces on the third and matching layers respectively. The names of the coding objects on the same layer should be aligned vertically. When the code table is the second table described in 6.3.4.2 or 6.3.4.3, the names of the coding objects on each layer can be aligned vertically. 7.2.2 Requirements
7.2.2.1 The names of coding objects should use the terms specified in the current standards as much as possible. GB/T20001.3—2001
7.2.2.2 The names of coding objects should use standardized words to concisely describe the coding objects and accurately reflect the full content and meaning of the coding objects.
7.2.2.3 The names of coding objects should be composed in the same form as much as possible, and the fonts and sizes of the names of coding objects on the same level should be consistent. 7.3 Description column
7.3.1 Format
The contents of the description should be written in the description column with one space on the left. When the contents of the description are long, they can be continued to the next line. The continued part should be arranged in a grid from left to right.
7.3.2 Requirements
7.3.2.1 The description should be as brief and concise as possible.
7.3.2.2 A brief explanation should be given to easily confused or special coding objects so that the connotation and extension of the coding object concept can be correctly understood.
7.3.2.3 When a coding object has multiple names, synonyms of the coding object name can be listed in the description column. 8 Formatting
The format and size requirements of the information classification and coding standards shall comply with the provisions of Chapters 7 and 8 of GB/T1.1-2000. 5
GB/T20001.3-2001
Appendix A
(Informative Appendix)
Arrangement of classification and code tables
Table A.1 Examples of classification and code tables
Chemical hazards and harmful factors
Inflammable and explosive substances
Inflammable and explosive gases||t t||Flammable and explosive liquids
Flammable and explosive solids
Flammable and explosive dusts and aerosols
Other flammable and explosive substances
Pyrophoric substances
Toxic substances
Toxic gases
Containing substances that are flammable when wet
Including substances that are irritating, asphyxiating, sensitizing, teratogenic, carcinogenic, hemolytic, anesthetic, etc.
Table A.2 Examples of classification and code tables
.. ....
Al1111
A11112
Al111111
A1111199
A1111211
Ferro-alumina soil
Wet-heat ferro-alumina soil
Latosoil
Typical latosoil
Red muddy latosoil
Jinghong latosoil
Other red muddy latosoil
Sand-coated latosoil
Sand brick red soil
Red mud refers to the soil developed from the red clay parent material of the Quaternary
Sand coating refers to the soil developed from sandy
shallow sea sediment parent material
References
[1]GB/T17710 Data processing check code system (idtISO7064) [2] Zhao Yanhua, chief editor, Information classification and coding standardization, Beijing: China Standards Press, 1989GB/T20001.3—20011 The name of the coding object shall be written in the name column from the left to the top. Each coding object name occupies one line. When the coding object name is long, it can be continued to the next line, and the continued part shall be aligned with the previous line. 7.2.1.2 When the line classification method is adopted, the coding object name of the first level shall be written from the left to the top, the second level shall be left blank, and the coding object names of the third level, the second level, etc. shall be written with two and three characters left blank respectively. T
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.