content-type: Difference between revisions
Jump to navigation
Jump to search
AndyMabbett (talk | contribs) (should be used) |
(Switched SHOULD to MAY, the publisher does not always have control over the end media, much like hreflang the end site does not have to honor the publisher declarations) |
||
Line 7: | Line 7: | ||
* [http://en.wikipedia.org/wiki/Internet_media_type media type]. Recommend AGAINST using the term "media type" to refer to content-type as it is overloaded, and often (even more often among web design circles) used to refer to '''[http://www.w3.org/TR/CSS21/media.html CSS media types]'''. | * [http://en.wikipedia.org/wiki/Internet_media_type media type]. Recommend AGAINST using the term "media type" to refer to content-type as it is overloaded, and often (even more often among web design circles) used to refer to '''[http://www.w3.org/TR/CSS21/media.html CSS media types]'''. | ||
In microformats, as elsewhere, content-type {{ | In microformats, as elsewhere, content-type {{may}} be used when linking to audio files, PDF files, and other attachments. |
Revision as of 10:43, 5 February 2008
Content Type
AKA:
- HTTP Content-Type - this is the preferred terminology, especially as it emphasizes the content aspect.
- MIME type. This terminology is deprecated.
- media type. Recommend AGAINST using the term "media type" to refer to content-type as it is overloaded, and often (even more often among web design circles) used to refer to CSS media types.
In microformats, as elsewhere, content-type MAY be used when linking to audio files, PDF files, and other attachments.