BaseX-Talk

basex-talk@mailman.uni-konstanz.de

9 participants
5241 discussions

XSD 1.1 validation: base-uri(.) in the assert
by ykhabins＠bellsouth.net 11 Jul '24

11 Jul '24

Hello, We are using the final release BaseX 11.0 and Xerces 2.12.2 XSD 1.1 engine. There is a need to validate XML file and check XML file name for naming convention. Unfortunately, the assert with the base-uri(.) function is not working as expected in the assert expression. Observations: The XPath expression on the XML file emits, as expected, the following: o XPath: base-uri(.) o Results: file:/C:/Users/i300179/Downloads/ATF_NESS/base-uri/input.xml The XPath expression on the XML file emits, as expected, the following: o XPath: tokenize(base-uri(.),"/")[last()] o Results: input.xml I tried multiple expressions around base-uri(.) function. None of them worked. You will find all my attempts in the XSD file. The test case XQuery/XML/XSD is below. We are using Xerces, but the following Saxon excerpt could be pointing to the root cause of the problem. For the reference: https://www.saxonica.com/html/documentation10/functions/fn/base-uri.html "It is possible for the base URI of a document to be absent (unknown). This happens when the document is supplied to Saxon with no location information: for example when the node is represented using a tree model such as DOM that has no base URI information; or when a Source is supplied for which getSystemId() returns null. The most common example of this is a Source created using new StreamSource(new FileInputStream("input.xml")). The problem can be fixed by using the second argument of the StreamSource constructor, or by using the constructor that expects a File rather than an InputStream." XSD11_Validation.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 input.xml ======================= <root> <event> <id>1</id> </event> </root> input.xsd ======================== <?xml version="1.0" encoding="UTF-8"?> <xs:schema version="1.0.1" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning" xmlns:xerces="http://xerces.apache.org" vc:minVersion="1.1"> <xs:element name="root"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="event"/> </xs:sequence>  <xs:assert test="tokenize(base-uri(.), '/')[last()] eq 'input.xml'" xerces:message="Rule #21: XML file name shall match file naming convention">   </xs:assert> </xs:complexType> </xs:element> <xs:element name="event"> <xs:complexType> <xs:sequence> <xs:element ref="id"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="id" type="xs:integer"/> </xs:schema> Regards, Yitzhak Khabinsky

2 1

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk