Hi Francisco, On Tue, May 12, 2015 at 7:37 AM, FRANCISCO XAVIER SUMBA TORAL < [email protected]> wrote: > > I thought of using an external library (Geotools Library) to translate > only GeoSPARQL functions to the functions supported by this library. So it > is not limited to the postgres utilization (Postgis). However, this > implementation (using geotools library) may require much modification of > the original code >
Well, PostgreSQL is our main database for production environments. So I guess you'll have to get some figures about the performance of both options, and then take a decision. What about starting to write down those things on our wiki? I've just added the base structure there: https://wiki.apache.org/marmotta/GSoC/2015 What we could maybe do is use the PostGIS if available, falling back to Geotools in the other cases. What do you think? In that case, I'd focus first on one of those things, and once it's ready add the second, but don't put in the risk the minimum functionality because addressing the use case. > I'll check on the extension to determine what would be the best > alternative. in order to perform the least amount of modifications to the > original code. Some more hints: the extensions are by implementing the KiWi NativeFunction interface, and registered using the Sesame FunctionRegistry. You can find a concrete implementation example at: https://github.com/apache/marmotta/blob/master/libraries/kiwi/kiwi-sparql/src/main/java/org/apache/marmotta/kiwi/sparql/function/custom/FulltextQueryFunction.java#L48 Hope that helps to come closer to define the goals of the project. Cheers, -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
