General resource of military and civilian—Compiling requirements for data element
other information
drafter:Liu Zhi, Wang Limeng, Wang Haiwei, Yang Xiaojun, Qian Lufeng, Li Ying, Li Sucai, Ma Wenjing, Sun Wenfeng, Yang Ying, An Jing, Yang Jun, Luo Qiuke, Han Shuwen, Wang Pei, Ren Jie, Liu Wen, Wang Jing, Xu Junxia, Chen Jun, Zhang Yanqi, Yang Wenhong, Liu Xinjian, Huang Nan, Xing Yanlin, Du Jingrong, Li Yurong, Li Junmei, Xu Ni
Drafting unit:Joint Service College of National Defense University of the Chinese People's Liberation Army, Academy of Military Science of the Chinese People's Liberation Army, China Article Coding Center, China National Institute of Standardization, China Aviatio
Focal point unit:National Logistics Information Management Standardization Technical Committee (SAC/TC 267)
Proposing unit:National Logistics Information Management Standardization Technical Committee (SAC/TC 267)
Publishing department:State Administration for Market Regulation National Standardization Administration
Some standard content:
ICS35.040
National Standard of the People's Republic of China
GB/T37948—2019
General resource of military and civilian
Requirements for data element compilation
2019-08-30Release
State Administration for Market Regulation
Standardization Administration of the People's Republic of China
2020-03-01Implementation
Normative reference documents
Terms and definitions
Data element classification
Data element attributes and requirements
Appendix A (Normative Appendix)
Appendix B (Normative Appendix)
Appendix C (Informative Appendix)| |tt||Appendix D (Informative Appendix)
References
+++++++
Description of data element attributes……·
Data element attribute related code table
Data element example using multiple code tables
Data element description example in list form
GB/T37948—2019
This standard was drafted in accordance with the rules given in GB/T1.1-2009. This standard was proposed and managed by the National Technical Committee for Logistics Information Management Standardization (SAC/TC267). GB/T37948—2019
Drafting units of this standard: Joint Service College of National Defense University of the Chinese People's Liberation Army, Academy of Military Sciences of the Chinese People's Liberation Army, China Article Numbering Center, China National Institute of Standardization, China Aviation Comprehensive Technology Research Institute, China Electronics Technology Standardization Institute, Information Center of the Logistics Support Department of the Central Military Commission, Military Standard Research Center of the Institute of Systems Engineering of the Chinese People's Liberation Army Academy of Military Sciences, and Qingdao Standardization Research Institute. The main drafters of this standard are: Liu Zhi, Wang Limeng, Wang Haiwei, Yang Xiaojun, Qian Lufeng, Li Ying, Li Sucai, Ma Wenjing, Sun Wenfeng, Yang Ying, An Jing, Yang Jun, Luo Qiuke, Han Shuwen, Wang Pei, Ren Jie, Liu Wen, Wang Jing, Xu Junxia, Chen Jun, Zhang Yanqi, Yang Wenhong, Liu Xinjian, Huang Nan, Xing Yanlin, Du Jingrong, Li Yurong, Li Junmei, Xu Nim
1 Scope
Requirements for the compilation of data elements for common military and civilian resources
This standard specifies the classification, attributes and requirements of data elements describing common military and civilian resource information GB/T37948—2019
This standard applies to the compilation of data elements describing common military and civilian resource information, the mapping of corresponding data items, and the collection, analysis, conversion and exchange of data.
2 Normative reference documents
The following documents are indispensable for the application of this document. For any dated referenced document, only the dated version applies to this document. For any undated referenced document, the latest version (including all amendments) applies to this document. GB/T7408 Data element and exchange format Information exchange date and time representation GB18030 Information technology Chinese coded character set GB/T18391.1—2009 Information technology Metadata registration system (MDR) Part 1: Framework 3 Terms and definitions
GB/T18391.1-2009 defined and the following terms and definitions apply to this document. 3.1
basic data element
Basic data element
A data element from which other data elements can be derived. 3.2
compositeattribute
composite attribute
The same attribute needs to be described differently in different components or under different conditions of the same military and civilian general resource. For example:
Material attribute of a shovel: the material of the shovel head is steel, and the material of the shovel handle is wood. 3.3
composite attribute code
compositeattributecode;identified secondaryaddresscoding;ISAC code used to distinguish different elements of a composite attribute. 4 Data element classification
Classification by derivation and inheritance relationship
Data elements are divided into basic data elements and derived data elements according to the derivation and inheritance relationship. Basic data elements specify the basic connotation and maximum extension of data. Derived data elements are instances derived from basic data elements in specific application environments, and can also be called application data elements. Their basic connotation is consistent with that of basic data elements, and their extensions vary according to specific applications, but do not exceed the extension of basic data elements. In special cases, it is necessary to further refine the description of complex objects through composite attribute codes. For example: "Material" is a basic data element, and its value range is various possible materials. "Pallet material" is an application data element derived from the basic data element "Material" when describing the application of pallets in GB/T37948-2019
. Its value range is "wood, metal, plastic", which is within the value range of the basic data element, but less than the value range of the basic data element: "Hammer material" is a special application data element, and its value range is "wood, metal, plastic". At the same time, a composite attribute code table needs to be attached to encode the two objects "hammer head" and "handle" respectively, so as to further refine the description. Its value example is "hammer head|metal&hammer handle|wood", indicating that the hammer head is made of metal and the hammer handle is made of wood. 4.2
Classification by military and civilian general resource types||tt| |According to the types of military and civilian common resources in national defense mobilization, data elements are divided into 7 categories, including: materials, equipment, facilities, personnel, institutions, and other categories. The classification codes are shown in Table 1. Table 1
Military and civilian common resource data element category code table Military and civilian common resource data element category code
Data element attributes and requirements
Data element attributes
Military and civilian common resource data element category name
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Military and civilian common resource data element
Material category
Equipment category
Equipment category
Facility category
Personnel category
Institution Class
Other classes
The attribute items used to describe the data element and their selection requirements are shown in Table 2. The detailed description of the data element attributes is shown in Appendix A. Table 2
Attribute category
Data element attribute list
Attribute name
Data element identifier
Identification class
Definition class
Representation class
Data element name
Abbreviation of data element
Synonymous name of data element
Data element definition
Data type of data element value
Representation form of data element value
Parameter of data element value
Unit of measurement of data element value
Composition mode code of data element value
Exchange format of data element value
Storage format of data element value
Entry format of data element value
Selection requirements| |tt||Attribute category
Representation class
Relationship class
Management class
Note 1: “Required” indicates a required attribute. Table 2 (continued)
Attribute name
Display format of data element value
Value range of data element
Compound attribute code table number
Data element multi-value identifier
Data element keyword
Data element submission agency
Data element submission date
Data element registration agency
Data element effective date
Data element abolition date
Alternative data element identifier
Data element update date
Data element registration status
Data element version identifier
Additional notes on data element
Note 2: “Optional” indicates an attribute that can be selected or not. Note 3: “Conditional selection” means that the attribute is selected when a certain condition is met. 5.2
Attribute requirements
Data element identifier
5.2.1.1 Structure
GB/T37948—2019
Selection requirements
Conditional selection
The data element identifier consists of 3 parts, using an alphanumeric code with a total length of 10 digits. The code structure is shown in Figure 1. XXXXX
Area XXX
Sequence number
Basic data element identification code
Main classification code
Among them:
Data element identifier structure
Part 1: Main classification code, indicating the category to which the data element belongs, see Table 1; for data elements shared by multiple categories, the category code of the standard to which it belongs or "Z" is used;
Part 2: Basic data element identification code, with a length of 5 digits, the first 4 digits are Arabic numerals or uppercase English letters (excluding "1" and "O"), and the last digit is uppercase English Letters (excluding \I\"O"); GB/T37948—2019
Part 3: Sequence number, represented by 4 Arabic numerals, and coded incrementally according to the rule of \0000\0001"; if it is \0000", it means that the data element is a basic data element, otherwise it means an application data element derived from the basic data element. 5.2.1.2 Compilation requirements
The data element identifier shall meet the following requirements: a) A data element has one and only one data element identifier, and a data element identifier can only identify one data element; b) The data element identifier shall remain unique.
5.2.2 Data element name
The data element name shall be concise and remain unique. 5.2.3 Data element abbreviation
When the data element has an abbreviation, it should be filled in; if there are multiple abbreviations, each abbreviation shall be separated by a half-width ",". 5.2.4 Synonymous name of data element
When a data element has a synonymous name, it should be filled in; if there are multiple synonymous names, each synonymous name should be separated by a half-width “,”. 5.2.5 Data element definition
The data element definition should be able to accurately express the essential characteristics of a data element and distinguish it from other data elements. The data element definition should be concise. 5.2.6 Data type of data element value
The data type of data element value can be selected from Table B.1 in Appendix B. 5.2.7 Representation form of data element value
The representation form of data element value can be selected from Table B.2. 5.2.8 Parameters of data element valuewwW.bzxz.Net
The parameters of data element value should be filled in in accordance with the following requirements: a) For data elements whose data element values are variable-length character strings and variable-length binary types, the minimum and maximum number of bytes shall be specified. The format is m..n, where m represents the minimum number of bytes and n represents the maximum number of bytes. If there is no requirement for the minimum number of bytes, m is o. The number can be followed by \K", \M\\G" and "T" to represent kilobytes, megabytes, gigabytes, or terabytes. Example 1:
1..90 represents the minimum number of bytes is 1 and the maximum number of bytes is 90; 0..200 represents the maximum number of bytes is 200; 0..100K represents the maximum number of bytes is 100Kb) For data elements whose values are fixed-length character strings and fixed-length binary data elements, an integer is used to specify the number of bytes. \K", "M\\G\\T" can be appended to represent kilobytes, megabytes, gigabytes, or terabytes. Example 2:
30 represents a fixed length of 30 bytes; 200K represents a fixed length of 200K bytes. c) For data elements whose values are integers, an integer is used to specify the maximum number of digits; d) For data element values For data elements that are decimals, specify their significant digits and precision. Use the format of mn, where m represents the number of significant digits of the value and n represents the number of digits after the decimal point. Example 3:
10.3 means that the number of significant digits is 10 and the precision is 3 decimal places. e) For data elements whose data type is date and time type, do not fill in the parameters of the data element value. 4
5.2.9 Unit of measurement of data element value
GB/T37948—2019
For data elements whose representation form is "numeric value" or "range value" and have a unit of measurement, the Chinese name of the unit of measurement should be filled in. For data elements of other representation forms, do not fill in.
Composition pattern code of data element value
The composition pattern code of data element value can be selected from Table B.3. 5.2.11
Exchange format of data element value
The rules for filling in the exchange format of data element values are determined according to the composition pattern of the data element values and are filled in according to the rules in Table 3. For examples of filling in the exchange format of data elements that use multiple code tables, see Appendix C Table 3 Rules for filling in the exchange format of data element values Composition pattern of data element value
Format code
Composition pattern of data element value
Format name
1 ordinary text
1 code text
1 value
1 date
1 date time
1 time
1 range value
Rules for filling in the exchange format of data element values
1. Variable-length character string: (*nX) or (*nN) or (*nA2. Fixed-length character string: (nX) or (nN) or (nA) (TABI|BA)
1. Integer: (INTIn)
2. Decimal: (DEC|mn)
1. Without separator: (YYYYMMDD)
2. With separator: (YYYY)-(MM)-(DD)1. Without separator: YYYYMMDDhhmmss)2. With separator: (YYYY)-(MM)-DD)T(hh):(mm):(ss)
1. Without separator: (hhmmss)
2. With separator: (hh):(mm):(ss)1. Integer: (INT|n1)/(INT/n2)
2. Decimal: (DEC/mn)|(DEC|mn)
Exchange format filling rules for data element values Note "*" is an indicator, indicating a variable-length string. "n\ is the maximum number of bytes in the string. "X" represents characters that meet the requirements of GB18030, \N\ represents pure numbers, and \A\ represents pure letters. Examples: *10X)*100N), (*6A), (10X) (7N). (9A)
TAB is a fixed identifier representing the code table, and TAB1 represents the code table. BA refers to the BA column of the code table
If it is an integer, fill in (INTIn), INT is a fixed identifier, representing an integer, "n is the maximum number of digits of the data element value. If it is a decimal, fill in (DECIm.n) DEC is a fixed mark, indicating a decimal, "mn\ indicates that the number of significant digits is m, accurate to the decimal point.
Example: (INT|8), (DECI10.3) YYYY indicates year, MM indicates month, DD indicates day. The use of separators should comply with the requirements of GB/T7408. YYYY indicates year, MM indicates month, DD indicates day, hh indicates hour, mm indicates minute, ss indicates second, and the time adopts 24-hour system. The use of separators should comply with GB /T7408 requirements: hh represents hours, mm represents minutes, ss represents seconds, and the 24-hour system is used. The separators used should comply with the requirements of GB/T7408. If the range value is an integer, fill it in the form of (INT|nl)I(INT|n2), where INT is a fixed identifier representing an integer, and "n1\\n2" is the maximum number of digits of the integer. If it is a decimal, fill it in as "DEC|mn" (DECIm.n). DEC is a fixed identifier representing a decimal. "\mn" means that there are m valid digits, accurate to n decimal places. Of the two elements, the smallest value comes first.
Example: INT|8)|(INT|8)(DEC|8.2)/(DEC10.25
GB/T37948—2019
Data element value
Composition pattern
Format code
Data element value
Composition pattern
Format name
1 Boolean value
1 group of binary numbers
2 code texts
1 code text
1 general|| tt||Common text
2 code texts
Text + 1 common
Common text
1 code text
2 code texts
Table 3 (continued)
Rules for filling in the exchange format of data element values
1. String type: (*nX) or *nN) or (*nA) or (nX) or (nN) or (nA)
2. Numeric type: (1N)
1. Variable length: f*nB) or *nHEX
2.Fixed length: (nB) or (nHEX)
(TABI|BA)|(TAB2|BA)
(TABI/BA)/*X)
(TABI|BA)TAB2|BA)(*X)
1. The value is an integer: (TABIBA)IINT|n)2. The value is a decimal: (TABI|BA)/(DEC|mn)1. The value is an integer: (TABI|BA/|(TAB2|BA)I(INTn)
2. The value is a decimal: (TABI|BA/I(TAB2|BA)I(DECIm.n)
Exchange format of data element value filling rules When the comment uses the string type, "*" is an indicator, It indicates a variable-length string. "n" is the maximum number of bytes in the string. "X\" indicates characters that meet the requirements of GB18030, "\N" indicates pure numbers, and "A\" indicates pure letters. When using numeric type, 1 digit is used to indicate
"" is an indicator, indicating a variable-length binary number. "B" indicates byte, "HEX\" indicates the byte value expressed in hexadecimal, and "n" is the maximum number of bytes in the binary number. When using hexadecimal expression, 1 byte of binary number is represented by 2 characters from 0 to 9.A to F, such as: 1E, 6F, A3. Example: *20B), (*32HEX). (40B (16HEX) TAB is a fixed identifier, indicating a code table, TABI indicates the th code table, TAB2 indicates The second code table. BA refers to the BA column of the code table
TAB is a fixed identifier, indicating a code table, and TAB1 indicates the th code table. BA refers to the BA column of the code table. "X\ represents an indefinite length character set that complies with the provisions of GB18030. TAB is a fixed identifier, indicating a code table, and TAB1 indicates the th code table. TAB2 represents the second code table. BA refers to the BA column of the code table. "*X\ represents an indefinite length character set that complies with the provisions of GB18030
TAB is a fixed identifier. indicates a code table, and TAB1 indicates the th code table. BA refers to the BA column of the code table. If the value is an integer, fill in INTi, INT is a fixed identifier, indicating an integer, and "n" is the maximum number of digits of the data element value. If If it is a decimal, fill in (DECIm.n), DEC is a fixed identifier, indicating a decimal, "mn\ indicates that the number of valid digits is m, accurate to n decimal places.
Example: (TABIBA)|(INT|8)TABI|BA)1(DEC|8.2)
TAB is a fixed identifier. It indicates a code table, TAB1 indicates the th code table, and TAB2 indicates the second code table. BA refers to the BA column of the code table. If it is an integer, fill in "INT|n)INT is a fixed identifier, indicating an integer, and "n" is the maximum number of digits of the data element value. If it is a decimal, fill in DEC|mn), DEC is a fixed identifier, indicating a decimal, \mn\ indicates that the number of valid digits is m, accurate to n decimal places. Example: (TABI|BA)|TAB2|BA)(INT8(TAB1|BA)|(TAB2|BA)(DEC|8.2) Composition pattern of data element value
Format code
Composition pattern of data element value
Format name
1 code text
Script+1 model
2 code texts
Script+1 model
Table 3 (continued)
Exchange format filling rules for data element values
1. Range value Integer: TABI|BA)I(INTn1)INT|n2)
2. Range value is decimal: (TABI|BA/I(DEC|mn)I(DECm.n)
1 Range value is integer: (TABI|BA)「(TAB2BA)/(INT|n1)/(INT|n2)
2. Range value is decimal: (TAB1/BA)|(TAB2BA)/(DEC|mn?/(DEC|mn)
GB/T37948—2019|| tt||Data element value exchange format filling rules Notes TAB is a fixed identifier, indicating a code table, TAB1 indicates the th code table. BA refers to the BA column of the code table. If the range value is an integer, fill in (INTnI)I(INT|n2), INT is a fixed identifier, indicating an integer, "n1" and "n2" are the longest number of digits of the integer. If it is a decimal, fill in (DECIm.n)|DECIm.n), DEC is a fixed identifier, indicating a decimal, \mn\ indicates that the number of valid digits is m, accurate to n decimal places. The smallest value comes first. || tt||Example: (TAB1|BA)|(INT|8)(INT|8)(TAB11BA)|(DEC|8.2)(DEC|10.2)
TAB is a fixed identifier, indicating a code table, TAB1 indicates the th code table, and TAB2 indicates the second code table. BA refers to the BA column of the code table. If the range value is an integer, fill in (INT|n}IINTn2}INT is a fixed identifier. Indicates an integer.\n1\\n2\ is the longest number of digits in an integer. If it is a decimal, fill in (DEC|mn)/n)
1. The range value is an integer: (TAB1|BA)「(TAB2BA)/(INT|n1)/(INT|n2)
2. The range value is a decimal: (TAB1/BA)|(TAB2BA)/(DEC|mn?/(DEC|mn)
GB/T37948—2019
Data element value exchange format filling rules Note TAB is a fixed identifier, indicating a code table, TAB1 indicates the code table. BA refers to the BA column of the code table. If the range value is an integer, fill in (INTnI)I(INT|n2), INT is a fixed identifier, indicating an integer, "n1" and "n2" are the longest number of digits of the integer. If it is a decimal, fill in (DE CIm.n)|DECIm.n), DEC is a fixed identifier, indicating a decimal, \mn\ indicates that the number of valid digits is m, accurate to n decimal places. The smallest value comes first.
Example: (TAB1|BA)|(INT|8)(INT|8)(TAB11BA)|(DEC|8.2)(DEC|10.2)
TAB is a fixed identifier, indicating a code table, TAB1 indicates the th code table, and TAB2 indicates the second code table. BA refers to the BA column of the code table. If the range value is an integer, fill in as (INT|n}IINTn2}INT is a fixed identifier. Indicates an integer. \n1\\n2\ is the longest number of digits of an integer. If it is a decimal, fill in as (DEC|mn)/n)
1. The range value is an integer: (TAB1|BA)「(TAB2BA)/(INT|n1)/(INT|n2)
2. The range value is a decimal: (TAB1/BA)|(TAB2BA)/(DEC|mn?/(DEC|mn)
GB/T37948—2019
Data element value exchange format filling rules Note TAB is a fixed identifier, indicating a code table, TAB1 indicates the code table. BA refers to the BA column of the code table. If the range value is an integer, fill in (INTnI)I(INT|n2), INT is a fixed identifier, indicating an integer, "n1" and "n2" are the longest number of digits of the integer. If it is a decimal, fill in (DE CIm.n)|DECIm.n), DEC is a fixed identifier, indicating a decimal, \mn\ indicates that the number of valid digits is m, accurate to n decimal places. The smallest value comes first.
Example: (TAB1|BA)|(INT|8)(INT|8)(TAB11BA)|(DEC|8.2)(DEC|10.2)
TAB is a fixed identifier, indicating a code table, TAB1 indicates the th code table, and TAB2 indicates the second code table. BA refers to the BA column of the code table. If the range value is an integer, fill in as (INT|n}IINTn2}INT is a fixed identifier. Indicates an integer. \n1\\n2\ is the longest number of digits of an integer. If it is a decimal, fill in as (DEC|mn)/
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.