@prefix rdf: . @prefix sioct: . rdf:type sioct:BlogPost . @prefix atom: . rdf:type atom:Entry . @prefix dc: . dc:title "5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo" . @prefix foaf: . @prefix ns5: . foaf:maker ns5:this . @prefix rdfs: . rdfs:label "5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo" . @prefix dt: . @prefix dcterms: . dcterms:created "2010-01-31T17:29:34-05:00"^^dt:dateTime ; dcterms:modified "2010-02-01T08:59:36-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "6455b2f5bef5f886204222f3b0b650e8" ; sioc:link ; sioc:content "\n Here are 5 powerful benefits you can immediately derive from the combination of Virtuoso and Amazon's AWS services (specifically the EC2 and EBS components): \n Acquire your own personal or service specific data space in the Cloud. Think DBase, Paradox, FoxPRO, Access of yore, but with the power of Oracle, Informix, Microsoft SQL Server etc.. using a Conceptual, as opposed to solely Logical, model based DBMS (i.e., a Hybrid DBMS Engine for: SQL, RDF, XML, and Full Text) Ability to share and control access to your resources using innovations like FOAF+SSL, OpenID, and OAuth, all from one place Construction of personal or organization based FOAF profiles in a matter of minutes; by simply creating a basic DBMS (or ODS application layer) account; and then using this profile to create strong links (references) to all your Data silos (esp. those from the Web 2.0 realm) Load data sets from the LOD cloud or Sponge existing Web resources (i.e., on the fly data transformation to RDF model based Linked Data) and then use the combination to build powerful lookup services that enrich the value of URLs (think: Web addressable reports holding query results) that you publish Bind all of the above to a domain that you own (e.g. a .Name domain) so that you have an attribution-friendly "authority" component for resource URLs and Entity URIs published from your Personal Linked Data Space on the Web (or private HTTP network). In a nutshell, the AWS Cloud infrastructure simplifies the process of generating Federated presence on the Internet and/or World Wide Web. Remember, centralized networking models always end up creating data silos, in some context, ultimately! :-) \n" ; atom:title "5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:Internet , dbpedia:World_Wide_Web , dbpedia:Linked_Data . @prefix ns12: . sioc:links_to ns12:this , , dbpedia:Entity , dbpedia:OpenLink_Data_Spaces , dbpedia:IBM_Informix , dbpedia:Friend_of_a_friend , , dbpedia:Microsoft_SQL_Server , dbpedia:SQL . @prefix ns13: . sioc:links_to ns13:Data_Spaces , dbpedia:Oracle_Database ; atom:source ; atom:author ns5:this ; atom:published "2010-01-31T22:29:34Z" ; atom:updated "2010-02-01T13:59:36Z" ; sioc:has_reply . @prefix opl: . opl:isDescribedUsing . rdf:type atom:Entry , sioct:Comment . ns5:this rdf:type foaf:Person . rdf:type sioct:Weblog , atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix sioct: . rdf:type sioct:Comment . @prefix atom: . rdf:type atom:Entry . @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 .