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
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
Hi,
Using BaseX 9.7.1 and saxon9he-9.9.1.jar
The documentation suggests the ?result from xslt:transform-report should be
*a* document-node where possible [1]
This seems not quite to be the case when there are processing instructions
or comments at the top level. In these cases a sequence of document-nodes
is returned.
/Andy
[1] https://docs.basex.org/wiki/XSLT_Module#xslt:transform-report
let $xslt:=<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="3.0">
<xsl:mode on-no-match="shallow-copy"/>
</xsl:stylesheet>
let $xml:=document{ <?something type="compact"?>, <foo/>}
return xslt:transform-report($xml,$xslt)
Returns
map {
"messages": (),
"result": (<?something type="compact"?>, <foo/>)
}
Hi,
Just discovered that the code samples on the basex wiki doesn't seem to be
working fully. Noticed it a couple of days ago and thought it was
temporary, but the problem is still there.
Regards,
Johan
I’m generating CSV data that includes URLs with multiple query parameters, so “&somekey” in them. These get serialized as “&somekey” where I want “&somekey”.
My CSV XML looks like this:
<record>
<AppID>sn_admin_center</AppID>
<DocsURL>=HYPERLINK(https://docs.servicenow.com/csh?topicname=admin-center-intro&version=vancouver)</DocsURL>
</record>
I’m then doing:
let $report := csv:serialize($csv, map{})
let $doWrite := file:write('/Users/eliot.kimber/temp/apps-to-topics.csv', $report)
To write the CSV file.
The resulting file looks like:
sn_admin_center,”=HYPERLINK(“"https://docs.servicenow.com/csh?topicname=admin-center-intro&version=va…")"
Note that the “&” is still escaped.
Reviewing the docs for the CVS module and the serialize options, I don’t see any option that looks like it would control how escaping is handled.
Is there a way to do what I want?
Thanks,
E.
_____________________________________________
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
servicenow.com<https://www.servicenow.com>
LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>
Hi Christian,
Thnx. You made me a bit worrying there.
Just a thought: shouldn’t util:if not just be part of the regular BaseX syntax? Together with fn:for-each, the fn:fold functions and hof:fold-left1, they represent the group of procesflow-controll-functions.
Best,
Rob
Sent from Mail for Windows
From: basex-talk-request(a)mailman.uni-konstanz.de
Sent: Friday, November 24, 2023 12:00 PM
To: basex-talk(a)mailman.uni-konstanz.de
Subject: BaseX-Talk Digest, Vol 167, Issue 9
Send BaseX-Talk mailing list submissions to
basex-talk(a)mailman.uni-konstanz.de
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
or, via email, send a message with subject or body 'help' to
basex-talk-request(a)mailman.uni-konstanz.de
You can reach the person managing the list at
basex-talk-owner(a)mailman.uni-konstanz.de
When replying, please edit your Subject line so it is more specific
than "Re: Contents of BaseX-Talk digest..."
Today's Topics:
1. Re: BaseX 10.7 and util:if (Christian Gr?n)
2. Debugging XML catalog with BaseX 10.7 (Andy Bunce)
----------------------------------------------------------------------
Message: 1
Date: Thu, 23 Nov 2023 15:30:47 +0100
From: Christian Gr?n <christian.gruen(a)gmail.com>
To: Andy Bunce <bunce.andy(a)gmail.com>
Cc: BaseX <basex-talk(a)mailman.uni-konstanz.de>
Subject: Re: [basex-talk] BaseX 10.7 and util:if
Message-ID:
<CAP94bnN+BFAv6cRqvRwiDMLSw6hqN7pU12PcgUeN54XF-BwoAw(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Andy, hi Rob,
util:if is back again.
Just give me a note if there are other functions in the Utility Module (or
in the HOF Module) that you rely on.
Best,
Christian
On Mon, Nov 20, 2023 at 1:15?PM Andy Bunce <bunce.andy(a)gmail.com> wrote:
> Hi,
> The documentation for the utility module [1] says certain functions will
> be removed in version 11 because they will be in XPath 4.0.
> However, util:if has been removed from the documentation and I think there
> is no equivalent function in this case.
> util:if is an alternative syntax for the BaseX Ternary operator [2].
>
> ( I have used it because it was easier than trying to get my XQuery parser
> EBNF to accept $ok ?? 1 !! 0 etc)
>
> Is util:if to be removed?
>
> /Andy
> [1] https://docs.basex.org/wiki/Utility_Module#util:if
> [2] https://docs.basex.org/wiki/XQuery_Extensions#Ternary_If
>
Hi,
I am following the guide at [1] with the aim of loading some XML with a
variety of DTD doctypes.
I have a catalog.xml set (which works in another app) and in lib/custom I
have
- saxon-he-10.9.jar
- xmlresolver-5.2.2-data.jar
- xmlresolver-5.2.2.jar
- xmlresolver.properties
It is not working as I hoped. Is there a way to get debug info from
xmlresolver to a file without going to the Java level?
The guide says "You must configure your environment with an appropriate
logging backend." [2]
I guess this is about SLF4J <http://www.slf4j.org/> but I have no
experience here.
/Andy
[1] https://docs.basex.org/wiki/Catalog_Resolver
[2] https://xmlresolver.org/ch06#xml.catalog.defaultLoggerLogLevel
Hi,
The documentation for the utility module [1] says certain functions will be
removed in version 11 because they will be in XPath 4.0.
However, util:if has been removed from the documentation and I think there
is no equivalent function in this case.
util:if is an alternative syntax for the BaseX Ternary operator [2].
( I have used it because it was easier than trying to get my XQuery parser
EBNF to accept $ok ?? 1 !! 0 etc)
Is util:if to be removed?
/Andy
[1] https://docs.basex.org/wiki/Utility_Module#util:if
[2] https://docs.basex.org/wiki/XQuery_Extensions#Ternary_If
Hello,
In BaseX 11.0 beta, I’m encountering a strange error. I’ve created a gist that illustrates the behavior: https://gist.github.com/timathom/7fd44b43de1fa72162cd59cf755c3d91.
I have a series of maps that I want to check against a lookup index and then filter the results. I’m setting a Boolean variable that only seems to get applied if I reference it within the then statement. I’ve tested the query in an earlier BaseX version (10.6), and it produces the expected result (without referencing the Boolean variable again).
Thanks in advance,
Tim
--
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
www.linkedin.com/in/timathompson<http://www.linkedin.com/in/timathompson>
timathom(a)protonmail.com<mailto:timothy.thompson@yale.edu>
Christian,
I really hope you will change your mind about this. In BaseX, as a function development environment, all structural constructs such as: “if then else” should be available as functions. Personally: as a functiondevelopmentjunky, I took a lot of effort replacing all ifThenElse-constructs into util:if-functions. I really would be disappointed if structural constructs aren’t available as functions in BaseX.
Hope you’ll change your mind about this point.
Regards,
Rob Stapper
Message: 4
Date: Tue, 21 Nov 2023 16:45:31 +0100
From: Christian Gr?n <christian.gruen(a)gmail.com>
To: Andy Bunce <bunce.andy(a)gmail.com>
Cc: BaseX <basex-talk(a)mailman.uni-konstanz.de>
Subject: Re: [basex-talk] BaseX 10.7 and util:if
Message-ID:
<CAP94bnMjeeXxsFBYVYjTJvJcSbGkzbxOnR99xNkpCv_oQ9GRWg(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
?thanks for the pointer. I?ve revised the documentation.
One property of util:if was that you could omit the argument for the else
branch. We decided to drop util:if, because the specification now provides
a new syntax for if expressions where the else branch is optional:
if ($test) { $then }
if ($test) { $then } else { $else }
The ternary operator was temporarily added to the spec as an official
feature, but we eventually dropped it again to reduce the number of
different notations for existing features (unfortunately, the popular A ? B
: C syntax was no option, as ? is already used for lookups).
Sent from Mail for Windows
From: basex-talk-request(a)mailman.uni-konstanz.de
Sent: Wednesday, November 22, 2023 12:00 PM
To: basex-talk(a)mailman.uni-konstanz.de
Subject: BaseX-Talk Digest, Vol 167, Issue 7
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com