SPEX / Dept. of Language and Speech University of Nijmegen Erasmusplein 1 NL-6525 HT Nijmegen The Netherlands SUBJECT: Validation French FDB5000 SpeechDat corpus AUTHORS: Henk van den Heuvel, Eric Sanders VERSION: 1.1 DATE : 9 November 2000 The speech databases made within the SpeechDat project were validated by SPEX, Nijmegen, the Netherlands, to assess their compliance with the SpeechDat format and content specifications, as documented in Deliverables 1.3.1, 1.3.2 and 1.3.3 of the project. The validation results of the French Fixed Network SpeechDat database (5000 speakers) are contained in this document. This database was validated and approved by the SpeechDat Consortium. In the validation procedure we systematically check a list of validation criteria for a range of subjects. In the following sections we will evaluate these criteria one by one. Validation results that call for attention because of deviations from the SpeechDat specifications are marked by =>. They can be easily extracted/'grepped' in this way. The following subjects were validated: 1 DOCUMENTATION 2 DATABASE STRUCTURE, CONTENTS AND FILE NAMES 3 ITEMS 4 SAMPLED DATA FILES 5 ANNOTATION FILES 6 LEXICON 7 SPEAKERS 8 ENVIRONMENTS 9 TRANSCRIPTION The document is concluded by 10 SUMMARY ==================================================================== 1. DOCUMENTATION - File DESIGN.DOC; & deliverables SD131 and SD132 can be handy OK, DESIGN.DOC is present - Language of doc file: English OK - Contact person: name, address, affiliation OK - Number of CDs OK - Contents of each CD OK - The directory structure of the CDs OK, section 1 - Description of all the items in the corpus OK, sections 1.2 and 3 - Prompting . linguistic specification (and motivation) for the prompting material (in case of additional optional items) . connection of sheet items to item numbers on CD . sheet example . items must be spread over the sheet to prevent list effects (e.g. three yes/no questions immediately after another are not allowed) OK, sections 2.3 and 9 See for connection of items with prompt codes the table in section 1.2 - Naming conventions for directories and files OK, sections 1.2 and 1.3 - Speaker recruitment OK, section 2.2 - Speaker demographics . which regions, how many of each . motivation for selection of regions . which age groups, how many of each . sexes: males, females, also children?; how many of each. . each call is made by a unique speaker OK, section 4 - Analysis of frequency of occurrence of the sub-word units represented in the phonetically rich sentences (either of phones, biphones, triphones) OK, section 3.11 - Analysis of frequency of occurrence of the sub-word units represented in the phonetically rich words (either of phones, biphones, triphones) OK, section 3.11 - Recording platform and telephone link description OK, section 2.1 => More details on the nature of the data acquisition board => and software are desirable - Signal characteristics (number of bits per sample; bandwidth; coding type; compression procedures) OK, section 1.1 - The format of the speech files (A-law, 8 bit, 8 kHz, uncompressed) OK, section 1.1 - The format of the annotation files (SAM label files) OK, section 1.4 - Annotation . procedure . quality assurance . character set used for annotation (transcription) (ISO-8859) . annotations symbols for non-speech acoustic events must be mentioned at least for Filled Pause, Speaker Noise, Stationary Noise, Intermittent Noise. . list of symbols used to denote word truncations, mispronunciations and not understandable speech . case sensitivity of transcriptions OK, section 2.4; only lower case letters have been usd => The tilde is also used to denote GSM distortions within sentences => as Table 6 states; => in this case the sign "&" for cellular distortions is in place - Lexicon information . Procedures to obtain phonemic forms from orthographic input (lexicon generation and lay out) . (Reference to) SAMPA symbols used . case sensitivity of entries (matching the transcriptions) OK, section 5 - Only one spelling of each word is allowed. Therefore a list of normalised spellings for words with alternative spellings should be included (SPELLALT.DOC). Otherwise a statement why such a list is not necessary. OK, such a statement is given in section 2.4 - Information on test (set) specification => Information on the test set and test specifications is missing - Indication of how many of the files were double checked by the producer together with percentage of detected errors OK, for transcriptions see section 2.4 - The validation report made by SPEX (VALREP.TXT) is referred to OK, section 1 ========================================================================== 2. DATABASE STRUCTURE CONTENTS AND FILE NAMES - Directory / subdirectory conventions Format of directory tree should be \\\ . data base: defined as <#> can be FIXED, MOBIL, VERIF <#> is 0 for SpeechDat(M) and 1 for SpeechDat is the ISO two-letter code for the language . block : defined as BLOCK where is a progressive number from 00 to 99. Block numbers are unique over all CDs. They correspond to the first two digits of below. . session: defined as SES where is the session code also appearing in file name OK - All text files should be in MS-DOS format () at line ends OK - A README.TXT file should be in the root describing all (documentation) files on the CD-ROM. OK - A file containing a shortened version of the volume name (11 chars max.) should be in the root directory. The name of this file is DISK.ID. This file supplies the volume label to UNIX systems that cannot read the physical volume label. Example of contents: FIXED1EN_01. OK - A copyright statement should be present in the file COPYRIGH.TXT (root) OK - Documentation should be in \\DOC . DESIGN.DOC . TRANSCRIP.DOC (optional) . SPELLALT.DOC (optional) . SAMPALEX.PS . ISO8859<1,2,7>.PS . SUMMARY.TXT . SAMPSTAT.TXT OK - The contents list (CONTENTS.LST) is in \\INDEX OK - Tables should be in \\TABLE . SPEAKER.TBL . LEXICON.TBL . REC_COND.TBL (optional) . SESSION.TBL (optional) OK, SPEAKER.TBL, LEXICON.TBL and REC_COND.TBL are present - Index files (optional) should be in \\INDEX OK - The index files (if present) obey the nomenclature .LST where e.g. A1ENN3.LST (see below for item_code) Not provided - Prompt sheet files (optional) should be in \\PROMPT Not provided - All sessions indicated in the documentation SUMMARY.TXT are present on the CDs OK - File naming conventions All file names should obey the following pattern: DDNNNNCC.LLF DD : database identification code For SpeechDat : A1 = fixed net, B1 = mobile, C1 = speaker verification NNNN : session code 0000 to 9999 CC : item code; first character is item type identifier, second character is item number LL : ISO-639 language code (with extensions) F : speech file type A is for A-law O is for Orthographic label file OK - Correct item codes should be used: A1-3/6: common application words B1 : sequence of isolated digits C1 : prompt sheet number C2 : telephone number C3 : credit card number C4 : PIN code D1-3 : dates E1 : application word phrase I1 : isolated digit L1-3 : spelled words M1 : money amount N1 : natural number O1 : spontaneous name O2 : city of call/birth O3 : most frequent city name O5 : most frequent company/agency name O7 : forename & surname Q1-2 : yes/no questions S1-9 : phonetically rich sentences T1 : time of day T2 : time phrase W1-4 : phonetically rich words OK, see section 3 for details - NNNN in filenames is not in conflict with BLOCK and SES numbers in pathname OK - Contents lowest level subdirectories should be of one call only OK - Empty (i.e. zero-length) files are not permitted OK - Missing items per speaker Check with documentation (SUMMARY.TXT) OK - File match: For each label file there must be one speech file and vice versa. => A13638W8.FRA is missing - Part of the corpus is designed for training and a smaller part for testing. OK The 500 calls selected for testing are all from existing calls The remaining 4540 calls for training exist and do not overlap with the testset. - All table files, and index files should report the field names as the first row in the files using tabs as in the data records following. OK - The contents of the database as given in CONTENTS.LST should comprise . CD-ROM volume name (VOL:) . full pathname (DIR:) . speech file name (SRC:) . corpus code (CCD:) . corpus repetition (CRP:) . speaker code (SCD:) . speaker sex (SEX:) . speaker age (AGE:) . speaker accent (ACC:) . orthographic transcription of uttered item (LBO:) The first line should be a header specifying the information in each record. This file must be supplied as an ASCII TAB delimited file. OK, the file isacceptable. There are some marginal issues: => CONTENTS.LST contains double line ends. => There are a couple of mismatches between CONTENTS.LST and => LBO-transcriptions in the label files in terms of number of interword => spaces. - The contents of the SUMMARY.TXT files should comprise: . The full directory name where speech and label files are to be found . the session number . a string of typically N codes. Each item present is represented by its code. If the item is missing, a '--' should appear. . recording date . recording time of first item . optional comment text . all these fields are separated by spaces . Note: The contents of the SUMMARY.TXT file are not CD-dependent OK ====================================================================== 3. ITEMS - 1 isolated digit (code I1) . read or prompted OK - 1 sequence of 10 isolated digit (code B1) . each sequence must include all digits . optional are hash and star OK - 4 connected digits (code C1-4) - 4-6 digit number to identify the prompt sheet . read - ~10 digit telephone number . read . local numbers . inclusion of GSM numbers recommended - 14-16 digit credit card number . read . set of 150 . if there is a checksum then formula must be provided - 6 digit PIN code . read . set of 150 . ~30 digits per call are required . digits must appear numerically on the sheet, not as words OK Credit card numbers are uniformly distributed and appear at least 30 times each PIN code numbers are uniformly distributed and appear at least 30 times each - 1 natural number (code N1) . read . provided as numbers (numerically) . numbers must be < 1,000,000 . decimal numbers only allowed for additional natural numbers OK - 1 money amount (code M1) . read . currency words should be included . mixture of small amount including decimals and large amounts not including decimals OK - 3 spelled words (code L1-3) . L1 is spontaneous name spelling linked to O1 . others are read . equal balance of all vocabulary letters artificial words can be used to enforce this balance . average length at least 7 letters . may include names, cities and other frequently spelled items . should include equivalents of : A-Z, accent words, CAPITAL, SMALL, UPPER-CASE, LOWER-CASE, DOUBLE, APOSTROPHE, HYPHEN OK The average length per spelt item is 7.80. Each letter appears at least 600 times. - 1 time of day (code T1) . spontaneous OK - 1 time phrase (code T2) . read . analogue form . equal balance of all words . should include equivalents of : AM/PM, HALF/QUARTER PAST/TO, NOON, MIDNIGHT, MORNING, AFTERNOON, EVENING, NIGHT, TODAY, YESTERDAY, TOMORROW OK - 1 date (code D1) . spontaneous OK - 1 date (code D2) . read, wordstyle . analogue form . covering all weekdays and months, ordinals and year expressions (also exceeding 2000) OK Each day name appears at least 700 times. Each month name appears at least 300 times => The year in D2 does not exceed the year 2000, as it should - 1 relative date (code D3) . read . analogue . should include forms such as TODAY, TOMORROW, THE DAY AFTER TOMORROW, THE NEXT DAY, THE DAY AFTER THAT, NEXT WEEK, GOOD FRIDAY, EASTER MONDAY, etc. OK, 32 different expressions were found - 2 yes/no questions (code Q1-2) . spontaneous, not prompted . one question should elicit (predominantly) 'no' answers; the other (predominantly) 'yes' answers . also fuzzy answers should be envisaged OK - 3/6 common application words (code A1-3/6) . read . set of 30 should be used, 25 of which are fixed for all . minimum number of examples of each word = #speakers/10 (this is a soft target) . 6 are needed, but only 3 for 4000+ FDBs Five application words are recorded in each call. In addition to the 30 obligatory words, another 45 words were recorded, totalling in 75 application words Each obligatory word appear at least 490 times The optional words appear at least 210 times - 1 application word phrase (code E1) . application word is embedded in phrase . read or spontaneous OK - 9 phonetically rich sentences (code S1-9) . read . minimum number of phone examples = #speakers/10 OK The following phones have less than 500 tokens: /a,N/. They are typically considered as rare phones in French. Compensation for /N/ is found in the phon. rich words. - 4 phonetically rich words (code W1-4) . read . minimum number of phone examples = #speakers/10 OK The following phones have less than 500 tokens: /9~,a/. These are typically rare phones in French. Eight phonetically rich words were recorded per session (W1-8). - 5 directory assistance names (code O1-7) . 1 spontaneous name (e.g. forename) . 1 spontaneous city name . 1 read city name (from list of 500 most frequent) . 1 read company/agency name (from list of 500 most frequent) . 1 read proper name, fore- and surname (from list of 150 SDB names) OK => A list of 500 different city names was used, but due some misspellings => or alternative spellings in the prompt 515 different names are found. => A list of 500 different company/agency names was used, => but due some misspellings or alternative spellings in the prompt 506 => different names are found. => A list of 150 different for/surnames names was used, => but due some misspellings or alternative spellings in the prompt 154 => different names are found. The following completeness checks are performed on obligatory SpeechDat items only: 1. Structurally missing items None of the mandatory items is structurally missing. In contrast, 8 additional optional items are recorded in each call: A7-8: 2 application words E2 : application word phrase O9 : spelt city of birth W5-8: 4 phon. rich words => Corpus code O9 should better be L4 since it is a spelt item 2. Incidentally missing items a. files that are not there 1697 files were found missing, according to the following distribution over the items: A1: 36 A2: 44 A3: 49 A7: 48 A8: 59 B1: 2 C1: 21 C2: 1 C3: 10 C4: 15 D1: 39 D2: 4 D3: 29 E1: 77 E2: 94 I1: 127 L1: 8 L2: 1 L3: 7 M1: 22 N1: 13 O1: 70 O2: 24 O3: 34 O5: 31 O7: 11 O9: 15 Q1: 158 Q2: 349 S1: 3 S2: 3 S3: 2 S4: 3 S5: 1 S6: 3 S7: 2 S8: 1 S9: 4 T1: 41 T2: 6 W1: 29 W2: 26 W3: 33 W4: 29 W5: 26 W6: 33 W7: 29 W8: 25 b. files with empty transcriptions in the LBO label field (effectively missing files) We found 414 files that have only noise symbols and/or ** in their transcriptions. If we merge these with the really missing items, then the following distribution of effectively missing files appears: 40 A1 47 A2 51 A3 54 A7 62 A8 4 B1 22 C1 3 C2 13 C3 18 C4 108 D1 4 D2 34 D3 92 E1 111 E2 134 I1 15 L1 2 L2 10 L3 24 M1 18 N1 110 O1 40 O2 40 O3 33 O5 14 O7 39 O9 213 Q1 387 Q2 6 S1 4 S2 6 S3 4 S4 1 S5 3 S6 3 S7 2 S8 7 S9 60 T1 13 T2 34 W1 30 W2 37 W3 31 W4 30 W5 36 W6 34 W7 28 W8 c. corrupted speech files If we regard utterances which have only truncated or mispronounced words as corrupted files, and merge these with the effectively missing files under b. then the following distribution emerges : 71 A1 93 A2 90 A3 83 A7 82 A8 4 B1 23 C1 3 C2 13 C3 19 C4 108 D1 4 D2 57 D3 93 E1 111 E2 154 I1 16 L1 5 L2 13 L3 24 M1 18 N1 211 O1 82 O2 139 O3 98 O5 17 O7 44 O9 240 Q1 398 Q2 7 S1 4 S2 6 S3 4 S4 1 S5 3 S6 3 S7 2 S8 7 S9 60 T1 13 T2 112 W1 110 W2 89 W3 105 W4 100 W5 104 W6 101 W7 87 W8 (This will not be used to reject or approve a database but it will be supplied as supplementary information.) d. files containing truncation and mispronunciation marks (*,**,~ are counted in the transcriptions of the individual items to get an idea of distorted speech data. This will not be used to reject or approve a database but it will be supplied as supplementary information.) We found 9083 transcriptions with at least one *, or **, or ~, according to the following distribution over the items: A1: 59 A2: 87 A3: 76 A7: 72 A8: 58 B1: 113 C1: 133 C2: 140 C3: 264 C4: 138 D1: 186 D2: 187 D3: 74 E1: 231 E2: 219 I1: 58 L1: 278 L2: 75 L3: 190 M1: 125 N1: 112 O1: 432 O2: 142 O3: 168 O5: 157 O7: 116 O9: 146 Q1: 112 Q2: 112 S1: 372 S2: 402 S3: 433 S4: 412 S5: 429 S6: 384 S7: 370 S8: 407 S9: 411 T1: 178 T2: 70 W1: 122 W2: 134 W3: 101 W4: 125 W5: 117 W6: 120 W7: 126 W8: 110 3. Overall conclusion SpeechDat has the following criteria for missing items: . At least 95% of the files of each mandatory item (corpus code) must be present. . As missing files are counted: absent files, and files containing non-speech events only. . There will be no further comparison of prompt and transcription text in order to decide if a file is effectively missing. As a consequence: If there is some speech in the transcription, then the file will NOT be considered missing, even if it is in fact useless. The criterion of 95% completeness should be considered against the background of a 5000 calls' database. It therefore implies that at least 4750 files for each corpus code should be present. This French FDB5000 database comprises 5040 calls. For this reason the maximum number of effectively missing files is 5040-4750 = 290. For the decision of completeness of an item the distribution given in 2b above should be used. It is clear from this distribution that item Q2 (yes_question) effectively misses more than 290 files, i.e. 387. This deviation has been clarified in section 8.2 of DESIGN.DOC. =========================================================================== 4. SAMPLED DATA FILES 1 Coding . A-law, 8 bit, 8 kHz, no compression OK 2 Sample distribution Several sample statistics are generated: File length, clipping rate, mean sample value, Signal-to-Noise Ratio (SNR). Statistics were generated on file level by the producer of the database, using SPEX software. The results were delivered to SPEX. SPEX compiled histograms on the basis these results. These histograms are presented below, both on file level and on directory (call) level. The histograms are presented as they are and not further interpreted by SPEX. On the basis of these data the user of the database should be able to decide which acoustic quality is still acceptable for the application at hand. Statistics on the acoustics of individual speech files can be retrieved from file \DOC\SAMPSTAT.TXT. The columns in SAMPSTAT.TXT have the following meaning: file max min #samples cliprate mean snr A11001C2.ENA:16384:-13056:80000: 0.00: -4.28: 35.89 2.1 File length We calculated the length of the files in seconds in order to trace spurious recordings if files were of extraordinary length. Duration distribution over all items: Length (s) #Occurrences 0 - 1 : 83 1 - 2 : 1963 2 - 3 : 53283 3 - 4 : 79840 4 - 5 : 38326 5 - 6 : 28412 6 - 7 : 21157 7 - 8 : 12694 8 - 9 : 8003 9 - 10 : 4535 10 - 11 : 2669 11 - 12 : 1416 12 - 13 : 801 13 - 14 : 471 14 - 15 : 274 15 - 16 : 171 16 - 17 : 103 17 - 18 : 67 18 - 19 : 53 19 - 20 : 57 20 - 21 : 30 21 - 22 : 8 22 - 23 : 22 23 - 24 : 13 24 - 25 : 11 25 - 26 : 3 26 - 27 : 6 27 - 28 : 5 28 - 29 : 7 29 - 30 : 4 30 - 31 : 6 31 - 32 : 4 32 - 33 : 3 33 - 34 : 3 34 - 35 : 3 35 - 36 : 3 36 - 37 : 2 37 - 38 : 2 38 - 39 : 3 39 - 40 : 5 40 - 41 : 1 41 - 42 : 1 42 - 43 : 1 43 - 44 : 2 44 - 45 : 1 47 - 48 : 2 49 - 50 : 2 51 - 52 : 1 52 - 53 : 1 57 - 58 : 1 59 - 60 : 3 64 - 65 : 1 68 - 69 : 2 Duration distribution over calls/directories: Length (s) #Occurrences 1 - 2 : 1 2 - 3 : 46 3 - 4 : 535 4 - 5 : 3517 5 - 6 : 853 6 - 7 : 64 7 - 8 : 14 8 - 9 : 4 9 - 10 : 2 10 - 11 : 1 12 - 13 : 1 16 - 17 : 1 Session 3887 has an extremely high average duration of 16.1 s per file. The recording quality is this sessions is good; it has quite some background babble, which is probably the reason why the auto-stop for the recording did not function. 2.2 min-max samples We provide a histogram with clipping ratios, The clipping ratio is defined as the proportion of samples in a file that is equal to the maximum/minimum value, divided by all samples in the file. The histogram, then, is an overview of how many files were found in a set of clipping rate intervals. Clip distribution for all items: Clipping Occurrences rate (in %) 0.0 - 0.1 : 3566 0.1 - 0.2 : 202 0.2 - 0.3 : 89 0.3 - 0.4 : 19 0.4 - 0.5 : 13 0.5 - 0.6 : 6 0.6 - 0.7 : 2 0.7 - 0.8 : 1 0.8 - 0.9 : 4 1.0 - 1.1 : 1 Number of files with absolute maximum < 32256: 250637 Clip distribution over calls/directories: Clipping Occurrences rate (in %) 0.0 - 0.1 : 655 0.1 - 0.2 : 5 Number of directories with absolute maximum < 32256: 4379 2.3 Mean values We computed the mean sample value of each item in each call. We provide a histogram with mean values below. The histogram, then, is an overview of how many files were found in a set of mean sample value intervals. This overview can be used to trace files with large DC-offsets. Mean distribution over all items: Mean Occurrences -100 - -90 : 1 -40 - -30 : 3 -30 - -20 : 96253 -20 - -10 : 158280 -10 - 0 : 2 0 - 10 : 1 Mean distribution over calls/directories: Mean Occurrences -30 - -20 : 2040 -20 - -10 : 2999 There are no calls with an alarming average sample value. 2.4 Signal to Noise Ratio We split each signal file into contiguous windows of 10 ms and computed the Mean Square (energy) in each window. The mean sample value over the complete file was subtracted from each individual sample value before MS was computed. 5% of the windows that contained the lowest energy were assumed to contain line noise. In this way the signal to noise ratio could be calculated for each file by dividing the mean energy over all windows by the mean energy of the 5% sample mentioned above. The result was multiplied by 10*log for scaling. SNR distribution over all items: SNR occurrences 0 - 5 : 17 5 - 10 : 87 10 - 15 : 410 15 - 20 : 1728 20 - 25 : 7217 25 - 30 : 24346 30 - 35 : 56597 35 - 40 : 76878 40 - 45 : 59520 45 - 50 : 23139 50 - 55 : 4414 55 - 60 : 186 60 - 65 : 1 SNR distribution over calls/directories: SNR occurrences 5 - 10 : 1 15 - 20 : 15 20 - 25 : 84 25 - 30 : 393 30 - 35 : 1219 35 - 40 : 1774 40 - 45 : 1162 45 - 50 : 354 50 - 55 : 37 => Session 4305 has an very low average value for SNR: 7 db, => and cannot be used for training for that matter. => This directory contains a sinusoid tone of about 200 Hz throughout => the recording. =========================================================================== 5. ANNOTATION FILE - Each line must be delimited by OK - Mandatory (SAM) mnemonics: LHD: SAM, 5.10 DBN: SPEECHDAT__Fixed_Network VOL: FIXED1_ SES: DIR: SRC: CCD: CRP: < = corpus repetition, empty> REP: RED: RET: SAM: 8000 < = sampling freq.> BEG: END: SNB: 1 < = number of bytes per sample> SBF: < = sample byte order, meaningless with single bytes> SSB: 8 < = number of significant bits per sample> QNT: A-LAW < = quantisation> SCD: SEX: M/F/UNKNOWN AGE: ! mnemo is not SAM ACC: ! mnemo is not SAM REG: ENV: LBD: LBR: , , [gain], [minimum value], [maximum value], LBO: , [centre sample], , EXT: 80 chars on one line> ELF: - Optional (SAM) mnemonics (may be omitted or left empty) TYP: orthographic TXF: CMT: NCH: 1 < = number of channels recorded> ARC: ! mnemo is not SAM SHT: ! mnemo is not SAM CMP: EXP: SYS: DAT: SPA: PHM: ! mnemo is not SAM NET: PSTN < = network> ! mnemo is not SAM DSC: < = discontinuity marker> EDU: ! mnemo is not SAM SOC: ! mnemo is not SAM HLT: TRD: RCC: ASS: ! mnemo is not SAM - Order restrictions: . LHD and TYP are first . LBR and LBO come after LBD . ELF is end of file keyword - All mnemonics should be SAM mnemonics or explicitly defined in documentation OK, all mnemonics are SAM as defined for the SpeechDat project. Additional optional mnemonics used in this database: RCC, NET, PHM - No illegal mnemonics used => We found 7 files with illegal label structures A11691O3.FRO: contains empty line, several LBO attributes, and misses ELF A12710L1.FRO: contains empty line, several LBO attributes, and misses ELF A13382D1.FRO: contains extra line breaks after final EXT and misses ELF A14634D3.FRO: final LBO is cut and restarts on new line; ELF misses A14895O9.FRO: final ELF missing A12002S3.FRO: misses SCD, and has double SEX A13931S7.FRO: misses SCD, and has double SEX - There are no mnemonics missing See above - All files must contain the same mnemonics. This holds as well for the optional mnemonics. OK - No illegal field values should appear => A12302A2.FRO contains an empty value for BEG => A12302C2.FRO contains an empty value for BEG => A12302W8.FRO contains an empty value for BEG => In SES3931 two values for PHM are used in different label files: => ROTARY and TOUCHTONE - No line may exceed 80 chars OK - Each lowest subdirectory does not refer to multiple sheet ids. OK - For spontaneous speech LBR should contain a mnemonic word. D1 : L1 : O1 : O2 : Q1 : or Q2 : or T1 :