BaseX-Talk

basex-talk@mailman.uni-konstanz.de

5251 discussions

Keep the comments when parsing HTML?
by Graydon Saunders 21 Aug '17

21 Aug '17

Hello -- So I have a pile of near-XML HTML with semantically significant comments to deal with. (I must have been sinning much more than I realized!) Using BaseX866-20170818.124137, BaseX will parse the content but all the comments go away. This is with passing the "lexical" option on the parser tab where it asks for TagSoup options, which I understand from https://github.com/orbeon/tagsoup/blob/master/trunk/README to pass through comments (and DOCTYPE declarations). How do I parse HTML and keep the comments? Thanks! Graydon

2 4

%input:csv annotation
by Kendall Shaw 21 Aug '17

21 Aug '17

Trying to use the example, in the RESTXQ section of the documentation: declare %rest:path("/store.csv") %rest:POST("{$csv}") %input:csv("header=true,encoding=CP1252") function page:store-csv($csv as document-node()) { "Number of rows: " || count($csv/csv/record) }; Using: curl -i -XPOST –data @test.csv<mailto:data@test.csv> -H’Content-Type: text/csv’ http://blah/basex/store.csv The result is [XPTY0004] Cannot cast xs:string to document-node() I can just invoke csv:parse but, is the example missing a detail? Kendall

1 0

Java 9 support?
by Chris West 19 Aug '17

19 Aug '17

Debian and Ubuntu are looking to move to Java 9 for their next releases, for all possible packages. basex currently fails to build with Java 9 due to some rather boring errors: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile) on project basex: Compilation failure: Compilation failure: [ERROR] /build/basex-8.5.1/basex-core/src/main/java/org/basex/query/func/inspect/Inspect.java:[34,3] reference to Module is ambiguous [ERROR] both class org.basex.query.Module in org.basex.query and class java.lang.Module in java.lang match [ERROR] /build/basex-8.5.1/basex-core/src/main/java/org/basex/gui/GUIInput.java:[253,13] incompatible types: javax.swing.JComboBox<java.lang.String> cannot be converted to javax.swing.JComboBox<java.lang.Object> [ERROR] /build/basex-8.5.1/basex-core/src/main/java/org/basex/query/func/crypto/MyKeySelector.java:[51,44] incompatible types: java.util.List<javax.xml.crypto.XMLStructure> cannot be converted to java.util.List<java.lang.Object> Would there be any interest in fixing these? The website suggests that any version of Java is supported, and Java 9 will be out soon (~31 days). I can have a go at a pull request, but I'd not heard of basex before today, so maybe someone else would like a stab at it. I had a quick poke through the mailing list archives, and can't see any other discussion about this; sorry if it's been brought up before. Chris.

2 1

Implement read lock and write lock
by DK Singh 18 Aug '17

18 Aug '17

Hi All, How can i implement read lock and write lock, any functions to do this Regards Dharmendra Kumar Singh

5 5

Reading JSON
by Giuseppe Celano 18 Aug '17

18 Aug '17

Hi, I have noticed different speeds when running the following functions (from slowest to fastest): parse-json(unparsed-text('example.txt')) json-doc("example.txt") parse-json(file:read-text('example.txt')) similarly for documents on the web: parse-doc('http://example.com/text') parse-json(fetch:text('http://example.com/text')) Does this make sense to you? Is there any recommendation to follow? Despite the runtime speed difference, I admit I love writing one single function (json-doc) to get map conversion. Everything is so immediate :) Best, Giuseppe Universität Leipzig Institute of Computer Science, Digital Humanities Augustusplatz 10 04109 Leipzig Deutschland E-mail: celano(a)informatik.uni-leipzig.de E-mail: giuseppegacelano(a)gmail.com Web site 1: http://www.dh.uni-leipzig.de/wo/team/ Web site 2: https://sites.google.com/site/giuseppegacelano/

2 6

value compare in namespace
by radim-havlicek＠post.cz 18 Aug '17

18 Aug '17

