Re: [basex-talk] Lookups and arrows

2016-01-10 Thread Joe Wicentowski
Thanks very much for this info, Christian! I'll pass your observations on to the eXist team. Joe On Sun, Jan 10, 2016 at 3:50 AM, Christian Grün wrote: > Hi Tim, hi Joe, > > The query works if you use parentheses around the arrow operands: > >

Re: [basex-talk] Lookups and arrows

2016-01-10 Thread Christian Grün
Hi Tim, hi Joe, The query works if you use parentheses around the arrow operands: (json-doc("http://lae.princeton.edu/catalog/0bp35.jsonld;)("@context") => json-doc())("@context") This is in compliance with the XQuery 3.1 spec [1]. Out of interest, I spent some time and looked up the W3

Re: [basex-talk] Lookups and arrows

2016-01-09 Thread Joe Wicentowski
Hi Tim, For your first question, I think your example falls into what the spec calls "funky looking" keys.  See the 3rd bullet point example under http://www.w3.org/TR/xquery-31/#id-lookup: > funky / an appropriate lookup for a map with rather odd conventions for keys. In other words, I think

Re: [basex-talk] Lookups and arrows

2016-01-09 Thread Tim Thompson
Thanks, Joe! I guess I'd glossed over the "funky" example ;-) Regarding the arrow operator, I was wondering whether something like this was possible: json-doc(" http://lae.princeton.edu/catalog/0bp35.jsonld;)("@context") => json-doc()("@context") which throws an error: [XPST0003] Unexpected end

Re: [basex-talk] Lookups and arrows

2016-01-09 Thread Joe Wicentowski
Hi Tim, "Funky" made me chuckle too! I tested your code with the closest thing at hand - a local build of branch of Wolfgang Meier's eXist repo with support for the arrow operator (https://github.com/wolfgangmm/exist/tree/feature/arrowop) - and your code worked fine there. So my hunch is that