Why the collection?

Hello everyone.

Between hydra:Link and hydra:supportedOperations, Hydra seems to have a lot
of descriptive power.

Wouldn't it be better to let developers pick whatever implementations of
the "collection" concept they like and just provide them with the necessary
tools to describe how a client should interact with them?

For however complex or simple the representations provided by such an
implementation might be, Hydra seems to be already capable of describing
what to do with it. A <METHOD> expecting X and returning Y is always the
same.

I guess my question is: why the focus on "collections"? What am I missing?



--

Jacopo Scazzosi
Developer
http://www.jacoscaz.com