- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Apr 2020 10:20:51 +0000
- To: public-hydra-logs@w3.org
>But the function's return value is a runtime concern that in theory can change on every invocation >of the function No questions about that >and thus isn't something that can exist as a part of the graph or API description. Why? Why a function can be a part of the graph but runtime results of that very function shouldn't be treated as like? I find a reasoning process similar to that situation. There are statements produced in the process and in order to correctly interprete all the data within the graph the produced statements should be taken into account, even when these additional statements are not explicitely declared (but are product of input data and algorithm). Am I wrong? >If the constructed URI is relative, it's up to the Hydra client to resolve it according to processing >rules that are outside of both scope and control of the serialization format used to communicate >the template. Not sure I understand this correctly. Indeed, RDF serialization has no IRI template matters within it's scope. But hydra clearly states that `hydra:template` is rooted in RFC 6570 (if not stated otherwise) and that template should be handled according to this RFC's rules. Product of is an URI that should also be handled according to RFCs related to Uris -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/208#issuecomment-619884752 using your GitHub account
Received on Monday, 27 April 2020 10:20:54 UTC