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

Futher comments on Dec 14th VoiceXML 2.0 draft

From: Edgar, Bob <Bob.Edgar@dialogic.com>
Date: Wed, 17 Jan 2001 14:18:48 -0500
Message-ID: <9D31D8D27C98D4119D8900B0D03E6411280F04@exchange1sa.dialogic.com>
To: "'www-voice@w3.org'" <www-voice@w3.org>
2.3.1.1 "The result is a string with the format UUUmm.nn, where UUU is the
three character currency indicator according to ISO standard 4217:1995 or
null if not spoken by the user. If the field value is subsequently used in a
prompt, it will be spoken as a currency amount appropriate to the current
locale."

Surely the four characters "null" are not inserted into the string? This is
not very clear, because "null" is a special symbol in ECMAScript, but this
kind of null can't be part of a string. If the proposal truly is to insert
"null" then, then I would suggest changing this to the three characters
"???" to be consistent with unknown fields in the date and to make it easier
to extract the numerical value (avoiding this one case where there are four
instead of three characters in front of the number). Also, shouldn't there
be a way to have a locale-specific default, e.g. a US browser might assume
USD rather than null?

2.3.1.1
The built-in boolean type is a special case: its value is stored as a string
"yes" or "no", but is <submit>ed as true or false. Other field types submit
the value as stored in the variable. There is no obvious reason for the
added complexity of this special case (backwards compaibility), should
either be explained or changed to be consistent.

2.3.1.1 "Note that use of the result as a number within an expression will
require use of the ECMAScript 'parseInt' function."

Why? ECMAScript automatically converts strings to numerical values when used
in an expression. 
Suggestion: it should be mandated that the browser does not use a leading
zero which would cause ECMAScript to interpret as an octal number.

2.3.6 "...MIME format of the recording."

There are several other references to MIME, e.g. 3.1.1.3 "The MIME type is
optional..". Is MIME type a properly defined term? The HTTP & MIME RFCs both
talk about "Media Types".

Appendix B (the DTD).

Both <option> and <script> have the value (#PCDATA)*. What is the difference
between #PCDATA and (#PCDATA)*? If you have two or more #PCDATAs isn't that
just exactly one #PCDATA?

Bob.
-------------------------------------------
Bob Edgar
Vice President, Parity Software Business Unit
Converged Communications Services and Solutions Division
Dialogic Corp., an Intel Company
(415) 332-5656 ext 111
Fax (415) 332-5657
mailto:Bob.Edgar@dialogic.com
http://www.parity.com
Received on Wednesday, 17 January 2001 14:21:09 GMT

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