- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2020 23:19:29 +0000
- To: public-dxwg-wg@w3.org
The expectation was that canonical URIs were preferred, but realistically URL encoding URIs as query string arguments is ugly and counter to typical practice for systems that already have some equivalent concept of alternative profiles that can be chosen. There are two things we need to consider: 1 - whether we should allow tokens in Accept-Profile values 2 - how to make the spec clearer whichever option we choose. Lets hears pros and cons from people about allowing tokens in the Accept header. (PS its no great drama for me in the implementation to allow it - so I'm agnostic, other than I feel there must be URIs for profiles accessible otherwise there is no interoperability benefit at the data level - and we are a Data Exchange WG :-) ) -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1219#issuecomment-592227362 using your GitHub account
Received on Thursday, 27 February 2020 23:19:31 UTC