From eecf3474118f8392614ee4e3a555b1cce0b9cc9e Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Thu, 27 Oct 2022 16:06:15 +0530
Subject: Reject virtuoso for full text search.

---
 issues/full-text-search.gmi | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

(limited to 'issues')

diff --git a/issues/full-text-search.gmi b/issues/full-text-search.gmi
index e0f958d..a8628de 100644
--- a/issues/full-text-search.gmi
+++ b/issues/full-text-search.gmi
@@ -1,9 +1,14 @@
 # Full text search
 
-Implement full text search on the dumped RDF using xapian. This may be a feature to be implemented in the dump-genenetwork-database repo using guile-xapian. It is also worth considering that virtuoso supports full text search in SPARQL. But, the query syntax is not as natural language like as xapian, and there may be no stemming.
+Implement full text search on the dumped RDF using xapian. This may be a feature to be implemented in the dump-genenetwork-database repo using guile-xapian.
 
 => https://xapian.org/ Xapian search engine library
 => https://git.genenetwork.org/arunisaac/dump-genenetwork-database dump-genenetwork-database repository
-=> http://docs.openlinksw.com/virtuoso/rdfsparqlrulefulltext/ Virtuoso full text search
 
 * assigned: aruni, bonfacem
+
+## Virtuoso full text search
+
+We also considered that virtuoso supports full text search in SPARQL. But, the query syntax is not as natural as xapian, and there may be no stemming. So, this option was rejected.
+
+=> http://docs.openlinksw.com/virtuoso/rdfsparqlrulefulltext/ Virtuoso full text search
-- 
cgit 1.4.1