BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

Many XML with the same path
by Henrique Oliveira 20 Jun '12

20 Jun '12

Hi guys, Why am I able to add/store several XML with the same path? <rest:database xmlns:rest="http://basex.org/rest" name="TRADES" resources="9 "> <rest:resource type="xml" content-type="application/xml" size="3"> henrique.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique1.xml</rest:resource> <rest:resource type="xml" content-type="application/xml" size="3"> henrique2.xml</rest:resource> <rest:resource type="raw" content-type="application/xml" size="21"> henrique2.xml</rest:resource> <rest:resource type="raw" content-type="application/xml" size="21"> henrique3.xml</rest:resource> </rest:database> -- Henrique Oliveira

2 6

Install issues
by André Milton 20 Jun '12

20 Jun '12

Hi guys, I'm having a hell of a time trying to install BaseX on CentOS with Yum. It says I'm missing xml-commons-resolver 1.2 and lucene-contrib: Resolving Dependencies --> Running transaction check ---> Package basex.noarch 0:7.2.1-3.2 set to be updated --> Processing Dependency: xml-commons-resolver = 1.2 for package: basex --> Processing Dependency: lucene-contrib for package: basex --> Processing Dependency: jline for package: basex --> Running transaction check ---> Package basex.noarch 0:7.2.1-3.2 set to be updated --> Processing Dependency: xml-commons-resolver = 1.2 for package: basex --> Processing Dependency: lucene-contrib for package: basex ---> Package jline.noarch 0:0.9.94-0.9.el5_6 set to be updated --> Finished Dependency Resolution basex-7.2.1-3.2.noarch from home_basex_opensuse has depsolving problems --> Missing Dependency: xml-commons-resolver = 1.2 is needed by package basex-7.2.1-3.2.noarch (home_basex_opensuse) basex-7.2.1-3.2.noarch from home_basex_opensuse has depsolving problems --> Missing Dependency: lucene-contrib is needed by package basex-7.2.1-3.2.noarch (home_basex_opensuse) Error: Missing Dependency: xml-commons-resolver = 1.2 is needed by package basex-7.2.1-3.2.noarch (home_basex_opensuse) Error: Missing Dependency: lucene-contrib is needed by package basex-7.2.1-3.2.noarch (home_basex_opensuse) I've downloaded both and added them to a CLASSPATH but the install script still complains. What step have I missed? Do I also need to add them to my PATH (would prefer not to)? Thanks! a+,a.

2 1

Java method signature: no empty sequence allowed
by Mattijs Ugen 20 Jun '12

20 Jun '12

Dear all, Calling methods from a QueryModule works nicely, yet I can't seem to get a particular method signature to work from XQuery. The function in question should be passed a string and the result of a path expression, yielding attribute values as strings. For example: ns:method($value, $context/ancestor-or-self::*/@some-attr/string()) Intuitively, I figure the signature for this method in the QueryModule should be: public String method(Str previous, Value additionals) { ... However, trying to use this method with BaseX won't work. The query editor accepts the syntax, but states "PXML:combine method: no empty sequence allowed". Changing the signature to Seq, ItemSeq or even Empty changes nothing; it keeps telling me (I think) the expression *could* yield an empty sequence and the method does not support it (even tho Empty is a valid value for Value, is it not?). How would I define my method so that BaseX will accept it? Kind regards, Mattijs Ugen

2 5

Basex + rdbms
by Henrique Oliveira 20 Jun '12

20 Jun '12

Hi, How hard to implement a data layer to use a RDBMS as a storage? e.g. Oracle, Postgre Regards -- Henrique Oliveira

3 2

BaseX has been updated on Filecluster.com
by FileCluster Support 19 Jun '12

19 Jun '12

Dear Developer, You have received this email because we have updated BaseX and this was the contact email for the application. Your application update status BaseX has been updated on FileCluster.com to the 7.3 version. You can check out your application on our site at: http://www.filecluster.com/Business-Office/Database-Management/Download-Bas… If you want to let your users know about your software page on FileCluster.com, to rate it and review it, you can also use this banner to link it: Promote your software As a software website, it`s our duty to help the developers promote their software. Fortunatelly, our software promotions are cost free, for more informations please visit our promotion page. Submit your press releases We are also accepting press releases from software developers. All you have to do is to submit your press release and we will take care of the rest. Useful developer links All the essential links you need as a developer on FileCluster.com: Link to us - download banners or text links for linking to FileCluster.com Submit your software - Submit your software via PAD or manually Submit your press release - submit your press releases using our online form Contact Us - contact our editors Promote your software - our promotions page If you do not wish to receive any further notifications or confirmations from FileCluster.com, please send us an email and request a contact removal (email removal). Keep in mind that this means you will not receive ANY contact from us, including: software promotions, update confirmations or security alerts (antivirus and spyware test results). Regards, Renta Cezar - Senior Editor FileCluster Labs www.filecluster.com

1 0

