BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk