Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation

I'd propose to get rid of the identifier for embedded operations altogether. It's completely fine making them blank nodes... and probably also easier to understand for people unfamiliar with Hydra. This is also in line with @alien-mcl's intention:

> This was actually on purpose - with a simple trick I can prevent clients with pre-loading capabilities from requesting other resources unnecessarily.

All the other changes in this PR look good to me and fix stuff that has actually been already called out in the original PRs (e.g. `method` vs. `httpMethod`). Github makes it pretty hard to keep track of such requests. Do you guys have any suggestions on how to keep a clear record on what changes were requested and which were implemented?


-- 
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/121#issuecomment-298741499 using your GitHub account

Received on Tuesday, 2 May 2017 19:49:31 UTC