Re: [basex-talk] XML element case sensitivity
by David Leigh 18 Jun '12

18 Jun '12

Ok, getting a little farther but need some assistance. I'm running this command to set the node case to lower case via the command processor. It's works great in the gui but now I need to adapt it for command line execution. I tried: for $i in //* return rename node $i as lower-case(name($i)) and got: Error: Stopped at line 1, column 14: [XPDY0002] No context item set for 'root()'. Thinking that, like for my queries, I needed to specify the database, I tried: for $i in collection("OpenSongSearch") return rename node $i as lower-case(name($i)) and got: Error: Stopped at line 1, column 84: [XUTY0012] Single element, attribute or pi expected as rename target. Any clues as to what I'm doing wrong? Thanks for your help! David <mailto:david@leighweb.com> DavidEmailSig From: David Leigh [mailto:david@leighweb.com] Sent: Monday, June 18, 2012 07:49 PM To: 'basex-talk(a)mailman.uni-konstanz.de' Subject: RE: [basex-talk] XML element case sensitivity Oops.didn't look at it closely enough. Of course it changes all the nodes. It's also fast so it will work perfectly. Thanks! <mailto:david@leighweb.com> DavidEmailSig From: David Leigh [mailto:david@leighweb.com] Sent: Sunday, June 17, 2012 09:28 PM To: 'basex-talk(a)mailman.uni-konstanz.de' Subject: [basex-talk] XML element case sensitivity Jens, Could I do this right after database creation and it would actually CHANGE the node names so that my queries could all still references the lower case node names? (that's what it looks like it's doing but I just wanted to confirm it). I need to do it for 3 node names, can it be done in one "for" loop? I don't mind taking the hit at database creation time as opposed to query time. Thanks! David *********************************************************************** Hi David, for preprocessing you could use something like for $i in //* return rename node $i as lower-case(name($i)) to rename all nodes to their lower-case equivalent. If you only want to process lyrics-nodes of all variations, insert Dirk's predicate to `//*`. Sadly the full-text index which offers case insensitivity doesn't include tag names, so you can't use this either. Kind regards from Lake Constance, Germany, Jens -- Jens Erat [phone]: tel:+49-151-56961126 [mail]: mailto:email at jenserat.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> [jabber]: xmpp:jabber at jenserat.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> [web]: http://www.jenserat.de PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B Am 16.06.2012 um 16:46 schrieb Dirk Kirsten: > There are functions like lower-case() and upper-case(). So you could do something like this > > //*[lower-case(name(.)) = "lyrics"] > > However, I guess it could result in a decreased performance. Therefore it might be reasonable to do this in some kind of preprocessing, if it is relevant for your use-case. > > cheers, > Dirk > > > On 06/16/2012 03:51 PM, David Leigh wrote: >> I've been searching in the BaseX docs online and can't seem to find >> reference to what I'm seeing. It may be common knowledge in the XML >> community but I'm not highly skilled in XML. >> >> Here's my issue: >> >> I have XML files that I'm loading into my database where there is >> inconsistency in the case (capital vs. lower-case) of the tag names (XML >> elements I think?). For instance, I have a tag named "lyrics" and >> sometimes in the files (whose source is not necessarily under my >> control) that will be <lyrics> and sometimes <Lyrics>. It could of >> course, by someone's error also be <lYrIcS> or any other weird >> combination. Is there a way, either at database creation or via some >> option or at query time to say that "lyrics" = "Lyrics" = "LyRics", etc. >> i.e. to be case insensitive for the XML tag names? >> >> Thanks! >> >> David >> >> DavidEmailSig <mailto:david at leighweb.com <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> > >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk <mailto:david@leighweb.com> DavidEmailSig

2 1

Nowa wiadomość
by DARIUSZ TRZASKA 18 Jun '12

18 Jun '12

We think you may be delighted to visit our website www.targipolitalia.com free registration gives you the option of advertising and can make a company successful. You may also want the ability to place advertisements in various languages, for such as looking for an investor, partner, etc... We propose to all companies, new: VIRTUAL GARDEN SHEDS, where you can submit videos and pictures that allow you to present your company's products and services. Please note that your e-mail was obtained directly from your website or databases accessible to the public. If it is placed on multiple pages, you can resubmit our investigation. In this case, ignore this message. This message is are quest for permission to send information and does not constitute an offer within the meaning of the Electronic Services Act of 18 July 2002 (OJ No 144, pos.1204) and is consistent with the legal interpretation of the Office of Competition and Consumer. I salute ORGANIZERS INVITE

1 0

Re: [basex-talk] XML element case sensitivity
by David Leigh 18 Jun '12

18 Jun '12

