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

Re: [basex-talk] XSLT with multiple outputs in BaseX 11.0
by ykhabins＠bellsouth.net 03 Jul '24

03 Jul '24

I completely concur. BaseX is a standard bearer of the latest XML standards. We are mostly using BaseX with its HTTP listener for the following: 1. XSD 1.1 validations (via Xerces 12.2.2) 2. XSLT 3.0 transformations (via Saxon engine) and not just as a XML database platform with its XQuery 4.0 support. Regards, Yitzhak Khabinsky

1 0

XSLT with multiple outputs in BaseX 11.0
by ykhabins＠bellsouth.net 03 Jul '24

03 Jul '24

Hello, I am using the latest BaseX 11.0 final. I am running an XSLT 3.0 transformation, by using SaxonHE12-4J, and hit a snag with it. The goal of the XSLT is to split large input XML file into few smaller XML files. The test case files: XML, XSLT, and xq, are below. The XSLT transformation is working as expected, producing multiple output files on the file system. Alas, BaseX GUI emits the following error: Error: Stopped at C:/Program Files (x86)/basex/src/xslt_transform30.xq, 6/15: [FODC0002] "" (Line -1): Premature end of file. My XSLT is a little bit unusual. It is leveraging powerful XSLT 3.0 functionality. It doesn't have one single output, but many output files directly to the file system, IMHO, that's the reason for the BaseX error. BaseX is expecting at least some output back from the XSLT transformation. For comparison, the Oxygen XML IDE is working as expected with such XSLT. What could be done to fix it? May be BaseX behavior needs some adjustment, so it will accept blank output as normal for the xslt:transform($input, $stylesheet)? BaseX is famous for its latest standards support. Modern XSLT versions, i.e. above XSLT 1.0, support multiple outputs. _xslt_transform30.xq =========================================== xquery version "4.0"; declare variable $input as xs:string external; declare variable $stylesheet as xs:string external; xslt:transform($input, $stylesheet) =========================================== Input.xml =========================================== <doc title="example document"> <chapter title="chapter 1"> <page>page 1</page> <page>page 2</page> </chapter> <chapter title="chapter 2"> <page>page 3</page> </chapter> </doc> =========================================== SplitProcess.xslt =========================================== <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:math="http://www.w3.org/2005/xpath-functions/math" exclude-result-prefixes="xs math" version="3.0" expand-text="yes"> <xsl:output indent="yes" method="xml"/>  <xsl:param name="directory" select="'c:/Temp/XSLT30/Split up a file into several files'"/> <xsl:template match="/"> <xsl:apply-templates select="doc/chapter/page"/> </xsl:template> <xsl:template match="page"> <xsl:result-document href="file:///{$directory}/page{position()}.xml"> <xsl:copy-of select="root(snapshot())"/> </xsl:result-document> </xsl:template> </xsl:stylesheet> =========================================== Regards, Yitzhak Khabinsky

5 4

Re: [basex-talk] file:write(...) is not respecting indent parameter correctly
by ykhabins＠bellsouth.net 02 Jul '24

02 Jul '24

