W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > September 2019

Re: [dxwg] Registration of target attribute "profile" for the Link-Header (#501)

From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Sep 2019 07:42:26 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-532562341-1568792545-sysbot+gh@w3.org>
The specification states ".. the profiles representations of resources conform to are unambiguously identified either by either a URI or a token. If the latter, it MUST be mappable to a URI within one particular client/server message pair." 

There is no concept of "preferred token" in conneg-by-ap - its always specified by an unambguous mapping.  

This is sort-of true "If URIs can be used everywhere else, then tokens need only fill the role of providing a nice-looking URI for API requests."  - however more important than nice-looking is that existing APIs that use tokens to specify profiles can be made to conform to this specification by supporting a "list profiles" function that provides the URI mapping - a significant step forward in self-documentation of services - the motivation for the current committed implementors of conneg.  So the subset of people include in "we" needs to include all the community that might use the spec - not a subset who might indeed not need one particular optional feature.

GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/501#issuecomment-532562341 using your GitHub account
Received on Wednesday, 18 September 2019 07:42:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:20 UTC