<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Lucky you, I would say.<div class=""><br class=""></div><div class="">Because for the people who need to use XQuery and JSON/Javascript in the same time</div><div class="">those inconsistencies will be such a constant source of frustration and a constant source of errors …. </div><div class=""><br class=""></div><div class="">Consequences:</div><div class="">- chances of XQuery (or XQuery ideas) being used by the JSON community go down significantly</div><div class="">- billions of dollars due to loss of productivity overall</div><div class="">- probably very tight restriction of the user population of XQuery.</div><div class=""><br class=""></div><div class="">Just saying… if this doesn’t bother you, consider yourself lucky.</div><div class=""><br class=""></div><div class="">Best regards</div><div class="">Dana</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 26, 2015, at 10:32 AM, W.S. Hager <<a href="mailto:wshager@gmail.com" class="">wshager@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">That should provide some positive perspectives for integrating with the web... wait, did I just get off-topic? Oops? No. I write a great deal of javascript, and this is actually why I would like my wishlist to be considered. Functions like array:index-of and array:for-each (called map in many more languages) feel off to me in xquery because of their resemblance to javascript, but with slightly different semantics. Since this pertains to "imperative" constructs, you may consider converging more towards javascript, which was the reason for the 3.1 spec in the first place, if I'm not mistaken. As an added advantage it would less surprise programmers coming from javascript, I think.<br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2015-06-26 19:14 GMT+02:00 daniela florescu <span dir="ltr" class=""><<a href="mailto:dflorescu@me.com" target="_blank" class="">dflorescu@me.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">><br class="">
><br class="">
> Which was of course a major failing of the original Xquery proposals.<br class="">
> It was staggering that an W3C XML query language should _not_ start from<br class="">
> that base. Fortunately It was redrafted to sit over Xpath.<br class="">
> XQuery 1 was basically (and should have been defined as) a non-xml<br class="">
> syntax for a simplified subset of XSLT.<br class="">
<br class="">
</span>BTW, David… it’s funny after 15 years… -)<br class="">
<br class="">
If the XSLT WG wanted a simple non-xml syntax for XSLT, they should have done it themselves…..why would this<br class="">
have been OUR problem !?<br class="">
<br class="">
What the XML QUERY Working Group wanted something COMPLETELY different, aka, a QUERY LANGUAGE,<br class="">
out of which XSLT isn’t one …. that’s all.<br class="">
<br class="">
Fun to see that those arguments don’t die even after 15 years :-)<br class="">
<br class="">
I remember having those discussion on-line and off-line with James Clark… like a decade and a half ago !?? :-)<br class="">
<br class="">
Actually, the first running implementation of the integration of XQuery and XPath parser was written by me and James<br class="">
(both bitching about the “features” in other’s side..:-)<br class="">
<br class="">
But overall, I think XSLT and XQuery ended up integrated pretty nicely, so it was worth the effort.<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
Best regards<br class="">
Dana<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
<a href="mailto:talk@x-query.com" class="">talk@x-query.com</a><br class="">
<a href="http://x-query.com/mailman/listinfo/talk" rel="noreferrer" target="_blank" class="">http://x-query.com/mailman/listinfo/talk</a></div></div></blockquote></div><br class=""><br clear="all" class=""><br class="">-- <br class=""><div class="gmail_signature"><div class=""><p class="">
W.S. Hager<br class="">
Lagua Web Solutions<br class="">
<a href="http://lagua.nl/" target="_blank" class="">http://lagua.nl</a><br class=""></p></div></div>
</div>
_______________________________________________<br class=""><a href="mailto:talk@x-query.com" class="">talk@x-query.com</a><br class="">http://x-query.com/mailman/listinfo/talk</div></blockquote></div><br class=""></div></body></html>