In reply to a tweet by @bobdc:
@bobdc, it makes sense because XHTML2 isn't a successor to XHTML1. Hopefully the XHTML2 guys rebrand like W3C said they would.