[PhilWolff] The ComponentBlog is the precursor to the AdaptiveBlogosphere.
The idea...
-
Bakers define recipe formats.
-
They teach them to their weblog tool (defining a form).
-
They post recipes.
-
They are syndicated.
-
Other bloggers notice the new format. By autodiscovery. By reading weblogs with structured content (sports scores in a nice table, for example).
-
They add it to their own blogging tool.
-
Then when they compose a new post, they can pick components to add (Pillsbury Commercial Recipe Format, imdb Movie Review Format (supported by Amazon), HR department's vacation survey).
-
You manage your list of formats, retiring some, promoting others.
-
Formats proliferate through the blogosphere. Some become de facto leaders for a type of content or transaction. Others carve out niches, perhaps associated with a vendor or an industry.
Hypothetical Consequences
Most people will still do plain old blogging, lucky if they use a title or main link.
Many will occasionally use a structure. Especially as Blog This buttons proliferate. So you can post an SAP invoice to your intranet blog, for example.
Others will find a few formats that tie in closely with a deep interest or passion, or their jobs. A runner's diary. A movie review. A project status report.
Enterprise applications will read components. So information will flow between the modestly structured blogosphere and the highly structured business infrastructure.
-
I'm a Macy's buyer. I get an echo feed from J.D.OracleSoft for orders processed in my category. I post some of them to my team weblog, marking them up with comments about the intended customers, thoughts about the vendor meeting, and terms that didn't fit in the software (front row seats for the family). J.D.OracleSoft reads my feed, looking for changes to the order, and adding the post's permalink to the transaction record.
Discussion
[DannyAyers] I like this idea. But then I would, it sounds like part of the Semantic Web.
See also SyntaxExtensionMechanism
Original author: PhilWolff