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

Re: VoiceXML 2.1 Working Draft

From: Dave Burke <david.burke@voxpilot.com>
Date: Thu, 14 Oct 2004 09:40:58 +0100
Message-ID: <009a01c4b1c9$8b883980$7a34283e@db01.voxpilot.com>
To: "James Wilson" <James.Wilson@vecommerce.co.nz>, <www-voice@w3.org>

Hi, James.

VoiceXML browsers need the binary data to allow them to <submit> the data
(usually in the body of a HTTP POST) to a Web server. A VoiceXML browser on
top of an MRCPv2 client would need to render ("download") the save_waveform
URI (by using a HTTP client inside the browser), if and when a <submit> was



----- Original Message -----
From: "James Wilson" <James.Wilson@vecommerce.co.nz>
To: <www-voice@w3.org>
Sent: Thursday, October 14, 2004 7:31 AM
Subject: VoiceXML 2.1 Working Draft


I have a question. Please can you explain why the mechanism defined in "7.
Recording User Utterances While Attempting Recognition" returns a binary
waveform rather than a URL that points to the waveform? Is it to avoid
firewall issues?

This is in the context of MRCP 2 where a mechanism is provided to save
waveforms on a recognition by recognition basis (using the save_waveform
parameter). The waveforms are saved on the rec server. The MRCP recognition
result does not return the binary waveform to the browser, but a URL that
points to it. This would appear to be more efficient.

James Wilson
Business Analyst
VeCommerce Limited - the future is hearŪ
Email: mailto:james.wilson@vecommerce.co.nz
Direct: +64 9 917 4049
Switch: +64 9 358 0588
Fax: +64 9 358 0627
Mobile: +64 21 946 121
VeCommerce (NZ) Limited.
Level 3, 195 Khyber Pass Rd,
P.O. Box 10311 Dominion Rd,
New Zealand.
Received on Thursday, 14 October 2004 07:41:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:37 UTC