BaseX-Talk June 2024

basex-talk@mailman.uni-konstanz.de

10 participants
11 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

Command line "-i" directory does not update files when file extension not "xml"
by Zimmel, Daniel 02 Jul '24

02 Jul '24

Hi, is the following behaviour a bug or does it need better documentation? When in a directory of XML files one file extension is not .xml but .xsl then with java -cp BaseX.jar org.basex.BaseX -u -w -i"localpath/" update.xquery only .xml-files get updates (not .xsl) Only with java -cp BaseX.jar org.basex.BaseX -u -w -i"localpath/file.xsl" update.xquery the .xsl-file does get an update. BaseX 11.0 The documentation only says: " Opens the specified XML file, directory with XML files, or database", but not anything about file extensions. https://docs.basex.org/main/Command-Line_Options Thanks, Daniel

2 2

Problem with inspect:xqdoc() in BaseX 11
by Clark, Ash 01 Jul '24

01 Jul '24

Hi! I'm working on an upgrade to BaseX 11 — which I love already, kudos to the team! Unfortunately, I found that my self-documenting API isn't working anymore. The function inspect:xqdoc() returns only numbers as the content of <xqdoc:description>. Here's an XQuery snippet that should reproduce the problem: inspect:xqdoc('https://raw.githubusercontent.com/NEU-DSG/tapas-xq/develop/modules/tapas-ap…')//*:description Is this a bug? Warmly, Ash Clark

2 2

HTTP headers are all lowercase in responses
by Marco Lettere 01 Jul '24

01 Jul '24

Dear all, just by trying the example of the documentation [1] (at least since 10.4+) you should be able to verify that the response contains all headers with lower-case names. I think a client should not take the freedom to alter HTTP responses if this is not strictly required. What is the concrete reason for this behaviour? hHanks, Marco. [1] http:send-request(<http:request method='get' href='http://www.google.com' timeout='10'/>)

3 2

XML no longer auto formats?
by Buddy Kresge 28 Jun '24

28 Jun '24

Hello, one of my co-workers moved to BaseX 10.7 and the output that is displace when he runs his .xqm file is no longer pretty printed, where as in 9.7 the output does pretty print. Is there an option that can be turned on or off to pretty print the resultant XML? Buddy Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

2 2

BaseX 11: The XMLPrague 2024 Edition
by Christian Grün 07 Jun '24

07 Jun '24

Dear all, We’ve been hard at work finalizing version 11 of BaseX, our open source XML framework, database system, and XQuery processor. First, we have revised our documentation, which is now generated with RESTXQ: https://docs.basex.org/ Next, you can now visit BXFiddle to launch XQuery and Invisible XML online: https://fiddle.basex.org/ Finally, we have added and updated valuable features to help you tackle your daily data challenges: STORAGE • Key/value Store: Better compactification when storing values • CSV/JSON/XML parsing: reduced memory consumption XQUERY • First release with new 4.0 features • Numerous new built-in functions (standard, maps, arrays, math) • Updates: Multiple targets in rename/replace/insert expressions • New custom functions: archive:refresh, validate:xsd-init, xslt:init • Full support for Invisible XML. GENERAL • GUI: Full Unicode character support • Web Server: Upgrade to Jetty 11 • Command-Line: New options -C, -Q, -W • Options: WRITESTORE, writes store to disk at shutdown time We took the opportunity of the version jump to drop various XQuery functions in favor of new 4.0 standard functions. Database storage has not changed. A big thank you to Gunther Rademacher, who is now helping us to make BaseX better every day. Thanks to all of you for your continuous support, Have fun with the new release, Your BaseX Team

4 8

Re: [basex-talk] validate:xsd-report() is not emitting warnings
by ykhabins＠bellsouth.net 05 Jun '24

05 Jun '24

Mr. Grun, I tested the latest BaseX 11.0 beta build f3a5359. It passed all the test cases on my side. Thanks a lot! Regards, Yitzhak Khabinsky

1 0

Re: [basex-talk] validate:xsd-report() is not emitting warnings
by ykhabins＠bellsouth.net 05 Jun '24

05 Jun '24

Mr. Grun, I tested the latest BaseX 11.0 beta build 9182be0. It emits the following result for the provided test case: <report> <status>valid</status> <message level="WARNING" line="12" column="40" url="file:/C:/Users/i300179/Downloads/Warning.xsd">FacetsContradict: For simpleType definition '#AnonType_ADDR_TYPE', the enumeration value '' contradicts with value of 'length' facet.</message> </report> We are almost there. There is one more wrinkle to smooth out. Messages' level attribute value became UPPER-CASED: level="ERROR" level="WARNING" That level attribute values shall be kept as before: level="Error" level="Warning" Otherwise, it breaks existing XQuery analysis of the XSD validation. Regards, Yitzhak Khabinsky

2 1

Re: [basex-talk] validate:xsd-report() is not emitting warnings
by ykhabins＠bellsouth.net 05 Jun '24

05 Jun '24

Mr. Grun, Thanks a lot for such a such quick turnaround. I tested the latest BaseX 11.0 beta build 88ebdb9. It emits the following result for the provided test case: <report> <status>invalid</status> <message level="Warning" line="12" column="40" url="file:/C:/Users/i300179/Downloads/Warning.xsd">FacetsContradict: For simpleType definition '#AnonType_ADDR_TYPE', the enumeration value '' contradicts with value of 'length' facet.</message> </report> There is one more outstanding issue to resolve. A logic for the final XSD validation result needs to be adjusted. 1) Messages with the attribute level="Warning" shall be NOT counted as invalid! As end result: <status>valid</status> 2) Messages with the attribute level="Error" shall be counted as a failed validation. As end result: <status>invalid</status> Such behavior would be consistent with the Oxygen XML IDE validation outcome. Regards, Yitzhak Khabinsky

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk June 2024