The solution was to add a stripws option. After that all output XML files are indented properly because causing the issue whitespaces were removed. Please see the working properly XQuery below. (: https://docs.basex.org/main/Options#stripws :) declare option db:stripws "true"; declare variable $input as xs:string external; declare variable $output_dir as xs:string external; for $x at $i in doc($input)/Events/Event return file:write($output_dir || file:dir-separator() || "event_" || $i || ".xml", $x , map {'method': 'xml', 'indent': 'yes', 'omit-xml-declaration': 'no'}) Regards, Yitzhak Khabinsky

2 1

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

Re: [basex-talk] missing invisible-xml library in BaseX 11.0?
by Gunther Rademacher 02 Jul '24

02 Jul '24

2 1

missing invisible-xml library in BaseX 11.0?
by C. M. Sperberg-McQueen 01 Jul '24

01 Jul '24

Some days ago I downloaded BaseX110.zip and installed it. When I try to invoke the invisible-xml function documented at [1], however, I get the error message: [basex:function] Function invisible-xml requires missing class: de.bottlecaps.markup.Blitz. At first, I thought this might be interference from an earlier version of BaseX (9.0.1, which is what my package manager offered me), but it persists now even after I have uninstalled that earlier version. Did I do something wrong in the installation? Or was there an oversight putting the zip file together? best, Michael Sperberg-McQueen [1] https://docs.basex.org/main/Invisible_XML -- C. M. Sperberg-McQueen Black Mesa Technologies LLC http://blackmesatech.com

1 0

file:write(...) is not respecting indent parameter correctly
by ykhabins＠bellsouth.net 01 Jul '24

01 Jul '24

Hello, I am using the latest BaseX 11.0 final. It looks like that file:write(...) is not respecting indent parameter correctly: 'indent': 'yes' Split.xq ======================== declare variable $input as xs:string external; declare variable $output_dir as xs:string external; for $x at $i in doc($input)/Events/Event return file:write($output_dir || file:dir-separator() || "event_" || $i || ".xml", $x , map {'method': 'xml', 'indent': 'yes', 'omit-xml-declaration': 'no'}) ======================== Input.xml ======================== <?xml version="1.0" encoding="utf-8"?> <Events> <Event><CaseNumber>22-0000124</CaseNumber> <EventDate>2022-04-16</EventDate> <AgencyORINum>ATF000001</AgencyORINum> <CrimeType>ROBBERY</CrimeType> </Event> <Event><CaseNumber>22-0000125</CaseNumber> <EventDate>2022-04-16</EventDate> <AgencyORINum>ATF000001</AgencyORINum> <CrimeType>ROBBERY</CrimeType> </Event> </Events> ======================== Regards, Yitzhak Khabinsky

1 0

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

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

05 Jun '24

Hello, I am using BaseX 11.0 beta build 587d1ca and Xerces 2.12.2 for the XSD 1.1 validation. It looks like that validate:xsd-report() call is not emitting warnings. Though Oxygen XML IDE shows the following upon validation: For simpleType definition '#AnonType_ADDR_TYPE', the enumeration value '' contradicts with value of 'length' facet. Warning.xq =========== declare variable $xml as xs:string external; declare variable $xsd as xs:string external; let $result := validate:xsd-report($xml, $xsd, map { 'http://apache.org/xml/features/validation/cta-full-xpath-checking': true(), 'cache': false() }) return $result It returns the following: <report> <status>valid</status> </report> But it should be as follow: <report> <status>valid</status> <message level="Warning" line="..." column="..." url="...">Warning message</message> </report> XML/XSD pair to reproduce the behavior. Warning.xml ============ <root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Warning.xsd"> <ADDR_TYPE>B</ADDR_TYPE> </root> Warning.xsd ============ <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="root"> <xs:complexType> <xs:sequence> <xs:element ref="ADDR_TYPE"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="ADDR_TYPE"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="1"/> <xs:enumeration value=""> <xs:annotation> <xs:documentation>NOT SELECTED</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="B"/> <xs:enumeration value="S"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:schema> Regards, Yitzhak Khabinsky

2 1

storing xml-elements
by Rob Stapper 27 May '24

27 May '24

Hi Christian, I'm looking for a way to store a xml-subelement during a session as a subelement and not as a rootelement. The store- and the session:set-function save xml-elements as a root-elements, loosing the origional root. My casus is that I have this batch-webservice that I want to turn into a online/interactive-webservice. The application makes use of the root- and ancestor functions/axis on xml-subelements. In the batch solution I have access to the origional xml-subelement. In the online-solution however I have not. This because the code is broken up due to a http-request/response interaction with the user. I would like the xml-subelement to survive this http-excursion in a way that its root-element stays available and the root- and ancestor-function gives the same result as in the batch-version. Do you have any suggestions on this? mvgr. Rob Stapper

2 2

Session problems with two BaseX installations
by Jack Steyn 27 May '24

27 May '24

Hi, I have two separate BaseX installations on the same machine. Each has its own set of databases and users. I run their HTTP servers simultaneously, configured to their own sets of ports. When I authenticate to the DBA webapp of one, I am logged out of the DBA webapp of the other. What might I do to prevent this? Best regards, Jack

2 3

Making store reactive
by Marco Lettere 22 May '24

22 May '24

Dear Christian and BaseX developers, just wondering if adding something like the following would be hard to implement. /store:observe($key as xs:string, $observers as function(*)*) / with $observers being something like /function($key as xs:string)./ The semantics is to call the registered observers whenever a value associated with the key in the store changes (put, remove, clear, ..). This would allow for nicely decoupled observer - notification pattern. Does it make sense? Regards, Marco.

3 3

Weird behaviour with sequence and random:integer
by Marco Lettere 22 May '24

22 May '24

Dear all, I have this strange behavior when running in BaseX 10.4: ["a","b","c"](1 + random:integer(3)) I got something empty result, sometimes (correctly) one out of the three, sometimes two results... I report the results and the trace in [1] and [2]. What is the reason for this? Thank you. Marco. [1] Two results a c Evaluating: 1 3 3 Compiling: - rewrite list to xs:string sequence: ("a", "b", "c") - swap operands: (1 + random:integer(3)) Optimized Query: ("a", "b", "c")[trace((random:integer(3) + 1))] Query: ("a", "b", "c")[trace(1 + random:integer(3))] Result: - Hit(s): 2 Items - Updated: 0 Items - Printed: 3 b - Read Locking: (none) - Write Locking: (none) Timing: - Parsing: 0.21 ms - Compiling: 0.4 ms - Optimizing: 0.1 ms - Evaluating: 0.57 ms - Printing: 0.02 ms - Total Time: 1.31 ms [2] Empty result () Evaluating: 3 3 1 Compiling: - rewrite list to xs:string sequence: ("a", "b", "c") - swap operands: (1 + random:integer(3)) Optimized Query: ("a", "b", "c")[trace((random:integer(3) + 1))] Query: ("a", "b", "c")[trace(1 + random:integer(3))] Result: - Hit(s): 0 Items - Updated: 0 Items - Printed: 0 b - Read Locking: (none) - Write Locking: (none) Timing: - Parsing: 0.16 ms - Compiling: 0.41 ms - Optimizing: 0.15 ms - Evaluating: 0.56 ms - Printing: 0.02 ms - Total Time: 1.3 ms Query Plan: <QueryPlan compiled="true" updating="false"> <CachedFilter type="xs:string*"> <StrSeq type="xs:string+" size="3"> <Str type="xs:string" size="1">a</Str> <Str type="xs:string" size="1">b</Str> <Str type="xs:string" size="1">c</Str> </StrSeq> <FnTrace name="trace" type="xs:integer" size="1"> <Arith op="+" type="xs:integer" size="1"> <RandomInteger name="random:integer" type="xs:integer" size="1"> <Int type="xs:integer" size="1">3</Int> </RandomInteger> <Int type="xs:integer" size="1">1</Int> </Arith> </FnTrace> </CachedFilter> </QueryPlan>

2 2

string:levenshtein producing incorrect results?
by Jack Steyn 13 May '24

13 May '24

Hi, According to my copy of BaseX 10.7, string:levenshtein('oil field', 'oilfield') and string:levenshtein('oil field', 'coalfield') both return the same value, 0.7777777777777778. My understanding is that the Levenshtein-Damerau distance between 'oil field' and 'oilfield' is 1 and between 'oil field' and 'coalfield' is 3, so following the formula from https://docs.basex.org/wiki/String_Module#string:levenshtein 1.0 – distance / max(length of strings) should give 0.888... and 0.666... respectively. Am I off-base here or is there something awry with string:levenshtein? Cheers, Jack

2 3

Re: [basex-talk] BaseX installation cannot see Java
by ykhabins＠bellsouth.net 10 May '24

10 May '24

Mr. Grun, It seems that the Windows Management Instrumentation Command-line (WMIC) command line utility gives a reliable result in windows. https://www.techtarget.com/searchenterprisedesktop/definition/Windows-Manage ment-Instrumentation-Command-line-WMIC It is deprecated, but working on any Windows OS, including Windows Server 2022. On my home machine with Windows 10 OS the following command c:\>wmic product where "Name like '%JRE%' or name Like'%Java%' or name Like'%JDK%' " get name,Vendor,Version emits the following 4 (four) Java installations: Name Vendor Version Java(TM) SE Development Kit 18.0.2 (64-bit) Oracle Corporation 18.0.2.0 Java 8 Update 391 (64-bit) Oracle Corporation 8.0.3910.13 Eclipse Temurin JDK with Hotspot 21.0.2+13 (x64) Eclipse Adoptium 21.0.2.13 Java Auto Updater Oracle Corporation 2.8.391.13 To see all available entries: c:\>wmic product where "Name like '%JRE%' or name Like'%Java%' or name Like'%JDK%' " get * /format:textvaluelist So, you can try to integrate wmic based method in the BaseX Windows installer. Regards, Yitzhak Khabinsky

2 1

Re: [basex-talk] BaseX installation cannot see Java
by ykhabins＠bellsouth.net 08 May '24

08 May '24

Mr. Grun, Good news on my end! The revised installation BaseX Windows installation was very helpful. It showed the following: --------------------------- BaseX Setup --------------------------- Please install Java 11 or higher before executing the installer. Analyzed Java version string: java version "1.6.0" Java(TM) SE Runtime Environment (build pwi3260sr9fp1-20110208_03(SR9 FP1)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows Vista x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) J9VM - 20110203_074623 JIT - r9_20101028_17488ifx3 GC - 20101027_AA) JCL - 20110203_01 --------------------------- OK --------------------------- I went to Control Panel, and sure enough, it showed two Java installations: 1) Eclipse Temurin JRE with Hotspot 17.0.8.1+1 (x64) 2) IBM 32-bit Runtime Environment v6 I uninstalled the IBM's Java v6, and successfully installed the latest BaseX 11.0 beta build c21851a!!! There are still some questions remaining. Where and how BaseX installer got into old Java v1.6 and missed a legitimate Eclipse Temurin JRE with Hotspot 17.0.8.1+1? c:\>java -version shows the following openjdk version "17.0.8.1" 2023-08-24 OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.8.1+1 (build 17.0.8.1+1, mixed mode, sharing) c:\>path shows the following: PATH=C:\Program Files\Eclipse Adoptium\jre-17.0.8.101-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOW S\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WI NDOWS\System32\OpenSSH\;C:\Windows\CCM;C:\Program Files\Eclypsium\;C:\Program Files (x86)\Microsoft SQL Server\160\DTS\Binn\;C:\Program Files\Azure Data Studio\bin;C:\Users\i300179\AppData\Local\Microsoft\WindowsApps; Overall, that's a lot for such a great support of the product. Regards, Yitzhak Khabinsky

