W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > April 2007

File suffix and media type of XHTML 1.1 test cases

From: Simone Onofri <simone.onofri@gmail.com>
Date: Mon, 23 Apr 2007 19:41:31 +0200
Message-ID: <52bd7c3d0704231041u407d6695g9373847bbe915922@mail.gmail.com>
To: RDFa <public-rdf-in-xhtml-tf@w3.org>

Dear TF,

Regarding media types [1] there a a document explain this:


The 'application/xhtml+xml' media type [RFC3236]
is the media type for XHTML Family document types, and
in particular it is suitable for XHTML Host Language document types.
XHTML Family document types suitable for this media type include
[XHTML11] and
An XHTML Host Language document type that adds elements and
attributes from foreign namespaces MAY identify
its profile with the 'profile' optional parameter or other means such as
the "Content-features" MIME header described in RFC 2912
Each namespace SHOULD be explicitly identified through
namespace declaration [XMLNS].  This document
does not preclude the registration of its own media type for specific
XHTML Host Language document type.


Of course for MIME [1]


application/xhtml+xml' SHOULD be used for serving
XHTML documents to XHTML user agents.  Authors who wish to support
both XHTML and HTML user agents MAY utilize content
negotiation by serving HTML documents as 'text/html' and XHTML documents
as  'application/xhtml+xml'.  Also note that it is not necessary
for XHTML documents served as 'application/xhtml+xml' to follow
the HTML Compatibility Guidelines.


Regarding suffix anyone have informations for (default) support of
.xhtml on Apache, IIS, browsers? Otherwise Web Authors may use to send
correct content-type:

- Server Side Languages (PHP, PY and more...)
- .htaccess on Apache
- Settings on IIS (but actually web hosts cannot permit to change
these settings)
- @http-quiv



[1] http://www.w3.org/TR/xhtml-media-types/#summary
Received on Monday, 23 April 2007 17:41:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:22 UTC