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

minor issue
by Rob Stapper 16 May '13

16 May '13

Hi guys, A minor issue. The marking of joint parenthesis in the editor of the BaseXGUI doesn't take account of parenthesis within strings. That is parenthesis of statements are joint to parenthesis within strings. This corrupts the marking of parenthesis. Example: the parenthesis marking of: concat( '(' , $var) , doesn't work properly because of the parenthesis-string within the concat-statement. I use the latest BaseX-snapshot Regards, Rob Stapper

2 1

XqueryDebugger
by Rob Stapper 16 May '13

16 May '13

Hi, Making intensive use of mappings {} and high-order recursive functions, I really could do with a nice debugger for the Xquery in BaseX. Is a debugger in the planning? Thnx. Regards, Rob Stapper

5 11

Error while storing "<" and "<=" in DB
by John Best 15 May '13

15 May '13

Hi there, I am trying to save the generated queries in database, to have a Search History. Some of my queries have "where" conditions with < (less than) and <= (less than equal to operators. This is the insert query - for $x in doc('SHIST')/Searches return insert node <SH><Id>0</Id><Date>20130515 14:05:44</Date><Query> for $x in doc('Docs')/Docs/Doc where$x/Title[Desc/@name='IT' and Year >= '2010' and Year <= '2013'] </Query></SH> as last into $x I am getting error "Expecting tag name, '<=' found Any workaround for the same...?? -- Have a nice day JBest

3 3

Fwd: Error while storing "<" and "<=" in DB
by Jens Erat 15 May '13

15 May '13

missed sending to list... -- Jens Erat [phone]: tel:+49-151-56961126 [mail]: mailto:email@jenserat.de [jabber]: xmpp:jabber@jenserat.de [web]: http://www.jenserat.de PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B Anfang der weitergeleiteten Nachricht: > Von: Jens Erat <jens.erat(a)uni-konstanz.de> > Betreff: Aw: [basex-talk] Error while storing "<" and "<=" in DB > Datum: 15. Mai 2013 11:40:29 MESZ > An: John Best <johnbest5673(a)gmail.com> > > Hi John, > > as I understand your query you want to store the XQuery code in line three as text content in an XML database. > > In Text nodes, the characters `<`, `>` and `&` must be escaped as entities. Either you write > > for $x in /Docs/Doc where $x/Title[Desc/@name='IT' and Year >= '2010' and Year <= '2013'] > > or you mark the whole Query as CDATA (probably to be preferred): > > for $x in Searches return > insert node <SH><Id>0</Id><Date>20130515 14:05:44</Date><Query><![CDATA[ > for $x in /Docs/Doc where $x/Title[Desc/@name='IT' and Year >= '2010' and Year <= '2013'] > ]]></Query></SH> as last into $x > > Regards from Lake Constance, Germany > Jens > > -- > Jens Erat > > [phone]: tel:+49-151-56961126 > [mail]: mailto:email@jenserat.de > [jabber]: xmpp:jabber@jenserat.de > [web]: http://www.jenserat.de > > PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B > > > > Am 15.05.2013 um 10:57 schrieb John Best <johnbest5673(a)gmail.com>: > >> Hi there, >> >> I am trying to save the generated queries in database, to have a Search History. >> >> Some of my queries have "where" conditions with < (less than) and <= (less than equal to operators. >> >> This is the insert query - >> >> for $x in doc('SHIST')/Searches return >> insert node <SH><Id>0</Id><Date>20130515 14:05:44</Date><Query> >> for $x in doc('Docs')/Docs/Doc where$x/Title[Desc/@name='IT' and Year >= '2010' and Year <= '2013'] >> </Query></SH> as last into $x >> >> I am getting error "Expecting tag name, '<=' found >> >> Any workaround for the same...?? >> >> -- >> Have a nice day >> JBest >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >

1 0

Web admin
by ski n 15 May '13

15 May '13

It's easy to deploy BaseX as a web application. I wondered if there is default admin (gui) application like BaseX GUI so I can have similar functionality in the browser. Raymond

2 1

Referential Queries
by James Wright 14 May '13

14 May '13

Hello Again, If this is the wrong forum for these type of questions let me know. By the way Liam I picked up your book last night, I like the flavor as it differs from my other reads such as those from Kay. Although I have been using XML for years and understand the core concepts it should be a great refresher. If you have time to read this and respond I appreciate it... If not I understand. :) The Organizational Overall Problem: There aren't many people in my industry that use XQuery and xml in the way it was intended (IMHO). In fact most developers in my organization are rather uneducated in it and as you know there is some un-rational backlash as many correlate XML to the DOM and XPath/XSLT 1.0 and as a competitor to JSON which is ludicrous. The DOM has its issues of scale-ability which our products are currently running into. This isn't really xml's or the DOM's problem but simply poor implementation. As you know though, all that matters is perception. I am having to work with a large number of un-schemad, basically hack job, developed xml documents and workflows. A lot of our product utilizes XSLT for reporting and transformation however only a few in the team understand the concepts and due to MS/Managerial BS we are stuck with a .NET XSLT 1.0 processor. Also almost all of our XSLT scripts utilize a Pull pattern which I find overly verbose and inefficient, but that is a personal opinion. I have been researching alternatives to the DOM and .NET's standard processor (I have used Saxon too) because I personally find XML useful and the query semantics of XQuery 3.0 awesome. Proposed Solutions: We have two primary use cases: 1) as a local db to replace the context DOM for our 'documents' which in our case relates to Utilitiy GIS Designs of circuit, subdivisions, fiber, etc... I am thinking BaseX coupled with RestXQ could replace our DOM for local installs and allow ourselves to decouple from the Geodatabase and provide a browser based UI. (Currently our xml documents are stored in a blob in the GIS database) The GIS we are using is ESRI however we are interested in also supporting Open Street Maps. (Noticed the Geo Module) 2) as a service for hosting uploading and allowing users/delivery and support to view, query and modify complex sets of interrelated XML configuration files. Some of our applications have hundreds. Again all these documents follow a similar semantics however their is no defined schema for any of them. Currently the client has to read a 50 page manual and edit the files one at time. Often there are nodes in several files which must match exactly or the entire application fails.... Its a nightmare and there is no concept of generalization in my organization when it comes to development. Every tool we do have to 'configure' is hand crafted and unique..... Its abysmal! Because of this we have tools that cover probably only 20% of the configuration. I think we can accomplish both of the above tasks using a single codebase and restXQ I have written an XQuery expression which using our 'common' xml semantics can ascertain entities/properties/relationships and distill this in the form of metadata which then using RestXQ is distilled into a metadata driven api for manipulated data centric xml documents. Similar to how you can transform a well formed xml document into an xsd however our metadata format compliments XSD but servers broader purposes for example to annotate triggers/mappings etc. This metadata is then consumed for each RestXQ operation to allow for a generalized API and all markup is applied on the Client to allow for more efficient caching mechanisms since users can share resources between different representations more efficiently. We currently use Knockout.js on the client for this. Here is an example of a generalized API endpoint for retrieving a unique entity by type. (: Removed error handling and some other stuff for brevity. Its not fully functional/vindicated but is more a representation of the concept :)declare %restxq:path("api/{$entityListName}/{$entityId}") %restxq:GET function page:GetEntity($entityListName as xs:string, $entityId as xs:string) { let $entityMetadata := $page:database/metadata/entity[@type = $entityListName] let $entity := if($entityMetadata/property[@key = 'true']) then (: Use the properties marked in the metadata as the key :) $page:database//*[name() = $entityListName and data((*|@*)[name() = $entityMetadata/property[@key = 'true']/@name]) = $entityId] <entity> { (: Construct the representation based on the metadata :) for $propMeta in $entityMetadata/property return attribute {$propMeta/@name} { data($entity/(*|@*)[name() = $propMeta/@name]) } } { (: Include a link to all related entities for further discovery by the client.. :) for $relMeta in $entityMetadata/relationship return if($relMeta/@multiplicity = '*') then (: creates a href like: api/worklocation/23/cost which would return the sequence of cost items associated with the work location 23 :) element link { (attribute href { concat( 'api/, $entityListName, '/', $entityId, '/', $relMeta/@with ), attribute rel { $relMeta/@with })} else ( (: creates a href to a single related entity :) let $relatedEntityMeta := $page:database/metadata/entity[@type = $relMeta/@with'] element link { (attribute href { concat( 'api/', $relMeta/@with, data( $entity/(@*|*)[name() = $relMeta/@type]/((@*|*)[$relatedEntityMeta/property[@key = 'true'] ) ) }, attribute rel { $relMeta/@with } ) } ) } </entity> }; With a metadata mapping of the document we can convert the 'tree' structure into a virtual 'relational table' structure allowing for granular node modification/addition/removal in a generalized way. Once the metadata is distilled using the same api with metadata describing the metadata we can then allow the client to further manipulate the view/aliasing/permissions/triggers/mappings of the entities archetypes metadata allowing for quick UI/Workflow generation. At least that is the idea... This obviously requires a client side library which understand this metadata orchestration. The XML/BaseX Question:We need to be able to query effectively across relationships. Are there any facilities in XML/XQuery/3rd party that do this? I was hoping Id and IDref could accomplish this but as you stated that is not the case.... Basically I won't know before hand whether a child node is inline or a reference but would like to be able to query both as those they were the same.. If I had two nodes (I will call them parents) both with the same child. One has the actual inline child node and the other has just a reference to it. Lets say the child's attribute name is 'Tom'. I would like to be able to query like this and return both parents nodes: //parents[child/@name = 'Tom'] Anything? If not, is this a weird use case? I wouldn't think so. I could imagine however that this use case may be hard to 'generally' support in xml given referential loops etc especially in a non schemed/validated document... - James

2 2

Namespaces on element construction
by Arto Viitanen 14 May '13

14 May '13

Why does this query (on BaseX 7.5, basexgui) let $ns := namespace {''} {'the-namespace'} let $c1 := <c xmlns="the-namespace">text</c> let $c2 := <c>{ $ns,'text'}</c> let $c3 := element {'c'} {$ns,'text'} let $qn := QName($ns, 'c') let $c4 := element {$qn} {'text'} let $nl := "
" return ($c1,$nl, $c2,$nl, $c3,$nl, $c4,$nl, '|' || namespace-uri-from-QName(node-name($c1)) || '|',$nl, '|' || namespace-uri-from-QName(node-name($c2)) || '|',$nl, '|' || namespace-uri-from-QName(node-name($c3)) || '|',$nl, '|' || namespace-uri-from-QName(node-name($c4)) || '|',$nl) outputs <c xmlns="the-namespace">text</c> <c xmlns="the-namespace">text</c> <c xmlns="the-namespace">text</c> <c xmlns="the-namespace">text</c> |the-namespace| || || |the-namespace| I.e, the namespace seems to exist on all four cases when outputted, by node-name finds it only if the namespace is given in element as text, or as QName value in computed element. -- Arto Viitanen Microteam Oy Finland

2 2

BasexGUI (minor) issue
by Rob Stapper 14 May '13

14 May '13

Hi guys, In the BaseXGUI, when expanded the windowframe with F11, clicking on the "opens existing file"-button, at the right-hand top of the editor-window, stops the GUI. Ectually the GUI is waiting for input of a filename but the inputbox is not visible. When this happens you have to abort the GUI with the windows taskmanager (in windows antway). Have fun, Rob Stapper

3 4

full text with search term in a variable gives no matches
by Liam R E Quin 14 May '13

14 May '13

The following query gives me no results: for $city as xs:string in ("Paris", "Cambridge", "London", "Oxford") return ( $city, count(/dictionary/letter/entry[.//p//text() contains text {$city}]), "
" ) However, BaseX rewrites it to for $city as xs:string in ("Paris", "Cambridge", "London", "Oxford", ...) return ($city, fn:count(db:fulltext("with-sources", { $city })/ancestor::*:p/ancestor::*:entry), " ") If I remove the braces around $city in the argument to db:fulltext() I get the right answers (or at least plausible answers). So this looks like a bug in the rewriting engine. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml

2 3

Proposal for programmatically setting index options
by Andy Bunce 14 May '13

14 May '13

Hi, The index settings for a database can make a huge difference to query performance. I have been playing with a database where the time for a query using distinct-values went from 4secs to 4ms by increasing the MAXCATS value. Currently it is rather fiddly to change these values, particularly to this programmatically. with different values per database. I would find it useful there was an easier way to do this. A quick suggestion as to how this might be done: db:optimize could be extended to taker a third argument that matched the format of in indexes portion of the db:info command <indexes> <uptodate>true</uptodate> <textindex>ON</textindex> <attributeindex>ON</attributeindex> <fulltextindex>OFF</fulltextindex> <updindex>OFF</updindex> <maxcats>100</maxcats> <maxlen>96</maxlen> </indexes> e.g db:optimize("mydb",fn:true(),$indexopts) This would rebuild "mydb" using the settings specified in $indexopts. The extra argument could also be added to db:create. /Andy

2 1