BaseX-Talk

basex-talk@mailman.uni-konstanz.de

5251 discussions

Whitespace chopping / option -w
by Hans-Juergen Rennau 27 Feb '18

27 Feb '18

Dear BaseX team, "whitespace chopping" (which happens by default unless command-line option -w is used) does not only remove "whitespace-only" text nodes, but also leading/trainling whitespace in element content, for example: doc.xml:<hello> BaseX is phantastic! </hello> basex -i doc.xml . => <hello>BaseX is phantastic!</hello> While the result is of course true, I regard leading/trailing whitespace in element content as information which has a different "level of significance" than whitespace-only text nodes. In other words: I think it is an important use case that leading/trailing whitespace must be preserved, while the "pretty print whitespace" should be discarded. Did I overlook a way to get rid of whitespace-only text nodes without touching leading/trailing whitespace in element content? If not, it would be wonderful if you added a new option doing just that. With kind regards -Hans-Jürgen

1 0

Update Module question: update:apply
by Bridger Dyson-Smith 26 Feb '18

26 Feb '18

Hi all -- I was working with the update:apply example [1], and it throws an error: [XPTY0004] Cannot convert xs:string to node(): "doc.xml". I'm a little confused by this: if I modify the example, and change the last to `db:add('existing-db', 'doc.xml')` (which is db:add#1, right?), it works fine. However, keeping the local:update and trying to use `db:add#1` generates another error: [XPST0017] db:add(database,input[,path[,options]]): 1 argument supplied, 2-4 expected Would someone be able to shed some light on where this is going wrong? Thanks, Bridger [1] http://docs.basex.org/wiki/Update_Module#update:apply

2 2

Re: [basex-talk] bug in XSLT
by Kristian Kankainen 24 Feb '18

24 Feb '18

2 1

bug in XSLT
by nikos dimitrakas 23 Feb '18

23 Feb '18

There seems to be a problem when using baseX to create html with XSLT. Saxon seems to add a META-tag if the head-tag is present. But it is not <meta/>. It is instead <meta> (without closing tag, which is ok in html) and this causes baseX to give an error: The element type "META" must be terminated by the matching end-tag "</META>". With the newer version of Saxon the error is the same but the case has been changed to <meta> instead of <META>. This can be easily reproduced with the following query: let $s := <xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="html"/> <xsl:template match="/"> <html><head/><body/></html> </xsl:template> </xsl:transform> return xslt:transform(/, $s) In the new XSLT version there is an option to set the output to xhtml and that works, but the html output (which is the only available option in XSLT 1) fails. The generated meta tag seem to be this <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> I have even tried to override this by specifying that meta tag myself with closing tag but that does not work. I even tried setting the attribute include-content-type in the xsl:output, but it had no effect. Setting the output method to xml would work if the html genererated is in fact correct xml (like in the example above). Output metod "text" seems to also behave strangely. Maybe BaseX ignores the output method and tries to treat everything as xml? /nikos

1 0

BaseX not running
by Leo Studer 21 Feb '18

21 Feb '18

Hello I try desperately getting baseX 8.6.7 to run on MacOS X 10.13.3 where I have Java 9 installed Here the error message: BaseX installed with homebrew today: MBP-2015:~ leo$ basexgui WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/usr/local/Cellar/basex/8.6.7/libexec/BaseX.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ and the same error with the Jar file Last login: Wed Feb 21 18:16:27 on ttys001 MBP-2015:~ leo$ java -jar ~/Downloads/BaseX867.jar WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/Users/leo/Downloads/BaseX867.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ Any suggestions? Thanks for caring Always Leo

2 1

inspect:functions does not return updating functions
by Rob Stapper 21 Feb '18

21 Feb '18

Hi Christian, After a period of focussing on Angular I'm back at to BaseX ;-). I found that the inspect:functions function does not return updating functions. Is that by design? I would like to be able to use the inspect:functions function for triggering my update function on the server side, which of course are updating functions TIA for you reply, Cheers, Rob Stapper

3 7

oXygen XML, content negotiation and #1220
by Omar Siam 20 Feb '18

20 Feb '18

