How to extend the interaction model to support queries?

All,

The last thread on the interaction model reminded me of a question we
have at work.

At Pellucid, we retrieve data from containers using a custom language.
For now, it does filtering, ordering, inlining, and grouping. No
SPARQL. No paging at the HTTP level like in LDP. It's RDF data all the
way.

Here is the way that works at the protocol level: the container
_itself_ supports the filtering API, and we POST the query to it. As
you can see, we violate the semantics of an LDPC, as we are not adding
the query to the container. We don't really want to have a separate
endpoint for each container. We would be happy to use HTTP SEARCH or
QUERY, if they were available or not overloaded.

Is there a good way to do that while being fully compliant with the
spec, *and* ?  This is the same question for people who wants to add
SPARQL query capabilities to an LDPC.

Alexandre

Received on Monday, 28 July 2014 17:18:57 UTC