- From: Ruben Verborgh via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Aug 2019 09:23:44 +0000
- To: public-dxwg-wg@w3.org
> there is a higher bar that URIs must be resolvable That's not the case for the IETF draft we are preparing through—URIs are just (unique) identifiers. Does the W3C document mandate resolving for _all_ URIs (not just HTTP URIs)? If the main advantage of tokens is that they do not resolve, URIs can do the same thing. It seems that we are building a complex system to not really solve anything. But my earlier questions still stand: what can we assume about clients that need to access the mapping? Can you (and hopefully several others) confirm that clients _always_ know the string of the token? Because if not, we don't even have a viable mechanism. -- GitHub Notification of comment by RubenVerborgh Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-526103182 using your GitHub account
Received on Thursday, 29 August 2019 09:23:46 UTC