Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Jonas Sicking
Maciej Stachowiak wrote: On May 14, 2007, at 9:26 AM, Bjoern Hoehrmann wrote: * Anne van Kesteren wrote: It was added for compatibility with WebKit. I don't really feel strongly about it, ... Excellent, I then look forward to a proposal that Jonas and I do not regard as inappropriate. I do

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Ian Hickson
On Mon, 14 May 2007, Maciej Stachowiak wrote: > > The question we should be examining is whether [text/xsl] is actually > used in practice. If it is, then the right course of action is to get it > registered with the IETF (and presumably marked deprecated). If it > isn't, then we can safely req

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Bjoern Hoehrmann
* Maciej Stachowiak wrote: >I don't personally feel strongly about this particular issue (I don't >think it is common for sites to send text/xsl as a MIME type on the >wire), but since when is the fact that someone "regard[s] [it] as >inappropriate" a valid reason to change something? Should

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Robert Sayre
On 5/14/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: Defining particular behavior when a type is seen is not the same as standardizing it, in my opinion. Disagree, since MIME types are used to route messages to code with particular behaviors. However, I personally don't feel too strongly

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Maciej Stachowiak
On May 14, 2007, at 10:52 AM, Robert Sayre wrote: On 5/14/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: Personally I don't think lack of registration is a particularly strong reason not to define handling for a particular MIME type. At the very least, the W3C/IETF liasons should discuss

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Robert Sayre
On 5/14/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: Personally I don't think lack of registration is a particularly strong reason not to define handling for a particular MIME type. At the very least, the W3C/IETF liasons should discuss this. It is exceedingly bad manners to squat a on pa

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Maciej Stachowiak
On May 14, 2007, at 9:26 AM, Bjoern Hoehrmann wrote: * Anne van Kesteren wrote: It was added for compatibility with WebKit. I don't really feel strongly about it, ... Excellent, I then look forward to a proposal that Jonas and I do not regard as inappropriate. I don't personally feel s

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Bjoern Hoehrmann
* Anne van Kesteren wrote: >It was added for compatibility with WebKit. I don't really feel strongly >about it, ... Excellent, I then look forward to a proposal that Jonas and I do not regard as inappropriate. -- Björn Höhrmann · mailto:[EMAIL PROTECTED] · http://bjoern.hoehrmann.de Weinh. Str

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Anne van Kesteren
On Thu, 10 May 2007 17:21:30 +0200, Bjoern Hoehrmann <[EMAIL PROTECTED]> wrote: * Anne van Kesteren wrote: If one UA treats Content-Type:text/foobar as XML and another UA does not and a site starts relying on text/foobar being treated as XML we have a problem. We have very many problems of

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Anne van Kesteren
On Wed, 09 May 2007 00:49:56 +0200, Jonas Sicking <[EMAIL PROTECTED]> wrote: Anne: was there a reason 'text/xsl' was included other than "IE does it"? Or is it known to actually break sites? A Contributor from WebKit implementing XMLHttpRequest requested it to be included for compatibility