I'm also thinking that if using revisions simply doesn't make too much sense in a package then it simply should not use it and instead overwrite the one (and only) revision for each item each time the content gets edited (don't know if that already happens, if not, then we might think about that).
I also have to add that it seems that we will not only need the name of objects that use the CR, but also for objects for which it doesn't make sense to store them in the CR.
I want to give an example: Currently, i'm working on a categorization and a mailing list package. Mailing lists can be assigned to some categories. Hopefully, the category package will get used in other packages, too, let's say bboard and file-storage. In the categories package i want to have a directory in which the user can specify a category and he'll get a list of all objects categorized in that way, so he'll see a list of all bboard-postings, files and mailing-lists assigned a selected category. But mailing-list objects will definetely not be kept in the CR since that really doesn't make any sense, wastes disc space and blows up the already huge CR tables.
That's just one example for objects which will not be in the CR, but still might to get displayed in an object list.
So that's why i'm proposing adding a seperate table for that information as i suggested above and not using only the infos in the CR.
