BaseX-Talk

basex-talk@mailman.uni-konstanz.de

9 participants
5241 discussions

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

(Newbie alert) I just discovered BaseX. Congratulations and big thanks to the authors and all involved! I have been investigating a LOT of alternatives (programming languages, OSs, toolkits, etc.) and have concluded that the best approach for my application (XML read-only) is to use XPath (plus some XQuery). I have found some introductory examples written in C++ (Xerces) where the authors go through all kinds of complex convolutions to redirect the result of the XPath query to the screen. I hate to state the obvious, but we newbies do not want to send the XML elements to the screen. We rather assign them to some variable. That is the request I have. I think the application "QueryExample" and similar could use some way to assign the retrieved values to a variable. Thanks again! -Ramon (I am not in this mailing list)

1 0

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

1 0

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

1 0

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

1 0

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

1 0

Suggestion about the tutorial examples
by ramon＠patriot.net 09 Oct '10

09 Oct '10

1 0

XML catalog support
by Imsieke, Gerrit, le-tex 08 Oct '10

08 Oct '10

Dear BaseX Team, I think I asked this a couple of months ago. We'd like to have XML catalog support when importing files into BaseX. Or do you have another solution for the following issues: 1. - a customer uses XHTML documents enriched with some semantic tagging which is not XHTML markup - they refer to an XHTML DTD though - we need to use the DTD for resolving entities Apart from the fact that it is obnoxious to retrieve the DTDs from W3C (and will be blocked if tried to heavily), the major advntage of catalogs will be that we can point BaseX to a modified XHTML DTD that is stored locally and that allows for the additional semantic tags. => alternative approach: Patch the data to use standard XHTML markup (such as <span class='supersemantic'>). This doesn't seem feasible because too many tools down the processing chain depend on these custom tags. => other approach: resolve all entities prior to import, discard DOCTYPE declaration. We can do that, but it seems second-best to using catalogs and unmodified data. => Patch data to refer to another DOCTYPE stored somewhere on their servers. This is clearly advisable, because these documents aren't XHTML documents. Need to install the necessary infrastructure. Catalogs are still desirable in this scenario 2. Some of their XML files refer to DTDs such as E:\book\book.dtd We need to resolve these to a DTD that is stored on the server where the import takes place. Again, we could patch the data to refer to some DTD stored centrally on one of their corporate HTTP servers Still, in order to speed up parsing, locally stored DTDs are desirable. I remember when I proposed to use Apache XML commons resolver [1,2] that Christian replied you would put it on the wish list. I'm trying to prioritize this issue. (N.B.: it's the same customer who paid someone of your team for solving the base-uri issue...) Gerrit [1] http://xml.apache.org/commons/ [2] mirrored at, e.g., http://apache.easy-webs.de//xml/commons/xml-commons-resolver-1.2.tar.gz -- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke(a)le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard Vöckler ---------------------------------------------------------------------- Besuchen Sie uns auf der Frankfurter Buchmesse in Halle 4.2, Stand G446. Mehr dazu unter www.le-tex.de/de/buchmesse.html

4 3

database format compatibility from a version to another
by Fabrice Etanchaud 06 Oct '10

06 Oct '10

Dear all at BaseX, could you explain how one can know that database format compatibility is broken from a version to another ? Is it in the version numbering, or do you broadcast the information ? Maybe i dreamed about it, but i cannot find the file module documentation on the website anymore... There is XML with BaseX, and XML without BaseX... Regards

2 1

Bug in Date.diff
by Dave Glick 05 Oct '10

05 Oct '10

I think there might be a bug in Date.diff - it looks like if the number of days are the same, it attempts to directly cast the incoming Item to a Date in order to compare seconds. However, if the incoming Item is actually a string or something else a cast failure will occur. My fix is below: Old code: @Override public int diff(final InputInfo ii, final Item it) throws QueryException { final long d1 = days(); final Date d = (Date) (it.date() ? it : type.e(it, null, ii)); final long d2 = d.days(); if(d1 != d2) return (int) (d1 - d2); return seconds().subtract(((Date) it).seconds()).signum(); } New code: @Override public int diff(final InputInfo ii, final Item it) throws QueryException { final long d1 = days(); final Date d = (Date) (it.date() ? it : type.e(it, null, ii)); final long d2 = d.days(); if(d1 != d2) return (int) (d1 - d2); return seconds().subtract(d.seconds()).signum(); } Dave

3 3

Provide OSGi conformant manifest headers in jar
by erdal.karaca.de＠googlemail.com 04 Oct '10

04 Oct '10

I am using the basex xquery implementation in an OSGi/Eclipse environment and need to provide/add additional manifest headers or wrap the delivered jar. I would like to have those manifest headers automatically included in the build, namely, these would be (minimally): Bundle-SymbolicName: org.basex.api Bundle-Version: 6.2.8.SNAPSHOT Export-Package: javax.xml.xquery, org.basex.api.xqj This way I would just require my components (jars/plugins/bundles) to depend on bundle org.basex.api and would not have to include/manage the basex versions myself...

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk