Re: [basex-talk] Anticipating more complex data to follow

2022-03-22 Thread Patrick Durusau
Thanks! Appreciate the quick response! Patrick On 3/22/22 17:08, Christian Grün wrote: I would write it as follows: let $string := '{ "parties": [ { "id": 0, "role": "CN", "name": "name1" }, { "id": 1, "role": "SH", "name": "name2" } ] }' let $data := json:parse($string) return $data/js

Re: [basex-talk] Anticipating more complex data to follow

2022-03-22 Thread Christian Grün
I would write it as follows: let $string := '{ "parties": [ { "id": 0, "role": "CN", "name": "name1" }, { "id": 1, "role": "SH", "name": "name2" } ] }' let $data := json:parse($string) return $data/json/parties[_[name = 'name1'][role = 'CN']] Martin provided the solution for the XQuery map/ar

Re: [basex-talk] Anticipating more complex data to follow

2022-03-22 Thread Martin Honnen
On 22.03.2022 21:48, Patrick Durusau wrote: I'm anticipating incorporation of JSON sources with anonymous nodes and if they all appear with the element name _, how do I distinguish one from another, structurally speaking? Are you not able to use XPath/XQuery 3.1 map/array lookup operators di

Re: [basex-talk] Anticipating more complex data to follow

2022-03-22 Thread Patrick Durusau
I'm anticipating incorporation of JSON sources with anonymous nodes and if they all appear with the element name _, how do I distinguish one from another, structurally speaking? MarkLogic offers some specific workarounds but those are unique (I suspect) to MarkLogic. The MarkLogic post has a

Re: [basex-talk] Anticipating more complex data to follow

2022-03-22 Thread Christian Grün
Hi Patrick, Which problem would you like to solve exactly? Maybe I should read the MarkLogic article in more detail, though. Best, Christian On Tue, Mar 22, 2022 at 12:15 AM Patrick Durusau wrote: > > Greetings! > > While working on some large but fairly simple data, I encountered BaseX > usin

[basex-talk] Anticipating more complex data to follow

2022-03-21 Thread Patrick Durusau
Greetings! While working on some large but fairly simple data, I encountered BaseX using the underscore "_" as an element name when importing JSON. Not leaving well enough alone for present purposes, I encountered this post about anonymous objects in MarkLogic and how they resolve the problem