- From: Annette Greiner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Sep 2019 00:26:51 +0000
- To: public-dxwg-wg@w3.org
Maybe we don't really need to worry so much about indicating tokens in headers. We already agreed in issue #453 that these tokens don't need to be globally unique, that they are just suggested or preferred identifiers. I would suggest we take that one step further and say that they are suggested/preferred specifiers, not identifiers. Rather than calling them alternative identifiers for profiles, we could limit their use to within application URLs. A given API may use any locally unique token to allow selection of a particular instance of a dataset that conforms to a profile, and it can always return the URI as the actual identifier for the profile used. A listing of available profiles can include the tokens or (better) full URIs for the dataset and also the actual URI identifiers for the profiles themselves. In this view, the token is simply a convenient specifier for use in a query string or the path of a URL. The suggested token needn't be specified anywhere except in the profile itself, and even that is just a helpful suggestion. This allows tokens to continue to be used where they are currently being used and where they nicely avoid complex URIs, and it avoids calling them a formal identifier for the profile. I don't see a need for the token to be dereferenceable on its own if the actual URI is included as the identifier in the server response. -- GitHub Notification of comment by agreiner Please view or discuss this issue at https://github.com/w3c/dxwg/issues/501#issuecomment-531055451 using your GitHub account
Received on Friday, 13 September 2019 00:26:52 UTC