Return-Path: <corbya@microsoft.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 1293C3A69B5 for <speechsc@core3.amsl.com>;
 Fri, 21 Aug 2009 18:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5
 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 VGeRr-a27y11 for
 <speechsc@core3.amsl.com>; Fri, 21 Aug 2009 18:13:23 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by
 core3.amsl.com (Postfix) with ESMTP id 334F93A6838 for <speechsc@ietf.org>;
 Fri, 21 Aug 2009 18:13:23 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by
 TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft
 SMTP Server (TLS) id 8.2.176.0; Fri, 21 Aug 2009 18:13:28 -0700
Received: from TK5EX14MBXC116.redmond.corp.microsoft.com ([169.254.7.27]) by
 TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi;
 Fri, 21 Aug 2009 18:13:22 -0700
From: Corby Anderson <corbya@microsoft.com>
To: "speechsc@ietf.org" <speechsc@ietf.org>
Thread-Topic: Confusuion with INTERPRET
Thread-Index: Acoixbz/oqwD7Tk/Sv6x0aOqfZ5kDw==
Date: Sat, 22 Aug 2009 01:13:20 +0000
Message-ID: <EF149B22CD1213419BF4DFE038422CAC6D6C23@TK5EX14MBXC116.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative;
 boundary="_000_EF149B22CD1213419BF4DFE038422CAC6D6C23TK5EX14MBXC116red_"
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 22 Aug 2009 08:38:25 -0700
Subject: [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: Sat, 22 Aug 2009 01:15:30 -0000

--_000_EF149B22CD1213419BF4DFE038422CAC6D6C23TK5EX14MBXC116red_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Does section 9.20 INTERPRET need some clarification? 9.20 states that INTER=
PRETATION 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 w=
ith 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=3D124535;duration=3D2340
   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

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 s=
o, 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.


Corby Anderson


--_000_EF149B22CD1213419BF4DFE038422CAC6D6C23TK5EX14MBXC116red_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>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:<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; S-&gt;C:&nbsp;&nbsp;&nbsp; MRCP/2.0 49 54=
3267
200 COMPLETE<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
Channel-Identifier:32AECB23433801@speechrecog<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
Completion-Cause:000 success<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
Content-Type:application/nlsml+xml<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
Content-Length:...<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>That S-&gt;C format is for responses (5.3), not events=
 (5.5).&nbsp;
Contrast this with the RECOGNITION-RESPONSE event to RECOGNIZE:<o:p></o:p><=
/p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; S-&gt;C:MRCP/2.0 486 RECOGNITION-COMPLETE
543260 COMPLETE<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Channel-Identifier:32AECB23433801@speechr=
ecog<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Completion-Cause:000 success<o:p></o:p></=
p>

<p class=3DMsoNormal>&nbsp;&nbsp;
Waveform-URI:&lt;http://web.media.com/session123/audio.wav&gt;;<o:p></o:p><=
/p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
size=3D124535;duration=3D2340<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Content-Type:applicationt/x-nlsml<o:p></o=
:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; Content-Length:...<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Shouldn&#8217;t the first line of the INTERPRETATION-C=
OMPLETE
event be something like the following?<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; S-&gt;C:&nbsp;&nbsp;&nbsp; MRCP/2.0 49 IN=
TERPRETATION-COMPLETE
543267 COMPLETE<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>The only mention of INTERPRETATION-COMPLETE in the spe=
c are<o:p></o:p></p>

<p class=3DMsoNormal>* table of contents<o:p></o:p></p>

<p class=3DMsoNormal>* 9.3 Recognizer events<o:p></o:p></p>

<p class=3DMsoNormal>* 9.21 where it&#8217;s described<o:p></o:p></p>

<p class=3DMsoNormal>* 13.1.2 MRCPv2 methods and events<o:p></o:p></p>

<p class=3DMsoNormal>* 15 Normative definition<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>I found no usage examples for INTERPRETATION-COMPLETE;=
 most
notably not in 9.20<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Also, section 9.9 states<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; For the recognizer resource, RECOGNIZE is=
 the
only request that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; returns a request-state of IN-PROGRESS, m=
eaning
that recognition is<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; in progress.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>But the example in 9.20 for INTERPRET shows<o:p></o:p>=
</p>

<p class=3DMsoNormal>&nbsp;&nbsp; S-&gt;C:&nbsp;&nbsp;&nbsp; MRCP/2.0 49 54=
3266
200 IN-PROGRESS<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
Channel-Identifier:32AECB23433801@speechrecog<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Is the recognizer resource the resource that performs
interpretation?&nbsp; If so, then the text in 9.9 should be changed to say =
the
following:<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp;&nbsp; For the recognizer resource, RECOGNIZE an=
d
INTERPRET are the only<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; &nbsp;requests that return a request-state of
IN-PROGRESS, meaning that<o:p></o:p></p>

<p class=3DMsoNormal>&nbsp; &nbsp;recognition or interpretation is in progr=
ess.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Corby Anderson<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

--_000_EF149B22CD1213419BF4DFE038422CAC6D6C23TK5EX14MBXC116red_--
