If you're drawn to open standards and solutions and you follow social networking trends, then open microblogging is a natural path that, not surprisingly, many have followed. If you also have faith in the semantic web, then open semantic microblogging is also a natural concept - the idea being that the text of a microblog entry can be embellished by semantic markup about what it is, where & where it came from, what can be done with it and so on. And because the platform is open, you have control over that semantic richness.
In A Flock of Twitters: Decentralized Semantic Microblogging, Jeff Sayre develops a very nice hydrological metaphor whereby microblog posts in an open, semantic ecosystem comprise Drops of water that flow, swirl and coalesce into eddies, streams rivers and, inevitably, the MicroBlogOcean. I'd been toying with a pointillist metaphor, whereby tiny Dabs of information comprise a much larger picture - but water works much better.
Following Jeff's ideas, I've been thinking about the role of mobile devices. Specifically, smartphone as ... wait for it ... cloud, in the sense of a cloud being a lightweight thing that floats around and, when the conditions are right, releases drops of water. Perhaps that's taking the metaphor too far. But in an open semantic microblogging world where, as in Jeffs model, I own my own stream and have control over what happens to my content, I want my mobile phone to give me Drop of semantic data whenever I
- make or receive an email, phone call, SMS, blog post etc etc
- write a note
- visit a web site
- use a web service
- book or attend a meeting
- take a photo
- run an application
- change application settings
- measure something
- move more than x metres from where I was
- appear to be in two places at once (stolen phone)
- do something else that uses my phone's OpenDrop (tm) API
- etc
Each Drop will contain all of the information relevant to the event that created it. If I take a note, the Drop contains the text of the note; if I change the settings on an application, the Drop records the changes; I take a photo, the Drop is the photo; visit a Web site, its the URL.
Thus, to the extent that my smartphone is central my (working) life, and increasingly it is, then my semantic Stream is a complete and private life-log. As I move around and do things, my phone releases a constant trickle of Drops; perhaps big Drops (containing video for instance) only fall when I'm in range of my home wireless network.
I will allow all that detailed personal information to be captured and released because I control what happens once all the Drops gets back to a fixed aggregator. My aggregator might be on my desktop (via XMPP) or a trusted cloud service (which I pay for with money, not personal information); it can filter, store, forward and generally act upon Drops as I see fit.
- Perhaps I will have a smart filter that reasons which Drops can be made public and tweets them. Or not, as I choose.
- Perhaps I want to send all photos and notes taken when I'm out bush-walking and bird-watching in a national park to a Citizen Science initiative set up to record biodiversity in that park.
- Almost certainly I'd like to keep all my notes and a log of my emails and phone calls in a private message store.
- Maybe I want my family to know where I am. Especially if I'm one of my children...
- Just for fun I'd like to make a map of where I went, if only to appreciate what a tiny world I live in.
The natural technology for all this stuff is, of course, the RDF stack. Drops are RDF graphs. Drops are filtered and routed in response to SPARQL queries. OWL reasoners and SWRL rules devise new semantic attributes. Triple stores keep it all.
Android looks like the right platform to do all this. The pieces are in place.