search

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group
Other
139 stars 25 forks source link

Add RetrieveResourceOperation #5

Closed lanthaler closed 10 years ago

lanthaler commented 11 years ago

_Raised by Thomas Hoppe:_

There are formal Operations for modification operations "CreateResourceOperation" etc. I'm opting for also having a corresponding Read operation.

This is for example useful to advertise possible operations and might also be useful for a formally sound integration with a AuthZ solution.

lanthaler commented 10 years ago

This issue was closed mistakenly by a git push running amok.

damnhandy commented 10 years ago

If a RetrieveResourceOperation is an operation with a hyrdra:method value of GET, we have to consider the role of IriTemplate. Functionally, they both offer the same utility but expressed differently. If that's the intent behind a RetrieveResourceOperation, I'd consider dropping IriTemplate in favor of this RetrieveResourceOperation.

vanthome commented 10 years ago

The keep or remove part is meanwhile tracked in https://github.com/HydraCG/Specifications/issues/11

lanthaler commented 10 years ago

PROPOSAL: Describe in the specification that operations are there to modify resource state, links (like hydra:search) and IRI templates, on the other hand, are there to drive the application state, i.e., allow navigation and retrieval of data. Consequently, a RetrieveResourceOperation would be inconsistent with this classification.

lanthaler commented 10 years ago

Call for consensus: http://lists.w3.org/Archives/Public/public-hydra/2014Jul/0078.html

lanthaler commented 10 years ago

RESOLVED: Do not introduce RetrieveResourceOperation and remove other Operation types.