Chris, I'm a bit lost here. The idea behind Koha::Object is that we have a common base class from which to derive Koha::Biblio, Koha::Serial and so forth. That is, this class would be used as the base for classes that have a simple 1 to 1 table mapping to encapsulate DBIC while maintaining a consistent set of methods across our many classes. ObjectSet would give us set iterators, set operations, and be a better place to have methods that return a set ( e.g. Koha::Issue::Set::GetOverdues would return a collection of overdue checkouts ).

I'm not sure why you disagree with this idea. Could you expand a bit?

Kyle