@prefix rdfs: . @prefix ns1: . ns1:this rdfs:label "Kingsley Idehen" . @prefix rdf: . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Person . @prefix sioct: . rdf:type sioct:Weblog . @prefix atom: . rdf:type atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "RDF Browsers & RDF Data Middleware" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "2008, Facebook Data Portability, and the Giant Global Graph of Linked Data" ; foaf:maker ns3:this ; rdfs:label "2008, Facebook Data Portability, and the Giant Global Graph of Linked Data" . @prefix dt: . @prefix dcterms: . dcterms:created "2008-01-05T17:11:55Z"^^dt:dateTime ; dcterms:modified "2008-01-07T11:44:42.000007-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "317d9bfa59ce72571472b16be4f1da85" ; sioc:link ; sioc:content "As 2007 came to a close I repeatedly mulled over the idea of putting together a usual "year in review" and a set of predictions for the coming year etc. Anyway, the more I pondered, the smaller the list became. While pondering (as 2008 rolled around), the Blogosphere was set ablaze with the Robert Scoble's announcement of his account suspension by Facebook. Of course, many chimed in expressing views either side of the ensuing debate: Who is right -- Scoble or Facebook. The more I assimilated the views expressed about this event, the more ironic I found the general discourse, for the following reasons:\n\n\n\nWeb 2.0 is fundamentally about Web Services as the prime vehicle for interactions across "points of Web presence"\n\nFacebook is a Web 2.0 hosted service for social networking that provides Web Services APIs for accessing data in the Facebook data space. You have to do so "on the fly" within clearly defined constraints i.e you can interact with data across your social network via Facebook APIs, but you cannot cache the data (perform an export style dump of the data)\n\nFacebook is a main driver of the term: "social graph", but their underlying data model is relational and the Web Services response (data you get back) doesn't return a data graph, instead it returns an tree (i.e XML)\n\nScoble's had a number of close encounters with Linked Data Web | Semantic Data Web | Web 3.0 aficionados in various forms throughout 2007, but still doesn't quite make the connection between Web Services APIs as part of a processing pipeline that includes structured data extraction from XML data en route to producing Data Graphs comprised of Data Objects (Entities) endowed with: Unique Identifiers, Classification or Categorization schemes, Attributes, and Relationships prescribed by one or more shared Data Dictionaries/Schemas/Ontologies\n\nA global information bus that exposes a Linked Data mesh comprised of Data Objects, Object Attributes, and Object Relationships across "points of Web presence" is what TimBL described in 1998 (Semantic Web Roadmap) and more recently in 2007 (Giant Global Graph)\n\nThe Linked Data mesh (i.e Linked Data Web or GGG) is anchored by the use of HTTP to mint Location, Structure, and Value independent Object Identifiers called URIs or IRIs. In addition, the Linked Data Web is also equipped with a query language, protocol, and results serialization format for XML and JSON called: SPARQL.\n\n\n\nSo, unlike Scoble, I am able to make my Facebook Data portable without violating Facebook rules (no data caching outside Facebook realm) by doing the following:\n\n\nUse an RDFizer for Facebook to convert XML response data from Facebook Web Services into RDF "on the fly"\nEnsure that my RDF is comprised of Object Identifiers that are HTTP based and thereby dereferencable (i.e. I can use SPARQL to unravel the Linked Data Graph in my Facebook data space)\n\nThe act of data dereferencing enables me to expose my Facebook Data as Linked Data associated with my Personal URI \n\n\nThis interaction only occurs via my data space and in all cases the interactions with data work via my RDFizer middleware (e.g the Virtuoso Sponger) that talks directly to Facebook Web Services.\n\n\n\nIn a nutshell, my Linked Data Space enables you to reference data in my data space via Object Identifiers (URIs), and some cases the Object IDs and Graphs are constructed on the fly via RDFization middleware.\n\nHere are my URIs that provide different paths to my Facebook Data Space:\n\n\nPersonal URI\n\n\nMy Facebook Data Space (best viewed via a Linked Data Browser/Viewer session)\n\n\nMy Facebook Photo Gallery -- WWW2007 Photo Collection (also best viewed via a Linked Data Browser/Viewer session)\n\n\nTo conclude, 2008 is clearly the inflection year during which we will final unshackle Data and Identity from the confines of "Web Data Silos" by leveraging the HTTP, SPARQL, and RDF induced virtues of Linked Data. \n\nRelated Posts:\n\n\n 2008 and the Rise of Linked Data\n\n\n Scoble Right, Wrong, and Beyond\n\n\n Scoble interviewing TimBL (note to Scoble: re-watch your interview since he made some specific points about Linked Data and URIs that you need to grasp)\nPrior Blog posts my this Blog Data Space that include the literal patterns: Scoble Semantic Web\n\n" ; atom:title "2008, Facebook Data Portability, and the Giant Global Graph of Linked Data" . @prefix ns11: . sioc:has_creator ns11:this ; sioc:has_container . @prefix ns12: . sioc:links_to ns12:i . @prefix ns13: . sioc:links_to ns13:data_portability_scoble_explains , , . @prefix dbpedia: . sioc:links_to dbpedia:Robert_Scoble , , dbpedia:IRI , , , , , . @prefix ns15: . sioc:links_to ns15:a080103p154 , dbpedia:Uniform_Resource_Identifier , dbpedia:Social_Networking , , ns1:this , dbpedia:Web_service , , , , dbpedia:Linked_Data , , , dbpedia:Facebook , ; atom:source ; atom:author ns3:this ; atom:published "2008-01-05T17:11:55Z" ; atom:updated "2008-01-07T16:44:42Z" . @prefix opl: . opl:isDescribedUsing . ns11: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 . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .