- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jul 2021 20:27:32 +0000
- To: public-hydra-logs@w3.org
> This is not OOP, where I gather a term like ReadOnlyCollection would originate.
I know, but nothing better came up.
> Not unique? Yes, you would introduce custom operation/action types for more precise semantics.
Imagine that:
```turtle
# ApiDocumentation
api:Basket a hydra:Class;
hydra:supportedOperation [
a hydra:Operation, api:AddToBasket;
hydra:expects api:Product
],[
a hydra:Operation, api:AddToBasket;
hydra:expects api:Service
]
```
```turtle
</services/whatever> a api:Service;
hydra:operation [
a hydra:Operation, api:AddToBasket;
hydra:expects api:Service;
hydra:availability hydra:Forbidden
]
```
User may have a `Service` (this class is disjoined from `Product` as i.e. in GoodRelations) being configured, but it cannot be added to the basket yet - and in the example above providing a type is not enough. It will be unique enough with expected type, but it's getting complex. I'd stay at operation's Iri.
--
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/241#issuecomment-878572492 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:27:35 UTC