- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Apr 2020 20:48:57 +0000
- To: public-hydra-logs@w3.org
> But after template expansion you will get a relative IRI that needs to be resolved to an absolute one. Yes, and I propose two base Uris to choose from: link context or one provided by the API > That IRI/URI somehow becomes part of the graph IRI template is an algorithm of how a client can create IRI's of reasources that normally would be provided within the graph. I do not see how it becomes "part of a graph". You have no reason to ever add it as a triple. You only need to construct the absolute URL and use it to perform a HTTP request. > Having that in mind that very IRI/URI should fit all the procedures applicable to an ordinary Uri. I have no clue what "procedures" you refer to :) > mentioned explicit mechanism sounds like a consensus `hydra:LinkContext` would be the option I am looking for right now. What about any alternatives? A property of the `ApiDocumentation`? And the default behaviour in case of no value specified? -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/208#issuecomment-619622746 using your GitHub account
Received on Sunday, 26 April 2020 20:48:59 UTC