Re: Moving forward with hydra:filter (ISSUE-45)

The problem with that approach was that it introduced coupling, where the client required intimate knowledge about the data structures (used terms and the graph layout)

Tom



On Dec 20, 2015, 20:49, at 20:49, "Karol Szczepański" <karol.szczepanski@gmail.com> wrote:
>>Very common in current rest API is a query param like 
>>"fields=created,modified,...".
>>Something like this should be easy to model with IRI templates.
>>
>>Alternatively or additionally it might make sense to let the client
>specify 
>>a shape.
>
>Just to share my experience within this area, in one of our projects
>we've 
>approached that scenario with HTTP Expect Header where we've used
>SPARQL 
>like property paths to define which properties/graphs to 
>return/explode/block.
>Only issue with that is that XMLHttpRequest Level 1 spec disallows that
>
>header to be sent and we had to send a Prefer header instead (RFC
>7240).
>
>Best
>
>Karol