Re: [xml-dev] YPath, ZPath?
Thank you, Dana and Liam.
Does JSONiq support navigation axes apart from the child axis?
Concerning XQuery 3.1, my reading of the spec is that support for JSON navigation (the lookup operator) is restricted to the child axis.
My feeling is that support for other navigation axes besides the child axis is an essential feature of XPath.
With kind regards,
Hans-Jürgen
daniela florescu <[email protected]> schrieb am 20:54 Sonntag, 10.April 2016:
JSONiq had relatively sophisticated path expressions sublanguage, but designed specially for JSON.
Not all the “tree” structures are alike.
As for path expressions, during the 1990ies there was SO much work on that…..interested
parties should go back in time and read the literature.
HTH,
Dana
On Apr 10, 2016, at 11:45 AM, Hans-Juergen Rennau <[email protected]> wrote:Dear colleagues,the navigation model of XPath - navigation viewed as a sequence of steps, a step viewed as a combination of navigation axis, node test and optional predicates - enables the expression of item selection in a clear, concise and very readable way. But I do not think that the basic principles of the navigation model depend on XML trees, rather, that variations of the XPath model could be designed for other kinds of tree-structured information.Yet the only attempt to do so which I am aware of is JSONPath.I would be interested in learning about other approaches to apply XPath-like navigation to non-XML structures - can you help me discover them?And do you have thoughts about why one should not - or should - attempt such approaches?With kind regards,Hans-Juergen