8
I should add that the "taxonomy" stuff that was discussed recently in relation to XOOPS was not really so lofty as the entire "semantic web" which is what my previous post here was about.
I think what most people in XOOPS-land are interested in right now, regarding taxonomies, is some kind of common taxonomy system for content, like what Drupal has. This has been discussed in XOOPS before. Whatever the challenges in implementation, it seems pretty clear that any modern "CMS" should have some kind of common categorization system.
The real question, I think, is what is the benefit of having a common categorization system in XOOPS? In Drupal, it gives you cross-referencing of content, which is built into the Drupal core. In XOOPS, there's no core features like that, period. So just building the categorization system isn't enough. You can't just have a way of tagging everything as one kind of content or another kind of content. You need those tags to then cause something else to happen, such as having pages in the core that list content across modules, according to the categorizations.
Meanwhile, there are other things XOOPS does pretty well, like multi-language, and templating, that are probably higher on the list. I think it's important to be careful to push XOOPS strengths and not spend too much time trying to play catch-up. We'll never out-Drupal Drupal, so let's not try to have the world's best taxonomy system. If taxonomy is *the* feature someone needs, they won't use XOOPS, period. So let's focus on what makes XOOPS really good, and make that better. Taxonomy will be important to have in XOOPS at some point, but let's keep everything in perspective.
--Julian