Oops.didn't look at it closely enough. Of course it changes all the nodes. It's also fast so it will work perfectly. Thanks! <mailto:david@leighweb.com> DavidEmailSig From: David Leigh [mailto:david@leighweb.com] Sent: Sunday, June 17, 2012 09:28 PM To: 'basex-talk(a)mailman.uni-konstanz.de' Subject: [basex-talk] XML element case sensitivity Jens, Could I do this right after database creation and it would actually CHANGE the node names so that my queries could all still references the lower case node names? (that's what it looks like it's doing but I just wanted to confirm it). I need to do it for 3 node names, can it be done in one "for" loop? I don't mind taking the hit at database creation time as opposed to query time. Thanks! David *********************************************************************** Hi David, for preprocessing you could use something like for $i in //* return rename node $i as lower-case(name($i)) to rename all nodes to their lower-case equivalent. If you only want to process lyrics-nodes of all variations, insert Dirk's predicate to `//*`. Sadly the full-text index which offers case insensitivity doesn't include tag names, so you can't use this either. Kind regards from Lake Constance, Germany, Jens -- Jens Erat [phone]: tel:+49-151-56961126 [mail]: mailto:email at jenserat.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> [jabber]: xmpp:jabber at jenserat.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> [web]: http://www.jenserat.de PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B Am 16.06.2012 um 16:46 schrieb Dirk Kirsten: > There are functions like lower-case() and upper-case(). So you could do something like this > > //*[lower-case(name(.)) = "lyrics"] > > However, I guess it could result in a decreased performance. Therefore it might be reasonable to do this in some kind of preprocessing, if it is relevant for your use-case. > > cheers, > Dirk > > > On 06/16/2012 03:51 PM, David Leigh wrote: >> I've been searching in the BaseX docs online and can't seem to find >> reference to what I'm seeing. It may be common knowledge in the XML >> community but I'm not highly skilled in XML. >> >> Here's my issue: >> >> I have XML files that I'm loading into my database where there is >> inconsistency in the case (capital vs. lower-case) of the tag names (XML >> elements I think?). For instance, I have a tag named "lyrics" and >> sometimes in the files (whose source is not necessarily under my >> control) that will be <lyrics> and sometimes <Lyrics>. It could of >> course, by someone's error also be <lYrIcS> or any other weird >> combination. Is there a way, either at database creation or via some >> option or at query time to say that "lyrics" = "Lyrics" = "LyRics", etc. >> i.e. to be case insensitive for the XML tag names? >> >> Thanks! >> >> David >> >> DavidEmailSig <mailto:david at leighweb.com <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> > >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de <https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk <mailto:david@leighweb.com> DavidEmailSig

1 0

Re: [basex-talk] BaseX 7.2.1, lab diary
by Christian Grün 18 Jun '12

18 Jun '12

Hi Neven, thanks for your efforts! I'm forwarding your notes to our basex-talk mailing list (hope that’s ok with you). Currently, we don't have any section on external tutorials in our Wiki, but I'll have some thoughts about that, and give you an update soon. Enjoy 7.3, Christian ____________________________________ > my name is Neven Jovanovic, I work at the Department of Classical > Philology, University of Zagreb. I started exploring the possibilities > of BaseX because we have collected various bibliographical and > prosopographical data (on people from Croatia who wrote in Latin), > encoding it in TEI XML, and eventually we would like to publish it and > use the data for research. > > My "lab notes" can be found here: > <http://www.ffzg.unizg.hr/klafil/dokuwiki/doku.php/z:basex-adv>. I > think that there are certain points which would be useful to let > beginners know (especially the "*:" notation for search over several > files in the same collection). If the BaseX team agrees, some of the > notes could be published on your wiki; in that case, please think > about a logical place where to put it. > > And thank you very much for developing BaseX -- the fact that I, who > am not a programmer, was able to use it almost immediately, at least > on my computer (for publication over the internet I will have to look > for some help), is very reassuring. I think you have made a good > thing. > > Best, > > Neven

1 0

Release BaseX 7.3
by Christian Grün 18 Jun '12

18 Jun '12

Hi everyone, we are glad to announce a great new release of BaseX, our XML database and XPath/XQuery 3.0 processor! Here are the latest features; - Many new internal XQuery Modules have been added, and existing ones have been revised to ensure long-term stability of your future XQuery applications: http://docs.basex.org/wiki/Module_Library - A new powerful Command API is provided to specify BaseX commands and scripts as XML: http://docs.basex.org/wiki/Commands#Basics - The full-text fuzzy index was extended to also support wildcard queries: http://docs.basex.org/wiki/Full-Text - The simple map operator of XQuery 3.0 gives you a compact syntax to process items of sequences: http://docs.basex.org/wiki/XQuery_3.0 - BaseX as Web Application can now start its own server instance: http://docs.basex.org/wiki/Web_Application - All command-line options will now be executed in the given order: http://docs.basex.org/wiki/Startup_Options - Charles Foster's latest XQJ Driver supports XQuery 3.0 and the Update and Full Text extensions: http://xqj.net/basex/ As usual, your feedback is welcome. More infos can be found on http://basex.org. For those of you in the Northern Hemisphere, we wish you a nice summer! No worries, we'll stay busy.. Christian BaseX Team, 2012

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk