Kimbro, I looked at your proposal and two things are missing, which we found very important for our current project (and had to develop ourselves to tell the truth).
1. Hierarchical locking A hierarchical locking manager (locks on collections/ subcollections). This should perhaps be implemented as part of the transactional service (because we don't want all users to be pending for a long transaction locking the entire collection and subcollections. 2. Versioning Optional, transparent versioning of resources is of extreme use in many projects. XHive has it, if you want to take a look at an example solution. I don't claim these are the most important features in the world, but they the fact that many commercial vendors include them in their product should be convincing enough to at least include them in the 'todo' list. Dawid KS> We need to get new development kick started here. To start I'm trying to KS> collect all the bits of information/features/ideas/questions into a KS> document for everyone to see. I've posted the start here KS> http://www.xindice.org/papers/planning.html KS> This is basically a brain dump of things that have been looked at/asked KS> for in the project. It isn't complete, but there's already a lot of stuff KS> there. KS> Number 1 on the list is "Critical to bring in more developers". This is KS> very important, if you're interested in getting involved here, now is the KS> time. KS> My plan for the immediate future is to continue filling in this outline KS> and to collect feedback and expand on the items. I know that right now it KS> probably isn't exactly clear what a lot of this stuff is, but I wanted to KS> get the general ideas down first and then expand and detail. There's a LOT KS> missing so please help me fill it in. KS> Thanks KS> Kimbro Staken KS> XML Database Software, Consulting and Writing KS> http://www.xmldatabases.org/
