We're making great progress at Concord today. I'll let the rest report on what they've been working on. I've been researching content management, to choose a system we can ship PRP with. Here's my proposal, http://www.telscenter.org/confluence/display/SAIL/Proposal+to+use+Jackrabbit+for+PRP
Basically, we go with Jackrabbit. It doesn't do distributed versioning, but I argue that we don't really need that. We need something that works quickly and easily, so developers can get going. The CVS/Subversion model of versioning is familiar to people and has worked for a long time, even if it has its weak points. The major advantage of Jackrabbit/JCR over any DSCM is that it knows the model of the stuff that's inside. Our Jackrabbit can have nodes and properties down to the object level. In Bazaar hat would be bizarre. Also, there are object content mapping utilities that could make authoring tools much easier to write. If not for us, then for new developers not acquainted with XMLEncoder or OTML. I hope this gets a discussion started. We need to ship PRP with a versioned content management system for authoring. So we need to choose one in time to get it working. We won't be committed to it forever, and we're not talking about inclusion in sail-core yet. Just PRP. -Turadg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
