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

Re: [dxwg] Query string implementation of profile selection (#544)

From: Lars G. Svensson via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 Sep 2019 04:48:30 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-534849991-1569386909-sysbot+gh@w3.org>
@agreiner [scripsit](https://github.com/w3c/dxwg/issues/544#issuecomment-474535369)

> Our charter calls for development of content negotiation by profile. Nothing in that document suggests a requirement to offer a query-string-based specification for handling profiles. I see no reason to think that such a thing would even be implied by the charter, as there exists no prior standard for handling content negotiation with query strings. If such a thing is needed at all, it would make the most sense to develop it in the context of existing use cases of content negotiation, such as language and media type. Offering normative specifications for a query-string-based negotiation method is overreaching our charter.

The conneg deliverable is [defined as](https://www.w3.org/2017/dxwg/charter#normative) "An explanation of how to implement the expected RFC and suitable fallback mechanisms as discussed at the SDSVoc workshop." QSA is proposed as a fallback mechanism, so I'd say it's definitely covered by the charter. That the implementation description is normative doesn't say that you have to implement it, only that _if_ you implement it, that is the interoperable way of doing it.

GitHub Notification of comment by larsgsvensson
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/544#issuecomment-534849991 using your GitHub account
Received on Wednesday, 25 September 2019 04:48:32 UTC

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