VoiceXML 2.1
Today the W3C published a new working draft of VoiceXML 2.1. This draft addresses a number of the comments that have been received to data and a fair amount of clarifications. Sadly there is not a detailed public change document or list but what can you do? ;-)
One of the major changes to this draft that I ended up pushing very hard for is an overhaul of the 2.1 <data> element security model. The new version now allows developers to set both allow and deny access control instructions and modifies the behavior of what to do when there is no access control instruction. Before it would always deny access if you did not have the ACL specified. The new version makes this dependent on the execution environment. The reason that you need to have this dependent on the environment is that the correct default setting really depends on where you are running the browser and what sort of data feeds you are accessing. These changes to the model make it much more like the Java or IE security models and will allow for much easer access to existing data feeds in deployment models where this makes sense.