There’s an article on TechCrunch about Yahoo offering support for a number of microformat standards.
They are saying that they will support a number of microformats at the start: hCard, hCalendar, hReview, hAtom and XFN. They will support vocabulary components from Dublin Core, Creative Commons, FOAF, GeoRSS, MediaRSS, and others. They will support RDFa and eRDF markup to embed these into existing HTML pages. Finally, Yahoo will support the Amazon A9 OpenSearch specification with extensions for structured queries to deep web data.
I replied to the post at techcrunch and will repost it here – I thought I’d change something, but I’ll just throw it out here for now for discussion.
=========
I’m a bit more reluctant to believe the hype or promise of this. There are technical and human hurdles to deal with – semantically marking up data is hard, and humans can still get things wrong. Yahoo will still need to put in ‘best guess’ algorithms and such to compensate.
But the bigger issue is why would someone like linkedin semantically mark up all their profile pages, at least for public consumption? It makes it that much easier for competitors to come and take away the one set of data that makes linkedin unique – the relationship data they have about their users. For me, what makes linkedin linkedin is the set of relationships (and to a lesser extent, what tools linkedin provides to exploit those relationships).
Adding semantic markup to linkedin profile pages will make it easier for Yahoo to show more information. Great. But it also makes it easier for everyone, including Linkedin and Yahoo’s competitors, to scrape intelligently, and offer bigger/better/faster/cheaper.
Now, there are certainly other benefits regarding cross-domain info linking – being able to better know the relationships between data across multiple data sets, for example. Again, good, but not great, imo.
It’s certainly a chicken/egg situation, but I’m also not sure that’ll we have the same incentives that we did 10 years ago before the massive commercialization. For every argument for semantic markup, there’s gotta be at least one competing commercial interest against it.
That’s my 2 cents as to why this will be an uphill battle.
=========
Any thoughts?