Ben asks if posts should be CR objects. Not being a coder I'll come at it from two user goals. First, posts (though more often threads) are valuable knowledge 'objects.' The opportunity to repurpose that content for display in other contexts within a site (articles, 1st drafts of documentation, etc.) suggests that making them content objects will enable some valuable innovation in the future.<br><br>
To me, the bigger problem is defining what the basic information architecture of an OACS application should be-- general principles that answer Ben's questions automatically. Then you look and see if those answers make sense in the context of the specific application (a bboard for .LRN for example). I'm not sure that there is a great handle on the IA side of things that would inform architecture and code. I would love to help to write this up in a way that is useful for application builders but am unsure of where to start.<br><br>
I
