I'll read it but my knee jerk reactions is:
So use what makes sense but don't worry about spec compliance and stuff. I want to do things that get us working. I suggest pulling ideas that you like. I care way more about multi-database support than "standards support" for the back end. Mail admins could give a crap less if we used JSR-170 and more about "can I get the damn thing installed on Oracle in 15 minutes or less".
Actually now that I have thought about the idea a little more, I am less keen on it. My problem with it will be performance. E.g. the pop LIST command currently (using the hibernate implemenation that I will commit tonight) can return all of the necessary information with a single query, with no joins, filtered only by a single foreign key (very quick). The schema needed to support JSR-170 will mean that more than a single row for each entry in the LIST result set, meaning joins and probably a fair bit of trickery to avoid the n+1 queries thing. We can get better performance & scalability with a schema explictly modeled for our objects and still have a clean design.