@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type sioct:BlogPost , atom:Entry . @prefix dc: . dc:title "RDF Browsers & RDF Data Middleware" ; foaf:maker ns1:this ; rdfs:label "RDF Browsers & RDF Data Middleware" . @prefix dt: . @prefix dcterms: . dcterms:created "2007-03-28T19:17:00-04:00"^^dt:dateTime ; dcterms:modified "2007-04-29T14:59:05-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "32afb48b88330ce7ff1e2ffcb039c49e" ; sioc:link ; sioc:content " Frederick Giasson penned an interesting post earlier today that highlighted the RDF Middleware services offered by Triplr and the Virtuoso Sponger Some Definitions (as per usual): RDF Middleware (as defined in this context) is about producing RDF from non RDF Data Sources. This implies that you can use non RDF Data Sources (e.g. (X)HTML Web Pages, (X)HTML Web Pages hosting Microformats, and even Web Services such as those from Google, Del.icio.us, Flickr etc..) as Semantic Web Data Source URIs (pointers to RDF Data). In this post I would like to provide a similar perspective on this ability to treat non RDF as RDF from RDF Browser perspective. First off, what's an RDF Browser? An RDF Browser is a piece of technology that enables you to Browse RDF Data Sources by way of Data Link Traversal. The key difference between this approach and traditional browsing is that Data Links are typed (they possess inherent meaning and context) whereas traditional links are untyped (although universally we have been trained to type them as links to Blurb in the form of (X)HTML pages or what is popularly called "Web Content".). There are a number of RDF Browsers that I am aware off (note: pop me a message directly of by way of a comment to this post if you have a browser that I am unaware of), and they include (in order of creation and availability): Tabulator DISCO - Hyperdata Browser OpenLink Ajax Toolkit's RDF Browser (a component of the OAT Javascript Toolkit) Each of the browsers above can consume the services of Triplr or the Virtuoso Sponger en route to unveiling a RDF Data that is traversable via URI dereferencing (HTTP GETing the data exposed by the Data Pointer). Thus you can cut&paste the following into each of the aforementioned RDF Browsers: Triplr's RDF Data (Triples) extractions from Dan Connolly's Home Page The Virtuoso Sponger's RDF Data (Triples) extractions from Dan Connolly's Home Page Since we are all time challenged (naturally!) you can also just click on these permalinks for the OAT RDF Browser demos: \n \n Permalink for Triplr's RDF Data (Triples) extractions from Dan Connolly's Home Page \n \n\n Permalink for the Virtuoso Sponger's RDF Data (Triples) extractions from Dan Connolly's Home Page\n\n" ; atom:title "RDF Browsers & RDF Data Middleware" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix ns11: . sioc:links_to ns11:tab , . @prefix ns12: . sioc:links_to ns12:blog . @prefix ns13: . sioc:links_to ns13:comments . @prefix ns14: . sioc:links_to ns14:LinkingOpenData , , , , , , . @prefix ns15: . sioc:links_to ns15:dereference-uri ; atom:source ; atom:author ns1:this ; atom:published "2007-03-28T23:17:00Z" ; atom:updated "2007-04-29T18:59:05Z" . @prefix opl: . opl:isDescribedUsing . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person ; foaf:made . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . @prefix sioc: . sioc:container_of ; atom:entry ; atom:contains . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "2008, Facebook Data Portability, and the Giant Global Graph of Linked Data" ; sioc:links_to . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .