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

Comments on CCXML Working Draft 19 January 2007

From: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>
Date: Tue, 6 Feb 2007 18:08:51 +0100
Message-ID: <015d01c74a11$795d8520$1301a8c0@envox.local.hr>
To: <www-voice@w3.org>

6.2.7: <fetch>

Current text:
"The event is one of fetch.done, which indicates that the identified content 
was fetched successfully, or error.fetch, indicative of a failure to fetch 
the requested content."

Proposed text:
"The event is one of fetch.done, which indicates that the identified content 
was fetched successfully and in case of CCXML document, XML parsing / 
validation was performed, or error.fetch, indicative of a failure to fetch 
the requested content. "

It is not quite clear from the description of <fetch> what the CCXML 
interpreter should perform before its sends the fetch.done event.

6.2.2.2: <meta> Attribute Details

Current text:
" Either the name or the http-equiv attribute has to be specified. If 
neither of them is specified, or if both are specified, an error.fetch event 
must be thrown."

Proposed text:
""

I think that this part of specification is in contradiction with section 
9.5.2: "Document Initialization Errors", which states: "Errors that occur 
during documentation initialization (elements that occur in the CCXML 
document before <eventprocessor>) occur outside of CCXML's event handling 
mechanism. These errors MUST cause the CCXML thread of execution to 
terminate and notify the platform of the document error."

The element <meta> occurs in the CCXML document before <eventprocessor>, so 
it should be handled according to section 9.5.2. 
Received on Tuesday, 6 February 2007 17:09:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 February 2007 17:09:02 GMT