W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2007

Re: Comments on CCXML Working Draft 19 January 2007

From: Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>
Date: Fri, 18 May 2007 17:57:29 +0200
Message-ID: <007001c79965$40670b30$1301a8c0@envox.local.hr>
To: "RJ Auburn" <rj@voxeo.com>
Cc: <www-voice@w3.org>, "W3C Voice Browser Working Group" <w3c-voice-wg@w3.org>

RJ and the working group,

Thanks for reviewing and answering my comments.

Regarding comments about <fetch> element, your answer
is completely acceptable to me.

Regarding <meta> element I still have some questions and doubts.

You said:
"One clarification to your comment:  The detection of the error
condition related to invalid use of attributes is something that
would happen during XML parsing and is therefore handled as described
in section 9.5.1 (fetching and compilation errors) rather than 9.5.2
(Document Initialization Errors)."

1)
If the statement: "the detection of the error condition related to invalid 
use
of attributes is something that would happen during XML parsing"
applies to the whole CCXML specification, I think it is very important
and it should be a part of the specification.

If I understand it well, it applies to the cases when exactly one of
several attributes must be present (like in <meta>, <dialogstarted>, <send>,
<script> and <move>) and possibly to some other cases. I think the 
specification
should explicitly state that such cases must be handled during XML parsing.

2)
The specification usually states that in such cases "an error.fetch must be 
thrown".
I think this is not good enough, because according to 9.5.1, there are three 
cases,
depending on how the fetching has been initiated:
 a) by <createccxml> --> throw error.createccxml to the parent session
 b) by <fetch> --> throw error.fetch to the same session
 c) by an incoming call or HTTP --> terminate the session

So I think that specification should state something like:
"an error.fetch or error.createccxml must be thrown, or the session
must be terminated (see 9.5.1)".

3)
This also applies to <meta>, so my original proposal was not correct;
the description of attributes "content" and "http-equiv" should contain
the phrase "an error.fetch or error.createccxml must be thrown,
or the session must be terminated (see 9.5.1)".

4)
In description of the <script> element, "src" attribute, the specification 
states:
"Note that the value of the src attribute must not be an ECMAScript 
expression
in order to allow it to be resolved at compile-time. If the script cannot be 
fetched
the implementation must throw an error.fetch event."

I think this needs clarification. Why the src attribute must be resolved at 
the
compile-time? Does it mean that all <script>s with the src attribute
should be fetched at compile time? If this is the case, I think the 
specification should
explicitly state it.

Should the statement "If the script cannot be fetched the implementation 
must throw
an error.fetch event" be also treated (and changed to) something like:
"If the script cannot be fetched an error.fetch or error.createccxml must be 
thrown,
or the session must be terminated (see 9.5.1)." ?

Best regards,
Hrvoje Nezic
Received on Friday, 18 May 2007 15:58:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 May 2007 15:58:10 GMT