- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 31 Jan 2021 09:39:40 +0000
- To: public-hydra-logs@w3.org
I believe this issue is somehow outdated. In recent changes we've modified ranges and domains of several predicates (i.e. `rdf:Resource` in favour of `hydra:Resource) as the dereferencable requirement is removed (as it was broken from the beginning). The `hydra:Class` is still there acting as a glue of all hydra defined concepts and `hydra:Resource` is left acting for developers as a _promise_ that heir API's resources are, well, dereferencable. As for the `hydra:title` and `hydra:description` I still see some use cases - these usually will be API specific, thus in case an API reuses some terms from other vocabularies, using hydra specific predicates will narrow their applicability only to that very API (in case some data aggregators will crawl those data). I'd leave those terms as they are. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/90#issuecomment-770354311 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 31 January 2021 09:39:41 UTC