- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jul 2021 20:03:58 +0000
- To: public-hydra-logs@w3.org
> Only how 'bout we make this an extension and not core? I'm keen to have it in the core - it's better to have extensions to take care of something that is out of scope of hydra. Hypermedia controls telling what can be done and what cannot be done feels to fall in that scope. > ...retracted has to be directly associated with a specific resource. Not really. I can imagine there is a supported operation for resources of class Collection, but resources of class ReadOnlyCollection would have that operation disabled on the API documentation level (I know that example is a long shot ;)) > And maybe we could reuse hydra:operation and add a class of unsupported operations? We could, but it seems not enough. Marking operations with logical behavior like `schema:RemoveAction` is outside of the spec and seems not be unique enough (you could have several operations on some resource marked the same way, but i.e. expecting different resources. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/241#issuecomment-878556876 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 July 2021 20:04:01 UTC