- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Jun 2020 08:11:28 +0000
- To: public-hydra-logs@w3.org
I think you are stretching the argument too thin over nit-picking on RDF nuances. Most people will not go into the details of URI vs the actual resource. To them if the spec says "hydra:Resource are guaranteed to be dereferenced" and this will be enough. Hence the desire to write implementation accordingly. The `hasDereferenceableUri` could be more kosher but more alien to non-RDF people still. That is not to say I don't agree. I would also like to remove the ranges. The promise of dereferencability is broken anyway. Even all the `hydra:Class` etc which come with an API Documentation could likely not be dereferencable, despite being an implied `hydra:Resource`. It would be a lot of additional burden to ensure that every API's Hydra term indeed nicely dereferences. Where the default behaviour is to simply find those resources in the API Documentation resource representation. Thus, the only resource which really does have to dereference is the API Documentation. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-640442456 using your GitHub account
Received on Monday, 8 June 2020 08:11:30 UTC