CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 20:24:45 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:33:02 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 07:49:45 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bc48808a188cbc
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=HH.inZuO4bH2aWfrn6Csqu641SeUYVlsptHeOTYExAc-1760041485-1.0.1.1-swA087Lfa738Z_4YMojr803sMkntzrkvsE.9Zi99.x9CGjQ6BnOyLuuyk550vNqzX_MQXFO3lDGVk6G28NrUot7MyKky.RKdzL85YnyMtDA; path=/; expires=Thu, 09-Oct-25 20:54:45 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c09a7018cc860e-BLR
alt-svc: h3=":443"; ma=86400
Re: "Protocol" requirement - Interpretation from Bjorn Bringert on 2010-12-14 (public-xg-htmlspeech@w3.org from December 2010)
Re: "Protocol" requirement - Interpretation
- From: Bjorn Bringert <bringert@google.com>
- Date: Tue, 14 Dec 2010 12:42:11 +0000
- To: "Young, Milan" <Milan.Young@nuance.com>
- Cc: public-xg-htmlspeech@w3.org
- Message-ID: <AANLkTi=jL9-FedXpVPZgYp1z95caqPguLm9QZS7QqpUA@mail.gmail.com>
I don't have any objections to this as a requirement other than that it adds API complexity. It's not a requirement that I would prioritize highly. /Bjorn On Mon, Dec 13, 2010 at 7:19 PM, Young, Milan <Milan.Young@nuance.com> wrote: > XmlHttpRequest may work fine, but it assumes a largely bypassed UA to handle other requirements such as session tracking. It also assumes a SS with an HTTP server. > > So while I share your optimism on these points, I agree with Michael that we need to be careful. > > Any objections with adding this to spec even if it may later be rendered trivial by device approach? > > Thanks > > > -----Original Message----- > From: Bjorn Bringert [mailto:bringert@google.com] > Sent: Monday, December 13, 2010 2:13 AM > To: Young, Milan > Cc: public-xg-htmlspeech@w3.org > Subject: Re: "Protocol" requirement - Interpretation > > Why does this have to be part of the speech API? Remote text > interpretation can be done without using any speech APIs. I've > implemented that myself a couple of times using just XmlHttpRequest. > > /Bjorn > > On Fri, Dec 10, 2010 at 7:57 PM, Young, Milan <Milan.Young@nuance.com> wrote: >> Summary - Web applications must be able to request NL interpretation based >> only on text input (no audio sent). >> >> >> >> Description - Recognizers commonly separate lexical speech token processing >> from its semantic understanding. This often requires multiple passes of >> semantic processing. >> >> > > > > -- > Bjorn Bringert > Google UK Limited, Registered Office: Belgrave House, 76 Buckingham > Palace Road, London, SW1W 9TQ > Registered in England Number: 3977902 > -- Bjorn Bringert Google UK Limited, Registered Office: Belgrave House, 76 Buckingham Palace Road, London, SW1W 9TQ Registered in England Number: 3977902
Received on Tuesday, 14 December 2010 12:42:40 UTC