Re: SCXML Test 354 uses datamodel-specific <content>?

Either conf:content or using 123 (unquoted) in both content and eventDataVal would fix this for me, and I think not break it for anyone else. (Though conf:content requires a new XSLT transform, it feels more pure to me, able to work with arbitrary data models and content interpretations.)
--
(-, /\ \/ / /\/

On Jun 30, 2014, at 04:22 PM, Jim Barnett <1jhbarnett@gmail.com> wrote:

Test354 is written against the scxml event i/o processor, so it is mandatory.  We can modify it to add conf:content or, as I suggested before, we can modify the test not to quote 123 in eventDataVal,  so you would get both values unquoted.  Does that work?   

- Jim
On 6/30/2014 6:15 PM, Gavin Kistner wrote:
On Jun 30, 2014, at 03:43 PM, David Junger <tffy@free.fr> wrote:

Le 30 jun 2014 à 17:47, Jim Barnett <1jhbarnett@gmail.com        > a écrit :
 
        > I'm not sure I follow. B.2.8.1 is part of the section on the ECMA Script data model. Nothing their applies to Gavin's datamodel.
 
 Oh, right. Sorry. So, that means Gavin shouldn't try to pass test 354. There, problem solved.
 
 
:D
If test 354 were marked as non-mandatory, I'd be happy to just skip it. 

Alternatively, I feel that this could be solved by not having
<content>123</content>
in the .txml, but instead something like:
<conf:content>123</content>.

Along with the existing conf:eventdataVal="123" then I could simply quote both values in my XSLT equivalent, and both ECMAScript and Lua data models would be happy.

-- 
Jim Barnett
Genesys