- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Sep 2019 01:21:03 +0000
- To: public-dxwg-wg@w3.org
If you cannot contemplate content negotiation occurring in your implementations then you are free to use the long-hand version @dr-shorthair suggests. If you have content negotiation and use that pattern then there is a lot of redundant duplication of the resource identifier, but it doesnt break. DCAT-AP is effectively saying thats the pattern you MUST use. If that is unacceptable to a user of DCAT-AP (such as implied by the feedback) thats still an issue with DCAT-AP not DCAT itself. The response to the question should not be dictated by whether people wish to use content-negotiation in their own environments, or understand its application in general, but whether DCAT itself needs to change - and I dont think it does because its not the source of the restriction which is apparently problematic. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1055#issuecomment-530625359 using your GitHub account
Received on Thursday, 12 September 2019 01:21:04 UTC