"MicroContent is Everywhere"
Dr. Arnaud Leene (MicroContent Musings), who is also going to be at Microlearning 2005, published a first draft of his paper: "MicroContent is Everywhere" (PDF).
I think it is a good point that he mentions how microcontent gets structured through the use of metadata, calling it Structured Microcontent. Very interesting is the lifecycle of microcontent items he describes: creation, storage, publication, viewing, changing and removing. The line between publication and viewing seems to be very thin, and I would like to add that viewing can also go further, when it comes to collaborative interaction. Somebody who views a microcontent item is not likely to be able (allowed) to change it, but she might be given various options on how to add to a microcontent item (for example by leaving a comment, sending a trackback, or assigning a tag).
When the creator of a microcontent item makes any changes on the item, these changes should be detectable by any viewer, writes Leene. I couldn't agree more, but I'd say that this is hardly the case. Implementations which might already work are notifications of changes in weblog-items though RSS (most readers don't highlight the changes, though) or a wiki page's version history.
One last question which came to my mind is if microcontent can be unstructured at all, and if metadata is a requirement for microcontent (I think it possibly is).
Tags: MicroContent, Metadata
I think it is a good point that he mentions how microcontent gets structured through the use of metadata, calling it Structured Microcontent. Very interesting is the lifecycle of microcontent items he describes: creation, storage, publication, viewing, changing and removing. The line between publication and viewing seems to be very thin, and I would like to add that viewing can also go further, when it comes to collaborative interaction. Somebody who views a microcontent item is not likely to be able (allowed) to change it, but she might be given various options on how to add to a microcontent item (for example by leaving a comment, sending a trackback, or assigning a tag).
When the creator of a microcontent item makes any changes on the item, these changes should be detectable by any viewer, writes Leene. I couldn't agree more, but I'd say that this is hardly the case. Implementations which might already work are notifications of changes in weblog-items though RSS (most readers don't highlight the changes, though) or a wiki page's version history.
One last question which came to my mind is if microcontent can be unstructured at all, and if metadata is a requirement for microcontent (I think it possibly is).
Tags: MicroContent, Metadata
9:44 AM
