I've expanded upon @smizell's work by refactoring the representer code so that common parts are extracted and used but Hydra-rspecific code independently.
As for Hydra, I generate paged collection with 20 items per page and also had to create additional files for JSON-LD context and Hydra API Documentation
Let me experiment with keeping the base URL completely out of the representer. Theoretically it should be handled bu JSON-LD processing code, based on the requested resource id
I've expanded upon @smizell's work by refactoring the representer code so that common parts are extracted and used but Hydra-rspecific code independently.
As for Hydra, I generate paged collection with 20 items per page and also had to create additional files for JSON-LD context and Hydra API Documentation
fixes #8