@prefix rdf: . @prefix sioct: . rdf:type sioct:Comment . @prefix atom: . rdf:type atom:Entry . rdf:type sioct:Comment , atom:Entry . @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 ; rdfs:label "Simple Explanation of RDF and Linked Data Dynamics" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "What is the Linked Data Meme about?" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "Linked Data & Identity" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "Exploring the Value Proposition of Linked Data" . @prefix ns6: . @prefix sioc: . ns6:this rdf:type sioc:User . rdf:type sioct:BlogPost , atom:Entry . @prefix dc: . dc:title "Getting The Linked Data Value Pyramid Layers Right (Update #2)" ; foaf:maker ns3:this ; rdfs:label "Getting The Linked Data Value Pyramid Layers Right (Update #2)" . @prefix dt: . @prefix dcterms: . dcterms:created "2010-01-31T17:44:04-05:00"^^dt:dateTime ; dcterms:modified "2010-02-01T09:02:14.000004-05:00"^^dt:dateTime ; sioc:id "0ab6a287aeaf2d731971460feb2d016e" ; sioc:link ; sioc:content "\nOne of the real problems that pervades all routes to Linked Data value prop. incomprehension stems from the layering of its value pyramid; especially when communicating with -initially detached- end-users. \n\n\nNote to Web Programmers: Linked Data is about Data (Wine) and not about Code (Fish). Thus, it isn't a "programmer only zone", far from it. More than anything else, its inherently inclusive and spreads its participation net widely across: Data Architects, Data Integrators, Power Users, Knowledge Workers, Information Workers, Data Analysts, etc.. Basically, everyone that can "click on a link" is invited to this particular party; remember, it is about "Linked Data" not "Linked Code", after all. :-)\n\nProblematic Value Pyramid Layering\n\nHere is an example of a Linked Data value pyramid that I am stumbling across --with some frequency-- these days (note: 1 being the pyramid apex):\n\n\nSPARQL Queries\n\nRDF Data Stores\n\nRDF Data Sets\n\n\nHTTP scheme URIs\n\n\nBasically, Linked Data deployment (assigning de-referencable HTTP URIs to DBMS records, their attributes, and attribute values [optionally] ) is occurring last. Even worse, this happens in the context of Linked Open Data oriented endeavors, resulting in nothing but confusion or inadvertent perpetuation of the overarching pragmatically challenged "Semantic Web" stereotype.\n\n\nAs you can imagine, hitting SPARQL as your introduction to Linked Data is akin to hitting SQL as your introduction to Relational Database Technology, neither is an elevator-style value prop. relay mechanism.\n\n\nIn the relational realm, killer demos always started with desktop productivity tools (spreadsheets, report-writers, SQL QBE tools etc.) accessing, relational data sources en route to unveiling the "Productivity" and "Agility" value prop. that such binding delivered i.e., the desktop application (clients) and the databases (servers) are distinct, but operating in a mutually beneficial manner to all, courtesy of a data access standards such as ODBC (Open Database Connectivity).\n\n\nIn the Linked Data realm, learning to embrace and extend best practices from the relational dbms realm remains a challenge, a lot of this has to do with hangovers from a misguided perception that RDF databases will somehow completely replace RDBMS engines, rather than compliment them. Thus, you have a counter productive variant of NIH (Not Invented Here) in play, taking us to the dreaded realm of: Break the Pot and You Own It (exemplified by the 11+ year Semantic Web Project comprehension and appreciation odyssey).\n\n\nFrom my vantage point, here is how I believe the Linked Data value pyramid should be layered, especially when communicating the essential value prop.:\n\n\n\nHTTP URLs -- LINKs to documents (Reports) that users already appreciate, across the public Web and/or Intranets\n\n\nHTTP URIs -- typically not visually distinguishable from the URLs, so use the Data exposed by de-referencing a URL to show how each Data Item (Entity or Object) is uniquely identified by a Generic HTTP URI, and how clicking on the said URIs leads to more structured metadata bearing documents available in a variety of data representation formats, thereby enabling flexible data presentation (e.g., smarter HTML pages)\n\n\nSPARQL -- when a user appreciates the data representation and presentation dexterity of a Generic HTTP URI, they will be more inclined to drill down an additional layer to unravel how HTTP URIs mechanically deliver such flexibility\n\n\nRDF Data Stores -- at this stage the user is now interested data sources behind the Generic HTTP URIs, courtesy of natural desire to tweak the data presented in the report; thus, you now have an engaged user ready to absorb the "How Generic HTTP URIs Pull This Off" message\n\nRDF Data Sets -- while attempting to make or tweak HTTP URIs, users become curious about the actual data loaded into the RDF Data Store, which is where data sets used to create powerful Lookup Data Spaces (e.g., DBpedia) come into play such as those from the LOD constellation as exemplified by DBpedia (extractions from Wikipedia).\n\nRelated\n\n\n Exploring the Linked Data Value Proposition\n\n\n Simple Explanation of Linked Data & RDF Dynamics\n\n\n What is the Linked Data Meme About?\n\n\n Linked Data & Data Item Identifiers (Identity)\n\n\n" ; atom:title "Getting The Linked Data Value Pyramid Layers Right (Update #2)" ; sioc:has_creator ns6:this ; sioc:has_container ; sioc:links_to . @prefix dbpedia: . sioc:links_to dbpedia:Entity , , . @prefix ns12: . sioc:links_to ns12:Datasets , , dbpedia:Uniform_Resource_Identifier , dbpedia:Open_Database_Connectivity , , dbpedia:Resource_Description_Framework , dbpedia:Uniform_Resource_Locator , dbpedia:Linked_Data , dbpedia:Semantic_Web , dbpedia:Information , , dbpedia:SPARQL , , dbpedia:SQL , dbpedia:DBpedia , dbpedia:Hypertext_Transfer_Protocol , dbpedia:Knowledge , dbpedia:Relational_database_management_system ; atom:source ; atom:author ns3:this ; atom:published "2010-01-31T22:44:04Z" ; atom:updated "2010-02-01T14:02:14Z" ; sioc:has_reply , . @prefix opl: . opl:isDescribedUsing . @prefix rdf: . @prefix sioct: . rdf:type sioct:Comment . @prefix atom: . rdf:type atom:Entry . @prefix sioc: . sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; 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 .