- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Aug 2019 13:01:01 +0000
- To: public-dxwg-wg@w3.org
The motivation for catering for tokens is that existing profile negotiation systems (pyLDAPI, OAI-PMH, OGC Name Server) all use tokens. The things clients using these services currently need to know is a resource URI as well as service endpoints, QSA parameters etc. With the inclusion of tokens in `list profiles` responses, then the number of things client needs to know is reduced - just the resource URI. The additional client burden, if tokens are given by a server but not wanted by the client, is that the client just has to ignore them in the Link header. -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-526174152 using your GitHub account
Received on Thursday, 29 August 2019 13:01:11 UTC