- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Apr 2020 07:54:20 +0000
- To: public-hydra-logs@w3.org
>I'm sorry but you are just rambling now For me the logic behind the Iri template is as follows (using a collection example): ``` Dear client, here is a collection and all (some) of it's members. You can GET and PUT them. But hey, if you want, here is also a formula on how you can point directly to each member without searching it through my members. You can use this formula to operate on those members, but don't forget, these are still my members ``` The iri template does not change the fact that the each member is in relation with that collection. Resource created at runtime using the formulat provided is not an exception here and it is correct to state (still following the example) that the _example collection) hydra:member some:iriTemplateCraftedIri is true. >Right, so a second, default (?) option would be to resolve against the effective URI of the request, >correct? Yes as it fits the RFC3986. What if there are multiple API documentations available? It is not forbidden and the server can provide multipe API documentation links (i.e. parts, incremental upgrades, whatever reason was behind such a behavior). -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/208#issuecomment-619802243 using your GitHub account
Received on Monday, 27 April 2020 07:54:21 UTC