OK, so these are now done and available:

[x] Server-side support for hydra:Collection in API Documentation [x] Server-side support for hydra:Collection and hydra:PartialCollectionView in in-band data payload (RDF only) [x] Client-side support for hydra:Collection in API Documentation [x] Client-side support for hydra:Collection and hydra:PartialCollectionView in in-band data payload (RDF only) [x] Support for hydra:Collection in XSLT API Documentation transformation

The worst nightmare was API documentation client-side analysis, especially the data model - OWL is wonderful for description, but terrible for analysis.

I need to think on the next steps. One of them would be finally to put my hands on the Hydra_console and test it against my API documentation. I’m somehow discouraged from doing it as I feel that it won’t work due to not-that-simple OWL description. I’d also try to fix the known (for me at least) bug in the framework that won’t match a controller action if a unpredicted query string parameter is introduced (i.e. random cache-disabling one). I’d also try to move the client code to a separate node.js project and think about pushing it to the NPM.

I need to write those down and pick one. But hey, where is my rest?