"The difference would be that you would map the message to different containers using acs_object_structure. You could easily create composite structures as well. For instance a web page could be composed of a series of messages, photos and other html fragments (each being objects themselves). However this composition would still need a method of arranging the data: a templating language which would specify what parts of the object to display, which subset to display, and in what arrangement...."
This sounds suspiciously like the current CR datamodel supported by the CMS application. We've talked about generalizing this stuff to work with objects for a long time. There's nothing novel about the idea. Perhaps we're getting to the point where we can realistically talk about devoting some resource to this now that the toolkit's become relatively useful. I actually have this on my hope-to-find-time-to-do list by summer.
