- From: Simon Pieters <simonp@opera.com>
- Date: Mon, 22 Jun 2009 10:13:54 +0200
- To: public-pfwg-comments@w3.org
- Cc: "wai-xtech@w3.org" <wai-xtech@w3.org>
http://www.w3.org/TR/wai-aria/#xhtml_dtd <!-- This is the driver file for a sample XHTML + ARIA DTD. Please use this public identifier to identify it: "-//W3C//DTD XHTML+ARIA EXAMPLE 1.0//EN" --> <!ENTITY % XHTML.version "XHTML+ARIA 1.0" > <!-- For example, if you are using XHTML 1.1 directly, use the public identifier in the DOCTYPE declaration, with the namespace declaration on the document element to identify the default namespace: <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+ARIA 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-aria-1.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> ... </html> Revisions: (none) --> Please remove the FPI from this sample DTD. Why? Because the following sequence of events have happened in the past: 1. A W3C WG mints a new XHTML FPI. 2. Some authors copy the doctype and use in their pages. 3. Some of those authors serve their pages as application/xhtml+xml to XHTML browsers. 4. Some of those pages have HTML entities like or ©. 5. Those pages don't work in XHTML browsers. 6. Browsers extend their list of magic FPIs that enable the HTML entities in XML. It is painful, unnecessary and wastes time for authors and browser implementors. The spec also says "To avoid competition with future formal XHTML DTDs that support ARIA, this is only a sample and has not been posted to a referenceable location." although it seems to be referencable from http://www.w3.org/MarkUp/DTD/xhtml-aria-1.dtd -- Simon Pieters Opera Software
Received on Monday, 22 June 2009 08:14:35 UTC