Help required digging into AnyData and DBD::AnyData

Dear Jeff,

I hope you're not completely off for Perl5 development. Maybe you are still
subscribed on [email protected] and see our progress of the last months
and weeks thanks to your great groundwork.

Unfortunately  I cannot improve AnyData and DBD::AnyData as I wanted,
it's much to complex. I fixed DBD::AnyData for DBI-1.612 of course, as
I promised and for what I received the co-maintainership from you.

I see that AnyData has a complete own storage backend and will always
use it, even in case of DBD::AnyData - what makes it not reasonable to
derive from DBD::File (for current implementation).

I want to understand (and improve) following parts (beside the general picture):
1) How is the abstraction of the storage meant? Would it be possible to have
   storage abstractions in DBD::File which can be used instead  (or to extend
   such a storage)?
2) Could you paint me a picture (UML, Dia or just words) how the parser,
   storage (especially the AnyData::Storage::TiedHash) work together?

Any help is very welcome, I'd love to bring DBD::AnyData beside DBD::Sys
as a meta driver for all important data beside OS internal (and related) tables.

Best regards and thanks in advance,
Jens