BaseX-Talk

basex-talk@mailman.uni-konstanz.de

13 participants
5244 discussions

stemming chinese texts
by Philippe Pons 14 Oct '20

14 Oct '20

Dear BaseX Team, I'm actually working on chinese texts in TEI. I would like to know if stemming chinese text is possible in BaseX, as we can do with other languages (like english or deutsch)? Or maybe there is a way to add this functionnality with Lucene? Best regards, Philippe Pons -- Ingénieur d'étude chargé de l'édition de corpus numériques Centre de recherche sur les civilisations de l'Asie Orientale CRCAO - UMR 8155 (Collège de France, EPHE, CNRS, PSL Research University, Univ Paris Diderot, Sorbonne Paris Cité) 49bis avenue de la Belle Gabrielle 75012 Paris https://cv.archives-ouvertes.fr/ppons

2 3

Re: [basex-talk] BaseX-Talk Digest, Vol 130, Issue 5
by Duncan Paterson 12 Oct '20

12 Oct '20

> I'm actually working on chinese texts in TEI. > I would like to know if stemming chinese text is possible in BaseX, as > we can do with other languages (like english or deutsch)? > Or maybe there is a way to add this functionnality with Lucene? > > Best regards, > Philippe Pons > Dear Philippe, if by stemming you mean the removal of prefixes and suffixes to arrive at normalized word stems, the concept simply doesn’t apply to Chinese, so no it can’t be done. What you are most likely looking for is the ability to tokenize strings into n-grams, which lucene can do. https://lucene.apache.org/core/6_6_1/analyzers-common/org/apache/lucene/ana… <https://lucene.apache.org/core/6_6_1/analyzers-common/org/apache/lucene/ana…> Greetings Duncan

1 0

XPTY0004 error when calling http:send-request inside of a local function
by Bridger Dyson-Smith 11 Oct '20

11 Oct '20

Hi all - I'm accustomed to writing something like the following: ```xquery declare function local:grab( $url as xs:string, $path as xs:string, $fname as xs:string ) as document-node() { let $req := http:send-request(<http:request method="get"/>, $url) return if (head($req)/@status = "200") then file:write($path || $fname, tail($req), map { "method": "xml" }) else ("something went wrong!") }; ``` but I've noticed that in version 9.4.3 this returns an XPTY error: Stopped at /home/bridger/bin/basex-src/basex-943-xpty0004-error.xq, 1/18: [XPTY0004] Cannot promote xs:string* to document-node(): (let $req_7 := http:send-request(<http:request method="get"/>, " https://dpla.lib.utk.edu/repox/OAIHa.... While this could be a bug, should I be writing this kind of local function differently? Or could I improve my typing on it? Thanks very much for any advice or insights you can provide. Best, Bridger

2 3

XQuery Optimizer Bug?
by Paul L. Merchant Jr. 07 Oct '20

07 Oct '20

Greetings everyone, I'm evaluating whether BaseX 9.4.3 might be suitable for my projects and I think I've run into an XQuery optimizer bug that's easily reproducible. I've got a test database "test-db" with two identical documents containing minimal xml: "<doc title='a-document'/>". The documents are stored in separate directories: test-db |- a/doc.xml |- b/doc.xml The XQuery I'm using I believe should retrieve only the document in path a, but I'm getting different results depending on whether I write the expression in a single let statement or two separate statements: declare function local:show-paths($nodes as node()*) as node()* { for $p in $nodes return <path>{$p/base-uri()}</path> }; let $docs_1 := collection('test-db/a')/doc[@title='a-document'] let $col := collection('test-db/a') let $docs_2 := $col/doc[@title='a-document'] return <result> <single-expr expr_docs="{count($docs_1)}"/> <single-expr-paths>{local:show-paths($docs_1)}</single-expr-paths> <split-expr collection_docs="{count($col)}" expr_docs="{count($docs_2)}"/> <split-expr-paths>{local:show-paths($docs_2)}</split-expr-paths> </result> This code produces this result: <result> <single-expr expr_docs="1"/> <single-expr-paths> <path>/test-db/a/doc.xml</path> </single-expr-paths> <split-expr collection_docs="1" expr_docs="2"/> <split-expr-paths> <path>/test-db/a/doc.xml</path> <path>/test-db/b/doc.xml</path> </split-expr-paths> </result> I'd expect the expr_docs values for both single-expr and split-expr to be the same. I'm happy to file this in the GitHub issue tracker, but as a newcomer to BaseX I thought I should checkin with the list first. What are you thoughts and wishes? Thanks, -- Paul

2 1

king Henry VIII dalenda est
by Liam R. E. Quin 05 Oct '20

05 Oct '20

At https://words.fromoldbooks.org/Search/ a search for henry shows lots of matches, and sodoes a search for henry i, but henry ii and henry viis missing and so is henry viii. I can search for viii and find Henry VIII and also Charles VIII, but i also can't search for Charles VIII. I can search for the king’s feet, and for Henry V, but not Charles II. It looks like words ending in ii are invisible. I'm using ft:search("wobo", $term)/ancestor-or-self::p Might this be related to stemming? i have that turned off This is used to create the db (from the Perl API) # create query instance t("drop db wobo"); t("create db wobo"); t("open wobo"); $session->send("set chop false"); $session->send("set ftindex true"); $session->send("set updindex true"); $session->send("set autooptimize true"); txf("/home/liam/w/Search/wobo.xml"); t("create index attribute"); t("create index text"); t("create index fulltext"); t("optimize"); t("close"); t("quit"); where t() just does a $session->execute() on its argument after printing a trace line, and txf does a delete followed by an add. Probably i can make a test case available if needed. Liam -- Liam Quin, https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org

3 4

Mapping query-params to $options argement of ft:functionj
by Günter Dunz-Wolff 05 Oct '20

05 Oct '20

Hi all, is there a possibility to match the query-parameters more directly to the $options argument of a ft:function? In the moment I have a rather complicated if-else-if-else-if…-scenario. Example: if ($wildcards = "on" and $all = "on" and $case_sensitive = "on" and $using_diacritics = "on") then $collection[.//text() contains text {$query} all words using case sensitive using diacritics sensitive using wildcards] else if and so on. Depending on query-params I want to build the ft:function with $options argument more directly. (But for example string-concatenation doesn’t work.) Thanks for any advice. Guenter

2 3

Re: [basex-talk] Paging results of an XQuery-Search
by Günter Dunz-Wolff 27 Sep '20

27 Sep '20

Thanks Gerrit, invoking search and passing all params per GET is the way to go.

2 1

Re: [basex-talk] XQuery Update delete attributes
by Günter Dunz-Wolff 27 Sep '20

27 Sep '20

Hi Martin, delete node //@foo did the job. Thanks.

1 0

XQuery Update delete attributes
by Günter Dunz-Wolff 27 Sep '20

27 Sep '20

Hi all, can’t figure it out. Is there any way in XQuery Update, to delete a specific attribute from any node? Thanks for help. Best regards Günter

2 2

Paging results of an XQuery-Search
by Günter Dunz-Wolff 26 Sep '20

26 Sep '20

Hi all, is it possible to present the results of an XQuery search in parts of 50? In order to speed up the search, only the first 50 results should be displayed and only if the user is interested in further results, 50 new results each should be displayed. Is this even possible? I did not find anything about it in the documentation. Example: let $collection := collection("data") let $hits := $collection//*:s[.//text() contains text {$query_string}] let $count_hits := count($hits) return <div> { if $count_hits <= 50 then <ol> {for $hit in $hits return <li>{$hit}</li> </ol> else ??? } </div> Thanks for any advice. Best regards Guenter

5 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk