Hi Paul, On 03/11/14 14:24, Paul Danckaert wrote:
First let me say that implementing an LD Client and Provider works quite well, and retrieving items by direct URI does work as expected, with the caching support and other normal capabilities. Once the item is cached, normal SPARQL queries are able to find the item based on it's URI or it's attributes, at least while it resides in the cache.
Great!
I was curious, however, if there is any planned mechanism for retrieving items from the LD Client based on item attributes in some form instead of direct resource retrievals? For example, being able to do an LD Path query that would invoke the LD Client implementation to search on specific attributes, and return any matches to the query? I'm not sure what is in the road map for LD Client, so it would be interesting to see where it might be planned to go.
Actually that's part of the complete design of the stack. And LDPath does use of LDClient, via LDCache, while evaluating paths.
In former times SPARQL did it too, but since the Sesame Sail is bypassed to directly translate SPARQL into native KiWi SQL queries, we broke a bit the original design and is not longer possible.
It may be that for maximum query flexibility the data should be propagated into Marmotta directly, but I'm still trying to consider data sources that are either too sizable or constrained, or perhaps just API driven and wouldn't be easily migrated.
If you need specialized behaviors there, you can play blacklisting some URIs (based on regex) or even providing specialized data providers to filter some data.
Hope that helps. Cheers, -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co
