W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2004

Comments for PR-voicexml20-20040203

From: Susan Lesch <lesch@w3.org>
Date: Sun, 29 Feb 2004 08:46:48 -0600
Message-Id: <p0601020bbc67908609ac@[192.168.6.15]>
To: www-voice@w3.org

Hello,

These are comments for your VoiceXML 2.0 Proposed Recommendation [1].

In these table of contents items and in their headings, I believe that these
element names should be lowercase (XML is case sensitive).
	2.2.1 MENU
	2.2.2 CHOICE
	2.2.4 ENUMERATE
	2.3.1 FIELD
	2.3.2 BLOCK
	2.3.3 INITIAL
	2.3.4 SUBDIALOG
	2.3.5 OBJECT
	2.3.6 RECORD
	2.3.7 TRANSFER

I think, in 4.1.6, that no matter what the example is trying to show, it
shows VoiceXML in an odd light -- forcing someone to abandon their favorite
ice cream flavor in favor of those in the menu. In 5.2, "when the user does
not respond, doesn't respond intelligibly" assumes the user "doesn't" do
something right (I would instead say "responds in a way the application
[or platform] doesn't understand").

Global corrections:
s/Universal Resource Identifiers/Uniform Resource Identifiers/ and RFC 2396
    should probably be introduced at this first occurrence.
s/web/Web/
s/ECMAscript/ECMAScript/
s/Feburary/February/
s/VoicexML/VoiceXML/
s/alteratives/alternatives/
s/familar/familiar/
s/metedata/metadata/
s/permited/permitted/
s/plaform/platform/
s/occurence/occurrence/
s/preceeding/preceding/
s/precendence/precedence/
s/refererence/reference/
s/resouce/resource/
s/specfied/specified/
s/specifc/specific/
s/speedvsacurracy/speedvsaccuracy/
s/W3C member/W3C Member/
s/working groups/Working Groups/
s/web-based/Web-based/
s/VoiceXML Interpreter/VoiceXML interpreter/
s/Form Interpretation Algorithm/form interpretation algorithm/
s/Master card/MasterCard/
s/Mastercard/MasterCard/
s/Special Information Tone/special information tone/
s/pzza/pizza/
s/social securit/US Social Security/
s/recommendation/Recommendation/
s/Text-To-Speech/text-to-speech/
s/members of the W3C Voice Browser Working Group/participants in the W3C Voice
Browser Working Group/

In 1.2.3 and 6.1.4, "The "http" URI protocol must be supported." http
is a URI scheme for the HTTP protocol (not a "URI protocol" as far as
I know).

In 2.1.4, the stray span around &lt;clear namelist="card_type card_num
expiry_date confirm"/&gt; makes it render in non-monospace. Same for
"&lt;link event="exit"&gt; &lt;grammar type="application/srgs+xml"
src="/grammars/exit.grxml"/&gt; &lt;/link&gt;" in 2.1.5.1 and "say-as
interpret-as="currency">$299.95</say-as" in 4.1.3 and most of the example
in Appendix C and parts of both examples in Appendix P.

Why is Catch ever capitalized (even in headings)? Param?

In 2.3.7.1 and 2.3.7.2.2 (and anywhere else font -1 appears), please
remove the font elements (<font face="Courier New, Courier, mono" size="-1">).
(CSS can accomplish the same thing better but there's no reason to reduce
the size of significant info here.)

In Appendix D, "<br clear="none" />" causes the figure label and the bottom
of the image to overlap in my browser. I'd replace that with simply <br />.
Also in Appendix D, please check image dimensions in the XHTML (they are
distorting the text).

[1] http://www.w3.org/TR/2004/PR-voicexml20-20040203/

Best wishes for your project,
-- 
Susan Lesch           http://www.w3.org/People/Lesch/
mailto:lesch@w3.org               tel:+1.858.483.4819
World Wide Web Consortium (W3C)    http://www.w3.org/
Received on Sunday, 29 February 2004 09:46:50 GMT

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