BaseX-Talk September 2022

basex-talk@mailman.uni-konstanz.de

14 participants
14 discussions

BaseX 9.6: The Summer Edition
by Christian Grün 28 Nov '24

28 Nov '24

Dear all, We provide you with a new and fresh version of BaseX, our open source XML framework, database system and XQuery 3.1 processor: https://basex.org/ Apart from our main focus (query rewritings and optimizations), we have added the following enhancements: XQUERY: MODULES, FEATURES - Archive Module, archive:write: stream large archives to file - SQL Module: support for more SQL types - Full-Text Module, ft:thesaurus: perform Thesaurus queries - Fulltext, fuzzy search: specify Levenshtein limit - UNROLLLIMIT option: control limit for unrolling loops XQUERY: JAVA BINDINGS - Java objects of unknown type are wrapped into function items - results of constructor calls are returned as function items - the standard package "java.lang." has become optional - array arguments can be specified with the middle dot notation - conversion can be controlled with the WRAPJAVA option - better support for XQuery arrays and maps WEB APPLICATIONS - RESTXQ: Server-Timing HTTP headers are attached to the response For a more comprehensive list of added and updated features, look into our documentation (docs.basex.org) and check out the GitHub issues (github.com/BaseXdb/basex/issues). Have fun, Your BaseX Team

11 43

recursively used variables
by Rob Stapper 12 Aug '24

12 Aug '24

