- From: Wasin Passornpakorn <pp.wasin@gmail.com>
- Date: Tue, 6 Oct 2015 15:15:01 +0700
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: public-hydra@w3.org
> You'd probably need something like (warning: mock-up)
>
> <http://example.org/collection>
> hydra-ex:filter [
> hydra:template "http://example.org/collection{?p}";
> hydra:mapping [ hydra:variable "p"; hydra:property rdf:predicate ],
> [ hydra-ex:constant "http://example.org/collection"; hydra:property rdf:subject ]
> ].
>
> Here, I used hydra-ex to indicate properties that do not exist officially.
>
> We thus need to inject a constant in the filter, I think.
> Any opinions?
I think just only hydra-ex:filter is enough.
I understand that you use following triples for identifying the collection:
"hydra-ex:constant "http://example.org/collection"; hydra:property rdf:subject"
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. The resource is the
<http://example.org/collection>.
Therefore, the hydra-ex:filter should be enough.
Do you have any opinion?
Thank,
Wasin
Received on Tuesday, 6 October 2015 08:15:31 UTC