Transcript Open Source Grammars

Open Source Grammars
David Thomson
CTO, SpeechPhone
(VoiceXML Tools Committee chair)
[email protected]
1
VoiceXML Forum Tools Committee
•
Part of the VoiceXML Forum
•
Charter: Make VoiceXML easier to use through better
development tools.
•
Members: AT&T, Avaya, Chrysalis, France Telecom,
Genesys, IBM, Intervoice, Lumenvox, Nuance, Oracle,
SpeechPhone, Voxeo, ….
2
Four Working Groups
1. Metalanguage: Standard language for application
servers.
2. Data Logging: Format for capturing run-time data.
3. Advanced Dialogs: Representing non-FSM
conversations.
4. Open Source Grammars: Standard grammars for
common tasks.
3
Project Overview
Objective: Create a set of open-source, standard grammars.
Motivation:
1. Make it easier to develop speech applications.
2. Unify the human-machine interface so applications from
different vendors have familiar behaviors.
3. VoiceXML 2.0 built-in grammar specification is incomplete.
4
Plans
Our task:
1. Gather contributions.
2. Standardization.
3. Conformance & test conditions.
4. Post grammars.
5. Test compliance?
Disclaimers:
1. The project is still in early stages.
2. Not everyone agrees with all points in this presentation.
3. Industry is divided on feasibility & value.
5
Project Guidelines
1.
2.
3.
4.
5.
6.
7.
8.
9.
Try to create a single grammar for each purpose.
Grammars are modular.
Use SRGS & SISR.
Start with contributions from industry.
Use a structured development process.
Grammars will be maintained under Sourceforge.
Grammars are free and available to everyone.
We do not specify the prompt.
We define reference grammars that embody the
specification and are also useful for developers.
6
Grammars in Initial Release
•
•
•
•
•
•
•
•
Boolean (yes/no)
Time
Date
Digits (1-16 digits)
VoiceXML built-in grammars
Number (1-16 digits)
Phone (10 digits)
Currency (dollars)
Credit Card (card number, expiration date)
–
•
With and without Luhn check?
Social Security Number
10
Jakarta RDC Atomic Tags
•
•
•
•
•
•
•
•
•
•
•
•
Collect a date
Collect a time
Collect a duration
Collect a credit card bill amount
Collect a credit card expiry date
Collect a credit card number
Collect a credit card type
Collect a zip code
Collect a major US city name
Collect a US state name
Collect a string of alphabets
Collect a currency value
•
•
•
•
•
•
•
•
•
•
•
Collect a alphanumeric string
Collect one choice from a list of
options
Collect a country name
Collect a social security number
Collect a international standard
book number
Collect a percentage
Collect a numerical value
Collect a string of digits
Collect a type of mortgage
*Collect mortgage information
*Collect credit card information
*Composite
11
Existing Grammars
•
•
•
•
•
RDC Tag Library
Voxeo
Nuance
VoiceXML 2.0
Others…
12
Points by Detractors
•
•
•
•
•
•
Creating a quality grammar is expensive.
No competent company will participate.
There are already several open source grammars.
Companies try to differentiate, won’t use them.
Recognizers & Dev. tools already have grammars.
Good applications require customization.
–
–
–
–
–
–
Application & context differences
Platform (CPU, connectivity, ASR) differences
Compatibility with a variety of development tools.
User base variations
Languages
Shifting standards
13
Open Issues
•
How do we handle multiple versions?
–
–
–
–
–
•
Languages
CPU constraints (embedded)
SRGS/SISR versions
Application dependencies
Grammar updates
How do we handle recognizer differences?
–
–
–
Weights
Efficiency tricks
Advanced use of ECMAScript in SISR
15
For More Information
Join the Committee email distribution list:
Cindy Tiritilli <[email protected]>
Questions:
David Thomson <[email protected]>
Bill Scholz <[email protected]>
VoiceXML Forum site
www.voicexml.org/grammars
16