SPEX / Dept. of Language and Speech University of Nijmegen Erasmusplein 1 NL-6525 HT Nijmegen The Netherlands SUBJECT: Validation Russian FDB1000 corpus AUTHORS: Henk van den Heuvel, Eric Sanders VERSION: 1.0 DATE : 17/07/98 The speech databases made within the SpeechDat project or associated to it 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 Russian Fixed Network SpeechDat database (1000 speakers) are contained in this document. For the cyrilic orthography Microsoft Windows ANSI: Code Page 1251 (CP1251) was used instead of ISO-8859-5. 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 RECORDING PLATFORM 9 TRANSCRIPTION The document is concluded by 10 SUMMARY ==================================================================== 1. DOCUMENTATION - File DESIGN.DOC is present OK - Language of doc file: English OK - Contact person: name, address, affiliation OK - Number of CDs OK We do not recommend the counting of CDs from 0/4 to 4/4, but rather 1/5 to 5/5. - Contents of each CD OK - The directory structure of the CDs OK, section 1 - Description of all the items in the corpus OK, sections 2 and 3 => Section 3.6 should say that it concerns a *fore*name - Prompting OK, see section 4 . linguistic specification (and motivation) for the prompting material (in case of additional optional items) OK,section 3 . connection of sheet items to item numbers on CD OK, section 3 . sheet example OK, appendix 15 . items must be spread over the sheet to prevent list effects (e.g. three yes/no questions immediately after another are not allowed) OK, appendix 15 - Naming conventions for directories and files OK - Speaker recruitment Information on speaker recruitment is very concise, section 6.2. Recruitment strategies are not explained. - 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 6 - 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 => The commentary about the affricates and phonemes with different notations => is not clear - Analysis of frequency of occurrence of the sub-word units represented in the phonetically rich words (either of phones, biphones, triphones) OK, section 3.13 => The commentary about the affricates and phonemes with different notations => is not clear - Recording platform and telephone link description (which part is digital) OK, section 5 - Signal characteristics (number of bits per sample; bandwidth; coding type; compression procedures) OK, section 5 - The format of the speech files (A-law, 8 bit, 8 kHz, uncompressed) OK, section 5 - The format of the annotation files (SAM label files) OK, sections 1.3 and 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 7, and Additional information - 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 9 - 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, see section 7 - Information on test (set) specification => Information on test specifications is missing Only the train and test files are listed in section 1.1 - The validation report made by SPEX (VALREP.TXT) is referred to OK ========================================================================== 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 => The following files are not in MS-DOS format on all CDs: => COPYRIGH.TXT => SAMPSTAT.TXT misses in the last line. => A total of 2011 files in the sessions => 0404 - 0453, 0700-0739, 0749, 0754, 0756, 0760, 0763-0765, 0775, 0777 => does not have a after the final mnemonic (ELF:) - A README.TXT file should be in the root describing all (documentation) files on the CD-ROM. OK, however, => The file names of speech and label files are neither given nor explained - 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 . ISO88595.PS . SUMMARY.TXT . SAMPSTAT.TXT OK, The file CP1251.PS is more appropriate - 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, SESSION.TBL, SPEAKER.TBL, LEXICON.TBL are delivered - Index files (optional) should be in \\INDEX Only CONTENTS.LST is mandatory. OK - The index files (if present) obey the nomenclature .LST where e.g. A1ENN3.LST (see below for item_code) Only CONTENTS.LST is 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 - 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. OK - Part of the corpus is designed for training and a smaller part for testing. OK, a set of 200 speakers is designed for testing. In addition, the remaining 800 speakers are designed for training. Both sets (A1TSTRU.SES and A1TRNRU.SES) do not show overlaps and refer to existing calls only. - 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 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, only digits used - 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, => 193 different Credit card numbers were used instead of 150 => The frequency of each credit card number ranges from 1 to 8 - 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, => Larger numbers between 100,000 and 1,000,000 are absent - 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 spelt items contain 7.01 characters on average - 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 - 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, => We found 196 different prompt texts for relative dates, whereas => 170 were expected according to Appendix 6. - 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 . 6 are needed, but only 3 for 4000+ FDBs => There are 33 application words instead of 30. The distribution was OK: > 175 samples per word - 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 - 4 phonetically rich words (code W1-4) . read . minimum number of phone examples = #speakers/5 OK, but => The following rare phones are represented by less than 200 samples: => /b', f', g', k', p', S':, t-s, t-S', x', x, z'/ - 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, => We found 499 different city names in O3 instead of 500 => We found 509 different company names instead of 500 => The APPENDIX.DOC refers to 150 company names which is probably an error The following completeness checks are performed on obligatory SpeechDat items only: 1. Structurally missing items There is no item structurally missing. The following additional, optional items are supplied: X1: the speaker's full name X2: environment of the call X3: place of call X4: telephone model X5: age of handset 2. Incidentally missing items a. files that are not there We found the 188 missing files. The number of missing files per item is shown below: 1 A3 1 A4 3 A5 11 A6 31 B1 1 C2 1 C3 22 C4 2 D3 9 I1 1 L3 1 N1 1 O3 1 O5 3 O7 2 S5 2 S6 4 S7 17 S8 40 S9 1 T1 1 W2 6 W3 26 W4 b. files with empty transcriptions in the LBO label field (effectively missing files) We found 92 files that have only noise symbols and/or ** in their transcriptions. If we merge these with the missing files presented above then we obtain the following distribution. 2 A1 6 A3 4 A4 5 A5 12 A6 32 B1 1 C1 4 C2 3 C3 24 C4 1 D1 3 D3 14 I1 2 L1 1 L2 2 L3 1 N1 6 O1 2 O3 1 O5 3 O7 7 Q1 4 Q2 1 S1 3 S2 3 S3 2 S5 2 S6 5 S7 18 S8 44 S9 8 T1 2 W1 3 W2 10 W3 26 W4 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 : 13 A1 4 A2 8 A3 10 A4 7 A5 16 A6 32 B1 2 C1 4 C2 3 C3 24 C4 3 D1 3 D3 16 I1 5 L1 6 L2 3 L3 1 N1 47 O1 5 O2 31 O3 18 O5 3 O7 8 Q1 5 Q2 2 S1 3 S2 3 S3 2 S5 2 S6 5 S7 18 S8 44 S9 15 T1 5 W1 7 W2 12 W3 29 W4 (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 1930 transcriptions with at least one *, or **, or ~, according to the following distribution over the items: A1: 18 A2: 19 A3: 15 A4: 13 A5: 8 A6: 8 B1: 15 C1: 46 C2: 51 C3: 73 C4: 19 D1: 87 D2: 37 D3: 23 E1: 38 I1: 6 L1: 47 L2: 52 L3: 41 M1: 58 N1: 33 O1: 69 O2: 21 O3: 37 O5: 40 O7: 21 Q1: 21 Q2: 11 S1: 88 S2: 92 S3: 81 S4: 110 S5: 98 S6: 86 S7: 84 S8: 82 S9: 92 T1: 123 T2: 20 W1: 15 W2: 12 W3: 10 W4: 10 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. For the decision of completeness of an item the distribution given in 2b above should be used. It is clear from this distribution that none of the items effectively misses 50 or more files. This even holds if the files with corrupted speech only are included in the computation. Thus it can be concluded that all obligatory items are sufficiently complete. =========================================================================== 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 : 1 1 - 2 : 29 2 - 3 : 6702 3 - 4 : 12999 4 - 5 : 7312 5 - 6 : 6199 6 - 7 : 5317 7 - 8 : 3734 8 - 9 : 2315 9 - 10 : 1445 10 - 11 : 905 11 - 12 : 569 12 - 13 : 720 13 - 14 : 196 14 - 15 : 86 15 - 16 : 198 16 - 17 : 17 17 - 18 : 50 18 - 19 : 9 19 - 20 : 1 20 - 21 : 8 Duration distribution over calls/directories: Length (s) #Occurrences 3 - 4 : 17 4 - 5 : 410 5 - 6 : 401 6 - 7 : 121 7 - 8 : 37 8 - 9 : 9 9 - 10 : 4 10 - 11 : 1 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 : 1473 0.1 - 0.2 : 229 0.2 - 0.3 : 78 0.3 - 0.4 : 48 0.4 - 0.5 : 22 0.5 - 0.6 : 33 0.6 - 0.7 : 21 0.7 - 0.8 : 23 0.8 - 0.9 : 18 0.9 - 1.0 : 18 1.0 - 1.1 : 13 1.1 - 1.2 : 16 1.2 - 1.3 : 13 1.3 - 1.4 : 6 1.4 - 1.5 : 5 1.5 - 1.6 : 10 1.6 - 1.7 : 6 1.7 - 1.8 : 6 1.8 - 1.9 : 4 1.9 - 2.0 : 3 2.0 - 2.1 : 2 2.1 - 2.2 : 1 2.2 - 2.3 : 3 2.3 - 2.4 : 5 2.4 - 2.5 : 3 2.6 - 2.7 : 2 2.7 - 2.8 : 2 2.9 - 3.0 : 2 3.0 - 3.1 : 1 3.1 - 3.2 : 1 3.3 - 3.4 : 2 3.9 - 4.0 : 1 4.3 - 4.4 : 1 4.5 - 4.6 : 2 5.0 - 5.1 : 1 5.4 - 5.5 : 1 5.5 - 5.6 : 1 5.9 - 6.0 : 1 6.4 - 6.5 : 1 8.8 - 8.9 : 1 Number of files with absolute maximum < 32256: 46733 Clip distribution over calls/directories: Clipping Occurrences rate (in %) 0.0 - 0.1 : 179 0.1 - 0.2 : 6 0.2 - 0.3 : 1 0.3 - 0.4 : 1 0.7 - 0.8 : 1 0.9 - 1.0 : 1 1.1 - 1.2 : 1 1.3 - 1.4 : 1 1.8 - 1.9 : 1 Number of directories with absolute maximum < 32256: 808 The calls with an average clip ratio above 1.0 were: Session Clip ratio: 0071 1.84 0285 1.12 0313 1.33 => All sessions 0071, 0285, 0313 are not suited for training due to clipping. 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 -260 - -250 : 1 -240 - -230 : 1 -210 - -200 : 1 -180 - -170 : 2 -170 - -160 : 1 -160 - -150 : 1 -150 - -140 : 1 -130 - -120 : 3 -120 - -110 : 2 -110 - -100 : 3 -100 - -90 : 3 -90 - -80 : 4 -80 - -70 : 15 -70 - -60 : 80 -60 - -50 : 114 -50 - -40 : 205 -40 - -30 : 533 -30 - -20 : 4472 -20 - -10 : 6174 -10 - 0 : 14276 0 - 10 : 4704 10 - 20 : 3102 20 - 30 : 2382 30 - 40 : 1997 40 - 50 : 1100 50 - 60 : 1712 60 - 70 : 2033 70 - 80 : 1000 80 - 90 : 1051 90 - 100 : 892 100 - 110 : 517 110 - 120 : 702 120 - 130 : 753 130 - 140 : 349 140 - 150 : 157 150 - 160 : 61 160 - 170 : 7 170 - 180 : 9 180 - 190 : 20 190 - 200 : 11 200 - 210 : 21 210 - 220 : 17 220 - 230 : 21 230 - 240 : 24 240 - 250 : 24 250 - 260 : 41 260 - 270 : 33 270 - 280 : 14 280 - 290 : 11 290 - 300 : 11 300 - 310 : 14 310 - 320 : 11 320 - 330 : 6 330 - 340 : 17 340 - 350 : 14 350 - 360 : 18 360 - 370 : 6 370 - 380 : 10 380 - 390 : 7 390 - 400 : 8 400 - 410 : 9 410 - 420 : 4 420 - 430 : 3 430 - 440 : 4 440 - 450 : 6 450 - 460 : 2 460 - 470 : 3 480 - 490 : 1 550 - 560 : 1 Mean distribution over calls/directories: Mean Occurrences -70 - -60 : 1 -60 - -50 : 3 -50 - -40 : 4 -40 - -30 : 13 -30 - -20 : 71 -20 - -10 : 145 -10 - 0 : 297 0 - 10 : 96 10 - 20 : 60 20 - 30 : 51 30 - 40 : 42 40 - 50 : 20 50 - 60 : 35 60 - 70 : 41 70 - 80 : 21 80 - 90 : 22 90 - 100 : 19 100 - 110 : 11 110 - 120 : 13 120 - 130 : 15 130 - 140 : 7 140 - 150 : 3 150 - 160 : 1 160 - 170 : 1 180 - 190 : 1 220 - 230 : 2 240 - 250 : 1 280 - 290 : 1 330 - 340 : 1 370 - 380 : 2 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 : 4 5 - 10 : 274 10 - 15 : 1357 15 - 20 : 3180 20 - 25 : 6383 25 - 30 : 9936 30 - 35 : 11246 35 - 40 : 8686 40 - 45 : 4936 45 - 50 : 2192 50 - 55 : 518 55 - 60 : 93 60 - 65 : 6 75 - 80 : 1 SNR distribution over calls/directories: SNR occurrences 5 - 10 : 1 10 - 15 : 21 15 - 20 : 56 20 - 25 : 129 25 - 30 : 220 30 - 35 : 251 35 - 40 : 187 40 - 45 : 89 45 - 50 : 38 50 - 55 : 7 55 - 60 : 1 => The call with an average SNR of 9.5 dB was session 0448. It has a background => buzz. The speech sounds like from a great distance. Unsuited for training. ============================================================================= 5. ANNOTATION FILE - Each line must be delimited by OK, but => in 2201 files the delimiter was forgotten after the mnemonic ELF: => (see section 2) - 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 OK - All mnemonics should be SAM mnemonics or explicitly defined in documentation OK, optional mnemonics used are: ASS, NET and PHM - No illegal mnemonics used OK - There are no mnemonics missing OK - All files must contain the same mnemonics. This holds as well for the optional mnemonics. OK - No illegal field values should appear NET has the value PSTN for FIXED (which is OK); PHM contains the value TOUCH-TONE for TOUCHTONE. This is acceptable => In session 0285 we find two different values for AGE: 17 and 27 => In session 0304 we find three different values for ACC: => SOUTH RUSSIA; ST.PETERSBURG; MIDDLE RUSSIA => In session 0323 we find two different values for ACC: => ST.PETERSBURG; MIDDLE RUSSIA => In session 0699 we find two different values for ACC: => ST.PETERSBURG; MOSCOW - 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 :