Re: Namelist continued
Jim Barnett <[email protected]> Thu, 5 May 2016 13:12:33 -0700
| Newsgroups | gmane.comp.web.voice |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail-087AB06D-9989-4E66-AC17-5AE2F7C61847 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Given the unfinished state of the XPath data model, I think you are right. I= f we ever decide to finish it, we might add language to the effect that '$va= r' should be considered to match 'var' in the XPath data model. =20 As it is, namelist is not useful with XPath. If you can find a way to make i= t useful in your implementation, feel free to go ahead even if you deviate f= rom the language in the spec. As it stands, the XPath data model is not a st= andard.=20 Jim Barnett Genesys > On May 5, 2016, at 12:32 PM, Jon Kerny <[email protected]> wrote: >=20 > Hi, >=20 > I'm making the final fixes to my scxml interpreter. to make it compliant w= ith 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) >=20 > 241 uses $var1 in namelist and of invoke and tries to match to var1 in inv= oked machine. So from your comments earlier I think that 241 and 244 shall f= ail for Xpath? >=20 > Thanks again for you great job, and your patient replies. >=20 > /Jon >=20 >> On Sat, Sep 26, 2015 at 6:16 PM, Jon Kerny <[email protected]> wrote: >> Hi,=20 >>=20 >> 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 m= e, and I felt that there was something I didn't understand. >>=20 >> Thanks. >>=20 >> /Jon >>=20 >>> On Sat, Sep 26, 2015 at 5:58 PM, Jim Barnett <[email protected]> wrot= e: >>> One further thought on the XPath data model and namelist. The XPath da= ta model _could_ be modified to say "for the purposes of passing a namelist= into invoke, the namelist attribute '$foo' shall be considered to match <da= ta id=3D"foo"/>. We didn't do that, because we didn't expect 'namelist' t= o be useful everywhere. However, the XPath data mode is not part of the fina= l specification, and is thus not a 'standard' at all, so people working with= it have some flexibility. >>>=20 >>> - Jim >>>=20 >>>> On 9/26/2015 9:12 AM, Jon Kerny wrote: >>>=20 >>>> HI, >>>>=20 >>>> I saw that there previously has been some discussions about the namelis= t, and that at least in some parts my questions has been adressed. But I fee= l that this is quite complicated. >>>>=20 >>>> In my understanding, namelist is a shorthand for param, but this name t= hing makes it more complicated than param where name is set explicitly in co= de. >>>>=20 >>>>=20 >>>> Here are some examples I'd like to get comments on: >>>>=20 >>>> What would be the names in an Xpath scxml if the following location exp= ressions was used in a namelist? >>>>=20 >>>> $var1 >>>> $var1/children >>>> $var1/children[last()] >>>> ancestor::$var1/children[last()]" >>>>=20 >>>> If the target of the invoke/send is an ecmascript scxml with the var1 a= s a top most id what would the result be? >>>>=20 >>>> If it instead is a xpath scxml what would be the result? >>>>=20 >>>> And in the opposite direction, what would the names of an ecmascript da= tamodel 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) >>>>=20 >>>> 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? >>>>=20 >>>> If it instead is a xpath scxml what would be the result? >>>>=20 >>>> Best regards, >>>>=20 >>>> Jon >=20 --Apple-Mail-087AB06D-9989-4E66-AC17-5AE2F7C61847 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto"><div>Given the unfinished state of the XPat= h data model, I think you are right. If we ever decide to finish it, we migh= t add language to the effect that '$var' should be considered to match 'var'= in the XPath data model. </div><div id=3D"AppleMailSignature"><br></d= iv><div id=3D"AppleMailSignature">As it is, namelist is not useful with XPat= h. If you can find a way to make it useful in your implementation, feel free= to go ahead even if you deviate from the language in the spec. As it stands= , the XPath data model is not a standard. </div><div id=3D"AppleMailSig= nature"><br>Jim Barnett<div>Genesys</div></div><div><br>On May 5, 2016, at 1= 2:32 PM, Jon Kerny <<a href=3D"mailto:[email protected]">jon.kerny@gmai= l.com</a>> wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D= "ltr">Hi,<div><br></div><div>I'm making the final fixes to my scxml interpre= ter. to make it compliant with the testcase suite. Currently there is only f= our 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 i= n namelist and of invoke and tries to match to var1 in invoked machine. So f= rom your comments earlier I think that 241 and 244 shall fail for Xpath?</di= v><div><br></div><div>Thanks again for you great job, and your patient repli= es.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">/Jo= n</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:jon.= [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;padding-left:1ex"><div dir=3D"ltr">Hi, <div><br></div><= div>thanks for the clarification. I think that part of my confusion came fro= m that it wasn't useful in the xpath model and thus it didn't make sense to m= e, and I felt that there was something I didn't understand.</div><div><br></= div><div>Thanks.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div><b= r></div><div>/Jon</div></font></span></div><div class=3D"HOEnZb"><div class=3D= "h5"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Sep 2= 6, 2015 at 5:58 PM, Jim Barnett <span dir=3D"ltr"><<a href=3D"mailto:1jhb= [email protected]" target=3D"_blank">[email protected]</a>></span> wrot= e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le= ft:1px #ccc solid;padding-left:1ex">One further thought on the XPath data mo= del and namelist. The XPath data model _could_ be modified= to say "for the purposes of passing a namelist into invoke, the namelist at= tribute '$foo' shall be considered to match <data id=3D"foo"/>. &= nbsp; We didn't do that, because we didn't expect 'namelist' to be useful ev= erywhere. However, the XPath data mode is not part of the final specificatio= n, and is thus not a 'standard' at all, so people working with it have some f= lexibility.<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 .8e= x;border-left:1px #ccc solid;padding-left:1ex"> HI,<br> <br> I saw that there previously has been some discussions about the namelist, an= d that at least in some parts my questions has been adressed. But I feel tha= t this is quite complicated.<br> <br> In my understanding, namelist is a shorthand for param, but this name thing m= akes 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 expressi= ons 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 t= op 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 datamod= el 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 scxm= l 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> </div></blockquote></body></html>= --Apple-Mail-087AB06D-9989-4E66-AC17-5AE2F7C61847--