- From: Alex Milowski <alex@milowski.org>
- Date: Mon, 3 Jan 2011 18:56:31 -0800
- To: public-webapps@w3.org
In reading through the current draft of XMLHttpRequest [1] I see a consistent use of the term 'MIME type' instead of 'Media Type' as defined by RFC 2046 [2]. RFC 2046 does not define the term 'MIME type' and only refers to 'MIME Media Type' once within the RFC document. Otherwise, it would seem the proper term is 'Media Type'. Further, the 'Content-Type' header used to type the MIME entity as described as: "The Content-Type field is used to specify the nature of the data in the body of a MIME entity, by giving media type and subtype identifiers, and by providing auxiliary information that may be required for certain media types." Again, it would seem the value is a 'Media Type' and not a 'MIME type'. I think it would be preferred for this specification and RFC 2046 agreed on the data type name for the value of the Content-Type header. [1] http://dev.w3.org/2006/webapi/XMLHttpRequest/ [2] http://www.ietf.org/rfc/rfc2046 -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Tuesday, 4 January 2011 02:57:05 UTC