Proposal to Separate Chrome Registry Interfaces into gecko and non-gecko portions

I have written up a proposal to separate the interfaces of the chrome 
registry into smaller pieces, some of which are defined/used by gecko 
and some of which are not. It also contains a system to pass 
uninstallation information back and forth between the chrome registry 
and xpinstall.

Please take a look at http://bdsmedberg.no-ip.org/chrome/

Hyatt and bz, could you give me some input on my proposed interfaces 
soon? I am hoping to implement the core part of this proposal by the 
middle of January for seamonkey 1.7a/FB0.9. I don't want to cause 
massive conflicts with the work that hyatt is doing on extension 
upgrade/uninstall for firebird.

In addition, this proposal contains a longer-term proposal for a new RDF 
vocabulary to define chrome packages.

--BDS