September 2010 - BaseX-Talk - mailman.uni-konstanz.de

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

Problem with basex:eval
by Maximilian Gärber 30 Sep '10

30 Sep '10

Hi there, I am using basex 6.2.7 (gui version) from the maven repo. Using eval (see below) gives me: Fehler: [XPST0017] Unknown function "local:name1(...)". If I call local:name1() directly, it works. Running the same script with Saxon (using saxon:evaluate) works, too. declare function local:name1() { let $msg := "hello from name1" return <msg>{$msg}</msg> }; declare function local:dispatch($e as element()) { let $func := local-name($e) let $res := basex:eval(concat("local:", $func, "()")) return $res }; let $elem := <name1>bla</name1> (: return local:name1() :) return local:dispatch($elem) Regards, Max

2 3

FW: XSLT support
by Fabrice Etanchaud 30 Sep '10

30 Sep '10

Thank your dear Michael, for your reply. Sorry, I missed a context for my request : When do you plan to include XSLT support in XQUERY ? For me, a basex function like 'basex:xslt($xslt_path as xs:string, $in as xs:node()) as xs:node() would be perfect stuff. -----Original Message----- From: Michael Seiferle [mailto:michael.seiferle@uni-konstanz.de] Sent: jeudi 30 septembre 2010 12:28 To: Fabrice Etanchaud Cc: basex-talk(a)mailman.uni-konstanz.de Subject: Re: [basex-talk] XSLT support Hi Fabrice, currently there is no XSLT support, but to quote Christian [1]: Am 09.03.2010 um 11:10 schrieb Christian Grün: > Dear Sebastian, > > currently, BaseX offers no extra XSLT implementation, but we know that > some users have applied the Java 1.5 XSLT implementation to transform > XML nodes from our database. As an indication, all Item instances > offer a java() method which converts nodes to Java data types (e.g. > DOM instances). > > Hope this helps, > Christian > ___________________________ So the Item.java() methods might be worth a look to transform database nodes. Feel free to ask more. Kind regards Michael [1] https://mailman.uni-konstanz.de/pipermail/basex-talk/2010-March/000119.html Am 30.09.2010 um 11:49 schrieb Fabrice Etanchaud: > Dear all at DBIS, > BaseX is a fantastic tool. > When do you plan to include XSLT support ? > > regards > Fabrice Etanchaud > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

2 1

XSLT support
by Fabrice Etanchaud 30 Sep '10

30 Sep '10

Dear all at DBIS, BaseX is a fantastic tool. When do you plan to include XSLT support ? regards Fabrice Etanchaud

2 1

meaningless numbers print out to std out
by Erdal Karaca 28 Sep '10

28 Sep '10

When running basex in XQJ mode and using copy... modify..., some numeric sequences are print out to std.out in the eclipse debug console, e.g.:0 / 0 1 / 0 ...

2 1

BaseXClient.java ignores EOF from server
by Godmar Back 27 Sep '10

27 Sep '10

BaseXClient.receive ignores EOF if the connection is severed: /** * Receives a string and writes it to the specified output stream. * @param o output stream * @throws IOException I/O exception */ private void receive(final OutputStream o) throws IOException { while(true) { final int b = in.read(); if(b == 0) break; o.write(b); } } The result is an out of memory error because you're trying to stuff infinitely many -1 values into the ByteArrayOutputStream backing o. - Godmar

1 0

Using the options
by Maximilian Gärber 27 Sep '10

27 Sep '10

Hi, from the FAQ ( http://www.inf.uni-konstanz.de/dbis/basex/faq#5.4 ), I read that there are several options available. However, I could not figure out how to set those options from jax-rx or any other client than Java (I found in Java there's something like CONTEXT.props("key", "value") ). Regards, Max

2 1

XPTY0019 error in basex 6.2.7 that did not appear in 6.2.3
by Godmar Back 25 Sep '10

25 Sep '10

This query: declare variable $metadata as xs:anyAtomicType := doc('libx2_meta')/metadata; let $roots := $metadata/roots[@document="libx2_feed"]/id return ... produces [XPTY0019] Context node required for roots[@document = "libx2_feed"]; xs:untypedAtomic found. in BaseX 6.2.7, but it works in 6.2.3 Is this correct? Substituting the declare variable with a let $metadata := ... works, so no showstopper here. On a related note, declaring a function "as xs:anyAtomicType()*" behaves differently in 6.2.7 than in 6.2.3. I suppose the correct semantics for this is to cast the result to an anyAtomicType; 6.2.3 did not do that but 6.2.7 does. - Godmar

2 3

explicit use of namespace prefixes in xquery expressions does not appear to work
by Godmar Back 25 Sep '10

25 Sep '10

I'm trying to create snapshots for the problems we're having with namespaces. Here's the first one (this is not a showstopper, just something I believe is wrong). In http://top.cs.vt.edu/~gback/bx/nsbug1/ you can find http://top.cs.vt.edu/~gback/bx/nsbug1/BaseXData.bug1.zip which contains a zipped BaseX folder. The script 'test.sh' demonstrates what I believe to be a problem with 6.2.7. Notably, the following query: declare namespace libx='http://libx.org/xml/libx2'; doc("libx2_feed")//libx:entry[@src="34"] returns: <libx:entry xmlns:libx="http://libx.org/xml/libx2" xmlns=" http://www.w3.org/2005/Atom" src="34"/> (the inherited default name space for the libx:entry element is 2005/Atom. But explicitly asking for atom:src in the query: declare namespace libx='http://libx.org/xml/libx2'; declare namespace atom='http://www.w3.org/2005/Atom'; doc("libx2_feed")//libx:entry[@atom:src="34"] returns an empty sequence when in my opinion it should provide the same result. Am I wrong? (As an aside, using libx:src also doesn't return anything:) Run test.sh to reproduce. - Godmar

2 1

namespace problems nehmen kein Ende
by Godmar Back 25 Sep '10

25 Sep '10

Hi, BaseX's server sends illegal XML to the client, see below. This should never happen, correct? - Godmar > java -cp "../../../../WEB-INF/lib/*" org.basex.BaseXClient -p 1985 Username: admin Password: BaseX 6.2.3 [Client] Try "help" to get some information. > *xquery declare namespace atom='http://www.w3.org/2005/Atom'; doc("libx2_feed")/atom:feed/atom:entry[atom:id="49"]* <entry xmlns="http://libx.org/xml/libx2" xmlns:libx=" http://libx.org/xml/libx2" xmlns="http://www.w3.org/2005/Atom"> <id>49</id> <title>Package 2</title> <updated>2010-09-23T19:17:06.183Z</updated> <author> <name>LibX Team</name> <uri>http://libx.org</uri> <email>libx.org(a)gmail.com</email> </author> <content type="html">Content created by LibX Libapp Builder</content> <libx:package> <libx:entry xmlns="http://libx.org/xml/libx2" src="50"/> </libx:package> </entry> Query executed in 2.19 ms. >

2 1