[Specifications] EntryPoint question

paul has just created a new issue for https://github.com/HydraCG/Specifications:

== EntryPoint question ==
I'm having trouble figuring out the "correct" way to have an EntryPoint. The use-cases documentation for Entry Point [1.entry-point.md](https://github.com/HydraCG/Specifications/blob/master/drafts/use-cases/1.entry-point.md#details) has an example where all the links are inside a `"collection"` attribute. The Hydra Console demo app has instead the links as attributes at the root level. I assume that the use-case example is just newer, and top-level attributes is no longer the correct way to do it?

I think however, the newer "style" is not as useful because there's no human-friendly "name" by which to find the link. For example, if I'm scripting a client to go get all the Issues from the entry point, in the old style I just look for "issues" attribute. In the new style, though, if I want to do the same for Events, I'm not even sure what to look for. `@id` is `[http://example.com]/api/events`, and `"title"` is a totally human "List of Events". There's the `manages.object` attribute with `"schema:Event"`, but I think this just says that this collection is a collection of Events. Ideally, I'd be able to tell my client "go look in the entry point document for `"events"` (or `"allEvents"` or something) and follow that URL". There doesn't seem to be any way to do that in the current scheme.

Sort of tangentially related, I also notice that the `supportedOperations` for all the entry point items are always "POST". Is a "GET" operation on all URLs just always assumed to be possible?

Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/155 using your GitHub account

Received on Wednesday, 10 January 2018 22:06:23 UTC