- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Jun 2020 18:40:34 +0000
- To: public-hydra-logs@w3.org
>My point is rather that the whole hydra:Resource and rdf:Resource distinction is the nitpicking. Yep - it returned in several discussions here and there. Maybe there is still hope for those terms. Imagine a given Urls are in local API's domain, let's say `http://some.uri/api/vocab#Class` provided by the `http://some.uri/api` - implementation may give a promise that this very resource may be safely dereferenced. Still, decoupling some ranges from `hydra:Resource` or `hydra:Class` (probably some class inheritance should be changed as well) sounds tempting. Anyway, does it answer topic of this issue - document forbidden dereferencability? Maybe giving tools promising a resource can be safely dereferenced leaving all other Uris unspecified (call it on your responsibility) is enough? -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-640802730 using your GitHub account
Received on Monday, 8 June 2020 18:40:35 UTC