General mechanism for user preferences.. excellent notion. No real comments on your document, however, I'm guessing whatyour proposing essentially puts the owness on the package itself to register potential preference types etc.. therefore has anyone estimated how much work is involved in retro-fitting existing packages?
I know you've mentioned it but I would re-emphasise that making it package 'instance' aware is critical. I assume of course it would also therefore be subsite aware?
This is of course assuming that the intention is to nake older packages use it, and that there is a development step there also, aplogies if I misunderstand.
