W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2006

RE: [scxml] else, elseif syntax

From: Barnett, James <James.Barnett@aspect.com>
Date: Wed, 8 Nov 2006 17:16:40 -0500
Message-ID: <57686697B4E28949A90094A6469165C7011AC5DE@ASP1EXCH1.aspect.com>
To: "Nestor Urquiza" <nestoru@yahoo.com>, <www-voice@w3.org>

Nestor,
  The current syntax of <else> and <elsif> was chosen for compatibility
with VoiceXML and CCXML, both of which lack closing tags.  However, you
make a good point that this is not pure XML, and we will revisit this
issue once we complete the draft that we are currently working on.
We'll post another response when we have had a chance to investigate the
issue. 

- Jim

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On
Behalf Of Nestor Urquiza
Sent: Monday, November 06, 2006 8:53 AM
To: www-voice@w3.org
Subject: [scxml] else, elseif syntax


Hi guys,

I have been working with scxml for a while now and I
have noticed a major debugging problem a developer
might find if <else>, <elseif> tags are empty as
proposed.

IMHO I would use openning and closing tags for those
elements (<lese></else>) since it is:

1)More pure XML approach since those tags are not
really empty (They hold nodes expressing assignments
for example). Empty tags like <br/> in XHTML make
sense because they are not containers but <else> is a
container in SCXML.

2)It allows a developer to see with an XML editor
better the code since expanding and collapsing the
<else> node will really mean showing and hiding the
corresponding code.

Thanks,

-Nestor



 
________________________________________________________________________
____________
Sponsored Link

Try Netflix today! With plans starting at only $5.99 a month what are
you waiting for?
http://www.netflix.com/Signup?mqso=80010030
Received on Wednesday, 8 November 2006 22:16:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 November 2006 22:16:51 GMT