Hi Paul,
On 04/11/14 21:00, Paul Danckaert wrote:
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.
So I'm not totally sure if you mean that capability (querying on
properties of items that are mapped via LD Client) is supported
currently, or if that's in the plans for the future? In my DataProvider
implementation I have retrieveResource returning a ClientResponse based
on the resource identified explicitly. How would I extend that to
support querying by attribute/relation values instead?
Yep, the business of LDClient is just to provide data for a specific
URI. Anything else is just custom behavior you can't expect from other
data providers.
Navigation (retrieval) via properties can be done via LDPath, which
transparently will call LDClient when required.
In my example, if I had a set of buildings mapped via an LD Client
provider, instead of retrieving by a building URI, could I retrieve all
with a specific number of floors, or some other characteristic, and have
my provider receive and process that request?
I think I'm not understanding your problem... First I'll recommend you
to take a look to the LDPath language to see if it give the
expressiveness required:
http://marmotta.apache.org/ldpath/language.html
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.
I'm not sure how blacklisting some URIs would help with that, do you
have any examples or specifics on that?
Blacklisting is typically used to avoid URIs (it's regex-based) that you
know there is not way to get RDF out of them. Not sure if it actually
solves your need...
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernan...@redlink.co
w: http://redlink.co
