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

Re: [dxwg] Specify the realisation order of precedence for conflicting profile negotiation situations (#505)

From: Annette Greiner via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Oct 2019 07:14:40 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-545780302-1571901279-sysbot+gh@w3.org>
I think it's okay to go with the QSA approach over HTTP headers, since handling query strings would have to be done by a separate web app, so the web server would know to hand it off without parsing anyway, and returning a 404 for a client request that assumes the wrong approach seems reasonable. Since we are allowing for alternative realizations, how does the order of precedence work with as-yet-unspecified ones? Maybe the only real conflict is between HTTP headers and web apps. When you say that "a client MAY specify conflicting choices via different mechanisms", I think you don't mean the RFC2119 version of "may" here. Maybe "In the case where a client requests one profile via one mechanism and another profile via a different mechanism, the order of precedence . . ."

-- 
GitHub Notification of comment by agreiner
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/505#issuecomment-545780302 using your GitHub account
Received on Thursday, 24 October 2019 07:14:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:58 UTC