Re: [xml-dev] XPath and a continuous, uniform information space
Oh Michael, this is music in my ears!
As I love the XPath syntax and am dismayed at the way how JSONiq replaces XPath by FLWOR when it comes to dealing with JSON - that is, replaces path syntax by SQL-like constructs.
Syntax is very important.
Hans-Juergen
Von: Michael Kay <[email protected]>
An: "Costello, Roger L." <[email protected]>
CC: "[email protected]" <[email protected]>
Gesendet: 11:13 Samstag, 17.August 2013
Betreff: Re: [xml-dev] XPath and a continuous, uniform information space
As I love the XPath syntax and am dismayed at the way how JSONiq replaces XPath by FLWOR when it comes to dealing with JSON - that is, replaces path syntax by SQL-like constructs.
Syntax is very important.
Hans-Juergen
Von: Michael Kay <[email protected]>
An: "Costello, Roger L." <[email protected]>
CC: "[email protected]" <[email protected]>
Gesendet: 11:13 Samstag, 17.August 2013
Betreff: Re: [xml-dev] XPath and a continuous, uniform information space
What is the semantic difference between an axis and a function call
It's largely syntax.
Don't underestimate the importance of
syntax!
There's a lot of difference in usability between
$customer/order[paid=false()]/product/price
and
for $c in $customer for $o in orders($c) for $p in products($o) where not(paid($o)) return price($p)
Michael Kay