W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2002

Re: VoiceXML2.0: Missing "destexpr" attribute in specification of <record> element

From: <mxd@cisco.com>
Date: Fri, 01 Feb 2002 10:16:46 -0800
Message-ID: <3C5ADB8E.67F7D8E7@cisco.com>
To: "Wyss, Felix" <FelixW@inin.com>
CC: www-voice@w3.org
dest was added to support streaming/chunked recording to rtsp/http servers.  

"Wyss, Felix" wrote:
> 
> If I understand it correctly, the "dest" attribute of <record> allows to explicitly specify the destination of the recording for platforms that support it.  For example, a platform that can directly record into WAV files could allow the "dest" attribute to specify the path to the recording (e.g. dest="file://c:\recordings\greeting_johndoe.wav").
> That is obviously different than recording into memory and then submitting it to the document server using <submit> as you suggest.
> 
> The "destexpr" attribute would allow synthesizing the filename at runtime based on an ECMAScript expression, which can be very useful.  In the above example, the userid could be appended at runtime, thus allowing reuse of the same VoiceXML document for different sessions instead of forcing the document server to assemble a new VoiceXML document for each userid.  I therefore think the standard should allow for a "destexpr" attribute in the <record> element.
> 
> Felix
> 
> -----Original Message-----
> From: James Salsman [mailto:j.salsman@bovik.org]
> Sent: Saturday, January 26, 2002 13:14
> To: Wyss, Felix
> Cc: www-voice@w3.org
> Subject: Re: VoiceXML2.0: Missing "destexpr" attribute in specification
> of <record> element
> 
> > The VoiceXML 2.0 specification introduces a "dest" attribute for the
> > <record> element.  However, there is no "destexpr" attribute (similar
> > to <transfer>).  I presume this is an omission in the working draft.
> 
> Perhaps you can use RECORD's NAME attribute in conjunction with the
> SUBMIT element's NAMELIST, METHOD=POST, and ENCTYPE="multipart/form-data"?
> 
> Speaking of omissions in VoiceXML drafts, I notice that Lernout &
> Hauspie left endpointing (also called segmentation and alignment)
> out of the so-called semantic interpretation working draft:
> 
>   http://www.w3.org/TR/2001/WD-semantic-interpretation-20011116/
> 
> even though they produce a product to accomplish the required task.
> 
> Anyway, with the large number of low-cost and no-cost recognition
> systems presently available, a handful of which have endpointing
> features built-in, this sorry state of affars is surmountable.
> However, VoiceXML is presently incapable of the task.
> 
> Endpointing is essential to perform the operations described on:
> 
>   http://llt.msu.edu/vol2num2/article3/#Figure3
> 
> Best wishes,
> James
Received on Friday, 1 February 2002 13:16:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:54 GMT