Re: [basex-talk] from xquery:parse to data paths ...

Hi Hans-Jürgen, One reason why I would favor to have an XQuery implementation first is because it would allow us to define the semantics behind this function. There are currently lots of questions that are unclear to me, so it’s mostly conceptual questions that would need to be solved before such

Re: [basex-talk] from xquery:parse to data paths ...

Hi Hans-Jürgen, Sounds like an interesting idea. As the output of xquery:parse is XML, the xquery:data-paths function could probably be written in XQuery itself? Best, Christian _ On Sat, Feb 20, 2016 at 12:24 AM, Hans-Juergen Rennau wrote: >

[basex-talk] from xquery:parse to data paths ...

Dear BaseX team, perhaps I hear an opinion about the following idea. (1) The function xquery:parse is already immensely useful as it allows to *validate* XPath expressions, as for example used in configuration data. (A practical example: the XPath expressions used in JMeter [1] test plans in

Re: [basex-talk] Automated Docker Build: basex/basexhttp

> The problem was that I wanted to add files to the /webapp directory, but > once the Dockerfile defines it as volume you can't modify it as part of > the container definition, you can only mount to it from outside. > > My general approach is to have two images, one without the volumes, for > use

Re: [basex-talk] Automated Docker Build: basex/basexhttp

The problem was that I wanted to add files to the /webapp directory, but once the Dockerfile defines it as volume you can't modify it as part of the container definition, you can only mount to it from outside. My general approach is to have two images, one without the volumes, for use in defining

Re: [basex-talk] Automated Docker Build: basex/basexhttp

Hi Eliot, > Looks like this version addresses the issue I had > (creating volumes in the base container made it impossible to add repos or > webapps in using Dockerfiles). that's also one of the issues the earlier Dockerfile of Dirk and Michael had -- and I also had issues with that when I

Re: [basex-talk] Automated Docker Build: basex/basexhttp

Cool--I'll try it as soon as I can. I have my own BaseX-based container with a custom Web app working now, but based on my own small mod of an earlier Dockerfile. Looks like this version addresses the issue I had (creating volumes in the base container made it impossible to add repos or webapps in

[basex-talk] Automated Docker Build: basex/basexhttp

Dear BaseX community, over the last weeks, interest in Docker utilization with BaseX hevily increased, and several images have been proposed. I've already made some experience running a BaseX pet project in BaseX for about a year now, and together with the BaseX core team created an image based

Re: [basex-talk] Getting element counts in the visualizations?

> Christian Grün : >> Could it be something to do with the namespacing in the document? > If your document has namespaces, you can use a wildcard for your prefix… > • count(//*:A/*), count(//*:B/*) > • for $c in /*:Top/* return count($c/*) > or define the prefix

Re: [basex-talk] Sending Bytes, Not Strings, To BaseX Using the Ruby Client

I suspect that using the REST API directly is the answer, although if I understand the Ruby client code, it's using direct socket connections, which would be more efficient. Not a critical issue at the moment but something I need to understand more fully before too long. Cheers, E. Eliot

Re: [basex-talk] Sending Bytes, Not Strings, To BaseX Using the Ruby Client

> Hmm. Is there a way to send other encodings to the server via the remote > API? A difficult one for me to answer, because I have never worked with Ruby before… Maybe there are some other users on the list who can reply on this? > I'm on my way to Japan for a workshop where we'll be using my

Re: [basex-talk] Sending Bytes, Not Strings, To BaseX Using the Ruby Client

Hmm. Is there a way to send other encodings to the server via the remote API? I'm on my way to Japan for a workshop where we'll be using my system and Japanese-language documents are more efficiently stored in UTF-16 so my expectation is that users will either already have documents in that

Re: [basex-talk] Setting base-dir for xquery:eval

Wow. You guys don't stop to amaze. Chris's suggestion would've worked. Andy's suggestion was what I actually had in mind when I wrote the post. So he reads my mind, Chris adds a new feature and all that before the clock of 10 less than 12 hours after the post. And that, probably, with a good

Re: [basex-talk] Setting base-dir for xquery:eval

> a base-uri set. I wonder if there is a case for adding base-uri to the > xquery:eval options map to handle this in a cleaner way? …now there is [1,2]. New features in the documentation will be marked with 8.5, but they will already available in the snapshots and patch versions. [1]

Re: [basex-talk] Getting element counts in the visualizations?

> Could it be something to do with the namespacing in the document? If your document has namespaces, you can use a wildcard for your prefix… • count(//*:A/*), count(//*:B/*) • for $c in /*:Top/* return count($c/*) or define the prefix in the query prolog: declare namespace abc = 'http:...';