L2/01-177 From: Frank Farance [frank@farance.com] Sent: Tuesday, May 01, 2001 12:19 AM Subject: CT22: ISO/IEC 2382 Vocabulary Issues for SC22 and SC32 =================================================================== Background: SC1, the JTC1 subcommittee dealing with vocabulary issues, has met the creator. Their major work, the vocabulary standard ISO/IEC 2382 consists of many parts that need maintenance - I volunteered SC2 for the maintenance of Part 4 where character set technology and related terms are defined. My suggestion to CT22, the combined US TAG to all SC22 subcommittees, triggered a detailed analysis by Frank Farance, copied below. I would like to discuss this subject at the next L2 meeting as part of our TAG to SC22/WG20 activity. A complete list of the parts of ISO/IEC 2382 is in document L2/01-178 Arnold At 11:56 2001-04-11 -0400, Winkler, Arnold F wrote: > Rex, > > In my humble opinion, Part 4 - character set technology, should be handled > by SC2. > > The various language committees treat character sets differently - only SC2 > looks at this subject from a generic point of view. > > "Things" like byte, octet, word, character, character set, encoding, coded > character set, etc... need to be defined by SC2 ! > > Arnold Arnold- I agree that some terms in Part 4 might "belong" to SC2, but not all terms. Here's my recommendations on SC2 "ownership" of terms: SC2? Term Subclause ===== ====================================== ========= Maybe 8-bit byte 04.05.10 Yes alphabet 04.03.03 Yes alphabetic character 04.03.02 Yes alphabetic character set 04.01.03 Yes alphabetic code 04.02.06 Yes alphabetic code element set 04.02.10 Yes alphabetic code set 04.02.10 Yes alphabetic string 04.05.03 Yes alphabetic word 04.06.02 Yes alphanumeric character 04.03.06 Yes alphanumeric character set 04.01.05 Yes alphanumeric code 04.02.08 Yes alphanumeric code element set 04.02.12 Yes alphanumeric code set 04.02.12 Yes alphanumeric word 04.06.04 No B-tree 04.10.08 No balanced tree 04.10.07 No beginning-of-file label 04.09.09 No beginning-of-volume label 04.09.07 No bidirectional list 04.08.04 Yes binary character 04.03.10 Yes binary character set 04.01.06 No binary code 04.02.09 No binary code element set 04.02.13 No binary code set 04.02.13 Yes binary digit 04.03.09 No binary tree 04.10.05 Maybe bit 04.03.09 Yes bit string 04.05.04 Yes blank 04.03.11 Yes blank character 04.03.11 No block (in organization of data) 04.07.07 No block length 04.07.08 No block size 04.07.08 No blocking factor 04.07.09 Maybe byte 04.05.08 No chained list 04.08.02 Yes character 04.01.01 Yes character set 04.01.02 Yes character string 04.05.02 No circular list 04.08.03 No code 04.02.01 No code (deprecated in this sense) 04.02.03 No code (deprecated in this sense) 04.02.04 No code (deprecated in this sense) 04.02.05 No code element 04.02.04 No code element set 04.02.05 No code extension character 04.04.05 No code set 04.02.05 No code value 04.02.04 Yes coded character set 04.02.03 No coded set 04.02.02 No coding scheme 04.02.01 Maybe computer word 04.06.05 Yes control character 04.04.01 No data element (in organization of data) 04.07.01 Yes decimal digit 04.03.07 Maybe delimiter (in organization of data) 04.09.01 No dequeue 04.08.09 Yes device control character 04.04.06 Yes digit 04.03.05 No double-ended queue 04.08.09 Maybe end-of-file label 04.09.10 Maybe end-of-volume label 04.09.08 Maybe EOF (abbreviation) 04.09.10 Maybe EOV (abbreviation) 04.09.08 No field (in organization of data) 04.07.02 No file 04.07.10 No file maintenance 04.07.12 No file updating 04.07.11 Yes format effector 04.04.04 Yes graphic character 04.03.01 No HDR (abbreviation) 04.09.09 No header label 04.09.09 No heap (in organization of data) 04.08.10 No height 04.10.06 No height-balanced tree 04.10.07 Yes hexadecimal digit 04.03.08 Yes identifier (in organization of data) 04.09.02 Yes ideogram 04.03.04 Yes ideographic character 04.03.04 No internal label 04.09.06 No key (in organization of data) 04.09.03 No label (in organization of data) 04.09.05 Yes letter 04.03.02 No linear list 04.08.05 No linked list 04.08.02 No list 04.08.01 No list processing 04.08.08 No logical record 04.07.04 Yes machine word 04.06.05 Maybe n-bit byte 04.05.09 No node (in organization of data) 04.10.01 Yes null string 04.05.05 Yes numeric character 04.03.05 Yes numeric character set 04.01.04 Yes numeric code 04.02.07 Yes numeric code element set 04.02.11 Yes numeric code set 04.02.11 Yes numeric word 04.06.03 Yes octet 04.05.10 No ordered tree 04.10.04 No physical record 04.07.05 No pointer (in organization of data) 04.09.04 Yes position 04.05.07 No pushdown list 04.08.06 No pushup list 04.08.07 No queue 04.08.07 No record (in organization of data) 04.07.03 No record length 04.07.06 No record size 04.07.06 No ring 04.08.03 No rooted tree 04.10.02 Yes space character 04.04.03 Yes special character 04.03.12 No stack 04.08.06 Yes string 04.05.01 No subtree 04.10.03 No symmetrical list 04.08.04 No table 04.07.13 No trailer label 04.09.10 Yes transmission control character 04.04.02 No tree 04.10.02 Yes unit string 04.05.06 No volume header 04.09.07 No volume label 04.09.07 Yes word 04.06.01 Yes word length 04.06.06 Yes word size 04.06.06 Note: Yes = Term should "belong" to SC2. Maybe = Requires further discussion. No = Term should not "belong" to SC2. -FF ----------------------------------------------------------------------- Frank Farance, Farance Inc. T: +1 212 486 4700 F: +1 212 759 1605 mailto:frank@farance.com http://farance.com Standards, products, services for the Global Information Infrastructure 4