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

I've turned operations into blank nodes, which seems the most agreed state as for today.

> But /api/events#new and /api/events are not the same IRIs? 

I've never said that, I said that `/api/events` denotes what I consider two different resources:
the api resource on which client can perform supported operations
```json
{
  "@id": "/api/events",
  "@type": "hydra:Collection"
}
```
on of the supported operations on that resource
```json
{
  "@id": "/api/events",
  "@type": "hydra:Operation",
  "method": "GET",
  "returns": "hydra:Collection",
  "operations": [ "/api/events" ]
}
```

since the same IRI denotes them, it means that one can consider them the same resource, which may result in merging them into
```json
{
  "@id": "/api/events",
  "@type": ["hydra:Operation", "hydra:Collection"],
  "method": "GET",
  "returns": "hydra:Collection",
  "operations": [ "/api/events" ]
}
```

now operation has a supported operation (itself) which should return an instance of "hydra:Collection", even if your response includes both in separate named graphs (as in @RubenVerborgh's [Turtles all the way down](https://ruben.verborgh.org/blog/2015/10/06/turtles-all-the-way-down/)) IMO conflating the resource with one of the operations on that resource can cause a lot confusion.

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

Received on Wednesday, 3 May 2017 01:11:00 UTC