Within that system, users can issue both simple free text queries and advanced queries for specific properties of the resources, some of which may hold literals. The main motivation for backing this is that the migration costs between ARQ and Virtuoso was high due to the differing syntax. search only resources that are approved for publication).Ĭomputas has delivered a system that has a public search interface, and where the freetext search capabilities is a major feature. When SPARQL is used against a backend triplestore, it is very important to be able to use the freetext keywords in the SPARQL query, as one may need to combine the search term in conjunction with other properties (e.g. Nowadays, almost every site has a "search box", and this is an important and useful feature users have come to expect. Links to postponed Issues Related Features No issues because expressions can be recognized by ftcontains that was not in use before. XQuery and XPath Full Text 1.0 Compatibility
There is Fulltext Querying SAIL for Sesame based on Lucene.ARQ has a LARQ extension that uses Lucene to maintain indexes, and it supports Lucene text condition syntax.
Virtuoso supports the functionality but not with the proposed syntax. Support of the XPATH/XQuery text expression syntax is not very hard on implementors since they already must parse some syntax for text conditions.įinally, one could address the problems encountered in use cases where a number of literals should be indexed, which is a common requirement in "simple free text search" scenarios. Reusing existing proposals makes the addition trivial. Not reusing the XPATH or possibly SQL MM specifications would make the task unachievable within the scope of the WG. This will not interoperate with existing implementations. The next level is to retain the score, as in the above example.įor the convenience of standardization, Openlink propose to reuse the XPATH/XQuery full text extension. The simplest possible implementation is just to standardize the function to do it and possibly a requirement that the string should be possible to truncate. They are not interoperable however.įulltext search capabilities can be discussed on different levels. Since a full text match typically returns a match score, this would be in the form of a pattern like We propose support for a full text search capability. We need a full text search functionality, so XPATH/XQuery full text extension can be reused. 1.4 Existing Specification / Documentation.
0 kommentar(er)
