Simon Willison wrote: > HTML 5 is the > final nail in the coffin - the refocusing of the W3C on that over > XHTML 2 is an acknowledgement that XML is no longer the future of the > Web. I actually think Django's XHTML output makes us look a bit out of > date.
I don't think either of those conclusions can be drawn from the facts. XHTML 2 was a bold attempt to redefine what it is exactly that web pages produce: less crud, more content. I'm, personally, a bit disappointed that it has been "canceled", but I assume that smart people will continue to explore concepts in that direction. XHTML 2's cancellation does not say that XHTML 1 was a bad idea or is in anyway invalidated and it absolutely says nothing about XML. (Also, whether or not XML is the "future" of the web, it is a strong part of what defines the "present".) Furthermore, support for XHTML "5" (which is indeed a part of the HTML 5 standard) shows that XHTML 1's principles are still around and still respected. Django's XHTML output can't be "out of date" if XHTML 5 is considered a successor to XHTML 1. -- --Max Battcher-- http://worldmaker.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
