1 / 12

Open Source Grammars

Open Source Grammars. David Thomson CTO, SpeechPhone (VoiceXML Tools Committee chair) david@speechphone.com. VoiceXML Forum Tools Committee. Part of the VoiceXML Forum Charter: Make VoiceXML easier to use through better development tools.

keisha
Download Presentation

Open Source Grammars

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open Source Grammars David Thomson CTO, SpeechPhone (VoiceXML Tools Committee chair) david@speechphone.com

  2. 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, ….

  3. Four Working Groups Metalanguage: Standard language for application servers. Data Logging: Format for capturing run-time data. Advanced Dialogs: Representing non-FSM conversations. Open Source Grammars: Standard grammars for common tasks.

  4. Project Overview Objective: Create a set of open-source, standard grammars. Motivation: Make it easier to develop speech applications. Unify the human-machine interface so applications from different vendors have familiar behaviors. VoiceXML 2.0 built-in grammar specification is incomplete.

  5. Plans Our task: Gather contributions. Standardization. Conformance & test conditions. Post grammars. Test compliance? Disclaimers: The project is still in early stages. Not everyone agrees with all points in this presentation. Industry is divided on feasibility & value.

  6. Project Guidelines 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.

  7. Grammars in Initial Release VoiceXML built-in grammars Boolean (yes/no) Time Date Digits (1-16 digits) Number (1-16 digits) Phone (10 digits) Currency (dollars) Credit Card (card number, expiration date) With and without Luhn check? Social Security Number

  8. 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 Jakarta RDC Atomic Tags 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

  9. Existing Grammars RDC Tag Library Voxeo Nuance VoiceXML 2.0 Others…

  10. 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

  11. 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

  12. For More Information Join the Committee email distribution list: Cindy Tiritilli <cindy@ieee-isto.org> Questions: David Thomson <david@speechphone.com> Bill Scholz <bill.scholz@comcast.net> VoiceXML Forum site www.voicexml.org/grammars

More Related