@prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:BlogPost . @prefix dc: . dc:title "URIBurner: Painless Generation & Exploitation of Linked Data (Update 1 - Demo Links Added)" . @prefix foaf: . @prefix ns5: . foaf:maker ns5:this . @prefix rdfs: . rdfs:label "URIBurner: Painless Generation & Exploitation of Linked Data (Update 1 - Demo Links Added)" . @prefix dt: . @prefix dcterms: . dcterms:created "2010-03-10T12:52:03-05:00"^^dt:dateTime ; dcterms:modified "2010-03-11T10:16:34.000003-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "22a8e8c9f05f0032b8f9cf9bf6b7b701" ; sioc:link ; sioc:content "What is URIBurner? \nA service from OpenLink Software, available at: http://uriburner.com, that enables anyone to generate structured descriptions -on the fly- for resources that are already published to HTTP based networks. These descriptions exist as hypermedia resource representations where links are used to identify: \n\n\nthe entity (data object or datum) being described,\neach of its attributes, and\neach of its attributes values (optionally). \n\nThe hypermedia resource representation outlined above is what is commonly known as an Entity-Attribute-Value (EAV) Graph. The use of generic HTTP scheme based Identifiers is what distinguishes this type of hypermedia resource from others.\nWhy is it Important?\n\nThe virtues (dual pronged serendipitous discovery) of publishing HTTP based Linked Data across public (World Wide Web) or private (Intranets and/or Extranets) is rapidly becoming clearer to everyone. That said, the nuance laced nature of Linked Data publishing presents significant challenges to most. Thus, for Linked Data to really blossom the process of publishing needs to be simplified i.e., "just click and go" (for human interaction) or REST-ful orchestration of HTTP CRUD (Create, Read, Update, Delete) operations between Client Applications and Linked Data Servers.\n\n\nHow Do I Use It?\n\nIn similar vane to the role played by FeedBurner with regards to Atom and RSS feed generation, during the early stages of the Blogosphere, it enables anyone to publish Linked Data bearing hypermedia resources on an HTTP network. Thus, its usage covers two profiles: Content Publisher and Content Consumer.\n \n\n\n\n\nContent Publisher\n \n\n\nThe steps that follow cover all you need to do:\n\n\nplace a tag within your HTTP based hypermedia resource (e.g. within section for HTML )\nuse a URL via the @href attribute value to identify the location of the structured description of your resource, in this case it takes the form: http://linkeddata.uriburner.com/about/id/{scheme-or-protocol}/{your-hostname-or-authority}/{your-local-resource}\nfor human visibility you may consider adding associating a button (as you do with Atom and RSS) with the URL above.\n\n\nThat's it! The discoverability (SDQ) of your content has just multiplied significantly, its structured description is now part of the Linked Data Cloud with a reference back to your site (which is now a bona fide HTTP based Linked Data Space).\nExamples\n\n\nHTML+RDFa based representation of a structured resource description:\n\n\n\n<link rel="describedby" title="Resource Description (HTML)"type="text/html" href="http://linkeddata.uriburner.com/about/id/http/example.org/xyz.html"/>\n\n\n\nJSON based representation of a structured resource description:\n\n<link rel="describedby" title="Resource Description (JSON)" type="application/json" href="http://linkeddata.uriburner.com/about/id/http/example.org/xyz.html"/>\n\nN3 based representation of a structured resource description:\n\n\n<link rel="describedby" title="Resource Description (N3)" type="text/n3" href="http://linkeddata.uriburner.com/about/id/http/example.org/xyz.html"/>\n\n\n\nRDF/XML based representations of a structured resource description:\n\n\n\n<link rel="describedby" title="Resource Description (RDF/XML)" type="application/rdf+xml" href="http://linkeddata.uriburner.com/about/id/http/example.org/xyz.html"/>\n\nContent Consumer\nAs an end-user, obtaining a structured description of any resource published to an HTTP network boils down to the following steps:\n\ngo to: http://uriburner.com\ndrag the Page Metadata Bookmarklet link to your Browser's toolbar\nwhenever you encounter a resource of interest (e.g. an HTML page) simply click on the Bookmarklet\nyou will be presented with an HTML representation of a structured resource description (i.e., identifier of the entity being described, its attributes, and its attribute values will be clearly presented).\n\nExamples\n\n\n Description of a Book culled from an Amazon web page\n\n\n Description of a product offering culled from a BestBuy web page\n\n\n Description of a product (a camera) culled from a CNET web page\n\n\n Description of the same CNET product as an Offer on eBay (exposed by the description above via seeAlso property value).\n\nIf you are a developer, you can simply perform an HTTP operation request (from your development environment of choice) using any of the URL patterns presented below:\n HTML:\n\n \n\n curl -I -H "Accept: text/html" http://linkeddata.uriburner.com/about/id/{scheme}/{authority}/{local-path} \n\n\n \n JSON:\n \n curl -I -H "Accept: application/json" http://linkeddata.uriburner.com/about/id/{scheme}/{authority}/{local-path} \n curl http://linkeddata.uriburner.com/about/data/json/{scheme}/{authority}/{local-path}\n\n \n\n \n Notation 3 (N3):\n\n \n curl -I -H "Accept: text/n3" http://linkeddata.uriburner.com/about/id/{scheme}/{authority}/{local-path} \n\n curl http://linkeddata.uriburner.com/about/data/n3/{scheme}/{authority}/{local-path}\n\n\n \n \n curl -I -H "Accept: text/turtle" http://linkeddata.uriburner.com/about/id/{scheme}/{authority}/{local-path} \n\n curl http://linkeddata.uriburner.com/about/data/ttl/{scheme}/{authority}/{local-path} \n\n \n \n RDF/XML:\n\n \n curl -I -H "Accept: application/rdf+xml" http://linkeddata.uriburner.com/about/id/{scheme}/{authority}/{local-path} \n\n curl http://linkeddata.uriburner.com/about/data/xml/{scheme}/{authority}/{local-path} \n\n\nConclusion\nURIBurner is a "deceptively simple" solution for cost-effective exploitation of HTTP based Linked Data meshes. It doesn't require any programming or customization en route to immediately realizing its virtues. \n If you like what URIBurner offers, but prefer to leverage its capabilities within your domain -- such that resource description URLs reside in your domain, all you have to do is perform the following steps:\n\n \n download a copy of Virtuoso (for local desktop, workgroup, or data center installation) or\n instantiate Virtuoso via the Amazon EC2 Cloud \n enable the Sponger Middleware component via the RDF Mapper VAD package (which includes cartridges for over 30 different resources types)\n\nWhen you install your own URIBurner instances, you also have the ability to perform customizations that increase resource description fidelity in line with your specific needs. All you need to do is develop a custom extractor cartridge and/or meta cartridge. \nRelated:\n\n\n Virtuoso Sponger Middleware -- (technology behind URIBurner Service)\n\n Animation demonstrating how the Virtuoso Sponger works.\n\n" ; atom:title "URIBurner: Painless Generation & Exploitation of Linked Data (Update 1 - Demo Links Added)" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container ; sioc:links_to , , . @prefix ns11: . sioc:links_to ns11:Offer , . @prefix dbpedia: . sioc:links_to dbpedia:Uniform_Resource_Locator , dbpedia:Entity-attribute-value_model , , dbpedia:World_Wide_Web , . @prefix ns13: . sioc:links_to ns13:this , dbpedia:RDFa , dbpedia:Linked_Data . @prefix ns14: . sioc:links_to ns14:VirtSponger , dbpedia:Entity . @prefix ns15: . sioc:links_to ns15:Data_Spaces , dbpedia:Tag ; atom:source ; atom:author ns5:this ; atom:published "2010-03-10T17:52:03Z" ; atom:updated "2010-03-11T15:16:34Z" ; sioc:has_reply , . @prefix opl: . opl:isDescribedUsing . ns13:this rdf:type foaf:Organization . @prefix ns17: . ns13:this rdfs:seeAlso ns17:this . 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 . rdf:type atom:Entry , sioct:Comment . rdf:type sioct:Comment , atom:Entry . @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 . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "Virtuoso Linked Data Deployment In 3 Simple Steps" ; sioc:links_to . rdf:type sioct:Comment , atom:Entry ; sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; sioc:reply_of .