BaseX-Talk

basex-talk@mailman.uni-konstanz.de

9 participants
5241 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk