- From: Annette Greiner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Nov 2018 22:57:12 +0000
- To: public-dxwg-wg@w3.org
agreiner has just created a new issue for https://github.com/w3c/dxwg: == Query string implementation of profile selection == I understand the value of offering an example of how to implement selection of a dataset by its profile in ways other than using content negotiation. My expectation has been that we would describe one example of how a system could be designed to enable requests for datasets that implement specific profiles. I would expect that to appear in the profiles guidance document. The conneg document, however, currently specifies a method of implementing negotiation (not just selection), which I see little reason to demonstrate. We have a mandate to explain how to use content negotiation, not to explain how to implement the equivalent in some other way. In fact, I think that if people want to enable negotiation by profile, they should simply be using conneg. I see little reason to create an alternative that implements the same features. Also, this exercise should not be normative. I don't believe in specifying architecture choices that are better made in the context of a particular system. A related nit is that the document draws a distinction between 'HTTP' and 'QSA', which erroneously suggests that using query strings is not using HTTP. Please view or discuss this issue at https://github.com/w3c/dxwg/issues/544 using your GitHub account
Received on Tuesday, 6 November 2018 22:57:14 UTC