BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

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

java.io.IOException: Das Handle ist ungültig
by Bodo Hüsemann 18 Jun '12

18 Jun '12

Hi, the following xquery (BaseX721, Java, embedded server): for $guildchar in collection('default')/apiresponse/guild[@name="Guild"]/characters/character return for $detailchar in collection('default')/apiresponse/character where $detailchar/@name=$guildchar/@name return $detailchar produces the exception: java.io.IOException: Das Handle ist ungültig java.io.RandomAccessFile.seek(Native Method) org.basex.io.random.TableDiskAccess.readBlock(TableDiskAccess.java:519) org.basex.io.random.TableDiskAccess.readIndex(TableDiskAccess.java:502) org.basex.io.random.TableDiskAccess.cursor(TableDiskAccess.java:481) org.basex.io.random.TableDiskAccess.read1(TableDiskAccess.java:189) org.basex.data.Data.kind(Data.java:293) org.basex.query.item.DBNode$4.next(DBNode.java:350) org.basex.query.path.IterStep$1.next(IterStep.java:44) org.basex.query.iter.NodeIter.next(NodeIter.java:1) org.basex.query.path.IterPath$1.next(IterPath.java:64) org.basex.query.iter.NodeIter.next(NodeIter.java:1) org.basex.query.flwor.For$1.next(For.java:85) org.basex.query.flwor.FLWR$1.next(FLWR.java:63) org.basex.query.expr.Constr.add(Constr.java:63) org.basex.query.expr.CElem.item(CElem.java:82) org.basex.query.expr.CElem.item(CElem.java:1) org.basex.query.expr.CFrag.item(CFrag.java:1) org.basex.query.expr.ParseExpr.value(ParseExpr.java:66) org.basex.query.QueryContext.value(QueryContext.java:286) org.basex.query.func.UserFunc.value(UserFunc.java:153) org.basex.query.QueryContext.value(QueryContext.java:286) org.basex.query.func.TailFuncCall.value(TailFuncCall.java:46) org.basex.query.QueryContext.value(QueryContext.java:286) org.basex.query.func.UserFunc.value(UserFunc.java:153) org.basex.query.QueryContext.value(QueryContext.java:286) org.basex.query.func.BaseFuncCall.value(BaseFuncCall.java:55) org.basex.query.func.BaseFuncCall.iter(BaseFuncCall.java:68) org.basex.query.QueryContext.iter(QueryContext.java:275) org.basex.query.QueryContext.iter(QueryContext.java:229) org.basex.query.QueryProcessor.iter(QueryProcessor.java:74) org.basex.server.QueryListener.execute(QueryListener.java:122) org.basex.server.ClientListener.query(ClientListener.java:463) org.basex.server.ClientListener.run(ClientListener.java:148) The Query is doing ok in the BaseX Gui but fails in my Application (other queries are running like a charm). Reformulations or similar variants of the query fail the same way. Do you have a hint what could be wrong here? What should I try next? Thanks a lot for this great xml db! Best regards, Bodo

2 1

XML element case sensitivity
by David Leigh 17 Jun '12

17 Jun '12

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

REST service : How to run server side query with params?
by Anupam Bakshi 17 Jun '12

17 Jun '12

Hello, I understand that one way to run a rest based XQuery with parameters is to use the following ... http://localhost:8984/rest/DB/mult.xq?a=21&b=2 This is possible if the query is in the BaseX database. I need to use REST, but the query file (.xq) and .xqm, .xsl files need to be located on the server but not in the database. Can someone give me a pointer about how to do that? Thanks, Anupam

3 4

Bug by saving a big result file (4,2MO)
by Maud Ingarao 16 Jun '12

16 Jun '12

Hello I am generating quite big files from quite big xml datasources using xquery in BaseX (local). Everything works fine (5,8 minutes processing, but fine ;) But saving the file result is impossible : the GUI freezes and the file remains empty. When I generate the same file using XSLT in Saxon-B, it's a little bit longer but in the end, I get my 4,2MO result file. Have a nice day :) Maud -- Maud Ingarao IHPC (UMR 5037) Institut d’histoire de la pensée classique, de l’Humanisme aux Lumières Ecole Normale Supérieure de Lyon - Site Descartes - Bureau R322 15 Parvis René Descartes - BP7000 - 69342 Lyon CEDEX 07 +33 4 37 37 65 79 - maud.ingarao(a)ens-lyon.fr cerphi.ens-lyon.fr - pensee-classique.ens-lyon.fr institutdesanti.ens-lyon.fr - hyperdonat.ens-lyon.fr mutec-shs.fr - projet-plume.org - ahn.ens-lyon.fr http://www.cahier.paris-sorbonne.fr/ - je suis absente le vendredi - out of office on Fridays -

2 1

XML element case sensitivity
by David Leigh 16 Jun '12

16 Jun '12

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 <mailto:david@leighweb.com> DavidEmailSig

3 2

puzzle over namespace qualification and absolute vs. relative location paths
by C. M. Sperberg-McQueen 16 Jun '12

16 Jun '12

An unexpected phenomenon has arisen in the XQuery course I'm teaching today and tomorrow; I wonder if anyone on this list can shed any light on it. To reproduce: 1 build a database containing the document http://blackmesatech.com/2012/06/data/sonnet92.xml 2 evaluate the following expressions (a) . (displays the entire document) (b) ./* (ditto) (c) declare namespace n = "http://www.tei-c.org/ns/1.0"; ./n:TEI (again returns entire document) This one didn't surprise me; it's what I expected. (d) /TEI (ditto) This one surprised me, since the TEI element in the document is namespace-qualified, and I would not have expected the expression to match anything. At this point, I would be tempted to say "well, maybe when we built the database, BaseX set the default element namespace in the static context to the TEI namespace." That would explain the evaluation of this expression. But ... (e) ./TEI (returns nothing) If the default element namespace in the static context were the TEI namespace, I would expect this to work. If it were NOT the TEI namespace, I would expect (d) to fail. I'm having trouble explaining to the participants in my course (or to myself) why expressions (d) and (e) return different results. What am I missing? best regards, Michael Sperberg-McQueen

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk