@prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:Comment . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Person . rdf:type sioct:Weblog , atom:Feed . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Semantic Web Data Spaces" ; foaf:maker ns3:this ; rdfs:label "Semantic Web Data Spaces" . @prefix dt: . @prefix dcterms: . dcterms:created "2007-04-13T21:15:54Z"^^dt:dateTime ; dcterms:modified "2007-04-13T18:19:29.000001-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "cdcc4c28cdae8d4c10884224ef8aca73" ; sioc:link ; sioc:content "Web Data Spaces\nNow that broader understanding of the Semantic Data Web is emerging, I would like to revisit the issue of "Data Spaces".\nA Data Space is a place where Data Resides. It isn't inherently bound to a specific Data Model (Concept Oriented, Relational, Hierarchical etc..). Neither is it implicitly an access point to Data, Information, or Knowledge (the perception is purely determined through the experiences of the user agents interacting with the Data Space.\nA Web Data Space is a Web accessible Data Space.\nReal world example:\nToday we increasing perform one of more of the following tasks as part of our professional and personal interactions on the Web:\n\nBlog via many service providers or personally managed weblog platforms\nCreate Event Calendars via Upcoming.com and Eventful\n\nMaintain and participate in Social Networks (e.g. Facebook, Orkut, MySpace)\nCreate and Participate in Discussions (note: when you comment on blogs or wikis for instance, you are participating in, or creating, a conversation)\nTrack news by subscribing to RSS 1.0, RSS 2.0, or Atom Feeds\nShare Bookmarks & Tags via Del.icio.us and other Services\nShare Photos via Flickr\n\nBuy, Review, or Search for books via Amazon\n\nParticipates in auctions via eBay \nSearch for data via Google (of course!)\n\n\nJohn Breslin has nice a animation depicting the creation of Web Data Spaces that drives home the point.\nWeb Data Space Silos\n\nUnfortunately, what isn't as obvious to many netizens, is the fact that each of the activities above results in the creation of data that is put into some context by you the user. Even worse, you eventually realize that the service providers aren't particularly willing, or capable of, giving you unfettered access to your own data. Of course, this isn't always by design as the infrastructure behind the service can make this a nightmare from security and/or load balancing perspectives. Irrespective of cause, we end up creating our own "Data Spaces" all over the Web without a coherent mechanism for accessing and meshing these "Data Spaces".\nWhat are Semantic Web Data Spaces?\nData Spaces on the Web that provide granular access to RDF Data.\nWhat's OpenLink Data Spaces (ODS) About?\n\nShort History\nIn anticipation of this the "Web Data Silo" challenge (an issue that we tackled within internal enterprise networks for years) we commenced the development (circa. 2001) of a distributed collaborative application suite called OpenLink Data Spaces (ODS). The project was never released to the public since the problems associated with the deliberate or inadvertent creation of Web Data silos hadn't really materialized (silos only emerged in concreted form after the emergence of the Blogosphere and Web 2.0). In addition, there wasn't a clear standard Query Language for the RDF based Web Data Model (i.e. the SPARQL Query Language didn't exist).\n\n\n\nToday, ODS is delivered as a packaged solution (in Open Source and Commercial flavors) that alleviates the pain associated with Data Space Silos that exist on the Web and/or behind corporate firewalls. In either scenario, ODS simply allows you to create Open and Secure Data Spaces (via it's suite of applications) that expose data via SQL, RDF, XML oriented data access and data management technologies. Of course it also enables you to integrates transparently with existing 3rd party data space generators (Blogs, Wikis, Shared Bookmrks, Discussion etc. services) by supporting industry standards that cover:\n\n\nContent Publishing - Atom, Moveable Type, MetaWeblog, Blogger protocols\n\n\nContent Syndication Formats - RSS 1.0, RSS 2.0, Atom, OPML etc.\n\n\nData Management - SQL, RDF, XML, Free Text\n\n\nData Access - SQL, SPARQL, GData, Web Services (SOAP or REST styles), WebDAV/HTTP\n\n\nSemantic Data Web Middleware - GRDDL, XSLT, SPARQL, XPath/XQuery, HTTP (Content Negotiation) for producing RDF from non RDF Data ((X)HTML, Microformats, XML, Web Services Response Data etc).\n\n\nThus, by installing ODS on your Desktop, Workgroup, Enterprise, or public Web Server, you end up with a very powerful solution for creating Open Data access oriented presence on the "Semantic Data Web" without incurring any of the typically assumed "RDF Tax". \nNaturally, ODS is built atop Virtuoso and of course it exploits Virtuoso's feature-set to the max. It's also beginning to exploit functionality offered by the OpenLink Ajax Toolkit (OAT).\n\n\n\n" ; atom:title "Semantic Web Data Spaces" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container ; sioc:links_to . @prefix ns11: . sioc:links_to ns11:spec . @prefix ns12: . sioc:links_to ns12:Network_model , , , , , , , , , , , ns12:SQL , , , , , ns12:Relational_model , , , ns12:Hierarchical_database , , , , . @prefix ns13: . sioc:links_to ns13:xslt . @prefix ns14: . sioc:links_to ns14:metaWeblogApi ; atom:source ; atom:author ns3:this ; atom:published "2007-04-13T21:15:54Z" ; atom:updated "2007-04-13T22:19:29Z" ; sioc:has_reply . @prefix opl: . opl:isDescribedUsing . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:Comment . @prefix sioc: . sioc:reply_of . @prefix ns4: . @prefix foaf: . ns4:this rdf:type foaf:Person ; foaf:made . rdf:type atom:Feed , sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" ; sioc:container_of ; atom:entry ; atom:contains . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .