Pagination of non-collections

Hi everyone

In my latest response to Markus [1] I've expressed my concerns about 
defining any kind of navigation scheme for Hydra may be a bad idea.

Having written that message I've come up with another though about 
partial representations.

We all concern ourselves with collections. But what about another kind 
of resources which are large enough so that it may be served in multiple 
smaller chunks. Like an object with multiple collections. Each 
collection may be small but together the size becomes significant.

/person/Tomasz
/person/Tomasz/friends
/person/Tomasz/interests
/person/Tomasz/projects
/person/Tomasz/hobbies
/person/Tomasz/family
etc.

Each URI above could contain a partial view of
/person/Tomasz and they would be linked by some custom properties.

Isn't this similar to paging collection? My point is that a lot of time 
is being invested to define one very specific way for addressing partial 
representations (of collections) while a more general approach could be 
possible to tackle a multitude of similar cases.

At the same time Hydra clients can be kept simpler because there is a 
general way for doing partial representation and for everything else 
there already are Links and IriTemplates...

Thoughts?

Regards,
Tom

Received on Sunday, 15 February 2015 12:19:35 UTC