Magnetic tape exchange format for terminological/lexicographical records (MATER)
Some standard content:
National Standard of the People's Republic of China
Magnetic tape exchange format for terminological/lexicographical records (MATER)
GB/T13726-92
This standard refers to the international standard ISO () 6156-1987 Magnetic tape exchange format for terminological/lexicographical records (MATER)1 Subject content and scope of application
This standard designs a framework for information exchange, specifies the connotation of terminological/lexicographical data items, and provides a universal format for the exchange of monolingual or multilingual terminological/lexicographical records data in a standardized manner. This standard is applicable to the information exchange of computer-readable data carriers between information systems. 2 Reference standards
GB1988 Information processing Seven-bit coded character set for information interchange Method of representation of 8-bit coded character set for information processing interchange on 9-track 12.7 mm magnetic tape1 GB 1989
Information processing Seven-bit and eight-bit abbreviated character set code expansion technology GB2311
GB 2312
Basic Chinese coded character set for information interchange Code for names of countries and regions around the world
GB 2659
GB 2001
GB 4880
Magnetic tape format for information interchange
Language name code
9-track 12.7 mm wide 63 lines/mm phase modulation recording tape for information processing interchange G 6550
GH 7574
GB 7589
Tape labeling and file structure for information processing exchange Information exchange Old Hanning coded character set second auxiliary nest GB7590
Chinese character coded character set for information exchange, fourth auxiliary set [GB8565.1-~8565.3 Double sense processing Coded character set for literary communication GB10112 General principles and methods for establishing pronouns GH11383 Information processing Information exchange Eight-bit code structure and code rules GH/T13715 Modern Chinese word segmentation specification for information processing "Hanyu Pinyin Orthography" The purpose of this standard is to promote the information exchange between terminology and dictionary databases, so that the database owner can provide all or part of the data to others in a standard format, and at the same time obtain the required data from other databases in a standard format. The role of this format is to allow each database owner to exchange data by only compiling two conversion programs: the first is to convert the external format into the standard format; the second is to convert the standard format into the internal format. This standard only specifies the format's application structure, and does not define the length of each record. In this standard, terminology and dictionary data should be interpreted as: approved by the State Technical Supervision Commission on October 6, 1992 and implemented on June 1, 1993. The content of the terminology database includes: GB/T 1372692. 4.1 Term and dictionary entry record: A combination of data fields, including a record header, a reference data area, a data area and an exchange unit containing terminology data and dictionary data. 4.2 Data area: An index of the location of all data fields in a record, including the field identifier, length, position and descriptor of each data field. 4.3 Data field: A variable length portion of a record containing a specific data item. It is located within a directory area and is associated with a directory entry. 4.4 Directory area description: A parameter that describes the structure of a directory entry. 4.5 Data item: a data segment that constitutes a terminology dictionary entry record and has a specific meaning. 4.6 Data item category: a group of data items that describe terminology and dictionary entries. 4.7 Field identifier: three characters used to identify a data field. 4.8 Specifier: a character that provides additional information for the content of the corresponding data field. 4.9 Terminology and dictionary exchange unit: a collection of data fields that describe a term (and its various meanings) or a concept (and all synonyms related to it).
5 Shared character set
Characters in GB1988 and other standard character sets (such as (H2312-GB7589.G7590) and other characters registered in S) called according to the method specified in GB2311 should be used. This standard stipulates that GB19 product & is the basic character set. All characters used in record headers and sub-areas, characters used in coded data, and various separators are taken from GB 1988. If a character set other than GB 1988 is used, it must be specified first before it can be called as the working character set. The method of specifying and calling complies with the provisions of GB 2311. The specific implementation method can refer to Article A2.6 of Appendix A of GB 2901.
Summary: The difference in the character set used by the equipment may cause serious obstacles to data conversion. The automatic conversion between different versions of the character set (national version or user version) is quite complicated, and it is often difficult to do if there is no description of its content. Therefore, the two parties to the data exchange should reach an agreement on the character set and character code to be used, and describe it in detail in the information exchange specification (see Appendix (3) 6 Structure of exchange files This standard specifies the document format for the exchange of technical and dictionary data (see Chapter 7). If other types of documents are to be exchanged, the data should be stored in a separate file in the format specified in GB 2901. Other data should be exchanged in the form of auxiliary files (see 6.2.4). The user must fill in the exchange instructions for the exchange files that are required by the user but cannot be submitted in machine-readable form. 6.1 Files and tapes All files on the tape should be marked according to the markings specified in GB 137574. All records are variable length. In the marking levels allowed by GB 137574, the level band protects variable length records. 6.2 Structure of exchange files The exchange unit and record structure of the exchange file are shown in Figure 1. 6. 2.1 Exchange unit
Offset record
GB/T 13726-92
Exchange unit
Transformation unit
The exchange file consists of an optional information record and several exchange units. Each exchange unit includes one or more variable-length records. The length of each record is represented by the first 5 digits of the record header (see 7.1.1). Note: The record length described here is a logical record length. According to the specific situation of the data machine processing, when the information of a record is recorded on a microprocessor, it may be divided into several physical blocks. I757 specifies the standard technology for implementing cross-blocks on tunnels. 6.2.2 Information record
Information record enables the receiving organization to automatically analyze the exchanged file immediately. In addition to general information (such as the name of the producer and the date of establishment), the information record should also include the separator character used, the character set name (i.e. the international registration number of the character set introduced by the escape sequence in ISO 100) and the character set reference table. The use of information record is optional. If information record is used, it should be the first record of the file. In order to uniquely identify the information record, all 8 bits of character position 5 in the record header (the second item of the record header, i.e. the record status bit) should be "I".
6.2.3 Data file
A separate file should be used to exchange the relevant data. The record structure of the data in this file should be consistent with the format specified in GB 2901.
6.2.4 Auxiliary file
This file includes auxiliary information about the exchanged data, such as mathematical diagrams, semantic information for data processing, data processing procedures, etc.
The record structure of this document is not fixed. The exchange institutions must reach or agree on this, or explain it in the annex to the information exchange instructions.
? Structure of exchange units
This chapter only defines the logical record structure that constitutes the exchange unit, and does not specify any special record entry system. This format is partially based on GB 290[,And suitable for terminology and dictionary entries: an exchange unit contains the data of a term or dictionary entry record (for example, a dictionary entry), usually a variable-length record in the exchange file. In some cases, an exchange unit can consist of several records. Records belonging to the same exchange unit should have the same identification number. They are distinguished by the sequence number in the record count. Record identification: reference data area character position (1~7 (see 7.1.2); record count: reference data area character position 8 and 9 (see 7.1.2). 7.1 Record structure
Figure 2 shows the general format of a record
Record header
Reference data area
Sub area
Data area
Record separator
GB/T 13726—92
A record contains the following contents, in the order shown in Figure 3: Record header: fixed length;
Reference data area: fixed length,
Day area: variable length;
Data segment: variable number and variable length;
Segment separator: characters: should use the field separator (RS) defined in GB198811; Record separator: one character: should use the record separator (GS) defined in GB1988. 7.1.1 Record header
The record header is the first part of the record, and its content is the semantic information for identifying and processing the record (see Table 1). Table 1
Character position
17~-19
Type
Record length
Record status
Execution code3
Indicator length
Data base address1
Number of bytes in the record
N=new
A-modification
J)=remove
00 or instruction code)
Number of characters occupied by the data field length of the service item in the sub-area||tt ||The number of characters occupied by the "starting character position" of each directory item in the directory area
Descriptor length"
Note: 1) C; left-aligned, digital type V: right-aligned, decimal character, fill in the front if necessary, 2) Used to indicate the record type; terminology, paragraph, month, etc., 3) The position of the th field in the data field area relative to the th byte of the record. 3
4) The descriptor has three digits. The first and second digits indicate the language of the data, and the third digit indicates the repetitiveness of the data segment or the group it belongs to (see 7.1.4.1). If not used, there is always one digit in the descriptor.
The number of character digits~4
10 ~17
18 - 23
24 ~ 47
48 ~71
+2 ~ 95
15 characters
E12~14
Data base address
3 characters
7.1.2 Reference data area
GB/T13726-92
Record length
Record status
Execution code
Indicator length
Data base address
Item length
Length of "study section length"
Date change item length
Length of "character position"
Indicator length
Exchange unit identification number
Record record
Source institution internal identification number
Generation date
Subject code|| tt||Language code
School section identifier
Number of fields length
Starting address
Description
Directory item
Directory entry
Field classifier RS
Indicator
Field separator RS
Directory section
Data field
Record separator GS
Data area
Directory entry
Sub-area
Data area
Fixed-length part
Variable-length part
In order to more conveniently access a complete exchange unit, a reference data area with a total length of 96 bytes (see Table 2) is set immediately after the record header. This part is different from GB2901 numbering
character position
18--23
24-~ 47
4S-~71
72 -95
Syntax: 1) C: Left align the character number 1
V; left align the decimal number character. 7.1.39 Identification number of exchange unit (GB/T 13726—92) The serial number of the exchange unit in the record file shall be in ascending order starting from 00000001 in the decimal system. The internal code assigned by the data provider to the exchange unit shall be assigned by the source institution. The subject area code of the exchanged degree shall be the language of the exchanged degree. The final revision date of the source tree (YYMMDD) shall be specified in the "Deposit and Transfer Instructions 15". GR 4880 shall be used. The daily time zone reflects the relevant information of the data in each data segment. The daily time zone is part of the record. It only reflects the data in this record and does not reflect the information of the data in other records belonging to the same exchange unit. Each record has its own monthly time zone. The length of the items in the daily time zone is 15 bytes. The number of times in the record varies from record to record but should be consistent with the number of data fields in this record. The structure of the corresponding daily time item is shown in Figure 1: Character sequence: 2--11 Character identifier Data segment length Starting character position of data field Name symbol (see Note 4 of Table 1 of 7.1.1) The order of the items in the daily time zone should be the same as the order of the corresponding data fields in the record. Note: The starting character position in the DH sub-area is relative to the data field (the 12th to 16th character positions in the record header are given at the factory base). The starting character position of the data field is
. The H sub-area should end with the R in the GB segment separator. If necessary, the field identifiers can be repeated alternately. 4: The data field length refers to the total length of the data field including the indicator and field separator. 7.1.4 Data field
The data field is used to store the data to be exchanged. Each field contains only one data field. The length of the data field is variable. The structure of the data segment is shown in Figure 5.
Character position
3~(K-1)
GB/T 13726
Indicator
Field separator (RS)
In order to facilitate the search and output of data without relying on the date and time zone, the field identifier in the entry is repeated here as an indicator. A data field cannot span two records. If necessary, use overflow records (see 7.2). 7.1.4.1 Grouping
Several data fields or data field groups can reuse the same field identifier. The third position of the descriptor is used to distinguish repeated segments or field groups.
7.1.4.2 Examples
Example 1: (single language)
Descriptor
Example 2, (multi-language)
Descriptor
7.2Record type
Field label
Field identifier
Contents of the corresponding data field
Term in language A
First meaning in language A
First synonym in language A
Second synonym in language A
Previous meaning in language A
Source of definition in language A
Contents of the corresponding data field
Term in language A
Synonyms in language A
Primary meaning in language A
Source of definition in language A
Term in language B
Source of definition in language B The first meaning of the first word in the language
The first meaning in the language
The definition of the main word in the language
The definition of the main word in the language
The source of the definition in the language
The exchange unit specified in this standard can be a single record or a combination of consecutive records. Figure 6 shows a conversion unit consisting of a single record without overflow (record count: 00): GB/T 13726
Reference data area
Character position ~
Character position 8~9
00000027
Identification number
Record count
If an exchange unit consists of several records, these records can be divided into two categories: nt main record;
h. overflow record.
The first record is a primary record, and the rest are overflow records. For example, the exchange unit FF consists of one record (record count of the main record: 01): the first record is a secondary record
character position 0~?
character position 8--0
the...th record is an overflow record
character position 0~
character position 8~9
the third record is the last overflow record, character position 6~
next character position 8~ 9
The record number of the last outgoing record is 99. 00000028#
Speech
0060029
00000528
Identification number
Record count
Mark number
Record count
If an exchange unit contains many information items in different languages, all information items in the same language should be arranged together. , and then continue to press the word (see 7. [.1.2 in Example 2) instead of arranging the basic items of each language together. In this case, a switching unit can be decomposed into several records. If only one record is used to represent a switching unit, the total length of its record header, reference data area, and sub-area exceeds the block length allowed by the data carrier, and the user does not intend to store the directory area in different blocks, then the switching unit can be decomposed into a main record and several overflow records. When decomposing, any data field must not start from one record and end at the next record, that is, the end of the record must be the end of the field.
In the switching code, each language can be reduced to a separate record. h.
8 Use
GB/T13726-92
The field identifier in the software item and the indicator in the data segment are collectively referred to as the data item code. Figure 8 is an example of a data item. Monthly item
Number of items
Data item
9Information exchange specifications
Field identifier
Data field length
Starting character of data field
Specifier
Indicator
Field separator
Information exchange specifications should be submitted when exchanging tapes to describe the structure and content of the exchanged data. The appendix gives the introduction to the information exchange specifications.
10 Exchange data categories
In order to exchange information, each sending organization should define each data item that constitutes the exchange unit. As a guide, Appendix A and Appendix B give the organization specifications.
The field identifiers used in the exchange file shall be constructed as follows: a. The first position of each data item field identifier shall be the classification number given in Table 3; b. If the data items described in Appendix A and Appendix B are used: the second and third positions shall be the numbers therein; if the data items in Appendix A and Appendix B cannot describe the sender's data, the second and third positions shall be two alphabetic characters. In the latter case, the field identifiers used in the exchange file shall be described in detail in the information exchange specification. Table 3 is a list of classification numbers for data items. Table 3
Reproducibility
Nature of data
Term or dictionary entry
Lexical description
Subject area of the term and its description
Definition, explanation, examples, context of the concept expressed by the term
Reproducibility
GB/I 13726—92
Continued Table 3
Nature of data
Relationship between concepts and (or) terms in the same language
Other correspondences
Other information
Responsibility of the exchange unit
Language of the term, common words, monosyllabic words, homophones (morphologies), variants, intersex words, and related words.
Information related to the source of any data item, including copyright
GB/T 1372692
Appendix A
Recommended terminology data items and their identifiers for the Chinese terminology database (supplement)
This appendix specifies terminology data items suitable for the characteristics of the Chinese language. A1 Terminology and dictionary entries
Identifiers
Repeatability
Removal of entry
Chinese phonetic spelling
Standard section names
Should follow the "Basic Rules of Chinese Phonetic Orthography" [Chinese Phonetic Spelling] Section and four tones
Simple (language)
Jinghua (industry terminology)
Note: w indicates that the data item can be repeated several times in a row: indicates that the data item is repeated in groups with other data items: should follow the basic rules of Chinese phonetic orthography. If you need to divide the subfield, use the division method of 5.7.2 in (1112), and indicate in the information exchange manual that the code 4 is abbreviated (language), use this field. When "ASEAN" is used as the term When using mountain terms, this field should indicate its complete form\ASEAN\
A: Historical evolution source, for example: \purple" source ten "tea 1\, foreign speaking. Example: "AIDS" originated from \AIIS (English)" A: Standard language variant, for example, the blade industry has used the skill spectrum example, matches, foreign fire <formerly used name)
1i: Dialect variant, for example, different usages in different regions example: Shuibi--Yangdong (dialect>
death: special language variant|| tt||Different terms that refer to the same concept as the main entry in a certain industry. Idioms, idioms, two-part allegorical sayings, idioms, metaphors, etc. that are synonymous (or near-synonymous) with the main entry
【A field can contain the contents of many fields. These words do not need to be separated by semicolons. A2 Lexical description
A2.1 Lexical complexity
The structural analysis of news entries can refer to GB/T13715. Segment
Identifier
A2.2 Word class
Repeatability
GB/T 1372692
Field name
If you need to indicate the ability of the term to form a new term, you can use subfields: A: root
JE: preceding
; following
If you need to further analyze the term, you can use subfields: 1. Simple word
13, compound word
HF derived word
: phrase (language)
other symbols expressed by non-Chinese characters
If you need to further analyze the term, you can use the learning section; F: joint tree, for example: input input
G, attributive structure, insurance: microcomputer
H. verb-object structure: for example: data acquisition
I: subject-predicate structure, for example: myocardial slow death
J: linked verb structure, for example: solitary positive breathing
for example: NA. Etc.
The data items listed in this clause should be selected according to the needs of terminology work. Table A3
Identifier
Repeatability
Segment name
C: proper noun
[): collective noun
F: abstract noun
V countable noun
w, uncountable noun
X time noun
Y: space noun
7..direction nounDirection NounDirection NounExample 2 in 2) Instead of arranging the basic items of each language together, in the case of a sequence, an exchange unit can be decomposed into several records. If only one record is used to represent an exchange unit, the total length of its record header, reference data area, and sub-area exceeds the block length allowed by the data carrier, and the user does not intend to store the directory area in different blocks, then the exchange unit can be decomposed into a main record and several overflow records. When decomposing, any data field must not start from one record and end at the next record, that is, the end of the record must be the end of the field.
In the exchange code, each language can be reduced to a separate record. h.
8 Use
GB/T13726-92
The field identifier in the software item and the indicator in the data segment are collectively referred to as the data item code. Figure 8 is an example of a data item. Monthly item
Number of items
Data item
9Information exchange specifications
Field identifier
Data field length
Starting character of data field
Specifier
Indicator
Field separator
Information exchange specifications should be submitted when exchanging tapes to describe the structure and content of the exchanged data. The appendix gives the introduction to the information exchange specifications.
10 Exchange data categories
In order to exchange information, each sending organization should define each data item that constitutes the exchange unit. As a guide, Appendix A and Appendix B give the organization specifications.
The field identifiers used in the exchange file shall be constructed as follows: a. The first position of each data item field identifier shall be the classification number given in Table 3; b. If the data items described in Appendix A and Appendix B are used: the second and third positions shall be the numbers therein; if the data items in Appendix A and Appendix B cannot describe the sender's data, the second and third positions shall be two alphabetic characters. In the latter case, the field identifiers used in the exchange file shall be described in detail in the information exchange specification. Table 3 is a list of classification numbers for data items. Table 3
Reproducibility
Nature of data
Term or dictionary entry
Lexical description
Subject area of the term and its description
Definition, explanation, examples, context of the concept expressed by the term
Reproducibility
GB/I 13726—92
Continued Table 3
Nature of data
Relationship between concepts and (or) terms in the same language
Other correspondences
Other information
Responsibility of the exchange unit
Language of the term, common words, monosyllabic words, homophones (morphologies), variants, intersex words, and related words.
Information related to the source of any data item, including copyright
GB/T 1372692
Appendix A
Recommended terminology data items and their identifiers for the Chinese terminology database (supplement)
This appendix specifies terminology data items suitable for the characteristics of the Chinese language. A1 Terminology and dictionary entries
Identifiers
Repeatability
Removal of entry
Chinese phonetic spelling
Standard section names
Should follow the "Basic Rules of Chinese Phonetic Orthography" [Chinese Phonetic Spelling] Section and four tones
Simple (language)
Jinghua (industry terminology)
Note: w indicates that the data item can be repeated several times in a row: indicates that the data item is repeated in groups with other data items: should follow the basic rules of Chinese phonetic orthography. If you need to divide the subfield, use the division method of 5.7.2 in (1112), and indicate in the information exchange manual that the code 4 is abbreviated (language), use this field. When "ASEAN" is used as the term When using mountain terms, this field should indicate its complete form\ASEAN\
A: Historical evolution source, for example: \purple" source ten "tea 1\, foreign speaking. Example: "AIDS" originated from \AIIS (English)" A: Standard language variant, for example, the blade industry has used the skill spectrum example, matches, foreign fire <formerly used name)
1i: Dialect variant, for example, different usages in different regions example: Shuibi--Yangdong (dialect>
death: special language variant|| tt||Different terms that refer to the same concept as the main entry in a certain industry. Idioms, idioms, two-part allegorical sayings, idioms, metaphors, etc. that are synonymous (or near-synonymous) with the main entry
【A field can contain the contents of many fields. These words do not need to be separated by semicolons. A2 Lexical description
A2.1 Lexical complexity
The structural analysis of news entries can refer to GB/T13715. Segment
Identifier
A2.2 Word class
Repeatability
GB/T 1372692
Field name
If you need to indicate the ability of the term to form a new term, you can use subfields: A: root
JE: preceding
; following
If you need to further analyze the term, you can use subfields: 1. Simple word
13, compound word
HF derived word
: phrase (language)
other symbols expressed by non-Chinese characters
If you need to further analyze the term, you can use the learning section; F: joint tree, for example: input input
G, attributive structure, insurance: microcomputer
H. verb-object structure: for example: data acquisition
I: subject-predicate structure, for example: myocardial slow death
J: linked verb structure, for example: solitary positive breathing
for example: NA. Etc.
The data items listed in this clause should be selected according to the needs of terminology work. Table A3
Identifier
Repeatability
Segment name
C: proper noun
[): collective noun
F: abstract noun
V countable noun
w, uncountable noun
X time noun
Y: space noun
7..direction nounExample 2 in 2) Instead of arranging the basic items of each language together, in the case of a sequence, an exchange unit can be decomposed into several records. If only one record is used to represent an exchange unit, the total length of its record header, reference data area, and sub-area exceeds the block length allowed by the data carrier, and the user does not intend to store the directory area in different blocks, then the exchange unit can be decomposed into a main record and several overflow records. When decomposing, any data field must not start from one record and end at the next record, that is, the end of the record must be the end of the field.
In the exchange code, each language can be reduced to a separate record. h.
8 Use
GB/T13726-92
The field identifier in the software item and the indicator in the data segment are collectively referred to as the data item code. Figure 8 is an example of a data item. Monthly item
Number of items
Data item
9Information exchange specifications
Field identifier
Data field length
Starting character of data field
Specifier
Indicator
Field separator
Information exchange specifications should be submitted when exchanging tapes to describe the structure and content of the exchanged data. The appendix gives the introduction to the information exchange specifications.
10 Exchange data categories
In order to exchange information, each sending organization should define each data item that constitutes the exchange unit. As a guide, Appendix A and Appendix B give the organization specifications.
The field identifiers used in the exchange file shall be constructed as follows: a. The first position of each data item field identifier shall be the classification number given in Table 3; b. If the data items described in Appendix A and Appendix B are used: the second and third positions shall be the numbers therein; if the data items in Appendix A and Appendix B cannot describe the sender's data, the second and third positions shall be two alphabetic characters. In the latter case, the field identifiers used in the exchange file shall be described in detail in the information exchange specification. Table 3 is a list of classification numbers for data items. Table 3
Reproducibility
Nature of data
Term or dictionary entry
Lexical description
Subject area of the term and its description
Definition, explanation, examples, context of the concept expressed by the term
Reproducibility
GB/I 13726—92
Continued Table 3
Nature of data
Relationship between concepts and (or) terms in the same language
Other correspondences
Other information
Responsibility of the exchange unit
Language of the term, common words, monosyllabic words, homophones (morphologies), variants, intersex words, and related words.
Information related to the source of any data item, including copyright
GB/T 1372692
Appendix A
Recommended terminology data items and their identifiers for the Chinese terminology database (supplement)
This appendix specifies terminology data items suitable for the characteristics of the Chinese language. A1 Terminology and dictionary entries
Identifiers
Repeatability
Removal of entry
Chinese phonetic spelling
Standard section names
Should follow the "Basic Rules of Chinese Phonetic Orthography" [Chinese Phonetic Spelling] Section and four tones
Simple (language)
Jinghua (industry terminology)
Note: w indicates that the data item can be repeated several times in a row: indicates that the data item is repeated in groups with other data items: should follow the basic rules of Chinese phonetic orthography. If you need to divide the subfield, use the division method of 5.7.2 in (1112), and indicate in the information exchange manual that the code 4 is abbreviated (language), use this field. When "ASEAN" is used as the term When using mountain terms, this field should indicate its complete form\ASEAN\
A: Historical evolution source, for example: \purple" source ten "tea 1\, foreign speaking. Example: "AIDS" originated from \AIIS (English)" A: Standard language variant, for example, the blade industry has used the skill spectrum example, matches, foreign fire <formerly used name)
1i: Dialect variant, for example, different usages in different regions example: Shuibi--Yangdong (dialect>
death: special language variant|| tt||Different terms that refer to the same concept as the main entry in a certain industry. Idioms, idioms, two-part allegorical sayings, idioms, metaphors, etc. that are synonymous (or near-synonymous) with the main entry
【A field can contain the contents of many fields. These words do not need to be separated by semicolons. A2 Lexical description
A2.1 Lexical complexity
The structural analysis of news entries can refer to GB/T13715. Segment
Identifier
A2.2 Word class
Repeatability
GB/T 1372692
Field name
If you need to indicate the ability of the term to form a new term, you can use subfields: A: root
JE: preceding
; following
If you need to further analyze the term, you can use subfields: 1. Simple word
13, compound word
HF derived word
: phrase (language)
other symbols expressed by non-Chinese characters
If you need to further analyze the term, you can use the learning section; F: joint tree, for example: input input
G, attributive structure, insurance: microcomputer
H. verb-object structure: for example: data acquisition
I: subject-predicate structure, for example: myocardial slow death
J: linked verb structure, for example: solitary positive breathing
for example: NA. Etc.
The data items listed in this clause should be selected according to the needs of terminology work. Table A3
Identifier
Repeatability
Segment name
C: proper noun
[): collective noun
F: abstract noun
V countable noun
w, uncountable noun
X time noun
Y: space noun
7..direction noun
Information related to the source of any data item includes copyright
GB/T 1372692
Appendix A
Recommended terminology data items and their identifiers for the Chinese terminology database (supplement)
This appendix specifies terminology data items suitable for the characteristics of the Chinese language. A1 Terminology and Dictionary Identifiers Repeatability Delimited Date Chinese Pinyin Section Name Should Follow Basic Rules of Chinese Pinyin Orthography Syllables and Four Tones Simple Chinese Speech (Language) Jargon (Industry Terms) Note: w indicates that the data item can be repeated several times in a row: indicates that the data item is repeated in groups with other data items: Should Follow Basic Rules of Chinese Pinyin Orthography If sub-fields are required, use the division method in 5.7.2 of (1112) and indicate in the Information Exchange Instructions that the code is abbreviated (language), use this field. When "ASEAN" is used as a term, this field should indicate its full form Association of Southeast Asian Nations A: History The source of evolution, for example: \紫”源十”茶1\, foreign speaking. Example: "AIDS" originated from \AIIS (English)" A: Standard language variant, for example, the blade industry has used the technical spectrum example, matches, foreign fire <formerly used name)
1i: Dialect variant, for example, different usages in different regions example: Shuibi--Yangdong (dialect>
Death: Special language variant
Different terms that refer to the same concept as the main entry in a certain industry Idioms, idioms, two-part allegorical sayings, idioms, metaphors, etc. that are synonymous (or near-synonymous) with the main entry
[Death request A field can contain the contents of many fields, and these words do not need to be separated by semicolons. A2 Lexical description
A2.1 Lexical complexity
The structural analysis of the news entry can refer to GB/T13715. Segment
Identifier
A2.2 Part of speech
Repeatability
GB/T 1372692
Field name
If you need to indicate the ability of the term to form a new term, you can use subfields: A: root
JE: preceding
; following
If you need to further analyze the term, you can use subfields: 1. Simple word
13, compound word
HF derived word
: phrase (language)
other symbols expressed by non-Chinese characters
If you need to further analyze the term, you can use the learning section; F: joint tree, for example: input input
G, attributive structure, insurance: microcomputer
H. verb-object structure: for example: data acquisition
I: subject-predicate structure, for example: myocardial slow death
J: linked verb structure, for example: solitary positive breathing
for example: NA. Etc.
The data items listed in this clause should be selected according to the needs of terminology work. Table A3
Identifier
Repeatability
Segment name
C: proper noun
[): collective noun
F: abstract noun
V countable noun
w, uncountable noun
X time noun
Y: space noun
7..direction noun
Information related to the source of any data item includes copyright
GB/T 1372692Www.bzxZ.net
Appendix A
Recommended terminology data items and their identifiers for the Chinese terminology database (supplement)
This appendix specifies terminology data items suitable for the characteristics of the Chinese language. A1 Terminology and Dictionary Identifiers Repeatability Delimited Date Chinese Pinyin Section Name Should Follow Basic Rules of Chinese Pinyin Orthography Syllables and Four Tones Simple Chinese Speech (Language) Jargon (Industry Terms) Note: w indicates that the data item can be repeated several times in a row: indicates that the data item is repeated in groups with other data items: Should Follow Basic Rules of Chinese Pinyin Orthography If sub-fields are required, use the division method in 5.7.2 of (1112) and indicate in the Information Exchange Instructions that the code is abbreviated (language), use this field. When "ASEAN" is used as a term, this field should indicate its full form Association of Southeast Asian Nations A: History The source of evolution, for example: \紫”源十”茶1\, foreign speaking. Example: "AIDS" originated from \AIIS (English)" A: Standard language variant, for example, the blade industry has used the technical spectrum example, matches, foreign fire <formerly used name)
1i: Dialect variant, for example, different usages in different regions example: Shuibi--Yangdong (dialect>
Death: Special language variant
Different terms that refer to the same concept as the main entry in a certain industry Idioms, idioms, two-part allegorical sayings, idioms, metaphors, etc. that are synonymous (or near-synonymous) with the main entry
[Death request A field can contain the contents of many fields, and these words do not need to be separated by semicolons. A2 Lexical description
A2.1 Lexical complexity
The structural analysis of the news entry can refer to GB/T13715. Segment
Identifier
A2.2 Part of speech
Repeatability
GB/T 1372692
Field name
If you need to indicate the ability of the term to form a new term, you can use subfields: A: root
JE: preceding
; following
If you need to further analyze the term, you can use subfields: 1. Simple word
13, compound word
HF derived word
: phrase (language)
other symbols expressed by non-Chinese characters
If you need to further analyze the term, you can use the learning section; F: joint tree, for example: input input
G, attributive structure, insurance: microcomputer
H. verb-object structure: for example: data acquisition
I: subject-predicate structure, for example: myocardial slow death
J: linked verb structure, for example: solitary positive breathing
for example: NA. Etc.
The data items listed in this clause should be selected according to the needs of terminology work. Table A3
Identifier
Repeatability
Segment name
C: proper noun
[): collective noun
F: abstract noun
V countable noun
w, uncountable noun
X time noun
Y: space noun
7..direction noun
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.