Re: [Speechsc] Confusuion with INTERPRET

Dan Burnett <dburnett@voxeo.com> Tue, 29 December 2009 11:29 UTC

Return-Path: <dburnett@voxeo.com>
X-Original-To: speechsc@core3.amsl.com
Delivered-To: speechsc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E88473A677C for <speechsc@core3.amsl.com>; Tue, 29 Dec 2009 03:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.152
X-Spam-Level:
X-Spam-Status: No, score=0.152 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7uenUvUEJvze for <speechsc@core3.amsl.com>; Tue, 29 Dec 2009 03:29:22 -0800 (PST)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with ESMTP id 5A4F53A6767 for <speechsc@ietf.org>; Tue, 29 Dec 2009 03:29:22 -0800 (PST)
Received: from [71.204.33.81] (account dburnett HELO [192.168.15.111]) by voxeo.com (CommuniGate Pro SMTP 5.2.3) with ESMTPSA id 55101780; Tue, 29 Dec 2009 11:29:01 +0000
Message-Id: <E1BF1CBD-FBA6-4221-8DB0-C86BC9AB7E08@voxeo.com>
From: Dan Burnett <dburnett@voxeo.com>
To: Corby Anderson <corbya@microsoft.com>
In-Reply-To: <EF149B22CD1213419BF4DFE038422CAC6D6C23@TK5EX14MBXC116.redmond.corp.microsoft.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-41-311098442"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 29 Dec 2009 06:28:59 -0500
References: <EF149B22CD1213419BF4DFE038422CAC6D6C23@TK5EX14MBXC116.redmond.corp.microsoft.com>
X-Mailer: Apple Mail (2.936)
Cc: "speechsc@ietf.org" <speechsc@ietf.org>
Subject: Re: [Speechsc] Confusuion with INTERPRET
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speechsc>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Dec 2009 11:29:24 -0000

Corby,

Thanks for catching these typos.  You are correct, and I will update  
as you suggest.  See below.

-- dan

On Aug 21, 2009, at 9:13 PM, Corby Anderson wrote:

> Does section 9.20 INTERPRET need some clarification? 9.20 states  
> that INTERPRETATION should return an INTERPRETATION-COMPLETE event  
> (as described in 9.21), but the example in section 9.20 shows the  
> following response:
>
>    S->C:    MRCP/2.0 49 543267 200 COMPLETE
>            Channel-Identifier:32AECB23433801@speechrecog
>            Completion-Cause:000 success
>            Content-Type:application/nlsml+xml
>            Content-Length:...
>
> That S->C format is for responses (5.3), not events (5.5).  Contrast  
> this with the RECOGNITION-RESPONSE event to RECOGNIZE:
>
>    S->C:MRCP/2.0 486 RECOGNITION-COMPLETE 543260 COMPLETE
>    Channel-Identifier:32AECB23433801@speechrecog
>    Completion-Cause:000 success
>    Waveform-URI:<http://web.media.com/session123/audio.wav>;
>                 size=124535;duration=2340
>    Content-Type:applicationt/x-nlsml
>    Content-Length:...
>
> Shouldn’t the first line of the INTERPRETATION-COMPLETE event be  
> something like the following?
>    S->C:    MRCP/2.0 49 INTERPRETATION-COMPLETE 543267 COMPLETE

Yes.  I will correct this in 9.20 and 9.21 in the next draft.

>
> The only mention of INTERPRETATION-COMPLETE in the spec are
> * table of contents
> * 9.3 Recognizer events
> * 9.21 where it’s described
> * 13.1.2 MRCPv2 methods and events
> * 15 Normative definition
>
> I found no usage examples for INTERPRETATION-COMPLETE; most notably  
> not in 9.20
>
>
>
> Also, section 9.9 states
>    For the recognizer resource, RECOGNIZE is the only request that
>    returns a request-state of IN-PROGRESS, meaning that recognition is
>    in progress.
>
> But the example in 9.20 for INTERPRET shows
>    S->C:    MRCP/2.0 49 543266 200 IN-PROGRESS
>            Channel-Identifier:32AECB23433801@speechrecog
>
> Is the recognizer resource the resource that performs  
> interpretation?  If so, then the text in 9.9 should be changed to  
> say the following:
>    For the recognizer resource, RECOGNIZE and INTERPRET are the only
>    requests that return a request-state of IN-PROGRESS, meaning that
>    recognition or interpretation is in progress.

I will also make this change in the next draft.

>
>
> Corby Anderson
>
> _______________________________________________
> Speechsc mailing list
> Speechsc@ietf.org
> https://www.ietf.org/mailman/listinfo/speechsc
> Supplemental web site:
> &lt;http://www.standardstrack.com/ietf/speechsc&gt;