Some Thaughts on Hydra Core

Hello,

I'm a intrigued follower of the efforts around Hydra.
Now the time has come to contribute my thoughts on some aspects:

- "CRUD" stands by convention for 
(http://en.wikipedia.org/wiki/Create,_read,_update_and_delete) for 
Create, Read, Update, Delete while in the Spec "R" means Replace. I 
recommend to stick to this convention. A replace operation is just a 
special kind of "Update".
- There are formal Operations for modification operations 
"CreateResourceOperation" etc. I'm opting for also having a 
corresponding Read operation.
This is for example useful to advertise possible operations and might 
also be useful for a formally sound integration with a AuthZ solution.
- A typo "is be defined to"
- Sorting of paged collections should be specified and examplified which 
is not the case yet.
- Authorization is a major concern and therefore I would also like to 
see a chapter which describes how access to a hydra-driven API can can 
restricted.
I think the obvious strategy is to "render" hydra-core documents with 
only the operations which are allowed for by the requesting client.
This may sound natural but I think it is essential information for 
someone exploring the matters.

Keep up the good work,
Thomas