Re: [Specifications] EntryPoint question

Oh, I see! So am I correct that the `"collection"` attribute at the top-level wasn't meant to imply that it is a "collection" of entry-point links, but rather that the object contained within is itself a `Collection`?

@alien-mcl I was also digging through the history of `1.entry-point.md` to figure out the intent, and it looks like whomever added the additional links was confused in the same way.

As for my "issues" example, let me be more specific. Lets say I'm writing a command-line tool that will import all Issues from the system described by the API and do something with them (save them to a local database, tweet about them, or publish them to another API). In a dumb CRUD API, I would write a client like `get("http://example.com/issues").each { do_something_with_issue }`. In an enlightened Hypermedia API, however, I know that "/issues" can change at any point, so I'm better off starting at the entry point and following a link to get to the resource for "all issues". With the "Issue Tracker example API", I can have my script look for the attribute `"http://www.markus-lanthaler.com/hydra/api-demo/vocab#EntryPoint/issues"` in the expanded JSONLD document. I could have my script do something like `api("http://example.com/").dereference("EntryPoint/issues")`

In the EntryPoint given in the 1.entry-point.md, I'm not sure how to do that. I was mistakenly trying to "select" the Issues item from the `"collection"` attribute, because of the misunderstanding I had. (As an aside, it would be extremely helpful if the Context for that EntryPoint was provided in that example.) How would I use that EntryPoint to "discover" the URL for the "events" resource?

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

Received on Friday, 12 January 2018 00:31:23 UTC