- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 6 Oct 2015 10:18:40 +0200
- To: pp.wasin@gmail.com
- Cc: public-hydra@w3.org
> I think just only hydra-ex:filter is enough.
Nothing constrains the subject of the triples then,
so you would get
>> CONSTRUCT { ?s rdfs:label ?label }
>> WHERE {
>> ?s rdfs:label ?label .
>> }
instead of
>> CONSTRUCT { ?member rdfs:label ?label }
>> WHERE {
>> <http://example.org/collection> hydra:member ?member .
>> ?member rdfs:label ?label .
>> }
> I understand that you use following triples for identifying the collection:
> "hydra-ex:constant "http://example.org/collection"; hydra:property rdf:subject"
Yes.
> However, in the REST manner. I think the operation should perform
> against the resource that attach to.
> In this case the operation is the filter.
There's no relation between hydra-ex:filter and the REST architectural style.
Also, there's no reason why this would apply to hydra-ex:filter
but not with hydra:search.
So I can't conclude that using hydra-ex:filter
would automatically constrain the subject of triples.
Best,
Ruben
Received on Tuesday, 6 October 2015 08:19:11 UTC