@prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:BlogPost . @prefix dc: . dc:title "Why Do I Need To Pay For ODBC , JDBC, ADO.NET, OLE-DB Drivers? (Update 3)" . @prefix foaf: . @prefix ns5: . foaf:maker ns5:this . @prefix rdfs: . rdfs:label "Why Do I Need To Pay For ODBC , JDBC, ADO.NET, OLE-DB Drivers? (Update 3)" . @prefix dt: . @prefix dcterms: . dcterms:created "2010-01-31T17:31:35-05:00"^^dt:dateTime ; dcterms:modified "2010-02-01T08:59:36.000004-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "e28082641c5c8e692e4e123c8ccc8fc4" ; sioc:link ; sioc:content "\n <ol> <li> It isn&#39;t <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id115dfd68">World Wide Web</a> Specific (HTTP != World Wide Web)</li> <li> It isn&#39;t Open Data Specific </li> <li> It isn&#39;t about &quot;Free&quot; (Beer or Speech) </li> <li> It isn&#39;t about Markup (so don&#39;t expect to grok it via &quot;markup first&quot; approach) </li> <li>It&#39;s about <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13a6aa98">Hyperdata</a> - the use of HTTP and REST to deliver a powerful platform agnostic mechanism for Data Reference, Access, and Integration.</li> </ol> <p> When trying to understand HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id18aa1490">Linked Data</a>, especially if you&#39;re well versed in DBMS technology use (User, Power User, Architect, Analyst, DBA, or Programmer) think: <br />\n</p> <ul> <li> Open Database Connectivity (<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1428fba0">ODBC</a>) without operating system, data model, or wire-protocol specificity or lock-in potential </li> <li> Java Database Connectivity (<a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id18d3c2a8">JDBC</a>) without programming language specificity </li> <li> <a href="http://dbpedia.org/resource/ADO.NET" id="link-id125725b8">ADO</a>.NET without .NET runtime specificity and .NET bound language specificity </li> <li> OLE-DB without Windows operating system &amp; programming language specificity </li> <li> XMLA without XML format specificity - with Tabular and Multidimensional results formats expressible in a variety of data representation formats. </li> <li>All of the above scoped to the Record rather than Container level, with Generic HTTP scheme URIs associated with each Record, Field, and Field value (optionally) </li> </ul> <p>Remember the need for Data Access &amp; Integration technology is the by product of the following realities:</p> <ol> <li> Human curated data is ultimately dirty, because: <ul> <li>our thick thumbs, inattention, distractions, and general discomfort with typing, make typos prevalent</li> <li>database engines exist for a variety of data models - Graph, Relational, Hierarchical;</li> <li>within databases you have different record container/partition names e.g. Table Names;</li> <li>within a database record container you have records that are really aspects of the same thing (different keys exist in a plethora of operational / line of business systems that expose aspects of the same <a href="http://dbpedia.org/resource/Entity" id="link-id13378338">entity</a> e.g., customer data that spans Accounts, CRM, ERP application databases);</li> <li>different field names (one database has &quot;EMP&quot; while another has &quot;Employee&quot;) for the same record</li>.</ul> </li> <li>Units of measurement is driven by locale, the UK office wants to see sales in Pounds Sterling while the French office prefers Euros etc.</li> <li>All of the above is subject to <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id17e46398">context</a> halos which can be quite granular re. sensitivity e.g. staff travel between locations that alter locales and their roles; basically, profiles matters a lot.</li> </ol> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1364" id="link-id128f0fe8">ODBC and WODBC (Web Open Database Connectivity) Comparison</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1364" id="link-id1367cd18">Creating, Deploying, and Exploiting Linked Data Presentation</a> </li> <li> <a href="http://www.odata.org/" id="link-id122ab708">Open Data Protocol Project</a> </li> </ul>\n" ; atom:title "Why Do I Need To Pay For ODBC , JDBC, ADO.NET, OLE-DB Drivers? (Update 3)" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:Java_Database_Connectivity , dbpedia:Entity , , dbpedia:Open_Database_Connectivity , , dbpedia:World_Wide_Web , , dbpedia:Linked_Data , ; atom:source ; atom:author ns5:this ; atom:published "2010-01-31T22:31:35Z" ; atom:updated "2010-02-01T13:59:36Z" . @prefix opl: . opl:isDescribedUsing . ns5:this rdf:type foaf:Person . rdf:type atom:Feed , sioct:Weblog ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" ; rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "ODBC & WODBC Comparison" . ns10:this rdf:type sioc:User .@prefix sioc: . sioc:link . @prefix rdf: . @prefix ns2: . @prefix foaf: . ns2: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" ; sioc:container_of ; atom:entry ; atom:contains . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .