- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Mar 2018 17:58:05 +0000
- To: public-hydra-logs@w3.org
If that knowledge (managers) is not exposed by the server, I believe there are few limited options here: - client has that knowledge `hardcoded` (the ugliest but the most obvious) - there is other place that can provide that knowledge - server can provide that knowledge within returned (partial) collection's payload - it's an RDF graph, thus it may contain several resources - client can obtain that knowledge from the end-user (i.e. with some kind of form or input field) - client can use any value - server will return with non-2XX response if something goes wrong or just empty result set if no match is found so the client will discover on the fly that the value used was somehow incorrect. Generally, variable mapping only says on which property given value will be used by the server for filtering - it does not say where this value should come from. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/161#issuecomment-376978711 using your GitHub account
Received on Wednesday, 28 March 2018 17:58:10 UTC