why does it cause the problems you're referring to if it's a "Type" that works via TypeContributor, but doesn't require users to write their own "TypeContributor" class but rather picks those up via scanning? I would think there wouldn't be any problem if the type itself knew the dialect it's for... or maybe a list of dialects it works for... perhaps I'm missing something. I'm not that passionate on having the types be able to provide it though, I'm just concerned when I see something that is going to turn into

 if ( driver1 ) else if ( driver2 ) else if (driver3 )