- From: visva-io via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2023 13:31:17 +0000
- To: public-hydra-logs@w3.org
I know this has been a while since this was merged, but I am starting to design a quite complex API using Hydra and I have an issue with (not the example but the `hydra:SupportedProperty` ):
```turtle
a hydra:SupportedProperty ;
hydra:propety vocab:id ;
hydra:required "true"^^xsd:boolean ;
hydra:writable "true"^^xsd:boolean ;
hydra:readable "true"^^xsd:boolean ] ;
```
since this is defined in the documentation, it seems to assume that the `required`, `writable` and `readable` values will be valid in all situations. In my API, a particular `supportedClass`, and I have many examples of this, may sometimes support `writable` but sometimes not, it could depend on many factors such as: the context in which the `supportedClass` instance is found, its state, the permissions of the user/client seeing the instance.
My questions: can the API documentation not provide this information when it cannot be provided (are they required properties)? Would the API still be Hydra compatible in such case?
--
GitHub Notification of comment by visva-io
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/164#issuecomment-1721288707 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 September 2023 13:31:18 UTC