Re: [Dmsp] clarifications requested in draft-engelsma-dmsp-02.txt

Chris Cross <xcross@us.ibm.com> Fri, 01 December 2006 18:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GqD54-0006Dw-Jz; Fri, 01 Dec 2006 13:25:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GqD52-0006Di-W6 for dmsp@ietf.org; Fri, 01 Dec 2006 13:25:48 -0500
Received: from e31.co.us.ibm.com ([32.97.110.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GqD50-0006vT-E9 for dmsp@ietf.org; Fri, 01 Dec 2006 13:25:48 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e31.co.us.ibm.com (8.13.8/8.12.11) with ESMTP id kB1IPkYc017274 for <dmsp@ietf.org>; Fri, 1 Dec 2006 13:25:46 -0500
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kB1IPjFC457140 for <dmsp@ietf.org>; Fri, 1 Dec 2006 11:25:45 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kB1IPjqD024638 for <dmsp@ietf.org>; Fri, 1 Dec 2006 11:25:45 -0700
Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com [9.17.195.145]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kB1IPjFT024616 for <dmsp@ietf.org>; Fri, 1 Dec 2006 11:25:45 -0700
In-Reply-To: <6806C66D71ED9241BAECC0478173B71F01072D05@de01exm69.ds.mot.com>
Subject: Re: [Dmsp] clarifications requested in draft-engelsma-dmsp-02.txt
To: "Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com>
X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006
Message-ID: <OFC9A8629E.A453C45F-ON85257237.0061422F-85257237.00653823@us.ibm.com>
From: Chris Cross <xcross@us.ibm.com>
Date: Fri, 1 Dec 2006 13:25:35 -0500
X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Release 7.0.2HF32 | October 17, 2006) at 12/01/2006 11:25:44
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: dmsp@ietf.org
X-BeenThere: dmsp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Multimodal Synchronization Protocol <dmsp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dmsp>
List-Post: <mailto:dmsp@ietf.org>
List-Help: <mailto:dmsp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1707142298=="
Errors-To: dmsp-bounces@ietf.org


"Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com> wrote on
12/01/2006 11:17:38 AM:

> All,
>
> We're working on another revision of the dmsp spec that we hope to
> complete in the next few days.  Here is a summary of some of the areas
> that need correction/clarification in the current version.  Please
> forward any comments you have on these or other areas
>
> While working on a C++ implementation of the client state machine, Jim
> Ferrans pointed out the following items that need attention:
>
> Item 1 -  Section 4.2.3.2 VXML Start Signal Message - currently only
> supports a dialog url.  In certain situations it may be desirable for
> the client application to be completely self contained, and not
> dependent on a network-based application server.  The VXML Start message
> should be able to include actual VoiceXML content instead of an url.
>
> Comments: There are a couple of possiblities.  1) Add a flag to the
> message that indicates whether the string in the Dialog URL field is an
> URL or VoiceXML content.  2) Leave the message as it is, and let the VUA
> infer from the value of Dialog URL itself, what it is.  For example, if
> the string begins with "<?xml" treat it as VoiceXML content, otherwise
> confirm it's a fully qualified URL.  Any preferences one way or the
> other?
>

I prefer the additional field. Much cleaner data model at the cost of one
bit in the message.

> Item 2 - Section 4.2.6.7 - 4.2.6.8. Originally, the Motorola
> implementation of the server state machine, only reported the slots
> corresponding to VoiceXML form items that have changed value during a
> given recognition cycle are reflected in the recognition result
> messages.  The motivation for this approach was to minimize message
> size.  However, application developers have argued convincingly that
> this is not helpful, and its best for the recognition result to fully
> represent what the user actually said...
>
> Comments: We should add wording in these sections to clarify this
> situation.  Any additional or contrary thoughts from other server
> implementors?
>

Interesting question. I've always read "field" in tables 7 and 8 to
referring to VoiceXML fields;-) When the VUA is a VoiceXML processor, reco
result can come from one of two situations: 1) when processing an
individual field or 2) from a form level grammar for a mixed initiative
form. In the first case, by definition the reco result should just return
the result for the field. In the second, the result should be returned for
all the fields that were filled. I believe if an implementation returns
more than the fields that were filled then it breaks the semantics of mixed
initiative which allows for partial filling of a form with a single
utterance that matches the form level grammar. This question requires a
careful reading of the VoiceXML spec. Re-reading Item 2, doesn't sending
only what changed "fully represent what the user actually said?"

> In addition to these issues Jim raised, there were a couple of other
> minor issues reported that need clarification/correction:
>
> Item 3: Table 11 - The 7th field in the table "Event Type" is actually a
> typo and will be eliminated in the next revision.
>
> Item 4: Section 4.2.4.9, Table 21.  The 5th field listed in the table
> "Fields" is meant to be an array of strings, NOT an array of Fields
> values as defined in Table 7.  Hence the reference "see Table 7" in the
> Value column in Table 21 is incorrect.  This will be updated in the next
> revision.

I concur with both corrections.

Chris
_______________________________________________
Dmsp mailing list
Dmsp@ietf.org
https://www1.ietf.org/mailman/listinfo/dmsp