- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 May 2017 18:58:18 +0000
- To: public-hydra-logs@w3.org
> Assuming that there is any API documentation. It is not mandatory. I still don't think it's a good idea to mix the identifiers. If you wanted to make the documentation URIs dereferencable, you'll end up in a weird place where you would be looking for description of the operation `/api/events#new` in the representation of the actual collection. It looks like you consider this a kind of shortcut but I think it's entanglement. Consider this: `/api/events` is unavailable to unauthorized users. Gives some kind of `401`/`403` response. Does it mean that it should be impossible to dereference `/api/events#new`? Finally there's the Occam's Razor argument. Newcomers to Hydra will not be thrilled to consider stuff like how RDF treats hash URI etc. They'll need simple guidelines: 1. My actual API resources go under `/api/whatever` 2. My Hydra documentation go under `/api-documentation` or something. Separate URI space will also make it easier to manage in a server-side implementation. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/121#issuecomment-298728605 using your GitHub account
Received on Tuesday, 2 May 2017 18:58:24 UTC