W3C home > Mailing lists > Public > public-xg-htmlspeech@w3.org > December 2010

RE: UA <=> SS Protocol

From: Young, Milan <Milan.Young@nuance.com>
Date: Wed, 8 Dec 2010 10:21:46 -0800
Message-ID: <1AA381D92997964F898DF2A3AA4FF9AD09981F55@SUN-EXCH01.nuance.com>
To: "Robert Brown" <Robert.Brown@microsoft.com>, "Satish Sampath" <satish@google.com>, "Bjorn Bringert" <bringert@google.com>
Cc: "Marc Schroeder" <marc.schroeder@dfki.de>, "Dave Burke" <daveburke@google.com>, <public-xg-htmlspeech@w3.org>
The requirement that began this thread was that we either specify or
reference a *concrete* protocol.  The principle disagreement is the
shades of grey in the word concrete.

 

I do not believe DeviceAPIs, for example, could be considered concrete
unless we constrain the way XHR is used.  I suspect Bjorn disagrees
based on his statement about "bilateral agreement", but others
(including Satish and Robert) have been silent.

 

Dan, could we please add this to tomorrow's agenda?

 

Thanks

 

 

________________________________

From: Robert Brown [mailto:Robert.Brown@microsoft.com] 
Sent: Tuesday, December 07, 2010 2:51 PM
To: Satish Sampath; Bjorn Bringert
Cc: Young, Milan; Marc Schroeder; Dave Burke;
public-xg-htmlspeech@w3.org
Subject: RE: UA <=> SS Protocol

 

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 Wednesday, 8 December 2010 18:22:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 December 2010 18:22:26 GMT