Picking up on the current focus of the current Identity Gang debate on how we might integrate and track our information (blog posts, comments, forum posts etc.) across multiple CMSs, here a few ideas I've been mulling over.
It seems to me that to solve this problem, we need to re-examine the nature of CMSs themselves, and re-invent them as IMSs—Identity Management Services. These IMSs would embody the key aspects of current CMS functionalities, but within an identity-centric conceptual framework.
One concept that's important to my IMS concept is that of a Space. I use "Space" to refer to a conceptual place where content items exist. A Space may have persistent identity, in the case of the Space of an individual (think blog) or community (think wiki or mailing list), or may have relatively transient identity, such as a Space representing all the entries in a conversation.
A content item can exist in multiple Spaces simultaneously—for instance, I might write a blog post in reply to a friend's post (I specify it as a "reply" to the original post, identified by its permalink), and copy it to the Identity Gang email list: in this case, my post exists:
1) in my blog Space—along with all the other blog content I create;
2) in the Identity mailing list Space—along with all the other Identity related posts the Identity Gang, of which I'm a member, create;
3) in a threaded conversation Space that is dynamically created (by and within my IMS) when I "replied" to the original post—along with the other person's original post, and all subsequent posts by us or others who become involved in the thread.
The beauty of this way of handling a distributed conversation is that we and others can participate in the conversation both in our individual Spaces and in the joint conversation Space simultaneously; moreover, we could choose to have additions to the conversation Space pinged to our individual Spaces and display the thread there also (or at least the items of the thread whose author permits this federation), much like the existing blog comments system.

In each case, the Space I post to respresents somewhere I have permission to express myself, whether exclusively (my blog), or as a participant in an explicit (ID mailing list) or ad-hoc (conversation with friend) community.
The
identity of a Space can be understood as being shaped by two main dynamics:
1) The permissions placed upon it by its administrator(s)—which determine
who can participate in it in
which ways (view? edit? set permissions for others? etc.)
2) What the participants in the Space do within the permissions restrictions of (1)—how they create and interact with their own and others' content
It seems clear, then, that the metaphor of a Space is a powerful one which subsumes key identity-centric aspects of content management.
Mimicking 3D limitationsTo a large extent, current CMSs like blog and wiki tools tend to assume that each piece of content belongs primarily in just one Space. So I publish a blog post—to my blog. I edit a wiki "page". I upload my photos to my account. This metaphor seems to me to be an unconscious hang-over from our experience of the physical world, where objects indeed do only occupy one location at any one time. However, as we have seen, this limitation doesn't really need to apply online.
Now some services like Flickr and, on the client, Ecto, are beginning to make it easier to pipe one piece of content into multiple Spaces. However, this concept is not yet embodied in the actual data model upon which these services are built: I have to manually re-post an item to each Space, rather than being given multiple choices of Space when I originally post, let alone being able to set up dynamic content flows between Spaces (e.g. updating my blog with new entries in a conversation Space). Finally, there is nothing like conversation Spaces in current CMS services—we have to rely on hyperlinks and thereby search services like Technorati to cobble our distributed conversations together.
Holding my horsesOf course, to develop a tech solution that embodies the Spaces concept, we have to crack all the familiar problems like authentication, ontology (currently, different services describe their information with as many different data structures ), caching, version control, privacy and security along the way! ; )
Technorati Tags: identity, ontology, IMS, CMS, space