W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2006

[PLS] wordsmith of 'more than Voice Browser applicability'

From: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Wed, 29 Nov 2006 10:14:40 -0500
Message-Id: <p0611040bc19353cc863c@[192.168.1.100]>
To: www-voice@w3.org
Cc: wai-liaison@w3.org

* References:
Current last call draft:
http://www.w3.org/TR/2006/WD-pronunciation-lexicon-20061026/#S1
Earlier comment/resolution:
http://www.w3.org/TR/2006/WD-pronunciation-lexicon-20061026/pls-disp.html#R104

*PFWG response:

Please consider rewriting Para. 1 as follows

<context-unchanged>

1. Introduction to Pronunciation Lexicon Specification

This section is informative.

The accurate specification of pronunciation is critical to the
success of speech applications. Most Automatic Speech Recognition
(ASR) and Text-To-Speech (TTS) engines internally provide extensive
high quality lexicons with pronunciation information for many words
or phrases. To ensure a maximum coverage of the words or phrases used
by an application, application-specific pronunciations may be
required. For example, these may be needed for proper nouns such as
surnames or business names.

</context-unchanged>

<change-from>

The Pronunciation Lexicon Specification (PLS) is designed to enable
interoperable specification of pronunciation information for both ASR
and TTS engines within voice browsing applications. The language is
intended to be easy to use by developers while supporting the
accurate specification of pronunciation information for international
use.

</change-from>

<change-to>

The Pronunciation Lexicon Specification (PLS) is designed to enable
interoperable specification of pronunciation information for both ASR
and TTS engines. The language is intended to be easy to use by
developers while supporting the accurate specification of
pronunciation information for international use.

</change-to>

<note> Just dropped "within voice browsing applications" from end of
first sentence. </note>

<context-unchanged>

The language allows one or more pronunciations for a word or phrase
to be specified using a standard pronunciation alphabet or if
necessary using vendor specific alphabets. Pronunciations are grouped
together into a PLS document which may be referenced from other
markup languages, such as the Speech Recognition Grammar
Specification [SRGS] and the Speech Synthesis Markup Language [SSML].

</context-unchanged>

<change-from>

In its most general sense, a lexicon is merely a list of words or
phrases, possibly containing information associated with and related
to the items in the list. This document uses the term "lexicon" in
only one specific way, as "pronunciation lexicon". In this particular
document, "lexicon" means a mapping between words (or short phrases),
their written representations, and their pronunciations suitable for
use by an ASR engine or a TTS engine. However, pronunciation lexicons
are not limited to voice browsers, because they have proven effective
mechanisms to support accessibility for persons with disabilities as
well as greater usability for all users (for instance in screen
readers and other user agents, such as multimodal interfaces).

</change-from>

<change-to>

In its most general sense, a lexicon is merely a list of words or
phrases, possibly containing information associated with and related
to the items in the list. This document uses the term "lexicon" in
only one specific way, as "pronunciation lexicon". In this particular
document, "lexicon" means a mapping between words (or short phrases),
their written representations, and their pronunciations suitable for
use by an ASR engine or a TTS engine. Pronunciation lexicons
are not only useful for voice browsers, because they have also proven
effective mechanisms to support accessibility for persons with
disabilities as well as greater usability for all users. They are
used to good effect in screen readers and user agents supporting
multimodal interfaces.

</change-to>

<note> Broke up over-long last sentence. </note>


Al Gilman
/chair, PFWG
Received on Wednesday, 29 November 2006 15:14:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 November 2006 15:14:54 GMT