- BaseX-Talk - mailman.uni-konstanz.de

Specific elements as function input types
by Kristian Kankainen 20 Apr '15

20 Apr '15

Hello! I wonder why I get a syntax error in BaseX for the following code. Is it really not possible to specify this fine granularity for function input types? <code> declare variable $local:ns := "somenamespace declare function local:afunction( $input as element( QName( $local:ns, "elementname" ) ) ) { <function-body /> }; </code> I get error XPST0003 Expecting ')' found '('. Best regards Kristian Kankainen

2 1

Updating xml takes more than usual
by George Karakatsiotis 20 Apr '15

20 Apr '15

Hi all, I have deployed basex.war (8.0.3) in a resin web server (with default options) and sometimes updating takes longer than usual. Here is a snippet from .logs: 1 resource(s) replaced in 2323.41 ms. 423273.55 ms My understanding is that updating takes 2323.41 ms, but overall the whole process takes 423273.55 ms. Do you have any suggestion what could be the cause of these delays? I should note that this happens while processing a big batch of documents in parallel (each HTTP request is in a different thread). Thank you for your time, GK

2 1

Working With Maps Using FLOWR Expressions?
by Eliot Kimber 19 Apr '15

19 Apr '15

I think I'm missing something fundamental but I haven't been able to find a relevant example of what I'm trying to do. I suspect I'm being derailed by procedural brain damage. I have a function that takes as input a map and will return a new map reflecting updates applied to input map. The business logic of this function is to iterate over some sequence and add or update map items as needed, e.g.: let $map := map { } for $key in ('A', 'B') return map:put($map, 'A', 'somevalue') The problem is that each interation of the for loop returns a new map. In the context of a FLOWR expression I'm not seeing how to effectively update the same map instance. What fundamental aspect of map manipulation am I missing? Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

3 3

How To Reflect XML Source in HTML Output?
by Eliot Kimber 18 Apr '15

18 Apr '15

I'm use the RESTXQ stuff (very nice) to build a little DITA link management application. In the service of this I need to sometimes show the raw XML source of the docs in the repo. I looked at the DBA Web app and it looks like it's using some Javascript for this and I didn't see any obvious solution in the various BaseX packages, but I could have missed something. I hacked a quick little typeswitch transform just to get something but it doesn't preserve newlines from the source XML (but I notice the DBA Web app does, so they must be preserved under the covers). Is there a built-in way to generate escaped XML for use in e.g., HTML <pre> or is there some silly thing I need to do in my typeswitch to make sure the newlines make it to the HTML result? Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

2 4

URLs for BaseX Documents and resolve-uri()
by Eliot Kimber 17 Apr '15

17 Apr '15

I'm migrating XSLT functions for working with DITA documents to XQuery. As part of this function package I have functions that resolve URI references from one document to another. This involves creating absolute URLs from relative URLs using a document or element as the base URI context. The problem I'm running into is that the URLs used within BaseX are not absolute (that is, they don't start with "/". For example, document-uri(root($node)) returns: dfst^dfst-sample-project^develop/docs/tests/complex_map/complex_map.ditamap not /dfst^dfst-sample-project^develop/docs/tests/complex_map/complex_map.ditama p This causes a problem for resolve-uri(), used like this: resolve-uri($topicResourcePart, base-uri($topicref)) This fails under BaseX: [FORG0002] Base URI is not absolute: "dfst^dfst-sample-project^develo.... These libraries are intended to be generic XQuery so I'm trying to avoid having any BaseX-specific logic in these functions. Is there workaround or other solution to this? Obviously, this way of representing document URIs internally is not something that could be easily changed but it is definitely a problem in terms of the expectations of URI handling by built-in XQuery functions. Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

2 3

Re: [basex-talk] URLs for BaseX Documents and resolve-uri()
by Eliot Kimber 17 Apr '15

17 Apr '15

Related question: is there a preferred way to determine from within an XQuery function that the current XQuery engine is BaseX? I know I could look to see if a particular BaseX-specific function exists but I was looking for something either more obvious or more general from an XQuery standpoint. Cheers, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 4/17/15, 10:51 AM, "Eliot Kimber" <ekimber(a)contrext.com> wrote: >I'm migrating XSLT functions for working with DITA documents to XQuery. As >part of this function package I have functions that resolve URI references >from one document to another. This involves creating absolute URLs from >relative URLs using a document or element as the base URI context. > >The problem I'm running into is that the URLs used within BaseX are not >absolute (that is, they don't start with "/". > >For example, document-uri(root($node)) returns: > >dfst^dfst-sample-project^develop/docs/tests/complex_map/complex_map.ditama >p > > >not > >/dfst^dfst-sample-project^develop/docs/tests/complex_map/complex_map.ditam >a >p > >This causes a problem for resolve-uri(), used like this: > >resolve-uri($topicResourcePart, base-uri($topicref)) > > >This fails under BaseX: > >[FORG0002] Base URI is not absolute: "dfst^dfst-sample-project^develo.... > > >These libraries are intended to be generic XQuery so I'm trying to avoid >having any BaseX-specific logic in these functions. > >Is there workaround or other solution to this? > >Obviously, this way of representing document URIs internally is not >something that could be easily changed but it is definitely a problem in >terms of the expectations of URI handling by built-in XQuery functions. > >Thanks, > >Eliot >————— >Eliot Kimber, Owner >Contrext, LLC >http://contrext.com > > > >

1 0

"Input is too large for a single database" error
by Huib Verweij 17 Apr '15

17 Apr '15

Hi Christian, congrats on the new release. I’ve downloaded it yesterday and while importing new data BaseX ran into a “Input is too large for a single database” error. It has been reported before and you mentioned Basex will be using 2^63 bits instead of 2^31 bits for counting nodes. Is there a branch that I could check out that already supports importing up to 2^63 nodes? The “node-counter” branch perhaps? For now I’ll just split the data and see if that works. Hartelijke groet, Huib Verweij

2 1

Is -L command-line option still supported?
by Amanda Galtman 16 Apr '15

16 Apr '15

Hi, The page http://docs.basex.org/wiki/Command-Line_Options lists an option "-L". However, it doesn't seem to work in version 8 and the "-h" output no longer mentions it. Was the -L option removed, perhaps because of changes in the serialization in version 8? This isn't holding up my work. I just came across it and wondered if the documentation needs an update. Cheers, Amanda

2 2

Released: BaseX 8.1.1. Upcoming: Finger trees
by Christian Grün 16 Apr '15

16 Apr '15

Hi all, BaseX 8.1.1 has just been released [1]. It mostly contains minor bug fixes, all of them uncritical. Since recently, our XQuery arrays are based on a Finger tree implementation [2]. This fancy data structure provides much better performance for insert and delete operations. With BaseX 8.2, this data structure is now used for arbitrary sequences. If you want to belong to our early testers, please check out the latest snapshot [3]. We are looking for your feedback! Have fun, Christian [1] http://basex.org/download [2] https://en.wikipedia.org/wiki/Finger_tree [3] http://files.basex.org/releases/latest

1 0

Way to React To Updates Using XQuery?
by Eliot Kimber 16 Apr '15

16 Apr '15

As part of my DITA link management system, I need to create and update various indexes and data structures whenever specific documents are added or updated. I was looking for some sort of trigger or event handler by which I would register an XQuery function and the system would call it on add, update, or delete, but I didn't see anything like that in the docs. Since my updates are, in my case, being driven by git commit hooks I could have the commit hook call a function following updates and pass that function the list of added, updated, and deleted docs. But that would not support the case where documents were loaded by some other route. Is such a mechanism available? Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

2 2