[openstreetmap-website] Added RDFa support for browse/node (#173)

Tom Morris notifications at github.com
Sun Dec 2 12:08:10 GMT 2012

Well, the main benefit I see RDFa implementation providing is being able to link OpenStreetMap data together with other published online datasets like [dbpedia](http://dbpedia.org). Being able to explicitly declare equivalencies (e.g. that [the river Thames](http://www.openstreetmap.org/browse/way/8125890) is the same as the [river Thames](http://dbpedia.org/resource/River_Thames)).

The key benefit that adding both microformats and RDF brings is that it allows reuse of basic metadata without having to learn how to use the API. Sites like [BBC Wildlife Finder](http://www.bbc.co.uk/blogs/bbcinternet/2009/09/wildlife_finder_david_attenbor.html) show the possibilities that flow from simple merging of linked data.

Regarding microdata, both can be used simultaneously. It was added unilaterally by the editor of the HTML5 specification because he decided that RDFa was too complicated. It provides a fairly limited subset of what RDFa provides. The main use of microdata has been by Schema.org, and they allow both microdata and RDFa. RDFa was in fairly wide use on the web before the introduction of microdata.

Regarding the use of <code>prefix</code>, yes, that is correct: <code>prefix</code> is preferable to <code>xmlns</code>. I'll fix that.

Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20121202/df43f023/attachment.html>

More information about the rails-dev mailing list