Re: [Speechsc] Problem with draft-6 RECOGNIZEcommandandtest/uri-listcontent type
"Dave Burke" <david.burke@voxpilot.com> Fri, 17 June 2005 09:54 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjDYk-0000aP-PO; Fri, 17 Jun 2005 05:54:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjDYj-0000aK-Rj for speechsc@megatron.ietf.org; Fri, 17 Jun 2005 05:54:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00264 for <speechsc@ietf.org>; Fri, 17 Jun 2005 05:54:42 -0400 (EDT)
Received: from fw01.db01.voxpilot.com ([212.17.54.82] helo=mail.voxpilot.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DjDvn-0005rO-SC for speechsc@ietf.org; Fri, 17 Jun 2005 06:18:36 -0400
Received: from daburkewxp (unknown [10.0.0.203]) by mail.voxpilot.com (Postfix) with ESMTP id D99D4214041; Fri, 17 Jun 2005 09:54:28 +0000 (GMT)
Message-ID: <005a01c57322$8d5271c0$cb00000a@db01.voxpilot.com>
From: Dave Burke <david.burke@voxpilot.com>
To: "Wyss, Felix" <FelixW@inin.com>, "Shanmugham, Saravanan" <sarvi@cisco.com>, "David R. Oran" <oran@cisco.com>
References: <8F9F1C6AA1D6834EACC379C8821533A6011524EC@i3mail1.i3domain.inin.com>
Subject: Re: [Speechsc] Problem with draft-6 RECOGNIZEcommandandtest/uri-listcontent type
Date: Fri, 17 Jun 2005 10:54:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: 7bit
Cc: speechsc@ietf.org, "Bennett, Patrick" <Patrick.Bennett@inin.com>
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
Sender: speechsc-bounces@ietf.org
Errors-To: speechsc-bounces@ietf.org
Looks good. Just one or two queries/comments: - Why delimit the first parameter with ":" and the subsequent with ";". Simpler, more uniform to just use ";"? - Is a comments mechanism really needed? "#" is very common in URIs to identify fragments (especially in SRGS!) - Should we include weight in "Optional Parameters" (we either define it here or in MRCP spec)? - We'll also use session: URIs with the grammar-ref-list (to allow weights on previously DEFINE'd-GRAMMARs). Fits BNF in RFC2396 and below Dave ----- Original Message ----- From: "Wyss, Felix" <FelixW@inin.com> To: "Shanmugham, Saravanan" <sarvi@cisco.com>; "Dave Burke" <david.burke@voxpilot.com>; "David R. Oran" <oran@cisco.com> Cc: <speechsc@ietf.org>; "Bennett, Patrick" <Patrick.Bennett@inin.com> Sent: Friday, June 17, 2005 4:24 AM Subject: RE: [Speechsc] Problem with draft-6 RECOGNIZEcommandandtest/uri-listcontent type Does this seem reasonable? Felix ******************************************************* text/grammar-ref-list MIME type registration IANA is requested to register the following MIME type according to the process defined in RFC 2048. To: ietf-types@iana.org Subject: Registration of MIME media type text/grammar-ref-list MIME media type name: text MIME subtype name: grammar-ref-list Required parameters: None Optional parameters: None Encoding considerations: Depending on the transfer protocol, a transfer encoding may be necessary to deal with very long lines. Security considerations: This media type contains URIs which may represent references to external resources. As these resources are assumed to be speech recognition grammars, similar considerations as for the media types "application/srgs" and "application/srgs+xml" [1] apply. Interoperability considerations: We make the assumption that '>' is not a valid character in a URI according to RFC2396. Published specification: The RECOGNIZE method of the MRCP protocol performs a recognition operation that matches input against a set of grammars. When matching against more than one grammar, it is sometimes necessary to use different weights for the individual grammars. These weights are not a property of the grammar resource itself but qualify the reference to that grammar for the particular recognition operation initiated by the RECOGNIZE method. The format of the proposed text/grammar-ref-list media type is as follows: body = *line line = (comment | reference) CRLF comment = "#" *<any CHAR excluding CR and LF> reference = "<" uri ">" [parameters] [comment] parameters = ":" parameter *(";" parameter) parameter = name "=" value uri = <same as 'URI-reference' production of RFC 2396> name = <same as 'token' production of RFC2616> value = <same as 'quoted-string' production of RFC2616> Note that MRCP currently only uses a 'weight' parameter, but there may be the need for additional parameters in the future (even vendor specific extensions). Names of vendor specific parameters SHOULD start with "x-". Example: # Input for 'Form 1' <http://example.com/grammars/field1.gram> # weight 1.0 is default <http://example.com/grammars/field2.gram>:weight="0.85" <http://example.com/grammars/universals.gram>:weight="0.75" Applications which use this media type: Media Resource Control Protocol (MRCP) Additional information: Magic number(s): none File extension(s): none Macintosh File Type Code(s): none [1] The W3C Speech Interface Framework Media Types: application/voicexml+xml, application/ssml+xml, application/srgs, application/srgs+xml, application/ccxml+xml and application/pls+xml; http://www.ietf.org/internet-drafts/draft-froumentin-voice-mediatypes-02 .txt > -----Original Message----- > From: Shanmugham, Saravanan [mailto:sarvi@cisco.com] > Sent: Wednesday, June 15, 2005 13:53 > To: Wyss, Felix; Dave Burke; David R. Oran > Cc: speechsc@ietf.org; Bennett, Patrick > Subject: RE: [Speechsc] Problem with draft-6 RECOGNIZEcommandandtest/uri- > listcontent type > > I am fine with the idea. > Would you be able to propose a content-type registration section for > this content-type. > We could add it to the current list of registrations and retire the > one-of header. > > Sarvi > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Wyss, Felix
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Shanmugham, Saravanan
- Re: [Speechsc] Problem with draft-6 RECOGNIZEcomm… David R. Oran
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Wyss, Felix
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Shanmugham, Saravanan
- Re: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Dave Burke
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Wyss, Felix
- Re: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Dave Burke
- RE: [Speechsc] Problem with draft-6 RECOGNIZEcomm… Wyss, Felix
- Re: [Speechsc] Problem with draft-6RECOGNIZEcomma… Dave Burke