So9q added a comment.
@KingsleyIdehen maybe you can help shed some light on the questions about Virtuoso here? > Data representation > Geographical triples specifying coordinate system can not be loaded: "http://www.wikidata.org/entity/Q405 Point(-49.2 -21.5)"^^http://www.opengis.net/ont/geosparql#wktLiteral > see https://github.com/openlink/virtuoso-opensource/issues/455 > "Point(-342.2 -52.7)"^^geo:wktLiteral not accepted by Virtuoso (more strict about the points than we are) > No extended date range support > Virtuoso has custom type support, so may be fixable > IRI inlining seems to be standard database normalization, thus we’d probably have to use long (64-bit) IDs, which may lead to larger space requirements. But Virtuoso seems to be able to support such scenario. > SPARQL capabilities > No support for custom services > Label service > Geo search (Virtuoso has its own geosearch functionality) > MWAPI bridge > May be replaced by Sponger? > GAS algorithms > Custom functions unavailable > Distance (may be supported under other name) > Coordinate parts > Decode URL > Date math functions work differently (e.g. diff is not days but seconds) > Functions need custom bif: prefix > This can be bridged by custom functions and procedures, but the syntax probably would be different from what we’re using now. > Service capabilities > Dynamic runtime query time limit - not sure whether it’s configurable/changeable > Throttling/concurrency control - probably will need to implement by ourselves > Read-only querying (Virtuoso has user permissions, so we may be able to get that working) > Not clear what extensibility APIs are - since we don’t have Servlet API like in Blazegraph, we may need to work with whatever Virtuoso allows. > Service features > No namespace support, but has graph (quads) support, which probably can replace it > Default prefixes support? > Federation whitelist? > Seems there is a limit for 10000 sql lines - which may be a problem for large queries/updater > LDF endpoint support unclear - may be implemented as proxy > Operational issues > Debian only has 7.x as experimental > Virtuoso has username/password/permission system, which we would need to isolate from outside and to make work with Updater > We will need to isolate other capabilities to reduce security exposure, Virtuoso is a full-scale container of which we won’t be using most capabilities. TASK DETAIL https://phabricator.wikimedia.org/T206561 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: So9q Cc: KingsleyIdehen, So9q, TallTed, Sj, Jerven, Base, TomT0m, Akuckartz, GreenReaper, Addshore, Lucas_Werkmeister_WMDE, Aklapper, Smalyshev, Invadibot, MPhamWMF, maantietaja, CBogen, Nandana, Namenlos314, Lahi, Gq86, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
