- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Fri, 15 Jan 2016 10:29:52 +0100
- To: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>, public-hydra@w3.org
Dear Tomasz, >> Curious to see the definition that describes >> exactly what separates a view from a collection :-) >> (That's what I'm after in this whole thread.) > > please tell me why are we mostly confined to collections in this discussion? We're not: as you can see above, I want to know how exactly a view _differs_ from a collection, such that we can proceed to think about views in their own right. I'm not trying to hijack the discussion; rather, I want to force us to clearly define a view, as this has not happened so far at the moment. My hunch is that any definition of a view will always be such that, implicitly or explicitly, a view is a collection (because all the views I've seen so far, are indeed a set of things with common properties, or in other words: a collection). So please prove me wrong, as this will get us closer to an understanding of what a view is. > The server could advertise a view, which filters by those properties' labels. > In my eyes a view should be defined as derived from any resource, collection or otherwise. As far as I understand, views so far were seen as views on a collection, hence hydra:PartialCollectionView. Best, Ruben
Received on Friday, 15 January 2016 09:30:36 UTC