Re: Namelist continued
Jon Kerny <[email protected]> Thu, 5 May 2016 21:32:47 +0200
| Newsgroups | gmane.comp.web.voice |
|---|---|
| Message-ID | <CAC5YMgHuDR=RaGo0_T7UEDwqrsZUg1uhRou8EWkVa_DaCULX=A@mail.gmail.com> |
--001a11408e9c36dde705321d68a4 Content-Type: text/plain; charset=UTF-8 Hi, I'm making the final fixes to my scxml interpreter. to make it compliant with the testcase suite. Currently there is only four testcases that fail for xpath, 241, 244, 240 and 354. (240, and 354 uses the strange data/data/data syntax) 241 uses $var1 in namelist and of invoke and tries to match to var1 in invoked machine. So from your comments earlier I think that 241 and 244 shall fail for Xpath? Thanks again for you great job, and your patient replies. /Jon On Sat, Sep 26, 2015 at 6:16 PM, Jon Kerny <[email protected]> wrote: > Hi, > > thanks for the clarification. I think that part of my confusion came from > that it wasn't useful in the xpath model and thus it didn't make sense to > me, and I felt that there was something I didn't understand. > > Thanks. > > /Jon > > On Sat, Sep 26, 2015 at 5:58 PM, Jim Barnett <[email protected]> wrote: > >> One further thought on the XPath data model and namelist. The XPath >> data model _could_ be modified to say "for the purposes of passing a >> namelist into invoke, the namelist attribute '$foo' shall be considered to >> match <data id="foo"/>. We didn't do that, because we didn't expect >> 'namelist' to be useful everywhere. However, the XPath data mode is not >> part of the final specification, and is thus not a 'standard' at all, so >> people working with it have some flexibility. >> >> - Jim >> >> On 9/26/2015 9:12 AM, Jon Kerny wrote: >> >>> HI, >>> >>> I saw that there previously has been some discussions about the >>> namelist, and that at least in some parts my questions has been adressed. >>> But I feel that this is quite complicated. >>> >>> In my understanding, namelist is a shorthand for param, but this name >>> thing makes it more complicated than param where name is set explicitly in >>> code. >>> >>> >>> Here are some examples I'd like to get comments on: >>> >>> What would be the names in an Xpath scxml if the following location >>> expressions was used in a namelist? >>> >>> $var1 >>> $var1/children >>> $var1/children[last()] >>> ancestor::$var1/children[last()]" >>> >>> If the target of the invoke/send is an ecmascript scxml with the var1 as >>> a top most id what would the result be? >>> >>> If it instead is a xpath scxml what would be the result? >>> >>> And in the opposite direction, what would the names of an ecmascript >>> datamodel be for the following location expressions in namelist? >>> var1 >>> var1.children >>> var1.children.slice(-1)[0] >>> (I don't know how to write something similar to ancestor) >>> >>> And what would happen if the target of the invoke/send is an ecmascript >>> scxml with the var1 as a top most id what would the result be? >>> >>> If it instead is a xpath scxml what would be the result? >>> >>> Best regards, >>> >>> Jon >>> >>> >>> >> >> > --001a11408e9c36dde705321d68a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi,<div><br></div><div>I'm making the final fixes to m= y scxml interpreter. to make it compliant with the testcase suite. Currentl= y there is only four testcases that fail for xpath, 241, 244, 240 and 354. = (240, and 354 uses the strange data/data/data syntax)</div><div><br></div><= div>241 uses $var1 in namelist and of invoke and tries to match to var1 in = invoked machine. So from your comments earlier I think that 241 and 244 sha= ll fail for Xpath?</div><div><br></div><div>Thanks again for you great job,= and your patient replies.</div><div class=3D"gmail_extra"><br></div><div c= lass=3D"gmail_extra">/Jon</div><div class=3D"gmail_extra"><br><div class=3D= "gmail_quote">On Sat, Sep 26, 2015 at 6:16 PM, Jon Kerny <span dir=3D"ltr">= <<a href=3D"mailto:[email protected]" target=3D"_blank">jon.kerny@gmai= l.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m= argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l= tr">Hi,=C2=A0<div><br></div><div>thanks for the clarification. I think that= part of my confusion came from that it wasn't useful in the xpath mode= l and thus it didn't make sense to me, and I felt that there was someth= ing I didn't understand.</div><div><br></div><div>Thanks.</div><span cl= ass=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>/Jon</div></font= ></span></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_e= xtra"><br><div class=3D"gmail_quote">On Sat, Sep 26, 2015 at 5:58 PM, Jim B= arnett <span dir=3D"ltr"><<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>></span> wrote:<br><blockquote class= =3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd= ing-left:1ex">One further thought on the XPath data model and namelist.=C2= =A0 =C2=A0The XPath data model=C2=A0 _could_ be modified to say "for t= he purposes of passing a namelist into invoke, the namelist attribute '= $foo' shall be considered to match <data id=3D"foo"/>.= =C2=A0 =C2=A0 We didn't do that, because we didn't expect 'name= list' to be useful everywhere. However, the XPath data mode is not part= of the final specification, and is thus not a 'standard' at all, s= o people working with it have some flexibility.<span><br> <br> - Jim<br> <br> On 9/26/2015 9:12 AM, Jon Kerny wrote:<br> </span><div><div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8= ex;border-left:1px #ccc solid;padding-left:1ex"> HI,<br> <br> I saw that there previously has been some discussions about the namelist, a= nd that at least in some parts my questions has been adressed. But I feel t= hat this is quite complicated.<br> <br> In my understanding, namelist is a shorthand for param, but this name thing= makes it more complicated than param where name is set explicitly in code.= <br> <br> <br> Here are some examples I'd like to get comments on:<br> <br> What would be the names in an Xpath scxml if the following location express= ions was used in a namelist?<br> <br> $var1<br> $var1/children<br> $var1/children[last()]<br> ancestor::$var1/children[last()]"<br> <br> If the target of the invoke/send is an ecmascript scxml with the var1 as a = top most id what would the result be?<br> <br> If it instead is a xpath scxml what would be the result?<br> <br> And in the opposite direction, what would the names of an ecmascript datamo= del be for the following location expressions in namelist?<br> var1<br> var1.children<br> var1.children.slice(-1)[0]<br> (I don't know how to write something similar to ancestor)<br> <br> And what would happen if the target of the invoke/send is an ecmascript scx= ml with the var1 as a top most id what would the result be?<br> <br> If it instead is a xpath scxml what would be the result?<br> <br> Best regards,<br> <br> Jon<br> <br> <br> </blockquote> <br> <br> </div></div></blockquote></div><br></div> </div></div></blockquote></div><br></div></div> --001a11408e9c36dde705321d68a4--