VoiceXML 2.0: Official Response #3 to Candidate Recommendation Issues

The Voice Browser Working Group (VBWG) is now completing its resolution
of 
issues raised during the review of the Candidate Recommendation version
of
VoiceXML 2.0 [1]. Our apologies that it has taken so long to respond.

Following the process described in [2] for advancement to Proposed
Recommendation, this is the VBWG's formal response to the issues you
raised.

Please indicate before 26 November 2003 whether you are satisfied with
the
VBWG's resolutions, whether you think there has been a misunderstanding,
or
whether you wish to register an objection.

If you do not think you can respond before 26 November, please let me
know.
The Director will appreciate a response whether you agree with the
resolutions
or not. However, if we do not hear from you at all by 26 November 2003,
we
will assume that you accept our resolutions.

Below you will find a summary of the VBWG's responses to each of your
issues. Please use the issue identifiers when responding.

Thank you,

Scott McGlashan
Co-chair, Voice Browser Working Group

[1] http://www.w3.org/TR/2003/CR-voicexml20-20030220/ 
[2] http://www.w3.org/2003/06/Process-20030618/ 


-----------------------------------------------
Issues you raised and VBWG responses
-----------------------------------------------

Issues:
http://lists.w3.org/Archives/Public/www-voice/2003JanMar/0074.html
CR7-1

Issue CR7-1
I would like to object that all the examples in VoiceXML2 come with an
XML declaration and a schemaLocation attribute. It makes the language
appear unneccesarily complex. The Hello World example would be much
simpler as:

<vxml xmlns="http://www.w3.org/2001/vxml" version="2.0">
  <form>
    <block>Hello World!</block>
  </form>
</vxml>

schemaLocation bothers me more than by just making the examples hard to 
read. It suggests that the declaration is mandatory (which the XMLSchema
refutes), or even that the use of the schema is.

CR7-1 Resolution: rejected 

It is good practise to provide the XML declaration (even though it is
not mandatory). Providing the schemaLocation allows documents to be
validated automatically by various tools, although as you correctly
point out neither the attribute nor schema are mandatory.

Received on Wednesday, 19 November 2003 14:33:22 UTC