Hi list! I like my oXygen editor to request raw XML data from my RESTxq endpoints to test XSL stylesheets. When I do this with RESTxq paths that have different %rest:produces it fails with the BASX0003 multiple functions error. Turns out oXygen sends application/xml, */* as Accept header without any quality. I understand that as documented in https://github.com/BaseXdb/basex/issues/1220 this is known not to work. My/our workaround is to branch in a single XQuery function using sth. like: if (some $a in tokenize(request:header("ACCEPT"), ',') satisfies $a = ('text/xml', 'application/xml')) then $xml else $xhtml I hope this is still on the agenda for 8.7. Best regards Omar Siam

3 7

Preparing BaseX 8.5.4 (please don't forget Issue #1341)
by Jan Dölle 20 Feb '18

20 Feb '18

Hi, we noticed you prepare release 8.5.4. Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341 Thx Jan -- Jan Dölle E-Mail: basex-list(a)id1.de Telefon +49-69-244502-0 Home: www.id1.de Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main Registereintrag: Amtsgericht Frankfurt am Main, HRB 52596 Vorstand: Robert Peters, Aufsichtsrat: Christian Hecht (Vorsitz)

4 5

General XQuery Help: identity transform best practices
by Bridger Dyson-Smith 19 Feb '18

19 Feb '18

Hi list -- apologies if you've seen this message in other mailing lists or IRC. This isn't BaseX-specific, and so I hope that's not troublesome. I'm trying to develop a better understanding of how to leverage the identity transform pattern (or whatever the best term would be) in XQuery. Based on some web searching, typeswitch seemed to be the recommended method; e.g. [1]. But I would run into problems with using `case element($node[@name='first') return local:do-something-specific-with-this($node)`. After some chat with Liam on IRC yesterday, he gave me the idea of trying a plain(er) `switch` but I couldn't quite work out the comparison of a local-name($node) to the atomized value, especially when I needed to evaluted an XPath expression as part of the `case`. Eventually I settled on if-then-else; e.g. [2]. It feels a little unwieldy. Note that in my (typical) usecases I'm transforming entire documents, see [3] for example output. I can't help but wonder though: it there a better way to handle this? Am I missing something obvious with the typeswitch method? I started with XSLT and I feel like maybe I'm doing something wrong :). Thanks for any suggestions or pointers you can offer. Best, Bridger PS Again, hopefully this isn't too off-topic for the list. (: [1] identity transform with typeswitch :) declare variable $input := <docs> <doc> <title>ABC: The Alphabet</title> <author>Some Person</author> <fields> <field name="first">First Field</field> <field name="second">Second Field</field> </fields> </doc> </docs>; declare function local:passthru( $node as node()* ){ local:dispatch($node/node()) }; declare function local:dispatch( $nodes as node()* ) as item()* { for $node in $nodes return typeswitch($node) case text() return $node case element(docs) return local:passthru($node) case element(doc) return local:docf($node) case element(title) return local:title($node) case element(author) return local:author($node) case element(fields) return local:passthru($node) case element(field) return () (:return empty sequence:) default return local:passthru($node) }; declare function local:docf($node) { <new>{local:dispatch($node/node())}</new> }; declare function local:title($node) { <new-title>{local:dispatch($node/node())}</new-title> }; declare function local:author($node) { <new-author>{local:dispatch($node/node())}</new-author> }; local:dispatch($input) (: [2] identity transform with if-then-else :) declare function local:dispatch( $nodes as node()* ) as item()* { for $node in $nodes return( if ($node instance of text()) then $node/data() else (), if (fn:local-name($node) = 'docs') then local:passthru($node) else (), if (fn:local-name($node) = 'doc') then local:docf($node) else (), if (fn:local-name($node) = 'title') then local:title($node) else (), if (fn:local-name($node) = 'author') then local:author($node) else (), if (fn:local-name($node) = 'fields') then local:passthru($node) else (), if (fn:local-name($node) = 'field' and $node/@name='first') then local:field-1($node) else (), if (fn:local-name($node) = 'field' and $node/@name='second') then local:field-2($node) else () ) }; (: [3] sample output :) <new> <new-title>ABC: The Alphabet</new-title> <new-author>Some Person</new-author> <new-subject>First Field</new-subject> <new-section> <new-entry>Second Field</new-entry> </new-section> </new>

3 4

JSON input files
by Jonathan Robie 08 Feb '18

08 Feb '18

I would like to add a JSON file to a collection that is otherwise composed of XML files. I'm hitting two issues: 1. Is there any way to import both JSON and XML files at the same time when creating a database? 2. I would like to import the JSON as an XQuery/XPath map, without mapping it to XML. Any way to do that? Thanks! Jonathan P.S. the input JSON looks like this: { "ααρων": { "gk": 2, "strongs": [ 2 ], "lemma": "Ἀαρών", "transliteration": "Aarōn", "frequencyCount": 5, "definition": "Aaron, pr. name, indecl., the brother of Moses (Exod. 4:14), Lk. 1:15; Acts 7:40; Heb. 5:4; 7:11; 9:4*" }, When I import it, I get this: <json type="object"> <ααρων type="object"> <gk type="number">2</gk> <strongs type="array"> <_ type="number">2</_> </strongs> <lemma>Ἀαρών</lemma> <transliteration>Aarōn</transliteration> <frequencyCount type="number">5</frequencyCount> <definition>Aaron, pr. name, indecl., the brother of Moses (Exod. 4:14), Lk. 1:15; Acts 7:40; Heb. 5:4; 7:11; 9:4*</definition> </ααρων> <αβαδδων type="object"> <gk type="number">3</gk> etc.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk