- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Fri, 15 Jan 2016 13:19:05 +0100
- To: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Cc: Karol Szczepanski <karol.szczepanski@gmail.com>, Markus Lanthaler <markus.lanthaler@gmx.net>, Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>, Hydra <public-hydra@w3.org>
>> It's the collection of properties that describe /people/karol, >> and you are requesting a subset (view) of those properties. >> > > This could work. But do I understand correctly that essentially this treats any data as a collection of triples? Yes—however, this is _not_ how I understood Hydra views. I was just arguing that, if necessary, Karol's example can be seen as such. > I expect most people, especially newcomers to hydra treat such simply as objects. +1 > This is where a clear distinction of collection and filter arises. A view /users?displayColumns=name,age would be applied to a collection of users but doesn't filter the members but rather the members' inlined representations. What do you think? This is were we cross the boundary of resources/representations; might get very tricky there. I think we should first focus on resources. Ruben
Received on Friday, 15 January 2016 12:19:38 UTC