* Matt Oshry wrote:
>The language in C.3 of VoiceXML 2.1 will be modified to clarify that the
>undefined behavior is specific to how a conforming VoiceXML 2.1
>processor handles a document that specifies a version attribute with a
>value other than 2.0 or 2.1. The statement was meant to clarify issue 88
>[3] from the comments on the Last Call Working Draft of VoiceXML 2.1.
With this change applied, would there be cases where a document is non-
conforming but behavior of processors would be undefined? Would the
specification still say that behavior is undefined?
--
BjÃ¶rn HÃ¶hrmann Â· mailto:bjoern@hoehrmann.de Â· http://bjoern.hoehrmann.de
Weinh. Str. 22 Â· Telefon: +49(0)621/4309674 Â· http://www.bjoernsworld.de
68309 Mannheim Â· PGP Pub. KeyID: 0xA4357E78 Â· http://www.websitedev.de/