- From: Jens O. Meiert <jens@meiert.com>
- Date: Sun, 30 Mar 2014 22:45:51 +0300
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: W3C Public HTML <public-html@w3.org>
> While this is true "by default", from 'XHTML™ Modularization 1.1 - > Second Edition', the XHTML 1.1 specification also includes a legacy > module which, by default, is ignored, but which, when enabled, AFAIK > covers all the transitional elements plus the 6 ruby elements, meaning > that it covers 95 elements. I’d need to look into the situation with Ruby but I just responded in https://plus.google.com/u/0/+JensOMeiert/posts/2w14E3V7bFc with respect to legacy elements. Essentially, the situation here appears different from the one with HTML 4 and XHTML 1.0 (whose Transitional doctypes have been chosen), and calling out XHTML 1.1 legacy elements seems to go against the spirit of the XHTML 1.1 spec. While I recognize Transitional vs. legacy to mean somewhat of a fine line, I believe the index itself to be consistent. It does call out the Transitional elements, but nothing that was tucked away for legacy support purposes. Which by the way also applies to HTML 5. Please let me know if you deem this problematic. -- Jens O. Meiert http://meiert.com/en/
Received on Sunday, 30 March 2014 19:46:42 UTC