2 1

Re: [basex-talk] BaseX installation cannot see Java
by ykhabins＠bellsouth.net 08 May '24

08 May '24

C:\>java -version openjdk version "17.0.8.1" 2023-08-24 OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1) OpenJDK 64-Bit Server VM Temurin-17.0.8.1+1 (build 17.0.8.1+1, mixed mode, sharing) Regards, Yitzhak Khabinsky

2 2

BaseX installation cannot see Java
by ykhabins＠bellsouth.net 07 May '24

07 May '24

Hello, Trying to install BaseX via launching BaseX110-20240320.152714.exe in Windows 10 OS environment in a corporate environment. The build version is irrelevant. I tried few of them with the same outcome. Even running the installation as "Run as administrator". Also, I am a local admin on the PC. Unfortunately, I am getting the following error message dialog box: --------------------------- BaseX Setup --------------------------- Please install Java 11 or higher before executing the installer. --------------------------- OK --------------------------- Somehow the BaseX setup cannot find Java on the machine. Though the OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1) is installed. The current BaseX installation is working properly. 1) Executing this XQuery in BaseX GUI to get Java VM properties: for $p in proc:property-names()[starts-with(., 'java.vm.')] return $p || ': ' || proc:property($p) It emits the following: java.vm.compressedOopsMode: 32-bit java.vm.info: mixed mode, sharing java.vm.name: OpenJDK 64-Bit Server VM java.vm.specification.name: Java Virtual Machine Specification java.vm.specification.vendor: Oracle Corporation java.vm.specification.version: 17 java.vm.vendor: Eclipse Adoptium java.vm.version: 17.0.8.1+1 2) Issuing PATH statement at the command prompt shows the following: PATH=C:\Program Files\Eclipse Adoptium\jre-17.0.8.101-hotspot\bin;C:\WINDOWS\system32;... It seems that some kind of security settings are causing it. Please advise. Regards, Yitzhak Khabinsky

2 1

minor issue in documentation
by Rob Stapper 03 May '24

03 May '24

Hi Christian, I stumbled on this minor issue in the documentation: @ docs.basex.org/wiki/Database_Module#db:type Examples * db:type("DB", "factbook.xml") returns true if the specified resource is an XML document. true should be 'xml'. mvgr. Rob Stapper

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk