The impending closing of Donna has bumped a couple of thoughts to blog to the front of the queue.

First off, Donna is an iOS calendaring app that focusses on one’s agenda for that day and upcoming days with a targetted focus on the transportation timing and how that impacts your day. If your life has children that need transporting between activities or work that is out and about bouncing to meetings or work sites Donna is utterly indespensable. Donna puts a focus on the getting between places, so calculates the travel time to let you know when you really should leave, as it monitors traffic and weather conditions. The app offers four different modes of transportation and the related times for those: Driving, public transit, biking, and walking.

One of the best parts of Donna, which many other applications also do, is it reads your native calendar on iOS and augments it. It isn’t a separate calendar to lose things in if you forget. Content you may modify to help plan in Donna, like search to find the exact location for a meeting, is added to the calendar object and can be used in other calendar apps. I will focus a bit more on this in the following section on “Small Apps Loosely Joined”.

Not only will Donna give you a warning when it is approching time to leave, but it can send those you are meeting with notification that you are on your way and / or you are running late. Donna also monitors the weather and can advise on transportation changes should you be walking or biking. One other really helpful element is having the option to use Uber, if you are in a city that has it (Donna knows) and the event is that day (this was incredibly helpful this week).

One of the wonderful things is the evening of the day prior Donna provides a notification of how many meetings you have the next day, but if you don’t have any in your calendar(s) it tells you to enjoy your day, which is a wonderful little touch.

Designing for Use

The thing that stands out with Donna is not just its really good interaction design and really well designed information structures for easy to scan appointments, but it is designed to solve a pain point. Most specifically it is designed for use. The design is focussed on solving a problem and to be an easy to use solution for that problem, which is: I have meetings and activities in my day that take me out and around and sorting out the timing so I can optimize my day for my interests (get more time by driving, more health and environmentally focusse using bike or walking, etc.). Letting others knwo when you are late or on your way is really helpful and directly tied to the mobility of getting to meetings and activities. Having an app that pulls all the needed information around that task set is fantastic.

Donna isn’t designed to be a full replacement for a calendar, but is there to augment it and the use needs around the activities of getting between places.

Donna also understands what is needed as well as not needed. Allowing for modifying settings for alerts and notifications is really helpful. Understanding when alarms are not going to be helpful, understanding helpful user preferences when you are running late (auto send notes, how far ahead, or not to send at all automatically). Donna was built with the idea of a really helpful human assistant who looks after your schedule and is a step ahead of you. This framing of use and a helpful model really shines through in the app.

Small Apps Loosely Joined

Donna and many other calendar apps that are on mobile devices are not aimed at fully augmenting your native calendar service, but to integrate and augment that service. The model that is increasingly familiar is along the idea of small apps loosely joined model. This model puts a focus on using standard data structures, common object types, and a central app or service as a hub to provide a foundation for other apps and services to use the core object and augment it, often with data that fits the model type, and exends use.

With Donna the object is a standard calendar entry that has day, time, timezone, location, who are meeting with, notes, etc. But, the app can improve the data in the object, such as location. But, most of the apps not only improve the information within itself, but improve the core data so all other apps that use that object as well. The apps are often offering agency to do a task, or set of tasks, around the object. Donna puts the use focus on the use needs for getting there and communicating with others around that activity.

With calendaring, many using Mac or iOS opt for Fantastical to imput new calendar items as its native language parsing into a calendar data structure is incredibly good. Some people really like the interface from Fantastical and use it to view their day and upcoming events. There are an incredible amount of viewing your calendar / schedule options out there. Another smart agent for the calendar is Tempo app, which works to aggregate everything around a calendar item and pull it into easy reach (very much in the Come to Me Web model). Tempo pulls all the contact information for all participants in a meeting, all related email, all related files, weather, etc. all within easy reach as part of its view of the calendar entry. Tempo is as indespensable as Donna is for me personally (and I heavily rely on Fantastical for easy input, on my mobile I talk the calendar entry info into Fantastical and let it do its thing).

Who is Living the Small Apps Loosely Joined Life?

So who is working this way? Not so surprisingly, if one has been paying attention to how people actually are using devices and services, the user survey’s the past year or so have been asking about using more than one app for task types (calendaring, notes, reminders, text, etc.) and finding that 60% to upper 70% of those surveyed are using multiple apps for task types. Those surveyed have often been well outside of the geek and nerd camps that have worked this way for years, but regular folks who are not deeply adept technically. The focus on apps that do a task or set of tasks insanely well and easily trump a large app that does many things somewhat well. That one size fits all and category winner thinking has been dead for quite a while and is far from helpful model for thinking about much of anything.

The last few years, either in conferasions or listening to them, with people talking about their apps and how they do things on the devices (often mobile and tablet) it is increasingly common to hear, “I use a few apps to do…” what follows is calendaring, text documents, notes, mapping, driving directions, reminders, etc. and two or more apps stated and the specific tasks and user flow they have for each app. These were often non-geeks, but having surveys targeted at mainstream users and their habits and use patterns really brought home how mainstream this actually is.

Good Bye Donna

As Harry McCracken pointed out in Yahoo to Donna Users: We’re Dispensing With Your Indispensable App Donna has become indispensable for me. The great folks at Incredible Labs (that includes bud Kevin Cheng) did a fantastic job with Donna. Keeping Donna going was likely going to be a struggle as the computing to suss out location and needs as well as the and licensing the transportation times they used was not going to live a long time as an ongoing free app. The competition with other apps starting to incorporate similar time for transit models (yet clearly not designed from a perspective of use, but as a feature to add) likely was going to make things tougher as well as Apple adding transporation times and notifications based on that in Mac’s Mavericks version (adding it to desktop OS and not the mobile OS really was an odd move that is very un-Apple as it was not designed from a use in mind perspective).

It has been a while that I have been worried about the long run for Donna. A chat with Kevin about running a start-up in this space somewhat gave legs to that concern. Many start-ups have an exit in mind from the start and with any luck and perseverence it is a positive exit (not just shutting it and going bankrupt). I am really happy for Kevin and the other Incredible Labs folks as they got a positive exit for them and I wish them well at Yahoo (for all that are making that transition). Incredible proved they could nail a service that is designed for use, which leads to it becoming a really valueable part of people’s lives. Thank your for bringing us Donna as an agent to greatly improve our lives.