Hello, I want to count failed reports in DB, it means where outcome value of report is "Failed". declare namespace TestResults='urn:IEEE-1671:2009.04:TestResults'; declare namespace Common='urn:IEEE-1671:2010:Common'; let $DocumentNames := (db:list("ASC", "Report")) for $DocumentName in $DocumentNames let $Document := db:open('ASC',$DocumentName) let $FailedTests := $Document/TestResults:TestResults/TestResults:ResultSet/ TestResults:TestGroup/TestResults:TestGroup/TestResults:TestGroup/ TestResults:TestGroup/TestResults:Test/TestResults:Outcome/data(@value) where $FailedTests="Failed" return count($FailedTests) However, it counts all reports, no matter if the value is "Passed" or "Failed". If I change the end to: return $FailedTests, it displays both "Failed" and "Passed" values. If I change it to: where $FailedTests="Test", it displays correctly 0 reports. What am I doing wrong? Thank you in advance for your reply. Radim Havlicek

3 3

Should xml-to-json ignore a "key" attribute of a "map" root element?
by Martin Honnen 18 Aug '17

18 Aug '17

When I try xml-to-json( <map xmlns="http://www.w3.org/2005/xpath-functions" key="root"> <number key="n">2</number> <string key="foo">a</string> <boolean key="checked">true</boolean> </map>, map { 'indent' : true() } ) with BaseX 8.6.5 I get an error "[FOJS0006] Element 'map' must have no key.". Saxon 9.8 however parses that input fine. Looking at https://www.w3.org/TR/xpath-functions-31/#func-xml-to-json there is some text saying "An element node E having a key attribute and/or an escaped-key attribute provided that E would satisfy one of the above conditions if the key and/or escaped-key attributes were removed." which sounds as if a "key" attribute should or could be ignored. Or is BaseX schema-validating the argument and that way ("Otherwise, the processor may attempt to validate the element against the schema, in which case it is treated as valid if and only if the outcome of validation is valid.") the "key" attribute is not allowed? It seems the spec that way allows some confusing lack of interoperability.

2 3

db:replace modified date
by Kendall Shaw 14 Aug '17

14 Aug '17

After debugging a query for a while, I figured out that db:replace isn’t changing the modification date of an XML resource, when the content hasn’t changed. The case is like this: db:replace(‘db’, ‘abc.xml’, doc(‘file:/tmp/abc.xml’)) Is that normal, or do I have an option set that results in that behavior? ADDCACHE is false. Kendall

2 1

Differences in serialization of arrays with JSON vs. adaptive methods
by Joe Wicentowski 13 Aug '17

13 Aug '17

