- From: Ruben Verborgh via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Aug 2019 13:39:56 +0000
- To: public-dxwg-wg@w3.org
I have a couple of questions, the answers of which might help me understand the reasons for a client to use a token instead of a URI. - Does the client, wishing to use a token, know the string value of this token in advance? (i.e., is the token programmed into the client?) - If no, I presume it must use the URI to look up the token? - Which then begs the question, why not use the URI? - If yes, what is the advantage of programming the token (which needs a server-specific lookup mechanism) over the URI (which does not)? - Or is this a matter for manual requests with `curl`, i.e., of saving keystrokes / avoiding typos? - Does the client, wishing to use a token, know the URI of the profile in advance? (i.e., is the URI programmed into the client?) - If yes, why does it still need the token? - If no, how will it verify whether the token indeed corresponds to the desired profile? - What are the reasons, in general, for a token to not be a URI (not specifically HTTP URI)? I'm asking specifically because this can help us assess the validity of a proposed [token mapping process](https://w3c.github.io/dxwg/conneg-by-ap/#listprofiles-tokens). -- GitHub Notification of comment by RubenVerborgh Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-525306101 using your GitHub account
Received on Tuesday, 27 August 2019 13:39:58 UTC