Hi Josselin,
you get an error because there are elements containing several text nodes,
while the matches() function expects a single item. An element can contain
several text nodes for various reasons, as for example mixed content, which is
text with elements interspersed. In your case the in
A comment concerning the big picture.
I regard BaseX as an exquisite - and in many respects unique - platform of data
integration. Therefore I would consider the most flexible and unconstrained
support for XSLT 3 as a high priority, worth extra miles, if necessary.
Kind regards, Hans-Jürgen Renn
Hi Antonio,
my experience is very different - quite comparable performance, except for very
specific cases, e.g. massive use of fn:idref(). Furthermore, the performance of
BaseX is often so stupendous that an improvement by an order of magnitude (not
to mention two) appears to me very difficult
Dear Leo,
it is important to remember that serialization - the transformation of the
logical query result, which is an XDM value, into a sequence of octets - is
defined by a W3C spec [1], and this definition is extremely detailed and
precise.
The item separator parameter is applied when concate
basex
and copy lib and BaseX.jar to your project
* also replace the .bat and .sh files in bin if you did not edit them for say
more RAM or different port. if you edited them you need to move these changes
over.
Best regards
Am 01.02.2024 um 11:34 schrieb Hans-Juergen Rennau:
Dear BaseX people,
suddenly RESTXQ does not work any more on my machine. (Here, "suddenly" means
when using RESTXQ again after a pause of three months and having installed a
new BaseX version in the meantime, 11.0 beta.)
Any attempt to access a RESTXQ-defined URL produces a mysterious error messa
Hi Marco,
I've also taken a look at the code and I think the observed behaviour is in
accordance with the logic of the accumulator function (local:stand-totaal),
while this logic is probably not really what. First - why do you get the result
which you get?
(1) The logic of local:stand-totaal(a)
Dear Alexander,
"the best way out is always through", the American poet Robert Frost wrote, and
this certainly applies to understanding the semantics of FLWOR expressions in
general and the group by clause in particular. When you agree to go through the
abstract principle behind FLWOR expressio
-Juergen Rennau wrote:
Dear BaseX folks,
the documentation of the XSLT module says:
"Variables can be bound to a stylesheet via $arguments (only strings are
supported when using XSLT 3.0 and Saxon). "
That is a pity! Are there plans to remove this limitation?
Kind regards,Hans-Jürgen
enforce the
adoption of namespace declarations that are not required):
in-scope-prefixes($n) ! namespace {.} {namespace-uri-for-prefix(., $n)},
Best,Christian
On Wed, Sep 20, 2023 at 6:34 PM Hans-Juergen Rennau wrote:
Dear BaseX folks,
constructing elements, I encounter a problem with namespaces
Dear BaseX folks,
constructing elements, I encounter a problem with namespaces which I do not
understand. Is it a bug or do I overlook something?
To reproduce the problem you need to create an XML file "doc.xml" with this
content:
http://basex.org/simply/the/best";>
And here's t
Dear BaseX folks,
the documentation of the XSLT module says:
"Variables can be bound to a stylesheet via $arguments (only strings are
supported when using XSLT 3.0 and Saxon). "
That is a pity! Are there plans to remove this limitation?
Kind regards,Hans-Jürgen
Dear BaseX folks,
question: what is the recommended way of ensuring that an application calling
BaseX via command-line (basex ...) uses a certain strip whitespace mode (true
or false), if the application is deployed on servers with different BaseX
versions? Option -w cannot naively be used, as
A pity (for me), because I need to preserve the information about an element's
origin without changing the element by adding a clumsy @xml:base.
Out of luck.
Kind regards,Hans-Jürgen
Am Montag, 28. August 2023 um 16:11:56 MESZ hat Christian Grün
Folgendes geschrieben:
after manifold
e-uri($copy))
Could you please provide us with a little self-contained example?
Thanks in advance,Christian
On Thu, Aug 24, 2023 at 6:12 PM Hans-Juergen Rennau wrote:
Dear BaseX team,
I seem to remember that in earlier versions of BaseX a copy/modify/return did
not change the base URI of the processe
Dear BaseX team,
I seem to remember that in earlier versions of BaseX a copy/modify/return did
not change the base URI of the processed document. However, now it is lost, or
more precisely, replaced with the static base URI of the processing XQuery
module.
Am I mistaken? At any rate it would be
Greetings, Eliot,
could it be that the problem arises from repeated inclusion of one and the same
resource, which is referenced by different resources? You might check this by
determining the cumulative size of the resources to be potentially included. Is
it really >1 GB?
Even if you use a recu
A call from the backbench: I think it would be interesting to have such a
serialization option! The esthetic aspect of XML can be important, depending on
context. What we get without such an option looks like a heap of information.
Παῦλος
Am Dienstag, 14. Februar 2023 u
Most helpful, cordial thanks, Christian!
Kind regards,Hans-Jürgen
Am Donnerstag, 19. Januar 2023 um 16:19:08 MEZ hat Christian Grün
Folgendes geschrieben:
Hi Hans-Jürgen,
Here’s a minimized example that demonstrates how to set a custom text
encoding for your HTTP response:
declare
%
Thank you, Gerrit! I am not sure, though, that the remedy can be adapted to my
case. The encoding is a level deeper, so-to-speak, than the text of a document
type declaration. In your case, the solution is a manipulation of the contents
of a string, but the encoding is a different matter. I mea
I am the hare, BaseX the hedgehog, no matter how fast I run, BaseX is already
there.
Am Donnerstag, 12. Januar 2023 um 12:23:29 MEZ hat Christian Grün
Folgendes geschrieben:
Hi Hans-Jürgen,
For deleting resources of any type, the existing db:delete function
can be used [1].
Best,
Chr
Hello,
the documentation ( https://docs.basex.org/wiki/REST ) contains an example
applying a query via REST to a complete database:
http://localhost:8080/rest/database?query=count(.)
(My understanding is that "database" should be replaced with the name of a
database.)
However, the URL yields an
PS. Pardon - a correction. The first clause may also be a sliding window or a
tumbling window.
Am Dienstag, 20. Dezember 2022 um 08:44:02 MEZ hat Hans-Juergen Rennau
Folgendes geschrieben:
Thank you for your kind words, Gerrit! Until a few weeks ago, my use of
grouping was a groping
, Gerrit, le-tex
Folgendes geschrieben:
Thank you, Hans-Jürgen, for shedding really insightful light (if there
is such a thing) on this aspect of XQuery grouping, which I use
gropingly (pun intended) without fully understanding it.
On 19.12.2022 23:19, Hans-Juergen Rennau wrote:
> I
I think the reason is a different one - it is related to the precise semantics
of the group by clause.
The group by clause maps each group of input tuples with equal grouping key(s)
to a single output tuple, in which- the grouping variable(s) is/are bound to
the key values (as you would expect)
Hello, Alejandro,
perhaps it is interesting for you that there is a BaseX-based open source
project [1] supporting a free mixing of node tree and file system navigation,
using two different operators (/ for file system navigation, \ for node tree
navigation; they can be swapped, using option -
Hello,
I wonder what is the recommended way how to store text files in a database.
What occurs to me is the use of db:put-value / db:get-value: Storage:
db:put-value($db, $filePath ! file:read-text(.), $dbPath) Retrieval:
db:get-value($db, $dbPath)
Would you recommend a different approach
Hello,
I encountered a behaviour of full-text search which appears to me a bug:
(1) OKbasex "'adverse' contains text 'adverse' using stemming"
=> true
(2) NOTOKbasex "'adverse' contains text 'adverse' all words using stemming"=>
false
(3) NOTOKbasex "'adverse' contains text 'adverse' any word usi
Thank you for this clarification, Christian.
In my opinion, it is a pity that the functions file:children and
file:descendants do not return absolute paths - I see only disadvantages.
When the argument is a relative path, you get back relative paths which only
make sense in the context of the cu
3 MESZ hat Graydon
Folgendes geschrieben:
On Sun, Sep 25, 2022 at 10:04:51AM +, Hans-Juergen Rennau scripsit:
> Hi, Graydon,
Hello!
> you ask what I mean by "Providing the parameter value to file:children as a
> relative path".
>
> With "the pa
. September 2022 um 21:03:18 MESZ hat Graydon
Folgendes geschrieben:
On Sat, Sep 24, 2022 at 06:22:41PM +, Hans-Juergen Rennau scripsit:
> Maybe this is a misunderstanding, Graydon: the ability to use
> relative paths *as parameter value*, and to have it automatically
> res
Maybe this is a misunderstanding, Graydon: the ability to use relative paths
*as parameter value*, and to have it automatically resolved against the current
working directory, is certainly essential. But the *result* should be
independent of whether the parameter was supplied as relative or abs
Hi Eliot, a very general remark (not really related to BaseX logs, but logs in
general): I have practiced the following approach already a number of times,
doing everything with BaseX, as it goes without saying, and it has always been
very satisfying:
(1) Parse the log files into an XML represe
Phantastic - it could not be easier, just insert "update:" before "apply("!
That'sBaseX.
Cordial thanks!
Hans-Jürgen
Am Donnerstag, 28. Juli 2022 um 12:17:23 MESZ hat Christian Grün
Folgendes geschrieben:
Hi Hans-Jürgen,
> Therer seems to be a checking looking for an updating function,
Strong, strong backing from the Western Fankurve (the cheap places under no
roof and without seats) for Eliot's request! BaseX, we all know it, is a
miracle of data integration (once one has discovered the secret of json:doc(),
html:doc(), csv:doc()), and YAML is missing! I believe that it is f
-Juergen Rennau wrote:
>
> Dear BaseX people,
>
> extension function file:resolve-path() shows a behaviour which appears to me
> inconsistent and probably not intended:
>
> - if called with a single parameter, a path containing ".." is resolved as
> expected
>
Hi Graydon, probably I misunderstand you, but isn't
$node/count(preceding-sibling::*) + 1 what you need?Kind regards, Hans-Jürgen
Am Donnerstag, 30. Juni 2022, 17:21:34 MESZ hat Graydon Saunders
Folgendes geschrieben:
Hello --
I've got an element node that's part of a document. I nee
Well - but are such concerns related to using maps as the output? I do not
think so, and therefore I suggest to avoid mixing specific how-to's with
general challenges. By now you know the idiom how to construct maps
dynamically, as you had already known how to construct node trees dynamically.
Hi Markus, you wrote
"How would you determine where unexpected gaps occur?"
Gaps? First, to avoid a misunderstanding: whereas map keys must not be the
empty sequence, map values may.
An elegant way to construct map entries safely - taking care that the key is
not empty - is to use the map operat
Hi Markus,
although I do not quite understand your description (why should I care for the
representation of the map I construct?), it may be that one piece of
information is useful to you, as it is not obvious from the spec: it's about
how to construct a map dynamically, that is,
(1) when the
I agree with Florian that navigation of db contents is important and support
is desirable - perhaps in analogy to file:children and file:descendants. Kind
regards, Hans-Jürgen
PS: The same applies to the contents of archives.
Am Dienstag, 10. Mai 2022, 16:28:52 MESZ hat Florian Schmitt
Fol
Many thanks for checking, Christian! I'll study the spec and get back to you
should I come to a different conclusion.
Kind regards,Hans-Jürgen
Am Montag, 25. April 2022, 12:00:41 MESZ hat Christian Grün
Folgendes geschrieben:
Hi Hans-Jürgen,
PS: I think there is a bug concerning "dif
Excellent - I think this is a common interest of those developing solutions
based on BaseX.
And "as-a-service-optionally-local" might pass as a BaseX Solution design
pattern.
Hans-Jürgen
(PS Sometimes the most straightforward ideas come to mind last, or late.)
Am Dienstag, 22. März 2022,
Am Anfang war das Wort und nicht das Geschwätz, und am Ende wird nicht die
Propaganda sein, sondern wieder das Wort.
Gottfried Benn
Am Donnerstag, 24. Februar 2022, 12:11:23 MEZ hat Christian Grün
Folgendes geschrieben:
It’s a dire day. We wish safety and the rapid establishment of
) )
If you give file:children an absolute path, that will be included in results,
so just resolve the relative folder path first.
— Steve M.
On Feb 11, 2022, at 1:40 PM, Hans-Juergen Rennau wrote:
Dear BaseX people,
I have a feature request:
a function which does the same as file:list, but
path-to-uri(file:resolve-path($dir))) ! doc(.)
Then, *please* let us have this instead:
file:list2($dir, false(), $fname) ! doc(.)
Kind regards,Hans-Jürgen
Am Freitag, 11. Februar 2022, 20:06:44 MEZ hat Liam R. E. Quin
Folgendes geschrieben:
On Fri, 2022-02-11 at 18:40 +, Hans-Juergen
[ Just a shout from the cheap seats in the gallery. In my experience, the
order of attributes may have considerable esthetic value and may have impact on
the acceptance of a program. The order therefore does deserve attention, in
spite of its theoretical insignificance. Even more important than
://files.basex.org/releases/latest/
On Sun, Jan 30, 2022 at 11:48 PM Hans-Juergen Rennau wrote:
>
> Thank you, Christian, now I understand!
>
> Incidentally, nevertheless I am not sure the following behaviour is correct:
>
> basex "<_ xmlns='bar'
Thank you, Christian, now I understand!
Incidentally, nevertheless I am not sure the following behaviour is correct:
basex "<_ xmlns='bar'>{element foo {namespace {''} {'bar'}}}/*"=>
[XQDY0102] Duplicate namespace declaration: ''.
As the dynamic constructor is located in a static context with a d
Am Freitag, 7. Januar 2022, 08:54:25 MEZ hat Martin Honnen
Folgendes geschrieben:
Am 07.01.2022 um 08:39 schrieb Martin Honnen:
Am 07.01.2022 um 01:29 schrieb Hans-Juergen Rennau:
Hello,
I face a problem with RESTXQ of a fairly general character, as it seems to
me
And I would like to conclude this year with yet another thank you for a
fantastic product which in my professional life serves as a bicycle, a car, a
truck, a train, a ship, an airplane and a spacecraft - whatever it takes to
translate a mental move from A to B into practice.
Hans-Jürgen
Am
And I would like to conclude this year with yet another thank you for a
fantastic product which in my professional life serves as a bicycle, a car, a
truck, a train, a ship, an airplane and a space craft - whatever it takes to
translate a mental move from A to B into practice.
Hans-Jürgen
tion exists with a default value, the bound context item
> is replaced by this default value.
>
> This contrasts with the behavior of variable declarations, though, so
> I might check if we can align the behavior in one or the other way.
>
> Schöne Grüße
> Christian
[ Unasked for comment from the gallery - this series of "parsers" - which
hopefully will be further extended - is the reason because XQuery has a
revolutionary character, because it turns the wealth of structured information
surrounding us into a uniform and homogeneous substrate of information
Another Rolls-Royce of functionality stopped inaudibly at the curb under my
window.
Am Donnerstag, 19. August 2021, 14:22:42 MESZ hat Christian Grün
Folgendes geschrieben:
Dear all,
We provide you with a new and fresh version of BaseX, our open source
XML framework, database system a
documents in the same query is a great idea.Can it treat stdin as one of those
resources?I suppose on unix you can use the special /dev/stdin path.
Regards,Iwan
On Wed, 23 Jun 2021, 00:42 Hans-Juergen Rennau, wrote:
Good evening, Iwan,
I think your ideas are very interesting, and they are about
Good evening, Iwan,
I think your ideas are very interesting, and they are about unleashing a
considerable potential. Your basexsed sketch could also be summarized liks
this: look, here's an expression E (or a query file Q); and there's a selection
of resources R - why should I say more in order
Indeed - common sense & top flexibility!
Am Samstag, 12. Juni 2021, 16:45:05 MESZ hat Marco Lettere
Folgendes geschrieben:
Thank you! I didn't want to disturb your weekend though Top quality BaseX
service! 😁🤩
Il sab 12 giu 2021, 16:37 Christian Grün ha scritto:
Grazie, Marco.
Y
21 at 12:56 PM Hans-Juergen Rennau wrote:
>
> Hi Christian, I had myself wondered if there is a database secretly involved.
> So I had checked that - there is no such database.
>
> Today I have already exploited the feature in serious, writing the query
> below, which does a li
.
Best,
Christian
On Fri, Apr 9, 2021 at 8:54 PM Hans-Juergen Rennau wrote:
>
> Hello, I would like to let you know that just as there is matter and anti
> matter, there are bugs and anti bugs. An anti bug is when something works
> which cannot possibly work. I am not surprised
Hello, I would like to let you know that just as there is matter and anti
matter, there are bugs and anti bugs. An anti bug is when something works which
cannot possibly work. I am not surprised that the first anti bug detected (by
me) is a BaseX one.
The following invocation
basex "doc('resu
BaseX = quality
Am Mittwoch, 7. April 2021, 12:25:37 MESZ hat Christian Grün
Folgendes geschrieben:
Hi Julia,
Thanks for the comprehensive background information and the references
to our documentation.
Your assumption that the MAXLEN value should be preserved in an
existing database
e use of a character map
(very similar to Gerrit’s suggestion):
serialize(/, map {
'method': 'json',
'use-character-maps': map { '/': '/' }
})
On Mon, Mar 22, 2021 at 2:19 PM Hans-Juergen Rennau wrote:
>
> Oh, thank you, Christian - only no
ut?
Best,
Christian
>
> But as the use of fn:serialize is a work around, the matter is not urgent.
> Thanks, Gerrit!
>
> Kind regards,
> Hans
>
> Am Montag, 22. März 2021, 08:49:59 MEZ hat Imsieke, Gerrit, le-tex
> Folgendes geschrieben:
>
>
> What’s wrong wi
s.
>
> Kind regards,
> Hans-Jürgen
>
> PS: Default parser behaviour is perfect, as it is: every JSON character
> is represented by the same Unicode character, e.g. \" becomes ", \/
> becomes /, \n becomes
.
>
> Am Sonntag, 21. März 2021, 19:25:25 MEZ hat Liam
ind regards,Hans-Jürgen
PS: Default parser behaviour is perfect, as it is: every JSON character is
represented by the same Unicode character, e.g. \" becomes ", \/ becomes /, \n
becomes
.
Am Sonntag, 21. März 2021, 19:25:25 MEZ hat Liam R. E. Quin
Folgendes geschrieben:
On Sun,
nd regards,Hans-Jürgen
Am Sonntag, 21. März 2021, 18:08:14 MEZ hat Liam R. E. Quin
Folgendes geschrieben:
On Sun, 2021-03-21 at 09:42 +0000, Hans-Juergen Rennau wrote:
>
> PPS: Please do not even dream of thinking about considering or not
> excluding to change the parsers beh
aping:
https://www.mhonarc.org/archive/html/xsl-list/2019-10/msg00078.html
Gerrit
On 20.03.2021 11:11, Hans-Juergen Rennau wrote:
> Dear BaseX team,
>
> there is something I don't understand about the parsing/serializing of JSON.
>
> When I
Dear BaseX team,
there is something I don't understand about the parsing/serializing of JSON.
When I serialize a document without options, backslashes are escaped. So for
example ...
https://help.openconnectors.ext.hana.ondemand.com/home/google-analytics
becomes"url":"https:\/\/help.openconnect
Hi, Christian, I am not qualified to speak about these things, being a Windows
user and without a clue concerning all those Unix things. My naive perspective
is this: as a Windows user, everything is wonderfully simple - download the
installer, click, click, click. done. But with Unix, it seems
Should this perhaps be part of the official documentation? Especially
installation and upgrade deserve maximum attention and helpfulness.
Am Mittwoch, 17. März 2021, 18:07:38 MEZ hat Bridger Dyson-Smith
Folgendes geschrieben:
Hi Joris,
On Wed, Mar 17, 2021 at 5:39 AM commandline-be
Speed + reliability + standard conformance + XXXL kit of extensions = BaseX
(Plus a team which could not be more responsive and helpful.)
Have I forgotten anything?
Thank you.
Am Donnerstag, 25. Februar 2021, 13:29:48 MEZ hat Marco Lettere
Folgendes geschrieben:
Really excited!
Thank y
Graydon, spread the word!
Am Donnerstag, 12. November 2020, 13:59:12 MEZ hat Graydon
Folgendes geschrieben:
On Thu, Nov 12, 2020 at 11:58:29AM +0100, Christian Grün scripsit:
> Gerrit has already mentioned fingerprinting techniques. If your time
> is limited, it may be sufficient to ap
[Protocol: applause from a backbencher]
Am Sonntag, 1. November 2020, 14:07:56 MEZ hat James Ball
Folgendes geschrieben:
Hi Christian,
I never cease to be amazed by the speed you manage to find and fix these - at
least me me - obscure bugs.
I have downloaded the snapshot and I’m now
PS: Rob - so do I.
Am Montag, 31. August 2020, 12:13:02 MESZ hat RobStapper
Folgendes geschrieben:
#yiv1151269877 #yiv1151269877 -- _filtered {} _filtered {} _filtered
{}#yiv1151269877 #yiv1151269877 p.yiv1151269877MsoNormal, #yiv1151269877
li.yiv1151269877MsoNormal, #yiv1151269877 d
Dear BaseX team,
it's really great that now we have functions json:doc(), csv:doc() and
html:doc(). In my opinion it becomes increasingly obvious that BaseX is a
powerful data integration platform.
Perhaps you will also add the corresponding xxx:doc-available() functions?
Kind regards,Hans-Jürg
Remark: support for a roundtrip-able XML representation of YAML would
consolidate BaseX's great position as a data integration platform, further
increasing the number of continents (mediatypes) which can be travelled on the
highway of XPath (XML, JSON, CSV, HTML, YAML).
In comparison, I think,
[off topic] Other people talk of agility, BaseX does it: BaseXity.
Am Sonntag, 26. April 2020, 11:50:24 MESZ hat Christian Grün
Folgendes geschrieben:
Hi Arjan,
The bug came in when we changed the error codes of db:open for
non-existing documents (maybe that already happened with 9.0.
Hi Luke, I would like to emphasize (or simply remind you) of two key features
of XPath (and XML technology in general). The FIRST one is that treating the
information in a single document or in a collection of documents or a
collection of document fragments is identical. So, for example, $data/
How very interesting, Luke! Answers will come from other people, but may I ask
a question?
Which is this: are you only interested in checks of referential constraints
performed as guards, before insertion, or would it be at least of some value to
have possibilities of analyzing existing db cont
Hi Jordan, without looking more closely, I suppose the problem is that you
incidentally put a slash in front of predicates, e.g.
packagedElement/[@xmi:id=$currID]/ownedAttribute...
while you probably wanted to say
packagedElement[@xmi:id=$currID]/ownedAttribute...
Apart from not expressin
Time and again I am amazed by the immediacy with which the BaseX team seizes
opportunities for instantaneous improvement. The obsessive idea of agility,
bugging ten-thousands of developing and managing heads, is dwarfed by the
practice of BaseX.
Am Donnerstag, 14. Februar 2019, 14:38:07 ME
div.yiv5615938040WordSection1 {}#yiv5615938040
With 1.1, I found that validate:xsd() requires you to explicitly give ‘1.1’ as
third parameter.
Having vs:minVersion is not being honored by BaseX.
Daniel
Von: Hans-Juergen Rennau [mailto:hren...@yahoo.de]
Gesendet: Dienstag, 22. Januar 2019 15:15
An
Dear BaseX team,
trying to use XSD 1.1, I encounter a problem.
As indicated in the documentation, I added to the lib folder the jar files from
the newest Xerxes distribution (Xerces-J-bin.2.12.0-xml-schema-1.1.zip,
download from http://xerces.apache.org/mirrors.cgi#binary ).
The problem: when usi
Dear BaseX team,
I face an issue with fn:generate-id.
Given: a document $doc parsed from the file system.Nodes obtained by
xquery_eval(EXPR, map{'':$doc}) and nodes obtained by $doc/EXPR
have the same identity (per $node1 is $node2), but the values generated by
fn:generate-id differ.
Interes
Dear BaseX team,
"whitespace chopping" (which happens by default unless command-line option -w
is used) does not only remove "whitespace-only" text nodes, but also
leading/trainling whitespace in element content, for example:
doc.xml: BaseX is phantastic!
basex -i doc.xml .
=>
BaseX is phan
cannot be overestimated.
Kind regards,Hans-Jürgen
Liam R. E. Quin schrieb am 22:02 Samstag, 26.August 2017:
On Sat, 2017-08-26 at 13:53 +, Hans-Juergen Rennau wrote:
> I find the W3C-defined format obtained from fn:json-to-xml
> unnatural and unpractical;
It is, but it works
Hi Günter, have you considered using
json:parse
instead? I find the W3C-defined format obtained from fn:json-to-xml unnatural
and unpractical; whereas BaseX-defined json:parse produces a very elegant,
intuitive and natural representation of the content - turning JSON documents
into near-e
Dear BaseX team,
if you are interested in further boosting the power of BaseX as a resource
monitoring tool, you might consider the tiny, yet useful extension described
below.
Currently we have various functions for parsing non-XML formats into node
trees: json:parse($text ...) csv:parse($te
Dear BaseX team,
if you are interested in further boosting the power of BaseX as a resource
monitoring tool, you might consider the tiny, yet useful extension described
below.
Currently we have various functions for parsing non-XML formats into node
trees: json:parse($text ...) csv:parse($te
To put it mildly, I disagree. I think the greatest mistake one can make is call
XQuery a query language. I prefer to say that it is an information language. If
this appears to be an incomprehensible statement, this reflects the novelty of
the concept of an "information language". A book should b
Dear BaseX team -
no bug, no question, no feature request - only the urge to thank you for your
work.
About a year ago I embarked on a piece of research work which has kept me busy
and excited ever since. This work is important to me because so much seems to
go into it, of what I have come to th
Dear BaseX team,
a question concerning the reading of archive files (e.g. .zip) via
archive:entries.
If I don't overlook something, the read function archive:entries returns one
per file contained in the archive. Folders containing files
(directly or recursively) can be inferred, but empty fold
Marco, I've faced the same problem and frustration, and I agree that it would
be great if BaseX could be used for such tasks. Strengthening its potential
role as a data integration engine.Kind regards,Hans
Marco Lettere schrieb am 10:57 Freitag, 11.November
2016:
Hi all,
I'm current
Dependent on your goals, perhaps variations on the theme of a sorted list of
all data paths might be useful? For example: considering the paths of all
simple elements and attributes, including indexes, and representing text
content as an appended last "step" - à la /a[1]/b[2]/c[2]#my text value.
Cordial thanks, Liam - I was not aware of that!
@Joe: Rule of life: when one is especially sure to be right, one is surely
wrong, and so was I, and right were you(r first two characters).
Liam R. E. Quin schrieb am 5:54 Montag, 12.September 2016:
Hans-Jürgen, wrote:
! Already the first
ose? It may not give us a full-featured CSV parser, but would handle
reasonably uniform cases.
Joe
Sent from my iPhone
On Sun, Sep 11, 2016 at 3:39 PM -0400, "Hans-Juergen Rennau"
wrote:
Joe, concerning your regex, I would complain, too! Already the first two
characters
Joe, concerning your regex, I would complain, too! Already the first two
characters
(?render the expression invalid:(1) An unescaped ? is an occurrence
indicator, making the preceding entity optional(2) An unescaped ( is used for
grouping, it does not repesent anything
=> there is no entity
Alexander Holupirek schrieb am 11:00 Freitag,
9.September 2016:
> On 08.09.2016, at 23:17, Hans-Juergen Rennau wrote:
>
> Dear BaseX team,
>
> is this a bug?
>
> serialize( )
>
> returns
>
>
>
> I need my blanks!
>
> Hans-
Dear BaseX team,
is this a bug?
serialize( )
returns
I need my blanks!
Hans-Jürgen
1 - 100 of 191 matches
Mail list logo
