Yipee! Yes! Yes! Yes! We need a new top level namespace, so we can fill it with XHTML::Simple, XHTML::Simpler, XHTML::Simplest, XHTML::Easy, XHTML::Easy::Simple and XHTML::HardButStandardAndJavaLike! ;--)
Seriously now... I am not sure there is a need for a new namespace: the boundaries between HTML, XHTML and XML are quite fuzzy, a lot of HTML modules can happily deal with XML input, a lot of XML modules have no problems with HTML input (libxml2 has an HTML mode, so all modules based on it can read HTML). Plus XHTML is really pushed by the W3C as just the natural evolution of HTML, so why differentiate them? I am not sure it would make it easier for users, who would have to look at one more namespace, beyond HTML and XML (plus DBIx and a couple of others).
In your specific case would XHTML::Table be very different from HTML::Table? If yes then the similarity in the names will confuse users, if not why not patch it to make it work nicely with DBIx::XHTML::Table?
In reply to Re: RFC: New rootlevel CPAN namespace: XHTML
by mirod
in thread RFC: New rootlevel CPAN namespace: XHTML
by jeffa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |