@prefix rdfs: . @prefix ns1: . ns1:this rdfs:label "Kingsley Idehen" . @prefix rdf: . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Organization ; rdfs:seeAlso ns1:this . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:BlogPost ; rdfs:label "Conversation with Jon Udell: Are We There Yet Re. Web++ ?" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Revisiting HTTP based Linked Data (Update 1 - Demo Video Links Added)" . @prefix ns8: . foaf:maker ns8:this ; rdfs:label "Revisiting HTTP based Linked Data (Update 1 - Demo Video Links Added)" . @prefix dt: . @prefix dcterms: . dcterms:created "2010-03-04T10:16:14-05:00"^^dt:dateTime ; dcterms:modified "2010-03-08T09:59:37.000010-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "bd3b2c33f411135be0aca4657089324d" ; sioc:link ; sioc:content "Motivation for this post arose from a series of Twitter exchanges between Tony Hirst and I, in relation to his blog post titled: So What Is It About Linked Data that Makes it Linked Data\u2122 ?\n\nAt the end of the marathon session, it was clear to me that a blog post was required for future reference, at the very least :-)\nWhat is Linked Data?\n"Data Access by Reference" mechanism for Data Objects (or Entities) on HTTP networks. It enables you to Identify a Data Object and Access its structured Data Representation via a single Generic HTTP scheme based Identifier (HTTP URI). Data Object representation formats may vary; but in all cases, they are hypermedia oriented, fully structured, and negotiable within the context of a client-server message exchange.\nWhy is it Important?\n\nInformation makes the world tick!\nInformation doesn't exist without data to contextualize.\nInformation is inaccessible without a projection (presentation) medium. \nAll information (without exception, when produced by humans) is subjective. Thus, to truly maximize the innate heterogeneity of collective human intelligence, loose coupling of our information and associated data sources is imperative.\nHow is Linked Data Delivered?\nLinked Data is exposed to HTTP networks (e.g. World Wide Web) via hypermedia resources bearing structured representations of data object descriptions. Remember, you have a single Identifier abstraction (generic HTTP URI) that embodies: Data Object Name and Data Representation Location (aka URL).\nHow are Linked Data Object Representations Structured?\nA structured representation of data exists when an Entity (Datum), its Attributes, and its Attribute Values are clearly discernible. In the case of a Linked Data Object, structured descriptions take the form of a hypermedia based Entity-Attribute-Value (EAV) graph pictorial -- where each Entity, its Attributes, and its Attribute Values (optionally) are identified using Generic HTTP URIs. \nExamples of structured data representation formats (content types) associated with Linked Data Objects include:\n\n text/html\n text/turtle\n text/n3\n application/json\n application/rdf+xml\n Others \n\nHow Do I Create Linked Data oriented Hypermedia Resources?\nYou markup resources by expressing distinct entity-attribute-value statements (basically these a 3-tuple records) using a variety of notations:\n\n (X)HTML+RDFa,\n \n JSON,\n \n Turtle,\n \n N3,\n \n TriX,\n \n TriG,\n \n RDF/XML, and\n Others (for instance you can use Atom data format extensions to model EAV graph as per OData initiative from Microsoft).\n\nYou can achieve this task using any of the following approaches:\n\n Notepad\n WYSIWYG Editor \n Transformation of Database Records via Middleware\n Transformation of XML based Web Services output via Middleware\n Transformation of other Hypermedia Resources via Middleware\n Transformation of non Hypermedia Resources via Middleware\n Use a platform that delivers all of the above.\n\nPractical Examples of Linked Data Objects Enable\n\n Describe Who You Are, What You Offer, and What You Need via your structured profile, then leave your HTTP network to perform the REST (serendipitous discovery of relevant things)\n Identify (via map overlay) all items of interest based on a 2km+ radious of my current location (this could include vendor offerings or services sought by existing or future customers)\n Share the latest and greatest family photos with family members *only* without forcing them to signup for Yet Another Web 2.0 service or Social Network\n No repetitive signup and username and password based login sequences per Web 2.0 or Mobile Application combo\n Going beyond imprecise Keyword Search to the new frontier of Precision Find - Example, Find Data Objects associated with the keywords: Tiger, while enabling the seeker disambiguate across the "Who", "What", "Where", "When" dimensions (with negation capability)\n Determine how two Data Objects are Connected - person to person, person to subject matter etc. (LinkedIn outside the walled garden)\n Use any resource address (e.g blog or bookmark URL) as the conduit into a Data Object mesh that exposes all associated Entities and their social network relationships\n Apply patterns (social dimensions) above to traditional enterprise data sources in combination (optionally) with external data without compromising security etc.\n\nHow Do OpenLink Software Products Enable Linked Data Exploitation?\nOur data access middleware heritage (which spans 16+ years) has enabled us to assemble a rich portfolio of coherently integrated products that enable cost-effective evaluation and utilization of Linked Data,\t without writing a single line of code, or exposing you to the hidden, but extensive admin and configuration costs. Post installation, the benefits of Linked Data simply materialize (along the lines described above).\nOur main Linked Data oriented products include:\n\n \n OpenLink Data Explorer -- visualizes Linked Data or Linked Data transformed "on the fly" from hypermedia and non hypermedia data sources \n \n URIBurner -- a "deceptively simple" solution that enables the generation of Linked Data "on the fly" from a broad collection of data sources and resource types\n \n OpenLink Data Spaces -- a platform for enterprises and individuals that enhances distributed collaboration via Linked Data driven virtualization of data across its native and/or 3rd party content manager for: Blogs, Wikis, Shared Bookmarks, Discussion Forums, Social Networks etc\n \n OpenLink Virtuoso -- a secure and high-performance native hybrid data server (Relational, RDF-Graph, Document models) that includes in-built Linked Data transformation middleware (aka. Sponger). \n\nRelated\n\n \n Hypertext Transfer Protocol 1.1 RFC\n\n \n Open Data Protocol Glossary\n\n \n Simple Explanation of RDF and Linked Data Dynamics\n\n \n Collection of post from the past about Linked Data\n\n \n Are We There Yet Re. Web++? -- includes link to podcast conversation with Jon Udell\n\n\n Web of Linked Data Pivoting Demo from TED -- by Microsoft's Gary Flake\n\n\n Microsoft Pivot atop Virtuoso Quad Store's Faceted Browser Engine-- My Demonstration of EAV model transcending data representation variations (i.e., RDF's EAV data model data served up in Microsoft CXML data representation format).\n \n" ; atom:title "Revisiting HTTP based Linked Data (Update 1 - Demo Video Links Added)" . @prefix ns12: . sioc:has_creator ns12:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:Blog , , dbpedia:Entity-attribute-value_model , dbpedia:Uniform_Resource_Locator , dbpedia:Information , , dbpedia:Uniform_Resource_Identifier , , , dbpedia:Linked_Data , dbpedia:RDFa , , , , . @prefix ns14: . sioc:links_to ns14:this , . @prefix ns15: . sioc:links_to ns15:RDF_JSON_Specification , , , ns1:this , dbpedia:World_Wide_Web , , dbpedia:Hypermedia . @prefix ns16: . sioc:links_to ns16:Notation3 , , , , , dbpedia:Entity , , . @prefix ns17: . sioc:links_to ns17:_Toc246716495 , ns3:this ; atom:source ; atom:author ns8:this ; atom:published "2010-03-04T15:16:14Z" ; atom:updated "2010-03-08T14:59:37Z" ; sioc:has_reply . @prefix opl: . opl:isDescribedUsing . ns8:this rdf:type foaf:Person . rdf:type sioct:Weblog , atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "Simple Explanation of RDF and Linked Data Dynamics" . ns12:this rdf:type sioc:User . rdf:type atom:Entry , sioct:Comment . @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:Comment , atom:Entry ; sioc:reply_of .