W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2006

RE: Please redefine foreach element as it is in VoiceXML 2.1 CR

From: Carter, Jerry <jerry.carter@nuance.com>
Date: Mon, 11 Sep 2006 13:16:28 -0400
Message-ID: <F8940C21CD563F49BC884A274C4653DF05AA0C51@bn-exch1.speechworks.com>
To: www-voice@w3.org, ken.waln@edify.com, Teemu.Tingander@tecnomen.com

Teemu Tingander and Ken Waln:

Thank you for your detailed comments [1][2] regarding the <foreach> element
in the VoiceXML 2.1 Candidate Recommendation.  The semantics of this element
have been the subject of much discussion within the working group.  We have
tried to clarify the text in several areas while maintaining much of the
enhanced expressive power.

The Voice Browser Working Group has received a series of concerns about the
content model of the <foreach> element.  We have considered the issues
raised and examined a number of use cases.  The result of this process is
that the content model of the <foreach> element will be altered.

    When the <foreach> appears within a <prompt> element, it will
    have the same content model as the <enumerate> element.  This
    allows application authors to perform prompt concatenation of
    Array content.  When the <foreach> element appears in
    executable content (other than within a <prompt>), any 
    executable content may appear.  This introduces a looping 
    construct in executable content which is otherwise difficult 
    to author.

These two content models will be enforced in the VoiceXML 2.1 schema.

We hope to publish a new draft shortly and we welcome your review of the
updated text.

[1] http://lists.w3.org/Archives/Public/www-voice/2005AprJun/0065.html
[2] http://lists.w3.org/Archives/Public/www-voice/2005AprJun/0064.html
Received on Monday, 11 September 2006 17:18:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:49:04 GMT