2
This will not be for 2.0.7, as the rule for 2.0.x releases is that there will be no database changes. This is a nice feature for XOOPS 2.2

However, it doesn't work quite the way you describe. The birthday module for instance, will only work if the field with the birthday data is actually there, is named the right way, formats the data the right way, etc... That's quite a lot to take into consideration.
The idea for XOOPS 2.2 is to make the whole user profile partly dynamic and optional. By doing this on the core, and making OO classes, modules can add 'their' fields to a user profile. That's the plan anyway. If it is feasible for 2.2, I don't know -yet. But rest assured, it's high on the to-do list.
(If you're wondering what happened to XOOPS 2.1, well, we've adopted the Linux version numbering scheme, which means that odd numbers are beta releases, and even release numbers are for stable ones. So, we're working on 2.2, and as a beta for that, we'll release a 2.1).
Herko