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)

> tokens (in the context of conneg) require less work for clients that already use them (because servers do) because now there would be a way of automating finding what they mean.

I have a hard time understanding that.

"finding what they mean" then equals "determining the URI for the non-URI identifier"?
To then use the URI in the future?
So those systems have to be _changed_ to look up the non-URI as URI?
If you have to change anyway, why not simply change it directly into a URI?

> the proposed solution is the only option we've identified that seems workable

And changing non-URIs into URIs is not workable because?
As I wrote above, we could just make a list.

> but less work than if they are forced to change APIS to support URIs

I can't see that. Tokens are strings, URIs are a subset of strings. The only change (if even needed) is to accept strings that start with `xyz:`.

…compared to implementing a whole mapping mechanism.

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

Received on Thursday, 29 August 2019 13:26:08 UTC