[Editor's Note: Thomas Vander Wal has spent many years as an infovore, gathering, reading, annotating and reusing the volumes of information he has run across. Over the years, he has searched for the ever-elusive one perfect solution, method or tool. But, this digging has surfaced many approaches that work for a variety of needs, and they are what he is sharing.]

Like many people, I struggle with a large amount of inbound information that has potential value today, but also value to myself and to others down the road. Being able to sift through the information and manage what is needed today, as well as keep potential future needs close at hand, is essential. A few approaches have helped me over the years, but a mix of personal practices and tools help keep some of this in check.

My practice started with a rather healthy RSS feed many years back where I followed 400 or so feeds. The daily new items in the feeds numbered well over 1,000. But in that flood, I found items of great value that I was not finding elsewhere, and that value still continues today. Those nuggets help me to be better informed for work, but also provide a solid repository for understanding and writing about the world around me.

The first round

The process still requires me to see things; it is a "who and what" pass through the information. I learned very quickly not to really read things on first pass, but to look at headlines of the individual feed items, and anything of remote interest gets opened into a Web browser with tabs. Paying attention to the source of the information, as well as to the headline, helps decide whether something gets opened in a browser tab, because certain people continually provide solid information that is worthy of attention. The first pass may have identified 60 to 70 items out of 1,000 potential ones. That step often takes 20 to 30 minutes, which indicates the depth of the review.

I found I could perform that portion of the process much more quickly in a desktop feed reader than an online reader because I could optimize the typeface size and only see headers, which allowed a view of 50 to 100 unread headers at a time to quickly skim through. Much of that was done on a Mac using NetNewswire.

A little closer look

After I have gone through all of the items in the inbound queue and things of potential value, I move onto a slightly deeper scan than just looking at the headlines. This pass assesses potential value and is a quick read of the first paragraph or scan of the whole piece to quickly assess if there is any value. If not, the tab is closed and I move on to the next item and skim it. At the end of this, I have removed duplicates and things that were not of interest or foreseen value, often in 10 minutes or so.

The last step is to go back to the remaining items (usually 10 items or so, with some days only one or two and others 30) in their open tabs and read them in more depth for current needs. Items that have current value I leave open. I will come back to them after I manage those with future value. I read the items with current value closely, summarize and add them to a work social bookmarking tool, as well as to a Web social bookmarking provider (if it is relevant and prudent).

I don't read as closely the items with future value, but I add them to a social bookmarking site, like Delicious, Diigo, or Pinboard (as well as to any work-related service), and tag them for my own context and others' needs, tie them to future needs as much as possible, and summarize them. I may also add those items to Instapaper to read at my leisure.

One nice benefit of Instapaper and Pinboard is that they work together. As I find things I want to read in depth in Instapaper, it will put the link into Pinboard as to-read, if you have the two services and accounts connected. That connection makes it relatively easy to update in Pinboard to add tags to put your context on it and a summary. I also can view the "from Instapaper" tagged items and read those I have not read, which have a tag "mark as read," if I have not read them in Instapaper.

This interwoven system is just one slice of keeping on top of the information that streams past us. As it is with many things these days, staying on top of the inbound information is essential. This approach is one of many options, but can make a good dent on staying current and informed today and tomorrow.

This was written in April 2011 and a publication had interest in publishing it, but it didn't fit their editorial cycle so it sat. I have annotated this with an endnote to bring it current.

A funny thing happened on the way to the next big thing, the big thing was little. Many people are looking to build the next Facebook or Twitter, but those that are gaining traction and actually being used don’t focus on collection and aggregation of the masses, they focus on the small groups of people who know each other and really aren’t connecting or interacting in or for the public eye.

At SXSW this past year, 2011, the next big thing wasn't one thing, it was many things. It was these same smaller group interaction platforms that let people who know each other already interact. The funny thing is this really shouldn't be a surprise to anybody who has actually been following or connecting to the mainstream in the crowd using Facebook or any other large service. Most people are are connected to a small group friends or other label for the people they share information, status, and possibly location with. When Facebook took its service beyond the walls of the university and let any old Joe and Jane in many of the students had fear and cut back their usage of the service. They wanted a service to have more regular communication and more private interactions with out of the eye of the hoards. This isn't because they are doing things they are ashamed of or would cause them consternation if others found out, it is because that is how most people in mainstream interact and consider normal. Many of these students kept their Facebook accounts and use them occasionally, but this is not their social home, this is not where they check the pulse of the group of people they want to connect with.

When you consider how this plays out you see it really clearly inside organizations that have openly social communication and collaboration platforms up and running. Much of the interaction is often not out in the open, but in the more focussed less travelled (or even semi-closed) groups and forums. These are the comfortable spaces with permeable walls. But, this is often where much of the sharing and interacting happens in organizations.

For many who drank the Kool Aide of people want to be openly social, this is an odd trend. But, it isn't really a trend it is the norm and for most of time going back this has been the norm. There is something to Robin Dunbar's postulation of “theoretical cognitive limit to the number of people with whom one can maintain stable social relationships”, which is commonly known as “The Dunbar Number” and is approximately 150 (with bounds of 100 to 230 as reasonable lower and upper reaches for most people). But, for small very close knit groupings of friends you often see from a a few teens in groups up to 40 to 50. But, about 40 to 75 the dynamics shift and is repeatedly comes up when talking to people in digital services with the number of people where the service shifted from being fun and easy to use to being more work.

At SXSW this year the proffering of small social services, many for smart mobile devices only, like Beluga, Ditto, GroupMe, etc. were the talk of the event in Twitter and from the remote conversations I was picking up on. The question was, “which service are you on?” for those you deemed viable enough to connect with outside of the masses in Facebook and Twitter. These services are where people look for who wants to meet up for dinner, where is the good place to hang, or most importantly “where are my peeps?”

Invisible Communities

This past week I caught Chris Heathcote's presentation on “Invisible Communities” from February 2011 at Lift Conference. Chris talks about all of the unseen communities on the internet and web, which have nearly always been there and keep growing. These are the web forums where the “good” information is shared. These are the handled application based services, some with web presence, but very few are searchable or open to the public. Chris' talk echoed most everything I hear when I talk to the famed “millennials” in organizations who are claimed to be “openly social” and heavy users of these huge web social tools, but when I sit with them in organizations regarding social tools inside the organization (they are included as they are supposed to be the heavy users and the ones that really know this stuff well), but dang if I have ever run across one that has claimed this. Very few use Facebook or Twitter (the “Twitter is for old people” (over 25) is commonly stated) and they all state some different small social tool where they keep in touch with their good friends with.

Personal InfoCloud

Doc Searls wrote a real gem of a post, “The Sense of Bewronging”. Doc's post is about the need for personalization and putting things in context that “I” care about, or as talked about here in this site the Come to Me Web and Personal InfoCloud. A post that triggered Doc was a presentation and post by Louis Gray “The Third Wave of the Web Will Be Uniquely Personal”. Both of these posts talk about aggregating all that we have inbound and as well share out (our digital exhaust) so to filter and hone what it is we care about so to serve it up more to our actual interests and with out information overload.

Why Does this Matter?

All of this matters because for as much as we use ThinkUp, My6sense, Momento app, Summify, etc. for our aggregation of personal exhaust data and to filter to ease our attention focus as well as use and most importantly reuse what flows through this at some point. In using these services most are focussing on the big social stops like Facebook and Twitter, just like malls have big box stores, but most people are not going to the mall for the big box they are hitting the smaller stores or skipping the mall altogether for more personal customer service and supporting businesses of people whom they know. If the social aggregation and information filtering tools are keeping their focus on the mall’s big boxes of social web, they are missing where many people are actually spending their valued attention. Having a wonderful service like ThinkUp to provide a history of what I have shared and was shared with me (or the more impersonal fact, shared to many and my friend hooks, nabbed a digital copy of that sucker) so that I can search and pull things together later is missing some key valued elements.

While it is worth the time these services are spending (all pulling the same big sites and services and missing the less broadly known services) on the big box social web services, so we can pay a bit less attention on them but for some digests and pay attention to our more valued services. But, what looses out is the use and reuse of across all those services. You have a friend share a book she just finished she thinks you and your group would like, but shared it in your tight friend space you won’t have easy recall from a central place. A real personal aggregation and attention management tool needs to capture all streams we consider to have value. Being able to build a Granular Social Network that really works and that keeps our attention from being over taxed is where much of this really should head. We have been stating what this third wave of the web should be for a long time as a personal web, we now have the tools start getting there, but we need to ensure our focus fits our needs and our actual interactions.

Yes, for those of you that have made it this far and have been waiting to state all this is walling ourselves off from the rest of the world, well I think this aggregation, archiving, and filtering to keep our attention from hitting overload is needed so we can take a much broader look at what is outside our bounds. If we enable keeping what is valuable in front of us we can explore and interact even more.

Some things have changed a little bit in the past year, but largely not much has changed. Facebook has its Timeline, which has thin value for being able to scan the real volume of our activities and then be able to aggregate and reuse that information in more usable and valuable (for one's self and others) format. It is an interesting visualization, but the value of making deeper sense just isn't there and understanding things never seems to fit in Facebook's plans.

Redundancy

Never the less, this brings-up an important point: Redundancy. One lesson I learned many years ago related to the web (heck, related to any thing digital) is it will fail at some point. Cloud based services are not immune and the network connection to those services is often even more problematic. But, one of the tenants of the Personal InfoCloud is it is where you keep your information across trusted services and devices so you have continual and easy access to that information. Part of ensuring that continual access is ensuring redundancy and backing up. Optimally the redundancy or back-up is a usable service that permits ease of continuing use if one resource is not reachable (those sunny days where there's not a cloud to be seen). Performing regular back-ups of your blog posts and other places you post information is valuable. Another option is a central aggregation point (these are long dreamt of and yet to be really implemented well, this is a long brewing interest with many potential resources and conversations).

With regard to Delicious I’ve used redundant services and manually or automatically fed them. I was doing this with Ma.gnol.ia as it was (in part) my redundant social bookmarking service, but I also really liked a lot of its features and functionality (there were great social interaction design elements that were deployed there that were quite brilliant and made the service a real gem). I also used Diigo for a short while, but too many things there drove me crazy and continually broke. A few months back I started using Pinboard, as the private reincarnation of Ma.gnol.ia shut down. I have also used ZooTool, which has more of a visual design community (the community that self-aggregates to a service is an important characteristic to take into account after the viability of the service).

Pinboard has been a real gem as it uses the commonly implemented Delicious API (version 1) as its core API, which means most tools and services built on top of Delicious can be relatively easily ported over with just a change to the URL for source. This was similar for Ma.gnol.ia and other services. But, Pinboard also will continually pull in Delicious postings, so works very well for redundancy sake.

There are some things I quite like about Pinboard (some things I don’t and will get to them) such as the easy integration from Instapaper (anything you star in Instapaper gets sucked into your Pinboard). Pinboard has a rather good mobile web interface (something I loved about Ma.gnol.ia too). Pinboard was started by co-founders of Delicious and so has solid depth of understanding. Pinboard is also a pay service (based on an incremental one time fee and full archive of pages bookmarked (saves a copy of pages), which is great for its longevity as it has some sort of business model (I don’t have faith in the “underpants - something - profit” model) and it works brilliantly for keeping out spammer (another pain point for me with Diigo).

My biggest nit with Pinboard is the space delimited tag terms, which means multi-word tag terms (San Francisco, recent discovery, etc.) are not possible (use of non-alphabetic word delimiters (like underscores, hyphens, and dots) are a really problematic for clarity, easy aggregation with out scripting to disambiguate and assemble relevant related terms, and lack of mainstream user understanding). The lack of easily seeing who is following my shared items, so to find others to potentially follow is something from Delicious I miss.

For now I am still feeding Delicious as my primary source, which is naturally pulled into Pinboard with no extra effort (as it should be with many things), but I'm already looking for a redundancy for Pinboard given the questionable state of Delicious.

The Value of Delicious

Another thing that surfaced with the Delicious end of life (non-official) announcement from Yahoo was the incredible value it has across the web. Not only do people use it and deeply rely on it for storing, contextualizing links/bookmarks with tags and annotations, refinding their own aggregation, and sharing this out easily for others, but use Delicious in a wide variety of different ways. People use Delicious to surface relevant information of interest related to their affinities or work needs, as it is easy to get a feed for not only a person, a tag, but also a person and tag pairing. The immediate responses that sounded serious alarm with news of Delicious demise were those that had built valuable services on top of Delicious. There were many stories about well known publications and services not only programmatically aggregating potentially relevant and tangential information for research in ad hoc and relatively real time, but also sharing out of links for others. Some use Delicious to easily build “related information” resources for their web publications and offerings. One example is emoted by Marshall Kirkpatrick of ReadWriteWeb wonderfully describing their reliance on Delicious

It was clear very quickly that Yahoo is sitting on a real backbone of many things on the web, not the toy product some in Yahoo management seemed to think it was. The value of Delicious to Yahoo seemingly diminished greatly after they themselves were no longer in the search marketplace. Silently confirmed hunches that Delicious was used as fodder to greatly influence search algorithms for highly potential synonyms and related web content that is stored by explicit interest (a much higher value than inferred interest) made Delicious a quite valued property while it ran its own search property.

When thinking through social software (also known as social computing, social media, and social web) I have been influenced by many ideas, but at the core there are two things that stick in my head: 1) Good visualization; and 2) Object-centered sociality. Getting the two to mesh, while accounting for most of the important components of social software has been really difficult for me to square for quite some time.

One of my starting point for visualization has been Gene Smith's wonderful honeycomb adaption of the social software building blocks. The strength of the graphic is having identity at the core of the social interaction. The honeycomb allows Gene to display many different services deployed has the pieces of the social software stack (stack is a collection of elements that comprise a whole set of services).

One of the things with Gene's graphic that has always bugged me is I have not been able to square it with the object also being at the center of the social interaction. A second piece that also bothered me is it did not account for the action element of collaboration (people working together as part of a group or team to build something, while acting with one goal as their focus, which can be a broad goal). Collaboration is central to nearly every enterprise or work organization effort (directly or tangentially) I am or have been involved in professionally, so I feel it is essential to include it.

One characteristic of the present situation is that perhaps for the first time in recent history it appears unclear whether other persons are, for human beings, the most fascinating part of their environment. Objects may also be the risk winners of the relationship risks which may authors find inherent in contemporary human relations.

The short of this is the person may not be the sole focus and possibly the person is not the focus of social interaction as the objects being discussed in social interactions is the focus for the people and take the role of the most interesting element in the social discourse.

When we look at social web services like Flickr we see the photos that a person takes and shares are the focus of social interaction. It is around these objects that the conversation takes place. Jyri Engeström calls these objects of social focus "social objects".

It is these social objects that are in need of being accounted for in a visualization of the social software stack. While in Germany for the most recent IA Konferenz I wanted to include his more fleshed out understanding of the social software stack, in this case it is actions or components that comprise sociality from the perspective on an individual in a social environment. I really wanted a graphic that brought these elements together so I could talk through it more easily in a workshop on the foundations of social software and tagging. The visual model is this Venn diagram that I put together sitting in the hallway for an hour or so. While it is not as interesting as Gene's graphic, for me it is a much better representation of the important components in social software if your goal is wanting your service/software to work optimally.

Explaining the Graphic

Yes, the inclusion of the object into the graphic is given a central focus equal to that of identity. Identity and the object are the two important elements that comprise the social software stack. All elements that are represented in the graphic may or could be seen by others and are triggers for social interaction with other people (yes, the interaction can be with just other objects, but that is another subject I am not addressing in this writing). This ability to see all the elements represented is the social aspect of the software service. The overlaps are where there are direct interactions. But, there is a specific order to the revealing and relevance of each of the elements after the identity and object are shown.

The order is important because if one leaves out an element (or does not account for the elements in some manner) the next step is really not going to be capable of being fully realized and there will be a weakness in the social software. I can not stress this enough, this is not a list of items to pick from, but if you want to have reputation in the system there previous elements really need to be in place or accounted for through using an outside service that can be pointed to or brought into the service through using an outside service.

Order of the Elements

The colors were chosen so the bridging elements were orange and fit with the color scheme of my company and the usual slide templates I use when presenting (orange with blue highlights, text, and accents). After I built the graphic I realized the similarity to a finance industry logo, but when playing with other color combinations the graphic lost its punch and also did not fit within the color scheme of my long used slide template, so I have left the colors alone.

The Elements in the Social Software Stack

The Central Focus

Identity

Identity is comprised of the information about the person using the social software tool. Often the identity is a built upon profile information such as name, username, location, personal website, e-mail, photo or avatar, and sometimes the person's age. These pieces help others recognize the person and can carry associations from other interactions and/or services to the current service (that is if the individual wants this cross-service tracking). Contact information is normally required for setting up an account so the service (and the people running the service) can communicate with the person. Sometimes the contact information is shared if the person using the service permits the sharing of the contact information with other people using the software/service.

Identity is also augmented through the inclusion of usernames on other services and sites the person contributes to or has an account on. This cross-service identity helps people who use other services to find their friends and contacts more easily. The cross-service identity also helps tie others understanding of the identity and possibly reputation as understood by other people. Cross-service identity connecting can also be used for aggregating content that an identity shared on another service into a new service.

Identity is included in the focus on object-centered sociality as it is people who are being social around the object. It seems that there is a codependent relationship between the person (their perceptions as expressed through their interest and actions around and about an object). The identity is a pivot to learn more about these understandings for a richer understanding by those reading/consuming what has been shared. This is much like the object is a pivot to find others who have interest in the same type of things.

Object

The object is the core focus of object-centered sociality and in this representation with one identity interacting it is part of the the codependent at the core of the graphic. The object is the center of the sociality. The object is what is being shared with others. This shared object may be a photo, bookmark/link, video, statement, or other matter. The object may be digital or non-digital in nature. Lastly, the object can also be what is being built in a collaboration-focussed effort.

Active Elements

Now that we have the cornerstone set of the two main components for sociality we can start looking at the elements around these two components. Again, these actions and elements are in a specific order that build upon the previous elements. These are active elements because they are either actions or are the result of sets of actions.

Presence

The identity is often built around static profile information, but people are not static as they have lives they lead and people have locations and tasks they perform that provide context for understanding perspective of statements or related actions. Presence can be a simple as Twitter's question of "what are you doing?" It can also be location, time, availability, and/or activity. These provide others a glimpse of understanding, or at least a hint of the identity's perspective.

In the case of Twitter and similar services the statement of presence is not necessarily related to another object, but the presence statement in and of itself acts as the object. In the case where presence is the object, the object is directly related to the person and not an external object. The presence statements may or may not be shared with others as the understanding is quite helpful information for the individual for later recollection as to why they made other statements or actions.

Actions

Using stated presence or the inferred presence, as the actions connote presence around an object that action is taking place around. The actions are what is being done as an expression communicating to one's self or to others what they understand. This may be as simple as just expressing interest (even if the interest is negative). These actions are expressions of the person's understanding can take the form of annotation, messaging, modification of the object, commenting, rating, tagging, flagging or favoring, storing, naming, etc. The actions are tied to the person who is taking the action and linked to the object around which they are taking the action. These actions are are in most cases the some form of adding data or meta data to or around the object.

In social bookmarking in del.icio.us the object is the link expressed as the URL and the person is taking the action of saving the link and is likely also annotating and tagging that link for at least their own retrieval.

The actions always include the identity and the object (which may be the person's own identity and presence). Actions may or may not be shared with others. As many services provide public, selective, and private access to the information and actions.

Sharing

The act of sharing is where we finally start fully acknowledging social actions. The presence and actions elements can be private, if the person behind the identity wishes. Sharing is the social action that opens up the capability for all others (or only others whom have been given permission) to see their actions and possibly presence around an object. This can also include opening access to an object for others to see and others to add their annotations and actions around the object. This includes open annotations of other's openly shared objects or objects shared to a closed community to which the person has access.

Reputation

Shared presence and actions are the elemental building blocks for reputation. Reputation can build upon something as simple as existence on a service, by having an identity there. Reputation grows based on the interpretation of others based on shared presence and actions.

The actions that build reputation can be through the content that has been created by that identity. Others' understanding grows through seeing annotations that are by an identity (ratings, notes, comments, what is shared, etc.). Others also see actions that have been attributed to the identity, which may not be the direct actions that are seen, but can be actions of stating a relationship, joining a group, rewards (top contributor, etc.), or other indirectly perceived action.

The volume of actions also builds reputation. This can be the breadth of actions or breadth of subjects covered. Volume can also be depth of actions. Depth is how many in a subject area and/or the depth of understanding showed on a subject.

The breadth and depth lead to understanding of quality. Quality is often attributed by others based on their own perceptions and understanding. Perceptions, as we know, vary from person to person and that builds trends of reputation. Quality is also interpreted through perception. These interpretations are can be reflected in what others actions taken around an identity (identity can be the focal object in this activity) such as rating contributions made by an identity, favoriting/holding on to the actions of an identity (comments, their favorites, etc.), electing to follow the actions through subscribing or other similar actions, etc. Others may also write about an identity to express and understanding of the identity.

Relationships

Based on reputation people chose to interact with that identity. Through interaction relationships are established or built. This may be explicitly stated in some manner (the "connection" or "collaborator" or "friend" distinctions in some social services are examples). Relationships may also be an inferred relationship based upon actions. The inferred relationship is through another's actions of following, subscribing to actions, annotating an object, or other actions.

Relationships may be causal (as result of actions) or intended. The breadth of the relationship needs also be considered. A relationship between people or their identities can be based only on a precise subject matter or many distinct subjects in a granular social manner. The relationship may be more broad-line by encompassing most subjects that around a person and their identity.

There is rich derived value that can be built upon through identifying and understanding the granular subjects of common interest between people. The relationship can be one that is expansive, in that one person or both are learning and exploring new ideas and material through the shared experiences and shared understanding of the other. Understanding that a relationship is only as broad as a similar interest(s) (it does not have to be the same polarity (like/dislike)) such as for acoustic bebop jazz will help framing the relationship for what is shared, followed, and interaction made around.

Conversation

A relationship predicated on some understanding of reputation (remembering that it may be a rather thin understanding of reputation) provides a good foundation the next stage, conversation. The conversation is most often with an identity about or around an object.

The conversation may be a 2-way or multi-directional. This communication may be a synchronous live conversation or asynchronous over time (message boards or other services what allow comments or time ordered annotations. The conversation in a social environment is open and often around an object (keeping in mind the object may be a person's presence statements as in Twitter).

These conversations may be structured through form-based forums or listserves. The conversations may be free-form as in Consumating'sflirting through tagging or other open communication structures.

Groups

It is in the conversation (derived from relationships based on reputation) that people with similar interest come to the point where they want a more formal relationship so to have more focussed communication and sharing and these people form a group. The group is a sub-set of the whole service, as in Ma.gnolia's groups for sharing social bookmarks (Ma.gnolia's groups can be open to all or they can be closed and not seen). The sharing is a collective understanding of the group with each individual identity openly sharing their actions around that subject matter or interest. The group is normally comprised of trusted listeners who have a relatively strong understanding of reputation. The group is a collective voice what accounts for each voice. There does not have to be a common goal other than sharing information around (tightly or broadly clinging to the subject of interest) and each voice matters in the group.

Collaboration

Groups working often leads to collaboration where not only are people openly sharing information as individuals, but aim to work together to build objects. One example of this is a wiki where there the object is the development of a page or set of pages built through a collaborative process. The collaborative process has one goal (explaining a subject in the case of a wiki) and the group works with a single focus and intentionally becomes a single voice. The object being built may be text content, video with different production tasks and skills needed, other media, an application or service, or other object (physical or digital). Central to collaboration is an understanding of what is being built. Collaboration is most often iterative though building upon what is there with the goal of improving it.

Summary

A walk through the elements in the social software stack should provide an understanding of the progressive relationship between the elements. The aim is for this to be used a guide to think through building and implementing social software. I talk to many organizations that are trying to get to collaboration but are missing some or many pieces of the social software stack that collaboration is built upon. Not all of the elements need to be in the same tool, but they need to be accounted for in an environment that is collaborating.

Those not building collaborative services will also greatly benefit from understanding at what stage their social software service or tool is aiming to serve and ensuring all of the preceding elements are included or accounted for in the service.

Lastly, but not least it is important to understand what is the object of focus in the social software tool or service. This social object is part of the starting foundation and the better the understanding of the object and how it works in the service or tool the better the whole of the project/product will be in the end.

I have been using the newly launched Stikkit for the last day and rather enjoying it. Stikkit, is a web-based postit with super powers of a notepad with bookmark, calendar, lite address book for people, tagging, to do, and reminders to SMS (in the U.S.) and/or e-mail.

This summer I was in Portland and got a preview of Stikkit and was really impressed. It was a slightly different application at that point, but it had the great bones to be a really nice application for one's own Personal InfoCloud. Much of the really good intuitive scripting that turns dates in text into calendar entries, text to do lists into ones that can be checked-off, and other text to real functionality is in the current version and just sings.

When I used the Stikkit bookmarklet it captured pertinent information from a page that I wanted to track, which had date related information that is essential to something I have interest in, it made a calendar entry. The focus of the Personal InfoCloud is to have applications and devices that let people hold on to information that they have interest in and move it across devices, as well as add their own context. Stikkit, really is a wonderful step in making a rather friction free approach to the Personal InfoCloud. It puts the focus on the person and their wants and needs for the use of the information in a page. Stikkit can free the information from the confines of the web page and alert the person to important dates. Stikkit also allows the person to share what they find easily.

I think the key to Stikkit is the term "easily", which is the underpinning of the whole application. The only thing I would love to see is <

In the Personal InfoCloud people have various means of keeping information close to them. But, these actions come down to two actions, which are non-exclusive (we can do both). These actions are copying the information to a device or location we are comfortable storing the information and pointing to where the information is located.

Copy, Point: What are We Missing?

Each action (copy & point) has its own benefits and detractors, but both methods are missing a central component that causes us grief at some point or another. We are missing a tether to that information. In our action of copy & point we are making an explicit action declaring our interest in the item. But, when that item changes we should have the option of finding that out. Sometimes it is a minor inconvenience that the information changed, such as spelling errors have been corrected or a more detailed explanation offered. When the modifications are not minor, we most often would benefit from having notification, such as the price of an object changes, the definition is changed, errors corrected, the date or time of an event changed, new article/post on the subject has been made, etc.

We live in a world of ever increasing updates and modifications, mostly because it is so easy to make the modification and we are increasingly becoming an iterative society. Digital information is making providing a platform for this iterative society. In a limited interaction we hit refresh to see the news updates on CNN or ESPN. This iterative society also builds tools to track systems that have a lot of volume and volatility, such as EBay.

Information volatility is a given, but when the flood of information we have interest in or have made explicit action statements about is more than we can refresh, how do we cope? How do those developing and designing these information systems make it easier for us?

We are tethering to the inflow of information. We subscribe to e-mail for product updates from services like Amazon and we have RSS/ATOM feeds for inflow of news services. These inflow tethers are adding to our information overload. We are finding new tools that allow us to copy & point to the bits that are of interest to us, such as social bookmarking tools like del.icio.us, Shadows, etc., but these tools do not truly tether the information in a manner that is helpful when the information changes.

Similarly, when we copy a chunk of information (microcontent) from a report, article, or on-line source we have no means to get an alert when that body of work we copied from was altered. We may be using, or more appropriately reusing the information. We should have an easy means of providing attribution for the item we found of interest (allowing credit where credit is dues is not something that most people are against, but it is not currently easy). There needs to be a solution that would allow easy attribution, in that action we are tethering the information chunk to our source. This attribution mechanism is similar to social bookmarking for larger addressable works (some services like Yahoo's MyWeb 2.0 save a copy of the work we are bookmarking), but neither provides an active tether that alerts us to changes in something we have made an explicit action show our interest in.

Let's begin with Ballmer's response to the question, "Ten years from now, what is the digital world going to look like? To which Ballmer responds:
A: People are going to have access to intelligence in multiple ways. I'm going to want to have intelligence in my pocket. I'm going to want to have intelligence in my TV. I'm going to want to have intelligence in my den and in my office. And what I may want in terms of size, of screen size, of input techniques, keyboard, handwriting, voice, may vary.

I think what we'll see is, we have intelligence everywhere. We have multiple input techniques, meaning in some sense you may have some bit of storage which travels with you everywhere, effectively. Today, people carry around these USB storage devices, but you'll carry around some mobile device.

The problem is people have the devices in their pockets today in the form of Blackberries, Treos, Nokia 770s, and just regular mobile phones with browsing and syncing. The access to the information is in people's pockets. The software to make it simple with few clicks is where the battle lies. My Palm OS-based Treo 650 is decent, but it has few clicks to get me to my information. My friends with the Windows version of the same device have six or more clicks for basic things like calendar and address book. Going through menus is not simplicity. Going directly to information that is desired is simplicity. A mobile devices needs simplicity as it is putting information in our hands with new contexts and other tasks we are trying to solve (driving, walking, meeting, getting in a taxi, getting on a bus, etc.).

The Information

Not only does the software have to be simple to access information in our Personal InfoCloud (the information that we have stated we want and need near us, but have structured in our personal framework of understanding). We also interact with the Local InfoCloud with is information sources that is familiar to us to which we have set a means of easing interaction (cognitively, physically, or mechanically).

This "intelligence" that Ballmer refers to is information in the form of data. It needs to be structured to make solid use of that information in our lives. This structure needs to ascend below the page level to at least the object level. The object level can be a photo with the associated metadata (caption, photographer, rights, permanent source, size, etc.), event information (event name, location, date and time, permanent location of the information, organizer, etc.), full-text and partial-text access (title, author, contact info, version, date published, rights, headers, paragraphs, etc.).

These objects may comprise a page or document on the web, but they not only have value as a whole, they have value as discrete objects. The web is a transient information store for data and media, it is a place to rest this information and object on its journey of use and reuse. People use and want (if not need) to use these objects in their lives. Their lives are comprised of various devices with various pieces of software that work best in their life. They want to track events, dates, people, ideas, media, memes, experts, friends, industries, finances, workspaces, competition, collaborators, entertainment, etc. as part of their regular lives. This gets very difficult when there is an ever growing flood of information and data bombarding us daily, hourly, consistently.

This is not a future problem. This is a problem right now! The information pollution is getting worse every moment we sit here. How do we dig through the information? How do we make sense of the information? How do we hold on to the information?

The solutions is using the resources we have at our finger tips. We need access to the object level data and the means to attach hooks to this data. One solution that is rising up is Microformats, which Ray Ozzie of Microsoft embraces and has been extending with his Live Clipboard, which is open for all (yes all operating systems and all applications) to use, develop, and extend. The web, as a transient information store, must be open to all comers (not walled off for those with a certain operating system, media player, browser, certain paid software, etc.) if the information is intended for free usage (I am seeing Microsoft actually understand this and seemingly embrace this).

Once we have the information and media we can use it and reuse it as we need. But, as we all know information and media is volatile, as it changes (for corrections, updates, expanding, etc.) and we need to know that what we are using and reusing is the best and more accurate information. We need the means to aggregate the information and sync the information when it changes. In our daily lives if we are doing research on something we want to buy and we bookmark it, should we not have the capability to get updates on the prices of the item? We made an explicit connection to that item, which at least conveys interest. Is it not in the interest of those selling the information to make sure we have the last price, if not changes to that product? People want and need this. It needs to be made simple. Those that get this right will win in the marketplace.

What is Standing in the Way?

So, the big question is, "what is standing in the way"? To some degree it is the tools with which we create the information and some of it is people not caring about the information, data, and media they expose.

The tools many of the large information providers are using are not up to the task. Many of the large content management systems (CMS) do not provide simple data structures. The CMS focusses on the end points (the devices, software, tools, etc.) not the simple data structures that permit simple efficient use and reuse of the objects. I have witnessed far too many times a simple web page that is well structured that is relatively small (under 40KB) get turned into an utter mess that is unstructured and large (over 200KB). Usable, parseable, and grabable information is broken by the tools. The tools focus on what looks good and not what is good. Not only is the structure of the data and objects broken, but they are no longer addressable. There are very few CMS that get it right, or let the developers get it right (one that gets it right is Axiom [open disclosure: I have done work with Siteworx the developer of Axiom]).

The other part of the problem is the people problem, which is often driven by not understanding the medium they are working within. They are focus on the tools, which are far from perfect and don't care enough to extend the tools to do what they should. Knowing the proper format for information, data, media, etc. on the web is a requirement for working on the web, not something that would be nice to learn someday. Implementing, building, and/or creating tools or content for the web requires understanding the medium and the structures that are inherent to building that well. I have had far too many discussions with people who do not understand the basics of the web nor the browser, which makes it nearly impossible to explain why their implementation fails. Content on the web has requirements to be structured well and the pages efficiently built. The pages need to degrade (not with an $80,000 plug-in) by default. Media on the web that is for open consumption must work across all modern systems (this should be a 3 year window if not longer for the "modern" definition).

Summary

So what is the take away from this? Content needs to be built with proper structure to the sub-object level (objects need the metadata attached and in standard formats). The content needs to be open and easily accessed. Portability of the information into the tools people use that put information in our pockets and lives must be done now. We have the technology now to do this, but often it is the poorly structured or formatted information, data, media, etc. that stands in the way. We know better and for those that don't know yet the hurdle is quite low and easy to cross.

Until May of 2005 I had trouble with one element in my work around the Model of Attraction and Personal InfoCloud (including the Local and Global InfoClouds as well) to build a framework for cross-platform design and development of information and media systems and services. This problem was lack of an easy of explaination of what changes have taken place in the last few years on the web and other means of accessing digital information. In preparing for a presentation I realized this change is manifest in how people get and interact with the digital information and media.

This change is easily framed as the "Come to Me" web. The "Come to Me" web, which is not interchangeable with the push/pull ideas and terms used in the late 90s (I will get to this distinction shortly). It is a little closer to the idea of the current, "beyond the page" examinations, which most of us that were working with digital information pre-web have always had in mind in our metaphors and ideologies, like the Model of Attraction and InfoClouds.

The I Go Get Web

Before we look at the "Come to Me" web we should look at what preceded it. The "I Go Get" metaphor for the web was the precursor. In this incarnation we sought their information. The focus was on the providers of the content and the people consuming the information (or users) were targeted and lured in, in the extreme people were drawn in regardless of a person's interest in the information or topic covered. The content was that of the the organization or site that provided that information.

This incarnation focussed on people accessing the information on one device, usually the desktop computer. Early on the information was developed for proprietary formats. Each browser variant had their own proprietary way of doing things, based around a few central markup tags. People had to put up with the "best view with on X browser" messages. Information was also distributed in various other proprietary formats that required software on the device just so the person could get the information.

The focus providing information was to serve one goal (or use) reading. Some of this was driven by software limitations. But it was also an extension of information distribution in the analog physical space (as opposed to the digital space). In the physical space the written word was distributed on paper and it was consumed by reading (reuse of it meant copying it for reading) and it took physical effort to reconstruct those words to repurpose that information (quoting sources, showing examples, etc.).

The focus was on information creation and the struggle was making it findable. On the web there were only limited central resources used to find information, as many of the search engines were not robust enough, did not have friendly interfaces. Findability was a huge undertaking, either to get people what they desired/needed or to "get eyeballs".

Just as the use of the information was an extension of the physical realm that predated the digital information environment, the dominant metaphor in the "I Go Get" web was based in the physical realm. We all designed and developed for findability around the navigation/wayfinding metaphor. This directly correlates to going somewhere. Cues we use to get us to information were patterned and developed from practices in the physical world.

Physical? Digital? Does it Matter?

You ask, "So what we used ideas from the physical world to develop our metaphors and methodologies for web design and development?" We know that metaphors guide our practices. This is a very good thing. But, metaphors also constrain our practices and can limit our exploration for solutions to those that fit within the boundaries of that metaphor. In the physical realm we have many constraints that do not exist in the digital realm. Objects are not constrained by the resources they are made from (other than the energy to drive digital realm - no power no digital realm). Once an object exists in the digital realm replicating them is relatively insignificant (just copy it).

Paths and connections between information and objects is not constrained by much, other than humans choosing to block its free flow (firewalls, filtering, limiting access to devices, etc.). Much like Peter Merholz desire lines where people wear the path between two places in a manner that works best for them (the shortest distance between two points is a straight line). Now, don't think of the physical limitation between two points, I need to go from my classroom on the fourth floor of building "X" to across campus, up the hill to the sixth floor office of my professor. Draw a straight line and walk directly. This does not work in physical space because of gravity and physical impediments.

Now we are ready to understand what really happens on the web. We go from the classroom to our professors office, but we don't move. The connection brings what we desire to us and our screen. In this case we may just chat (text or video - it does not matter) with the professor from our seat in the classroom (if we even need to be in the classroom). Connections draw objects to our screens through the manifestation of links. As differently as people's minds work to connect ideas together, there can be as many paths between two objects. Use of physical space is limited by limitations outlined in physics, but the limitations are vastly different in digital space, use of the same information and media has vastly different limitations also.

It is through breaking the constraints of old metaphors and letting the digital realm exist that we get to a new understanding of digital information on the networks of the digital realm, which include the web.

The Come to Me Web

The improved understanding of the digital realm and its possibilities beyond our metaphors of the physical environment allows us to focus on a "Come to Me" web. What many people are doing today with current technologies is quite different than was done four or five years ago. This is today for some and will be the future for many.

When you talk to people about information and media today they frame it is terms of, "my information", "my media", and "my collection". This label is applied to not only information they created, but information they have found and read/used. The information is with them in their mind and more often than not it is on one or more of their devices drives, either explicitly saved or in cache.

Many of us as designers and developers have embraced "user-centered" or "user experience" design as part of our practice. These mantras place the focus on the people using our tools and information as we have moved to making what we produce "usable". The "use" in "usable" goes beyond the person just reading the information and to meeting peoples desires and needs for reusing information. Microformats and Structured Blogging are two recent projects (among many) that focus on and provide for reuse of information. People can not only read the information, but can easily drop the information into their appropriate application (date related information gets put in the person's calendar, names and contact information are easily dropped into the address book, etc.). These tools also ease the finding and aggregating of the content types.

As people get more accustom to reusing information and media as they want and need, they find they are not focussed on just one device (the desktop/laptop), but many devices across their life. They have devices at work, at home, mobile, in their living space and they want to have the information that they desire to remain attracted to them no matter where they are. We see the proliferation of web-based bookmarking sites providing people access their bookmarks/favorites from any web browser on any capable device. We see people working to sync their address books and calendars between devices and using web-based tools to help ensure the information is on the devices near them. People send e-mail and other text/media messages to their various devices and services so information and files are near them. We are seeing people using their web-based or web-connected calendars to program settings on their personal digital video recorders in their living room (or wherever it is located).

Keeping information attracted to one's self or within easy reach, not only requires the information and media be available across devices, but to be in common or open formats. We have moved away from a world where all of our information and media distribution required developing for a proprietary format to one where standards and open formats prevail. Even most current proprietary formats have non-proprietary means of accessing the content or creating the content. We can do this because application protocols interfaces (APIs) are made available for developers or tools based on the APIs can be used to quickly and easily create, recreate, or consume the information or media.

People have moved from finding information and media as being their biggest hurdle, to refinding things in "my collection" being the biggest problem. Managing what people come across and have access to (or had access to) again when they want it and need it is a large problem. In the "come to me" web there is a lot of filtering of information, as we have more avenues to receive information and media.

The metaphor and model in the "I go get" web was navigation and wayfinding. In the "come to me" web a model based on attraction. This is not the push and pull metaphor from the late 1990s (as that was mostly focussed on single devices and applications). Today's usage is truly focussed on the person and how they set their personal information workflow for digital information. The focus is slightly different. Push and pull focussed on technology, today the focus is on person and technology is just the conduit, which could (and should) fade into the background. The conduits can be used to filter information that is not desired so what is of interest is more easily identified.

I have been traveling more than usual this year to places in the United States and Europe. Some I have been to before and others I have not. Many of the trips are to places for only a few days and are set around meetings, conferences, or speaking engagements. I am often making plans at the last minute or having to make arrangements on the fly as ancillary meetings (not the prime reason I am there) get moved or cancelled. I am often looking for food, coffee, wifi, electronic stores, hardware stores, etc. in a location I am not completely familiar with. I am needing services of the local businessman, but I am not local.

Most modern phones know your location, they have to by law in the United States for emergency service calls. The phones do not provide easy access to that location software because the carriers providing the service do not want you to have it for free, they want somebody to pay for that information. If I call information they are not going to tell me where I am, nor the type of service or store I am seeking.

A Hack Finds "Where"

My current hack is to stand in front of a store, which I know the street name and I send the request for information about the place to Google SMS (ritual coffee. san francisco, ca) and I get one important piece of information back, the zip code. The zip code in the United States is the key to getting location information. There is nothing when driving (or actually riding as a passenger, because one never text messages while driving) or walking around that tells you the zip code (I have given up asking strangers on the street the zip code as it is more often than not incorrect). Once I have the zip code I can ask the mobile services for "coffee 94110" and get another place to get coffee and sit down because Ritual Coffee Roasters is utterly packed and already has seat vultures hovering.

Ministry of Silly Steps

Doing this little dance I get options, but it is a few steps that I should never have to take. The information most needed in a local search when mobile is location

Zip It, Zip, Z..

With the zip code I can dump that into my Mobile Yahoo! "new location" and get results. But, even because Yahoo! Mobile knows it is me (they offered me my stored locations (such as Home and Work)) it does not use that information to give me things I have reviewed and stored in Yahoo! Local. In the online version of Yahoo! Local I get reviews from people in my "community" (that really really needs to get a firm understanding of the granular social network), which is often helpful (if I know the person and can adjust my perception because I know how close that person's preferences are to mine on that subject). Sometimes I need an extension cord or an Apple Store (or a good substitution).

Elsewhere: Missing Even Partial Solutions

Additionally, this only works in the United States. The global local versions of Yahoo don't have fleshed out local services that are anything close to what is available in the United States and my "community" (as imperfect of an approach as it is at the moment) is still more helpful at filtering than nothing and I know I have many people in my "community" that have not only been to the same locations I am in, but have reviewed restaurants, local stores, etc. on the web and I want to be able to pull that information back in. Yes, this means the services need to grasp and embrace digital identity to make this work (or just build a social network capable address book that knows who my friend's identities are on various other services and social networking tools where this information may be sitting - not rocket science by any means). I heard some native language services were around, but those would not be fully helpful to me (I think I could get through it however), but if I tried a service that did not work it is not pointing me to one that does (now that would be insanely helpful and I would likely go to the kind service people for everything first as they would point me to just the right place every time).

Ya Beats Goo

Well at least Yahoo! understands there are places outside the United States. Google's services are not there, or any where on the mobile front it seems. In my last trip to Europe nobody knew that Google offered these services, which it seems they do not, in one of the most mobile use intensive cultures in the Western Hemisphere.

Enough

I know, enough. I agree. We need mobile information that works. WiFi is not here everywhere. Even if it were I am not foolish enough to pull out my laptop to try and get a signal and then get the information I need. I have a mobile device with the perfect capability to do just this. Actually there are more than double (if not triple - can not put my fingers on this info) the users with this capability on their mobile than laptop users in the United States (foolishly most laptops do not have locative hardware in them to ease this possibility if it was your last possibility). The technologies are here. Why are we not using them?

One of the main concepts around the Personal InfoCloud is access to our information when we need it. It has become relatively easy to find digital information on the internet these days, but keeping track of information for ourselves is a huge problem. Not only do we have the problem of tracking our information on one device, but across our devices (our laptop and desktop at work, our mobile, our PDA, our desktop at home) it become nightmare. We have gone from the scent of information (Xerox Parc term), to the current stench of information, and we are trying to get to the sweet smell of information.

One of the tools that has helped many manage some of the information they find on the web is del.icio.us. Del.icio.us is a social bookmarking tool that give the person the means to save the bookmark in a web-based tool and add tags (keywords) to the link that are of their choosing for their own bookmark retrieval. The tool really caught on as people can easily refind that information they stored because it is saved using their own vocabulary. Other people can find the same object (it is a shared "social" tool) if they use the same vocabulary to describe the same object.

It is time we all start to focus on the person and how they use and reuse the information. How do people combine disparate information in what have been separate applications and separate devices? Our design and development has to get personal.

It is these solutions an focus that are lacking from many approaches to web and application development today. Yes, it is still lacking, but it may not be for much longer.

What has changed the environment? Personalization has triggered much of this change. No, not the giant portal personalization that the content management overloads want to sell for mega-bucks and still provide mini-returns. This is personalization that allows the person to decide what information or information source is important to follow. People and vendors (be it information or products) have a desire to strengthen their connection. Vendors need to make it easy on the person who has an interest in the vendor and one or many of their products.

One of the tools that has caught on in the mainstream is RSS/Atom feeds. This allows a person to subscribe to the information that most interests them. This information can be news feeds that are targeted to specific genres or it can be a listing of products newly available, as Apple is doing with its new additions to iTunes each week and Amazon is doing for it product categories. In the past e-mail has been one of the few avenues that has been available to provide a personal connection.

So if it is getting easier to have the information from vendors easily subscribed to, how difficult should it be to subscribe to our own information? This is one of the del.icio.us solutions, well it seems to be targeted to others subscribing to our shared bookmarks, but we can easily subscribe to an RSS feed of our own bookmarks or even our own specific tagged bookmarks, should we wish to.

With calendaring we have similar subscription options if we use the iCal standard. There are even RSS event capabilities that can be incorporated (RSS with Dublin Core attributes as Upcoming does, or event module attributes). Subscribing is one solution, but often I need to add calendar events into my mobile device (Treo 600 or Nokia Series 60 phone) with out having to rekey everything. There are open standards for calendaring, why don't mobile device calendar applications just incorporate accepting these standard file types? Using standard solutions to keep all of the facets of our life, or at least our calendar related facets, seems to be a wise and relatively easy solution.