- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Jul 2019 20:33:04 +0000
- To: public-hydra-logs@w3.org
I'm still not sure about this. In practice I could accept an API where a property is used both with a concrete URI as well as a template. The client would have to decide how to act based on what the object is (either present a form or a link). Makes sense? I'm mildly in favour of keeping the current solution. `hydra:Link` does have a fairly weak semantics. An indirect link could be acceptable. >But a hydra:TemplatedLink does mostly refer to a blank node, that is not dereferencable. See, technically, the presence of an URL identifier determines (potential) dereferencability. `Link` is an additional hint to prevent clients from blindly `GET`ing everything. A templated link is not so different, only with the URL being constructed by the client with extra input. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/197#issuecomment-507414937 using your GitHub account
Received on Monday, 1 July 2019 20:33:05 UTC