Re: [Specifications] How to document forbidden dereferencability (#216)

> But why does the server generate those non-existing URIs then?

Those don't have to be generated by the API in question. And quite specifically, this discussion started from hypermedia controls. 

In my APIs I often define operations as such with hash URIs like `http://my.app/api#SomePostOperation`. Just enough for the client to find them in the API Documentation graph. But strictly speaking this is not dereferencable and I already break the implicit promise of `hydra:Resource`

And `schema.org` and many other shared vocabularies will also not play ball

-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-640880158 using your GitHub account

Received on Monday, 8 June 2020 20:52:11 UTC