Re: Next HTML web api document

Section 3.1 Reco Attributes / Grammar

"The uri of a grammar associated with this reco. If unset, this defaults to
the default builtin uri."

Presumably using the grammar attribute overwrites the default grammar, so
if a developer wishes to add a grammar that supplements the default
grammar, then this alternative should work:   reco.request.addGrammar(url).
 A note to this effect would add clarity.

Section 3.4

"For type checkbox, the input should be set to a checkedness of true."

It would be nice to have a way to allow user to say something to set it to
false, but I can't think of a good convention for this other than adding an
attribute or grammar. Perhaps this could/should only be possible via
scripting.
(I don't like the idea of toggling the checkbox because some users may not
be able to easily observe what state the checkbox is currently in.)



"For date and time types ... type of color ... type of range the assignment
is only allowed if it is a valid ..."

On our call we discussed how these grammars are hints, and in particular
how pattern may be difficult to implement. We discussed that showing an
output response, even an invalid one, may be more valuable than no response.


Some typos...

Section 2:
- s/uesd/used/

Section 3:
- s/where ever/wherever/
- s/might be is unspecified/might be, is unspecified/

Section 3.3
- s/to not recognize offensive words/to not return offensive words in the
recognition results/

Section 3.4
- s/attribute set then the/attribute set, then the/
- s/is a button then if/is a button and if/
- s/a input/an input/
- s/high lighted text/highlighted text/