maybe it would be better to call the middle section something like 'core element' or 'the heart' where values, goals, to do, roles, etc are managed --Flower 10:16, 29 Jun 2006 (DST)
That's lookin' good and useful - don't spend too much time on design though as its not easily maintainable and reuseable in this environment. But having evolved collections of these templates and forms will be extremely useful peer content to migrate.
Also, on another note - I coudn't edit it directly on that form, but you should add in to your notions re channels: They have both input and output context - input is the different ways requests and information can get to the org and router to a role. But output is the media-channel, kind of like shared playlists (or content-schedule) over all the classes of media. --Nad 17:16, 23 Jun 2006 (NZST)
- Copy that re design, that's as flash as it gets, just trying to get a basic, friendly-looking layout for the high-level biz sitter ws. I'll add the input-output stuff to the comms channels notion, I was trying to get that defined more clearly for EA. I guess output would also include newsletters and suchlike, although blogs seem to be replacing those now.--Milan 17:22, 23 Jun 2006 (NZST)
- Yip newsletters, emails, blogs, websites, video, audio, presentations etc... But the key thing in thinking about it the nodal way is as channels ie items filling up timelines so that content in dynamic streams can be collaborated on while still in the future, and solidify as they approach the present and become history. --Nad 17:55, 23 Jun 2006 (NZST)
One further section is still missing, this is the "Events" one. It will be added soon and will include things like: "I want to order a product" or "A customer is calling on the phone", etc.--Milan 17:22, 23 Jun 2006 (NZST)
- Events are related to the input channels, they are occurences which happen within the context of an input channel --Nad 17:58, 23 Jun 2006 (NZST)
- Old content