The recent announcement from Google that they will start indexing RDFa and Microformats flew mostly under the radar, but is doesn’t go completely unnoticed (see Zemanta links below).

I personally think that this marks the start of “real world” adoption of semweb, be it through a surrogate approach via microformats.
Why now? Because improved representation of your content in Google is simply too big to ignore. If embedding microformatted content (or, hopefully, RDFa) brings you an advantage in Google Page Rank, web site owners and SEO specialists will rapidly adopt the technology. Without the google index incentive this never would happen.

The other side may be that data quality gets diluted in a way. Up till now we are used to working with reasonably clean and consistent collections (like DBpedia, MusicBrainz to name a few), where the data quality matters all by itself. That is radically different from entering some code for the purpose of cranking up your rank on the search engines.

Maybe in a year from now we are all busy with implementing trust- and reputation systems for linked data instead of spreading the word. I’m curious if the nature of linked data makes this job any easier than with the unstructured web of documents.

Update: Ivan Hermann tells it all in a nutshell: RDFa, Google.

Related articles by Zemanta

• Google supports RDFa – SEOs work changes forever (ithoughts.de)
• Rich Snippets: Tipping point for the semantic web (mikeaxelrod.com)
• Introducing Rich Snippets (googlewebmastercentral.blogspot.com)
• Google Announces Support for Microformats and RDFa (4cloudcomputing.blogspot.com)
• Will You Use Google’s New “Rich Snippets” Markups? (seroundtable.com)

Popularity: 13%

Tweet This Delicious Reddit This Post Stumble This Post

Image via Wikipedia - this version is in fact outdated again, by now the open resources have already doubled.

“Linked Media: Weaving non-textual content into the semantic web” – Raphaël Troncy

Traditional media cunsumption (like TV) is declining and moving to the web. The question is: how can we make media into a first class object on the web?

Lots of issues: codecs, metadata, content protection and so on. Is there a viable OSS alternative?

Media Fragments WG

Case: media fragments identification and selective retrieval of media fragments, the goal of the Media Fragments WG of the W3C. Basic principles apply: fragment identification needs to be based on the URI.

There are four dimensions which define a fragment: time (point or interval), space (rectangle for now), track (video, audio, subtitles) and id (the unique name of the fragment).

The possibilities are limited by the container format can express (e.g. quicktime and such) Protocols include http, rtsp and a lot of proprietary protocols like mms, and the various p2p protocols.

Much of the fragment identification is already possible for the most important players in the market, but the syntax is not standard in any way.

Warning, hardcore geekery ahead… Read the rest of this entry »

Popularity: 23%

Tweet This Delicious Reddit This Post Stumble This Post