index.html
25.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements</title>
<style type="text/css" xml:space="preserve">
.diff-add { background-color: #FFFF99; }
.diff-del { background-color: #FF9999; text-decoration: line-through }
.diff-chg { background-color: #99FF99; }
.diff-off { display: none }
.issues { font-style: italic; font-weight: bold; color: green }
:link { color: #0000FF }
:visited { color: #800080 }
.tocline { list-style: none; }
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/>
</head>
<body>
<div class="head">
<p>
<a href="http://www.w3.org/">
<img height="48" width="72" alt="W3C"
src="http://www.w3.org/Icons/w3c_home" /></a>
</p>
<h1 class="notoc" id="h1">Pronunciation Lexicon Specification (PLS) Version 1.0 Requirements</h1>
<h2 class="notoc" id="date">W3C Working Draft <i>29 October 2004</i></h2>
<dl>
<dt>This version:</dt>
<dd>
<a href="http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029/" shape="rect">http://www.w3.org/TR/2004/WD-lexicon-reqs-20041029/</a>
</dd>
<dt>Latest version:</dt>
<dd>
<a href="http://www.w3.org/TR/lexicon-reqs/" shape="rect">http://www.w3.org/TR/lexicon-reqs/</a>
</dd>
<dt>Previous versions:</dt>
<dd>
<a href="http://www.w3.org/TR/2001/WD-lexicon-reqs-20010312/" shape="rect">http://www.w3.org/TR/2001/WD-lexicon-reqs-20010312/</a>
</dd>
<dt>Editor:</dt>
<dd>Paolo Baggia, Loquendo</dd>
<dd>Frank Scahill, BT</dd>
</dl>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"> Copyright</a>
©2004 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>
<sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
<a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
<hr/>
</div>
<h2>
<a id="abstract" name="abstract" shape="rect">Abstract</a>
</h2>
<p>The W3C <a href="http://www.w3.org/Voice/" shape="rect">Voice
Browser Working
Group</a> aims to develop
specifications to enable access to the Web using spoken
interaction. This document is part of a set of requirements studies
for voice browsers, and provides details of the requirements for
markup used for specifying application specific pronunciation
lexicons.</p>
<p>Application specific pronunciation
lexicons are required in many
situations where the default lexicon supplied with a speech
recognition or speech synthesis processor does not cover the
vocabulary of the application. A pronunciation lexicon is a
collection of words or phrases together with their pronunciations
specified using an appropriate pronunciation alphabet.</p>
<h2 class="notoc">Status of this Document</h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This document describes the requirements for markup used for
pronunciation lexicon.
This new requirements list replaces the old requirements.
New requirements are now in line with <a href="http://www.w3.org/TR/voicexml20/">VoiceXML 2.0 Recommendation</a>,
and other <a href="http://www.w3.org/Voice/" shape="rect">Voice Browser Working Group</a>
specification requirements. Changes between these two versions are described in a <a
href="diff.html">diff document</a>.
You are encouraged to subscribe to
the public discussion list <www-voice@w3.org> and to mail us
your comments. To subscribe, send an email to <<a href="mailto:www-voice-request@w3.org" shape="rect">www-voice-request@w3.
org</a>> with the word <em>subscribe</em> in the subject line
(include the word <em>unsubscribe</em> if you want to unsubscribe).
A <a href="http://lists.w3.org/Archives/Public/www-voice/" shape="rect">public
archive</a> is available online.</p>
<p>This document has been produced as part of the <a href="http://www.w3.org/Voice/" shape="rect">W3C Voice Browser Activity</a>,
following the procedures set out for the <a href="http://www.w3.org/Consortium/Process/" shape="rect">W3C Process</a>. The
authors of this document are members of the <a href="http://www.w3.org/Voice/Group/" shape="rect">Voice Browser Working
Group</a> (<a href="http://cgi.w3.org/MemberAccess/AccessRequest" shape="rect">W3C
Members only</a>).</p>
<p>Patent disclosures relevant to this specification may be found on the
Working Group's <a href="http://www.w3.org/2001/09/voice-disclosures.html">patent disclosure page</a>. This document has been produced under the <a href="http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24 January 2002 CPP</a> as amended by the <a href="http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy Transition Procedure</a>. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p>
<p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
<h2>
<a id="toc" name="toc" shape="rect">Table of Contents</a>
</h2>
<ul class="toc">
<li class="tocline">1. <a href="#intro" shape="rect">Introduction</a></li>
<li class="tocline">2. <a href="#interop" shape="rect">Interoperability Requirements</a></li>
<li class="tocline">3. <a href="#lexicon" shape="rect">Lexicon
Requirements</a></li>
<li class="tocline">4. <a href="#ortho" shape="rect">Orthographic
Requirements</a></li>
<li class="tocline">5. <a href="#pronun" shape="rect">Pronunciation
Requirements</a></li>
<li class="tocline">6. <a href="#alphabet" shape="rect">Pronunciation alphabet
Requirements</a></li>
<li class="tocline">7. <a href="#future" shape="rect">Future Study</a></li>
<li class="tocline">8. <a href="#ref" shape="rect">References</a></li>
<li class="tocline">9. <a href="#acks" shape="rect">Acknowledgements</a></li>
</ul>
<h2>
<a id="intro" name="intro" shape="rect">1. Introduction</a>
</h2>
<p>This document establishes a prioritized
list of requirements for pronunciation lexicon markup which any
proposed markup language should address. This document addresses
both procedure and requirements for the specification development.
The requirements are addressed in separate sections on <a href="#lexicon" shape="rect">Lexicon Requirements</a>, <a href="#ortho" shape="rect">Orthographic Requirements</a>, <a href="#pronun" shape="rect">Pronunciation Requirements</a>, and <a href="#alphabet" shape="rect">Pronunciation alphabet Requirements</a>,
followed by <a href="#future" shape="rect">Future Study</a> and <a href="#acks" shape="rect">Acknowledgements</a> sections.</p>
<h3><a id="whydo" name="whydo" shape="rect">Why do we need such a markup language?</a></h3>
<p>In voice browsing applications there is often a need to use
proper nouns or other unusual words within speech recognition
grammars and in text to be read out by Text-to-Speech processors.
These words may not be present in the platforms' built-in
lexicons. In
such cases voice browsers typically resort to automatic
pronunciation generation algorithms, which may
be improved by manually specificied
pronunciations. The goal of the pronunciation lexicon markup is to
provide a mechanism for application developers to supply high
quality additional pronunciations in a platform independent
manner.</p>
<p>In many cases application developers will need to only provide
one or two additional pronunciations inline within other voice
markup languages, but there are
other cases where an application may make
use of large pronunciation
lexicons
that cannot conveniently be
specified inline and have to be provided as separate
documents. The pronunciation lexicon markup will address both
communities.</p>
<p>The markup language for pronunciation
lexicons
will be developed
within the following broad design criteria. They are ordered from
higher to lower priority. In the event that two goals conflict, the
higher priority goal takes precedence. Specific technical
requirements are addressed in the following sections.</p>
<ol>
<li>The pronunciation lexicon markup language
will enable
consistent, platform independent control of pronunciations for use
by voice browsing applications.</li>
<li>The pronunciation lexicon markup language
should be
sufficient to cover the requirements of speech recognition and
speech synthesis systems within a voice
browser.</li>
<li>The pronunciation lexicon markup language
will be an XML
language and shall be interoperable with relevant W3C
specifications (see section 2 <a href="#interop" shape="rect">Interoperability Requirements</a>
for details).</li>
<li>The pronunciation lexicon markup language
will be
usable in a large number of
human languages (see the
requirements <a href="#r3-4" shape="rect">3.4</a> and <a href="#r3-5" shape="rect">3.5</a>).</li>
<li>It should be easy and computationally efficient to
automatically generate and process documents using
the pronunciation lexicon markup language.</li>
<li>All features of the pronunciation lexicon markup language
should be implementable with existing, generally available
technology. Anticipated capabilities should be considered to ensure
future extensibility (but are not required to be covered in the
specification).</li>
<li>The pronunciation lexicon markup language
should be easy to author,
where appropriate deriving from
existing pronunciation
lexicons
formats and using existing pronunciation alphabets.</li>
</ol>
<h2>
<a id="interop" name="interop" shape="rect">2. Interoperability Requirements</a>
</h2>
<h3>
<a id="r2-1" name="r2-1" shape="rect">2.1 Integration with other Voice Browser Markup languages (must have)</a>
</h3>
<p>The pronunciation lexicon markup must be interoperable with
other relevant specifications developed by the W3C <a href="http://www.w3.org/Voice/" shape="rect">Voice Browser
Working Group</a>. In particular the pronunciation lexicon markup must
be compatible with the Speech Synthesis
Markup Language
[<a href="#ref-SSML" shape="rect">SSML</a>] and
Speech Recognition Grammar Specification [<a href="#ref-SRGS" shape="rect">SRGS</a>].</p>
<h3>
<a id="r2-2" name="r2-2" shape="rect">2.2 Embeddable within other
Voice Browser Markuplanguages
(nice to have)</a>
</h3>
<p>The pronunciation lexicon markup
may be embedded in the Speech
Synthesis Markup Language
[<a href="#ref-SSML" shape="rect">SSML</a>] and in
Speech Recognition Grammar Specification [<a href="#ref-SRGS" shape="rect">SRGS</a>].</p>
<h2>
<a id="lexicon" name="lexicon" shape="rect">3. Lexicon Requirements</a>
</h2>
<h3>
<a id="r3-1" name="r3-1" shape="rect">3.1 Multiple entries per lexicon (must have)</a>
</h3>
<p>The pronunciation lexicon markup must support the ability to
specify multiple entries within a document, each entry containing
orthographic and pronunciation
information.</p>
<h3>
<a id="r3-2" name="r3-2" shape="rect">3.2 Multiple lexicons per document (nice to have)</a>
</h3>
<p>
The pronunciation lexicon markup may provide
named groupings of lexicon entries within a single lexicon
document.
This may be useful for separating lexicons into
application specific classes of pronunciation e.g. all city
names.
</p>
<h3>
<a id="r3-3" name="r3-3" shape="rect">3.3 Pronunciation alphabet per lexicon (must have)</a>
</h3>
<p>The pronunciation lexicon markup must provide the ability to
specify the pronunciation alphabet for use by all entries within a
document, such as the phonetic
alphabet defined by the International Phonetic Association IPA
[<a href="#ref-ipahndbk" shape="rect">IPA</a>].</p>
<h3>
<a id="r3-4" name="r3-4" shape="rect">3.4 Language identifier per lexicon (must have)</a>
</h3>
<p>The pronunciation lexicon markup must provide the ability to
specify language identifiers for use by all entries within a
document. Each language identifier must be expressed following
RFC 3066 [<a href="#ref-rfc3066" shape="rect">RFC3066</a>].</p>
<h3>
<a id="r3-5" name="r3-5" shape="rect">3.5 Language identifier per Lexicon Entry (nice to have)</a>
</h3>
<p>The pronunciation lexicon may support the ability to specify
language identifiers for an individual entry within a document.
Each language identifier must be expressed following
RFC 3066 [<a href="#ref-rfc3066" shape="rect">RFC3066</a>].
</p>
<h3>
<a id="r3-6" name="r3-6" shape="rect">3.6 Lexicon can import other
lexicons (nice to have)</a>
</h3>
<p>The pronunciation lexicon markup may support the ability to
import other pronunciation
lexicons written
in the pronunciation lexicon markup.</p>
<h3>
<a id="r3-7" name="r3-7" shape="rect">3.7 Lexicon can import individual lexicon entries(nice to
have)</a>
</h3>
<p>The pronunciation markup may support the ability to import
lexicon entries from other pronunciation
lexicons.</p>
<h3>
<a id="r3-8" name="r3-3" shape="rect">3.8 Metadata information (should have)</a>
</h3>
<p>
The pronunciation lexicon markup should provide a mechanism for
specifying metadata within pronunciation lexicon documents. This
metadata can contain information about the document itself rather than
document content.
For example: record the purpose of the
lexicon document, the author, etc.
</p>
<h2>
<a id="ortho" name="ortho" shape="rect">4. Orthographic
Requirements</a>
</h2>
<h3>
<a id="r4-1" name="r4-1" shape="rect">4.1 Multi word orthographies (must have)</a>
</h3>
<p>The pronunciation lexicon markup must allow multi word
orthographies. This is particularly important for natural speech
applications where common phrases may have significantly different
pronunciations to that of the concatenated word pronunciations,
requiring a phrase level pronunciation. An example would be "how
about" often pronounced "how 'bout".</p>
<h3>
<a id="r4-2" name="r4-2" shape="rect">4.2 Alternate orthographies (must have)</a>
</h3>
<p>The pronunciation lexicon markup must provide the ability to
indicate an alternative equivalent form of the orthography.</p>
<p>This is required to cover the following situations:</p>
<ul class="noindent">
<li>Regional spelling variations e.g. "colour" and "color"</li>
<li>Free spelling variations e.g. "judgment" and "judgement"</li>
<li>Alternate writing systems e.g. Japanese Kanji and Kana</li>
<li>Ancient vs Modern spellings e.g. German before and after the
reform of the spelling system.</li>
</ul>
<p>See also related requirement <a href="#r4-4" shape="rect">4.4</a>.</p>
<h3>
<a id="r4-3" name="r4-3" shape="rect">4.3 Handling of orthographic
textual variability (must have)</a>
</h3>
<p>The pronunciation lexicon markup must
provide a mechanism to indicate
the allowable textual variability in the
orthography. Types of variability include, but are not limited
to,</p>
<ul class="noindent">
<li>Whitespace handling</li>
<li>Case sensitivity</li>
<li>Unicode sequence variation</li>
<li>Valid character sets</li>
<li>Diacritics within languages such as Arabic or Farsi</li>
<li>Accent matching within languages such as French.</li>
</ul>
<p>The definition of a standard text normalisation scheme is beyond
the scope of this specification.</p>
<h3>
<a id="r4-4" name="r4-4" shape="rect">4.4 Handling of homographs
(nice to have)</a>
</h3>
<p>The pronunciation lexicon markup may provide a
mechanism to deal with the problem of specifying
homographs (words with
the same
spelling, but potentially
different meanings and
pronunciations), within
the same document.</p>
<h2><a id="pronun" name="pronun" shape="rect">5. Pronunciation
Requirements</a></h2>
<h3>
<a id="r5-1" name="r5-1" shape="rect">5.1 Single Pronunciations (must have)</a>
</h3>
<p>The pronunciation lexicon markup must
provide the ability to specify a
single pronunciation for a given lexicon entry as a sequence of
symbols according to the pronunciation alphabet selected.</p>
<h3>
<a id="r5-2" name="r5-2" shape="rect">5.2 Multiple pronunciations (must have)</a>
</h3>
<p>The pronunciation lexicon markup must support the ability to
specify multiple pronunciations for a given lexicon entry.
</p>
<h3>
<a id="r5-3" name="r5-3" shape="rect">5.3 Dialect indication (nice to have)</a>
</h3>
<p>The pronunciation lexicon markup may provide a mechanism for
indicating the dialect or language variation
for each pronunciation, as described in
RFC 3066 [<a href="#ref-rfc3066" shape="rect">RFC3066</a>],
such as <code>"en-scounse"</code>. </p>
<h3>
<a id="r5-4" name="r5-4" shape="rect">5.4 Pronunciation preference (must have)</a>
</h3>
<p>The pronunciation lexicon markup must enable indication of
which pronunciation is the preferred form for use by a speech
synthesizer where there are multiple pronunciations for a lexicon
entry. The pronunciation lexicon markup
must
define the default selection behaviour for the situations where
there are multiple pronunciations but no indicated preference.</p>
<h3>
<a id="r5-5" name="r5-5" shape="rect">5.5 Pronunciation weighting (nice to have)</a>
</h3>
<p>The pronunciation lexicon markup may allow for relative
weightings to be applied to pronunciations. These weightings to
indicate the relative importance of the pronunciations within a
single lexicon entry. This can be useful for speech recognition
systems.</p>
<h3>
<a id="r5-6" name="r5-6" shape="rect">5.6 Orthographic
Specification of Pronunciation (should
have)</a>
</h3>
<p>The pronunciation lexicon markup should allow the specification
of the pronunciation of an orthography in terms of other
orthographies with previously defined pronunciations, for example,
the pronunciation for "W3C" specified as the concatenation of
pronunciations of the words "double you three see".</p>
<h2><a id="alphabet" name="alphabet" shape="rect">6. Pronunciation alphabet
Requirements</a></h2>
<h3>
<a id="r6-1" name="r6-1" shape="rect">6.1 Standard Pronunciation alphabets (must have)</a>
</h3>
<p>We will standardize on at least
one existing pronunciation alphabet, such as the phonetic
alphabet defined by the International Phonetic Association IPA [<a href="#ref-ipahndbk">IPA</a>].
We do not plan
of developing a new standard pronunciation alphabet.</p>
<h3>
<a id="r6-2" name="r6-2" shape="rect">6.2 Internationalization (must have)</a>
</h3>
<p>The pronunciation alphabet must allow the specification of
pronunciations for any language including tonal languages.</p>
<h3>
<a id="r6-3" name="r6-3" shape="rect">6.3 Suprasegmental annotations (must have)</a>
</h3>
<p>The pronunciation alphabet must provide a mechanism for
indicating suprasegmental structure such as, word/syllable
boundaries, and stress markings. The specification may address other
types of suprasegmental structure.</p>
<h3>
<a id="r6-4" name="r6-4" shape="rect">6.4 Interoperability (should have)</a>
</h3>
<p>The choice of pronunciation alphabet should take into account
the requirements of interoperability between platforms.</p>
<h3>
<a id="r6-5" name="r6-5" shape="rect">6.5 Vendor
Specific Pronunciation Alphabets (must have)</a>
</h3>
<p>The pronunciation lexicon markup must allow for vendor specific
pronunciation alphabets to be used.</p>
<h2><a id="future" name="future" shape="rect">7. Future Study</a></h2>
<p>This section contains issues that were identified during
requirements capture but which have not been directly incorporated
in the current set of requirements.</p>
<h3><a id="r7-1" name="r7-1" shape="rect">7.1 More powerful
addressing for Lexicon Entries</a>
</h3>
<p>It may be desirable to provide an addressing scheme for lexicon
entries that is more flexible than the document and fragment URI
schemes currently listed in the requirements. An example of a more powerful
addressing mechanism could be XPath.</p>
<h3><a id="r7-2" name="r7-2" shape="rect">7.2 Prefix/Suffix morphological rules</a></h3>
<p>In some situations the explicit specification of all the
morphological variants of a word can lead to extremely large
lexicons. A standard scheme for providing prefix and suffix
morphological rules would enable more compact lexicon documents. However it
is felt that the most common use of the pronunciation lexicon
markup will be for proper nouns where morphological variance is
less of an issue, and that standardisation of morphological rules
will be too difficult to achieve in a first draft. Off-line tools
may provide mechanisms for generating morphological variants.<br clear="none"/></p>
<h3><a id="r7-3" name="r7-3" shape="rect">7.3 Context Dependent orthographies</a></h3>
<p>In some languages the pronunciation of an orthography and the
orthography itself are dependent upon the context in which this
orthography is used. The requirements do not address this issue. It
may not be possible to resolve this issue in a vendor independent
manner. It is possible that the additional information could
be used to handle this situation in a platform dependent
manner.<br clear="none"/></p>
<h3><a id="r7-4" name="r7-4" shape="rect">7.4 Compound words</a></h3>
<p>In languages such as German and Dutch words can occur as part of
compound words and in some cases may only occur within compound
words. In the future, the pronunciation lexicon
markup should address handling compound words.</p>
<h2><a id="ref" name="ref" shape="rect">8. References</a></h2>
<dl>
<dt>
<a id="ref-ipahndbk" name="ref-ipahndbk" shape="rect">[IPA]</a>
</dt>
<dd><cite>
<a href="http://www2.arts.gla.ac.uk/ipa/handbook.html" shape="rect">Handbook of the
International Phonetic Association</a>
</cite>, International Phonetic Association,
Editors. Cambridge University Press, July 1999. Information on the Handbook is available
at <a href="http://www2.arts.gla.ac.uk/ipa/handbook.html" shape="rect">http://www2.arts.gla.ac.uk/ipa/handbook.html</a>.</dd>
<dt>
<a id="ref-rfc3066" name="ref-rfc3066" shape="rect">[RFC3066]</a>
</dt>
<dd><cite>
<a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">Tags for the Identification
of Languages</a>
</cite>, H. Alvestrand, Editor. IETF, January 2001. This RFC is available
at <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">http://www.ietf.org/rfc/rfc3066.txt</a>.</dd>
<dt>
<a id="ref-SRGS" name="ref-srgs" shape="rect">[SRGS]</a>
</dt>
<dd><cite>
<a href="http://www.w3.org/TR/2004/REC-speech-grammar-20040316/" shape="rect">Speech Recognition
Grammar Specification Version 1.0</a>
</cite>, Andrew Hunt and Scott McGlashan, Editors. World Wide
Web Consortium, 16 March 2004. This version of the SRGS 1.0 Recommendation is
<a href="http://www.w3.org/TR/2004/REC-speech-grammar-20040316/" shape="rect">http://www.w3.org/TR/2004/REC-speech-grammar-20040316/</a>.
The latest version is available at <a href="http://www.w3.org/TR/speech-grammar/" shape="rect">http://www.w3.org/TR/speech-grammar/</a>.</dd>
<dt>
<a id="ref-SSML" name="ref-ssml" shape="rect">[SSML]</a>
</dt>
<dd><cite>
<a href="http://www.w3.org/TR/2004/REC-speech-synthesis-20040907/" shape="rect">Speech Synthesis
Markup Language (SSML) Version 1.0</a>
</cite>, Daniel C. Burnett, et al., Editors. World Wide
Web Consortium, 7 September 2004. This version of the SSML 1.0 Recommendation is
<a href="http://www.w3.org/TR/2004/REC-speech-synthesis-20040907/" shape="rect">http://www.w3.org/TR/2004/REC-speech-synthesis-20040907/</a>.
The latest version is available at <a href="http://www.w3.org/TR/speech-synthesis/" shape="rect">http://www.w3.org/TR/speech-synthesis/</a>.</dd>
</dl>
<h2><a id="acks" name="acks" shape="rect">9. Acknowledgements</a></h2>
<p>The editor wishes to thank the previous author
of this document, Frank Scahill, and the old and new
members of the <a href="http://www.w3.org/Voice/" shape="rect">Voice
Browser Working Group</a> involved in this activity <i>(listed in alphabetical order)</i>:</p>
<dl>
<dd>Paolo Baggia, Loquendo <i>(current leading author)</i></dd>
<dd>Dan Burnett, Independent Consultant</dd>
<dd>Debbie Dahl, Conversational Technologies</dd>
<dd>Ken Davies, HeyAnita</dd>
<dd>Ellen Eide, IBM</dd>
<dd>Will Gardella, SAP</dd>
<dd>Andrew Hunt, ScanSoft</dd>
<dd>Jim Larson, Intel</dd>
<dd>Bruce Lucas, IBM</dd>
<dd>Dave Raggett, W3C/Canon</dd>
<dd>Frank Scahill, BT <i>(previous author)</i></dd>
<dd>Linda Thibault, Locus Dialogue</dd>
<dd>Luc Van Tichelen, ScanSoft</dd>
</dl>
<p>
<a href="http://validator.w3.org/check?uri=referer" shape="rect">
<img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" height="31" width="88"/>
</a>
</p>
<p>
<a href="http://jigsaw.w3.org/css-validator/">
<img style="border:0;width:88px;height:31px"
src="http://jigsaw.w3.org/css-validator/images/vcss"
alt="Valid CSS!" />
</a>
</p>
</body>
</html>