Hi, The code[1] below and send as attachment generates a error message: “Static variable depends on itself: $Q{http://www.w3.org/2005/xquery-local-functions}test”. I use these variables to refer to my private functions in my modules so I can easyly refer to them in a inheritance situation. It’s not a big problem for me but I was wondering if the error-triggering is justified or that it should work. [1]=========================================== declare variable $local:test := local:test#1 ; declare %private function local:test( $i) { if ( $i > 0) then $local:test( $i - 1) } ; $local:test( 10) =========================================== Kind regards, Rob Stapper Sent from Mail for Windows 10 -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

4 7

xslt:transform-report result
by Andy Bunce 11 Mar '24

11 Mar '24

Hi, Using BaseX 9.7.1 and saxon9he-9.9.1.jar The documentation suggests the ?result from xslt:transform-report should be *a* document-node where possible [1] This seems not quite to be the case when there are processing instructions or comments at the top level. In these cases a sequence of document-nodes is returned. /Andy [1] https://docs.basex.org/wiki/XSLT_Module#xslt:transform-report let $xslt:=<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"> <xsl:mode on-no-match="shallow-copy"/> </xsl:stylesheet> let $xml:=document{ <?something type="compact"?>, <foo/>} return xslt:transform-report($xml,$xslt) Returns map { "messages": (), "result": (<?something type="compact"?>, <foo/>) }

3 7

Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
by ykhabins＠bellsouth.net 30 Sep '22

30 Sep '22

Hello, I am using BaseX v.10.2 More specifically launching basexserver.bat and using c# samples from the following link: https://github.com/BaseXdb/basex/tree/9/basex-api/src/main/c%23 Everything is work fine when a computer with the Windows 10 OS has the following security policy disabled: System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing https://docs.trendmicro.com/all/ent/sc/v3.0/en-US/cmcolh/t_fips.html Alas, I am working for the company where that security policy is enabled. And I am getting the following error: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms." This particular function is erroring out. private string MD5(string input) { MD5CryptoServiceProvider MD5 = new MD5CryptoServiceProvider(); ... } I did some research and collected the following useful links: https://stackoverflow.com/questions/14509354/this-implementation-is-not-part -of-the-windows-platform-fips-validated-cryptogra https://docs.trendmicro.com/all/ent/sc/v3.0/en-US/cmcolh/t_fips.html https://stackoverflow.com/questions/6652850/enforcefipspolicy-flag-in-web-co nfig-doesnt-seem-to-working-for-web-application https://techcommunity.microsoft.com/t5/microsoft-security-baselines/why-we-a mp-8217-re-not-recommending-amp-8220-fips-mode-amp-8221/ba-p/701037 I also tried to add the following to the .config file to no avail: <configuration> <runtime> <enforceFIPSPolicy enabled="0" /> </runtime> </configuration> Is it possible to modify c# samples to work on the computers where mentioned above security poilsy is enabled? Regards, Yitzhak Khabinsky

1 0

BaseX 10.1 bug in GET command?
by Gabriel Lorenzo 27 Sep '22

27 Sep '22

Hello, I think I've found a possible bug. When I use the GET command the document retrieved is not always the same I requested. It only happens with the GET command, as using db:get() from xquery always works as expected. I haven't observed it happening with BINARY GET. I've reproduced it with the simplest example: BaseX 10.1 [Client]Try 'help' to get more information. > create db sample Database 'sample' created in 14.0 ms. > open sample Database 'sample' was opened in 0.03 ms. > add to hello.xml <hello>world</hello> Resource(s) added in 2.25 ms. > add to goodbye.xml <goodbye>world</goodbye> Resource(s) added in 2.22 ms. > get hello.xml <goodbye>world</goodbye>Query executed in 0.18 ms. > get goodbye.xml <hello>world</hello>Query executed in 0.19 ms. > xquery db:get('sample','hello.xml') <hello>world</hello> Query "BaseX" executed in 0.64 ms. > xquery db:get('sample','goodbye.xml') <goodbye>world</goodbye> Query "BaseX" executed in 0.23 ms. > I'm using BaseX 10.1 on Windows 10 with OpenJDK Temurin-17.0.4.1+1 Regards, Gabriel Lorenzo

2 1

Full text search with non-Latin scripts
by Andreas Hartmann 26 Sep '22

26 Sep '22

Hi, I have problems with full text search in 10.1, when non-Latin script is involved. Expressions such as "βάναυσος" contains text "67644567" using fuzzy "67644567" contains text "βάναυσος" using fuzzy "humbug" contains text "βάναυσος" using fuzzy all yield "true". It's the same with Hebrew strings. It does not matter which Greek/Hebrew word is used, as long as the word-length does not differ too much from the compared string. Is this really the expected behavior or could it be a bug? Best greetings Andreas

2 1

file:descendants() returns relative paths
by Hans-Jürgen Rennau 26 Sep '22

26 Sep '22

Dear BaseX people, functions file:descendants and file:children return relative paths, if input parameter $dir is a relative folder path. I regard this as a bug - relative folder paths should be resolved against the current working directory, so that a relative path and the corresponding absolute path are equivalent parameters. The functions should always return absolute paths, as the documentation promises. After all, a key use case is to find files which to access, and the accessor functions (doc(), json:doc(), unparsed-text() etc.) do *not* resolve relative paths against the current working dir. Kind regards, Hans-Jürgen

4 9

Full Text bug (?) - window ... words
by Hans-Juergen Rennau 26 Sep '22

26 Sep '22

Dear BaseX people, it seems to me there is a bug concerning Full Text Search, using option "window": let $text1 := '1 The usability of a Web site is how well the site' let $text2 := '2 The usability of a Web site is how well the sitx'let $text3 := '3 The usability of a Web site is how well the site'return ( $text1[. contains text 'usability web site' all words window 5 words], $text2[. contains text 'usability web site' all words window 5 words], $text3[. contains text 'usability web site' all words window 10 words] ) This query should return all three, $text1, $text2 and $text3, but it only returns $text2 and $text3. So it seems to me that the implemented logic is: "all matches of the "all words" search must be within a 5-words window, but it should be "there is a match of the "all words" search which is within a 5-words window. More detailed argument in PS. Kind regards,Hans-Jürgen PS: Compare https://www.w3.org/TR/xpath-full-text-30/#ftwindow "A window selection examines the matches generated by the preceding portion of the FTSelection, and selects those for which the matched tokens and phrases (more precisely, the individual StringIncludes of that match) are all found within a window whose size is a specified number of FTUnits (words, sentences, or paragraphs); for each such window, the window selection then generates a match containing the merge of those StringIncludes, plus any StringExcludes that fall within the window." (Italic added by me) The detailed semantics are given in 4.2.4 FTWords [1]. Pseudo-function fts:applyFtWordsAllWord() constructs for each of the words an fts:allMatches element and then performs conjunction of these elements, based on recursive application of 4.3.6.2 FTAnd [2]. Each fts:allMatches element contains one fts:match element for each occurrence of the word in question. The "ANDing" of two fts:allMatches is described by pseudo-function fts:ApplyFTAnd(), which creates one match for each pair of matches found in the operands - in other words, all combinations of operand matches are considered. As an example consider: "foo bar" all words and assume "foo" occurs two times and "bar" occurs two times. The fts:allMatches element representing the result is the result of applying fts:ApplyFTAnd() to two fts:allMatches elements, one obtained for word "foo", one obtained for word "bar". Schematically: $fts:allMatches_foo: <fts:match>foo(1)</fts:match> <fts:match>foo(2)</fts:match> $fts:allMatches_bar: <fts:match>bar(1)</fts:match> <fts:match>bar(2)</fts:match> fts:applyFTAnd($fts:allMatches_foo, $fts:allMatches_bar) is a single fts:allMatches containing four matches, each one of which is a combination of matches found in the operands: <fts:allMatches_allwords> = <fts:match>foo(1), bar(1)</fts:match> <fts:match>foo(1), bar(2)</fts:match> <fts:match>foo(2), bar(1)</fts:match> <fts:match>foo(2), bar(2)</fts:match> Now extend the query to "foo bar" all words window 5 words The result is true, if there is at least one combination of occurrences of "foo" and "bar" found in a window of at most 5 for word "bar". Referring to the semantic intermediates: if <fts:allMatches_allwords> contains at least one <fts:match> element for which all contained matches satisfy the window condition. [1] https://www.w3.org/TR/xpath-full-text-30/#tq-ft-fs-FTWords[2] https://www.w3.org/TR/xpath-full-text-30/#tq-ft-fs-FTAnd

2 1

Java 11
by Giuseppe G. A. Celano 13 Sep '22

13 Sep '22

Hi All, On the BaseX website (https://basex.org/download/ <https://basex.org/download/>), it is specified that “Java 11 is required to install and run BaseX (10.1)” . Since it is not specified “Java 11 or higher”, I am wondering whether this requirement is actually meant to be strict. Thanks! Best, Giuseppe

2 1

current-dateTime() function precision
by ykhabins＠bellsouth.net 09 Sep '22

09 Sep '22

Hello, I am using BaseX v.10.1 It seems that the current-dateTime() function precision is off. I am validating an XML file against an XSD 1.1 file via Xerces 2.12.2 validator. And trying to measure a timing of it. Here is my code. xquery version "4.0"; let $xml := '\\...\AForm-XSD-20211013\PD220224062681.XML' let $xsd := '\\...\AForm-XSD-20211013\Miami-ws-AForm.xsd' let $before_datetime := current-dateTime() let $result := validate:xsd-report($xml, $xsd, map { 'http://apache.org/xml/features/validation/cta-full-xpath-checking': true() }) return <root><metadata> <result>{data($result/status)}</result> <errors>{count($result/message)}</errors> <startTime>{$before_datetime}</startTime> <endTime>{current-dateTime()}</endTime> <xmlFile>{$xml}</xmlFile> <xsdFile>{$xsd}</xsdFile> <xsdProcessor>BaseX {data(db:system()//version)}, EE-Java, {validate:xsd-processor()} 2.12.2</xsdProcessor> <xsdVersion>{validate:xsd-version()}</xsdVersion> </metadata> <messages>{$result/message}</messages> </root> It is emitting the following output: <root> <metadata> <result>invalid</result> <errors>3</errors> <startTime>2022-09-09T11:32:29.667-04:00</startTime> <endTime>2022-09-09T11:32:29.667-04:00</endTime> <xmlFile>\\...\AForm-XSD-20211013\PD220224062681.XML</xmlFile> <xsdFile>\\...\AForm-XSD-20211013\Miami-ws-AForm.xsd</xsdFile> <xsdProcessor>BaseX 10.1, EE-Java, Xerces 2.12.2</xsdProcessor> <xsdVersion>1.1</xsdVersion> </metadata> <messages> ... </messages> </root> The question is why the before and after timing is the same: <startTime>2022-09-09T11:32:29.667-04:00</startTime> <endTime>2022-09-09T11:32:29.667-04:00</endTime> They are identical up to a millisecond. My expectations were that at least the millisecond time portion would be different. Regards, Yitzhak Khabinsky

3 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk September 2022