|
|
|
A service is an offering by an Online Service Provider on the Internet that helps the user to manage his MicroContent Items in one way or another.
I did an experiment with Flickr using their tags feature. The idea is that their service can be used to create a common photo set based on common experiences. Say I go to a conference on Microlearning in Innsbruck. I am taking pictures, but also other people do this. As conference attendees we share an experience and thus also pictures. How does this work out in reality.
I uploaded the pictures I made for my whole trip to Flickr. One can zoom in on the pictures that I created during the trip. But one can also zoom in on the pictures I made during the conference itself or during the blogwalk, thanks to the tags.
But I was not alone. Other people made the same trip and took slightly different pictures: Microlearning conference and Blogwalk. Luckily enough we seemed to have used the same tags.
It is a pity that Flickr aggregates only the pictures that have been hosted I their place. So I do not find pictures that have been hosted elsewhere easily. Flickr should aggregate Picture-feeds as well.
By the way, I like the possibility to add notes to a picture. Should be a standard feature in any image application. Is there already a MicroContent standard for this?
Peter Caputa drew my attention to spurl.net. I looked at it in the post, but on how many services do you want put your bookmarks. Now however it can suck out del.icio.us and post to del.icio.us. So the bookmarks get pooled. I do not know however whether del.icio.us can get and upload to Spurl.
The question now becomes whether Spurl offers any interesting functionality. I have some problem accessing the service, so I have to get back on this.
Jon Udell suggests that a recommendation engine should be created based on tags in del.icio.us. Tags will be great for this, as they are tangential to MicroContent type.
It is always a question what I should add to my blog-page. Should I add a tag this blog Item to my blog-page, should I add a look at this tag at Technorati, should I add a reblg this item on my blog-page, or a rate this item, etc.? In each case I made a service decision for my viewers. But maybe they prefer to use other services. Why should I hard-code this? There are enough bookmarklets out there, that will do the work for you.
For this reason I would rather get rid of the link to Technorati, but I think my posts are now added to their directory. Something to look in to. With Reblg it is slightly different, but a similar issue is at stake. On the one hand I like the idea of a link to a MicroContent Item XML-fragment, so that other people can reuse the Item. But why use their directory service? Drag&drop is OK for me. I prefer clients anyway. Or the MacOS-X service menu can do the work for me. But is still requires some work on the client side.
So let’s start with Reblg and get those fragments out there.
Today Marc Canter revealed what the ReBlg-service is about. I must say that their explanation on ReBlg did not help me at first. I really needed Marc’s explanation. I get it as follows: A user sees a Rblg-button on a web-site next to a MicroContent Item. Clicking on the button will take the MicroContent Item and send it to the blog host system of the user. There a new MicroContent Item will be created based on the copied Item and the structure of the copied Item will stay intact. Then the user can edit this Item as he likes.
As Marc explains it is like copy&paste, but then more advanced, flexible and independent. This kind of functionality is what I meant, when I talked about independent MicroContent Items, which are available as files. In ReBlg these files are in fact XML-code fragments. I already use this all the time, when I add MacGourmet-recipes to my collection, by drag&dropping them from the web-page. So certainly such a functionality is needed.
Is ReBlg the way to go? I do not know yet. We have to see at how it develops. But it surely indicates a new way to think about and handle MicroContent Items: as separate Items encoded as XML fragments. And adoption of this idea is in my mind very important. So now I have to understand how to use the service.