Malte,
your speculations about handling CR attributes in assessment seem right in line with a lot of other discussion about acs_attributes metadata, auto-generation of forms, moving table creation from standard DDL to pl/sql (or tcl) APIs, and pushing various CR features up the hierarchy into acs_objects.
Here are some relevant threads I found:
autogenerating tables vs using the CR's pl/sql (or tcl) api
https://openacs.org/forums/message-view?message_id=112355
acs_attributes metadata - February thread
https://openacs.org/forums/message-view?message_id=162095
CMS
https://openacs.org/forums/message-view?message_id=79731
Tom Jackson's query-writer
https://openacs.org/forums/message-view?message_id=109730
https://openacs.org/forums/message-view?message_id=79731
Re automatic form generation:
https://openacs.org/forums/message-view?message_id=81377
https://openacs.org/forums/message-view?message_id=28086
a recent TIP (approved) related to this:
https://openacs.org/forums/message-view?message_id=163736
some other miscellaneous relevant threads:
https://openacs.org/forums/message-view?message_id=124744
https://openacs.org/forums/message-view?message_id=148989
https://openacs.org/forums/message-view?message_id=33756
https://openacs.org/forums/message-view?message_id=109708
I don't at this point have any clear ideas about the best way to proceed, particularly since there are lots of OpenACS core implications in all this. I do think that we want to implement assessment in ways that work with these core developments, not against them.
By the way, shouldn't Assessment be put in /contrib/packages in CVS, not /packages/ where it is now? We've barely begun the implementation, and potentially much of it will need to be revised/redone depending on how we decide to build it on the CR -- among other basic decisions.
