Reactions

TwitterFacebook
Get flash to fully experience Pearltrees

SEO reaction

I'm hesitant to either use superlatives or make predictions concerning search engine innovations (I'm the first to deride commentators that use the phrase "game changer" in almost any context), but the joint announcement by Google , Yahoo and Bing introducing schema.org is, in my opinion, pretty big news. Schema.org at once provides a mechanism by which semantic web technologies can become a lot more mainstream, and at the same time offers the possibility of superior search visibility for search marketers that embrace this standardized, structured on-page markup. Both searchers and publishers of quality content (by which, in this context, I really mean "quality data") stand to gain by the introduction of schema.org. http://www.seoskeptic.com/what-schema-org-means-for-seo-and-beyond/
Crispin Sheridan | June 29, 2011 On June 2, 2011, Google, Yahoo, and Bing announced the launch of schema.org, their cooperative alliance providing a universal baseline of support for microdata types. Microdata are HTML5 specifications enabling webmasters to embed semantic data inside the code of existing web pages.

Schema.org - Do I Need to Pay Attention to This? | ClickZ

http://www.clickz.com/clickz/column/2081986/schemaorg-pay-attention

Danny Ayers : Raw Blog

http://dannyayers.com/2011/06/15/httpRange-14-Reflux By 2005 a resolution was accepted. If a GET is done and the thing being referred to isn't a document, then a 303 redirect should be used to provide something which is a document. As these things go, this is quite an elegant solution. Additionally it's accepted practice to use #-URIs for things which aren't documents. However, both approaches have their problems, many of which are listed in Providing and discovering definitions of URIs .
Includes a very handy-looking microdata2json Python script. Re. the "rumor that Ian Hixie [ + Ian Hickson ] of Google wrote up the Microdata spec in a weekend because he hates RDFa" - this appears to be Hixie's initial mail on the matter: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019681.html His main rationale here against just using RDFa is that it's too powerful. And we wouldn't want Web authors to have too much power now, would we? Re-posting + Ed Summers 's post so it can be shared Public (would I be right in thinking this is necessary for it to have a public URL?). https://plus.google.com/112609322932428633493/posts/haj4bwQBztK#112609322932428633493/posts/haj4bwQBztK

A microdata2json Python script

http://inkdroid.org/journal/2011/08/02/goodreads-microdata/ I’m not sure how long it has been there, but I just happened to notice that GoodReads (the popular social networking site for book lovers to share what they are reading and have read) has implemented HTML5 Microdata to make metadata for books available in the HTML of their pages. GoodReads has chosen to use the the Book type from schema.org vocabulary, most likely because the big three search engines (Google, Bing and Yahoo) announced that they will use the metadata to enhance their search results. So web publishers are motivated to publish metadata in their pages, not because it’s the “right” thing to do, but because they want to drive traffic to their websites. If you are new to HTML5 Microdata, schema.org and what it means for books, check out Eric Hellman’s recent post Spoonfeeding Library Data to Search Engines .

GoodReads microdata

SemTech2011BOF - Semantic Web Standards

http://www.w3.org/2001/sw/wiki/SemTech2011BOF We would like to invite all interested parties to take part at a BOF, organized during the SemTech 2011 conference , on Structured Data in HTML . The questions arising have been around us for a long time, but the recent announcement of schema.org made the discussion more timely. Here are the questions that we propose to discuss (but any participant is welcome to raise additional questions):

Microdata + RDF | Jeni's Musings

As part of the ongoing discussion about how to reconcile RDFa and microdata (if at all), Nathan Rixham has put together a suggested Microdata RDFa Merge which brings together parts of microdata and parts of RDFa , creating a completely new set of attributes, but a parsing model that more or less follows microdata’s. I want here to put forward another possibility to the debate. I should say that this is just some noodling on my part as a way of exploring options, not any kind of official position on the behalf of the W3C or the TAG or any other body that you might associate me with, nor even a decided position on my part. Simplifying RDFa As I’ve said before , RDFa, in my experience, is complicated not primarily because of the whole namespaces/CURIEs issue but because its processing model tries to be too clever. http://www.jenitennison.com/blog/node/162
http://www.w3.org/wiki/Microdata_RDFa_Merge Important: this is not a specification, or even a proposal, it's just some notes from Nathan Rixham, thinking out loud, in a publicly visible and editable space. This page focusses on taking the best elements of Microdata and RDFa and creating a simple, for now fictional, set of attributes to handle metadata needs in HTML. For now this note introduces the following attributes:

Microdata RDFa Merge - W3C Wiki

Last week the Web's three leading search companies - Google, Microsoft and Yahoo! - announced a new structured data collaboration called Schema.org . It includes more than 100 new types of website markup for content like movies, music, organizations, TV shows, products, places and more. The stated aim of Schema.org is to "improve the display of search results, making it easier for people to find the right web pages." http://www.readwriteweb.com/archives/is_schemaorg_really_a_google_land_grab.php#disqus_thread

Is Schema.org Really a Google Land Grab?

Richard Cyganiak - Multiple itemtypes in Microdata

http://richard.cyganiak.de/blog/2011/08/multiple-itemtypes-in-microdata/ There’s a lot of discussion recently around HTML5′s microdata proposal , and how it relates to W3C’s earlier RDFa standard that is currently being updated for HTML5 . Microdata solves many of the use cases of RDFa in a much simpler way. But some other use cases it cannot solve.

Peter Mika on schema.org

Bing, Google, and Yahoo! have announced schema.org yesterday, a collaboration between the three search providers in the area of vocabularies for structured data. As the ‘schema guy’ at Yahoo!, I have been part of the very small core team that developed technical content for schema.org.

schema.rdfs.org - Home

In early June 2011, the three big search engines Bing, Google and Yahoo! introduced Schema.org , a collection of terms that webmasters can use to markup their pages to improve the display of search results. This site is a complementary effort by people from the Linked Data community to support Schema.org deployment and usage with a special focus on Linked Data :
Philip Jägenstedt has developed MicrodataJS , a jQuery plug-in for microdata providing an API similar to the HTML5 Microdata DOM API, as well as the Live Microdata tool that allows you to test your markup in the browser. Gregg Kellogg has developed the RDF::Microdata gem to parse microdata into RDF using the RDF.rb platform. This functionality is also available as an online-service called RDF Distiller . Michael Hausenblas has released the omnidator (the omnipotent data translator), an online tool with a CORS-enabled API to translate formats that use Schema.org terms. Currently, microdata (using Ed Summers' rdflib-microdata plugin) and CSV as input formats and JSON as well as RDF serialisations as output are supported.

schema.rdfs.org - Tools

OpenLink Virtuoso version 06.03.3131, on Linux (x86_64-generic-linux-glibc25-64), Standard Edition Data on this page belongs to its respective rights holders. Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software

OpenLink conversion to RDFS+OWL

Microdata and RDFa in TopBraid Composer

The next release of TopBraid Composer will include comprehensive support for editing and processing schema.org Microdata , and will also have improved support for RDFa . TopBraid is an extension of Eclipse and thus inherits a lot of goodness from the platform, including a very nice HTML editor. It was straight-forward and highly desirable to extend TopBraid with native support for those Web Data formats. Here is a preview of what it will look like.