Re: [dxwg] A short token to specify a profile may be used as long as there is a discoverable mapping from it to the profile's identifying URI [ID5] (5.5) (#290)

>     * because as i tried to explain we offer a mechanism for them to discover both the URIs and tokens

Which gives them the token _and_ the URI—so why would they want to us the token then?

All of the above answers make I me very concerned about the token mechanism, as it complicates things unnecessarily, since there seems to be no single action that a client can do with a token that it could not already do.

The argument above that this mechanism would allow to

> describe systems that already, or prefer to, use short tokens.

is in my opinion not relevant, because the only case for such a preference seem to be legacy. Yet these would _still_ need to be adapted to use the mapping mechanism, so easier to just replace the tokens by URIs.

How many such tokens are actually in use today? Is it more than 10 or 20?
Wouldn't it just be easier to publish one constant token-to-URI mapping for those that exist (let's say `xyz` becomes `https://w3id.org?dxwg/tokens#xyz`) and leave it at that?

-- 
GitHub Notification of comment by RubenVerborgh
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-526171563 using your GitHub account

Received on Thursday, 29 August 2019 12:54:19 UTC