- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Jun 2020 21:08:55 +0000
- To: public-hydra-logs@w3.org
Thanks @RubenVerborgh for taking a part in the discussion. >As such, I prefer Option 1 – Downgrade. FWIW, I don't consider this a breaking change, given that I don't think the original definition was valid/compatible with RDF/enforceable anyways. As for considering what might get broken - I know TPF is close to RDF and downgrading hydra ranges for some of the terms will break reasoning process. Resources will be no more `hydra:Resource`, thus any implementation relying on this will get broken. >To me, usage of HTTP URLs implies dereferenceability This is the issue - one of our community members has issues with this assumption. He uses HTTP Urls for identifying resources be for some circumstances he knows that server won't provide any of these resources. Not using `hydra:Resource` will somehow help as it won't impose a resource is somehow guaranteed to have a GET operation supported, but still - HTTP based Url may not be safely obtained just because it is HTTP based. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-640280235 using your GitHub account
Received on Sunday, 7 June 2020 21:08:57 UTC