Hi all, First, I'm just back from DH2017, where Clifford Anderson and I taught two workshops on XQuery using BaseX, along with eXist and Saxon. BaseX performed like a champ. We were able to configure the GUI window to show just the query and results windows—perfect when you're projecting the screen in a large room and want everyone to see. Many thanks for such a great teaching tool! (Our materials are at https://github.com/CliffordAnderson/XQuery4Humanists.) Back to the topic of this post, though, I noticed a slight difference between BaseX's serialization of arrays when using JSON vs. adaptive methods: with JSON, the array's items are separated by newlines, whereas with adaptive, the items are separated by spaces. This is interesting since the serialization spec notes that the adaptive method delegates the handling of the "indent" parameter to JSON. Some code to reproduce this is below. I'm curious to know - is there a particular reason for this difference? Thanks, Joe serialization-test.xq ```xquery xquery version "3.1"; declare namespace output="http://www.w3.org/2010/xslt-xquery-serialization"; let $array := ["Cheapside","London","Dean Prior","Devon"] for $method in ("json", "adaptive") let $serialization-parameters := <output:serialization-parameters> <output:method>{$method}</output:method> <output:indent>yes</output:indent> </output:serialization-parameters> return fn:serialize($array, $serialization-parameters) ``` serialization-test_results.txt ```txt [ "Cheapside", "London", "Dean Prior", "Devon" ] ["Cheapside", "London", "Dean Prior", "Devon"] ```

3 11

Shouldn't CHOP = false make xml:space="preserve" the default behavior?
by Ottid Mes 10 Aug '17

10 Aug '17

(Sorry for the noise, but because my previous mail was shown under trimmed content in my Sent Mail, I will resend it without format just in case it was not shown properly to others as well) >From the documentation about the CHOP option I assumed that since xml:space="preserve" sets CHOP = false for that part of the document, that if I set CHOP = false in my configuration file, that the behavior you get when you use xml:space="preserve" would be applied to the whole database (I created the database after setting the option). However the only way I have ever been able to get this behavior, has been to set xml:space="preserve" at the root element. Am I missing something, or is this a bug? How could I get this behavior by default in my databases? I thought this would not warrent a thorough example given the clear conditions which cause the above situation, but I was asked for it anyway, so here it goes: A little bit of context, although it should not matter, I have had this issue for years (at least 4) under Arch Linux. At the time I just assumed I did something wrong and went with xml:space="preserve" workaround everywhere. > uname -a Linux phoenix 4.9.38 #1-NixOS SMP Sat Jul 15 10:17:55 UTC 2017 x86_64 GNU/Linux The default situation: No config file (.basex) > basex BaseX 8.6.4 [Standalone] > create db chop-test Database 'chop-test' created in 123.01 ms. > open chop-test Database 'chop-test' was opened in 1.19 ms. > replace /a <root><a>foo</a> bar</root> 0 resource(s) replaced in 103.68 ms. > xquery /root <root> <a> foo </a>bar</root> Query executed in 106.05 ms. I never use the REPL other than to create and drop databases, so I was a bit suprised that this did not work: > replace /a <root xml:space="preserve"><a>foo</a> bar</root> "a.xml" (Line 1): Open quote is expected for attribute "xml:space" associated with an element type "root". While this does: > replace /a <root xml:space='preserve'><a>foo</a> bar</root> 1 resource(s) replaced in 4.06 ms. > xquery /root <root xml:space="preserve"><a>foo</a> bar</root> Query executed in 0.95 ms. > quit Have fun. The resource with xml:space="preserve" is the behavior I want to have within my database, because all my documents are mixed content. On the wiki (http://docs.basex.org/wiki/Options#CHOP) this is also mentioned: It explicitly states that in my use case I should set CHOP to false: "The flag should be turned off if a document contains mixed content." It also states that setting the xml:space="preserve" attribute is the same as having CHOP = false: "If the xml:space="preserve" attribute is attached to an element, chopping will be turned off for all descendant text nodes." So lets do that: Let us first confirm that the config file is correctly read: > echo 'FOO = 0' > /some/path/.basex > BASEX_JVM='-Dorg.basex.path=/some/path' basex /some/path/.basex: Unknown option 'FOO'. /some/path/.basex: writing new configuration file. Now we set the option CHOP = false in our config: > echo 'CHOP = false' >> /some/path/.basex So lets see what this changes in the basex REPL: > BASEX_JVM='-Dorg.basex.path=/some/path' basex BaseX 8.6.4 [Standalone] > drop db chop-test Database 'chop-test' was dropped. > create db chop-test Database 'chop-test' created in 106.42 ms. > open chop-test Database 'chop-test' was opened in 0.05 ms. > replace /a <root><a>foo</a> bar</root> 0 resource(s) replaced in 39.24 ms. > xquery /root <root> <a> foo </a> bar</root> Query executed in 97.09 ms. > quit Have fun. This is not what I expect, it should have been: > xquery /root <root><a>foo</a> bar</root> And hence my question: Shouldn't CHOP = false make xml:space="preserve" the default behavior? I even tried this: > BASEX_JVM='-Dorg.basex.path=/some/path' basex BaseX 8.6.4 [Standalone] Try 'help' to get more information. > open chop-test Database 'chop-test' was opened in 90.65 ms. > set chop off CHOP: false > replace /a <root><a>foo</a> bar</root> 1 resource(s) replaced in 45.58 ms. > xquery /root <root> <a> foo </a> bar</root> Query executed in 96.78 ms. > quit See you. Am I making some mistake in the above? Is the wiki simply outdated and should this be configured differently? Is having having mixed content in basex so rare that this bug has gone unnoticed for years?

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk