Satish's example is very encouraging. Thanks Satish! In addition to end-pointing, the other thing that comes to mind with the <device> API is how we'd deal with codec requirements. The draft says "** This will be pinned down to a specific codec", but it's unclear to me what direction it's headed in. Maybe I'm repeating what's already been said today. But we should still work on defining the requirements are, and if Satish's approach satisfies them, albeit with some reasonable change requests to the groups involved, then great. From: Satish Sampath [mailto:satish@google.com] Sent: Tuesday, December 07, 2010 12:27 PM To: Bjorn Bringert Cc: Young, Milan; Marc Schroeder; Robert Brown; Dave Burke; public-xg-htmlspeech@w3.org Subject: Re: UA <=> SS Protocol > Our recommendation would still need to state that all Speech Services and UAs must support XmlHttpRequest as a means of communication. Top browsers/UAs already support it and the ones who haven't done yet will most likely have it by the time our XG produces the deliverables late next year. http://en.wikipedia.org/wiki/XMLHttpRequest#Cross-domain_request Regarding speech services supporting it - XMLHttpRequest is a client side technology implemented in UAs and what servers receive will be standard http requests. They don't have to do anything special if they already provide a http API. -- Cheers Satish
Received on Tuesday, 7 December 2010 22:51:43 UTC