> I have looked at Openinteract. More than one time. But it doesn't > feel right. I'm not sure SPOPS is flexible and powerful enough.
Although I don't have much practical experience with it yet, this is what I like about SPOPS: it knows its limits! I get very frustrated with O/R mapping systems that try to handle EVERY possible data model and come up with an enormous and inflexible API. With SPOPS, if you have a really strange class that can't be simply mapped to database tables you just bypass the automatic loading and write the load method yourself. You still get a consistent API and the security stuff. (Correct me if I've got this wrong, Chris.) > Not only should it have version management. But it should have > multidimensional version management. The same content for diffrent > audiences, diffrent languages, diffrent formats... > > The object properties should be dynamic. Using heiarcical values; > searching for an object with a specific property will also find > objects with properties that are subproperties of the specific > property (a simple form of inference). Be careful of getting too ambitious in early stages. Efficient persistence and searching for user-defined data types is HARD. If it was easy, everyone would do it. The Iaido project tried to deal with this, and it resulted in some very nasty SQL. - Perrin
