@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Organization . @prefix rdfs: . @prefix ns4: . ns1:this rdfs:seeAlso ns4:this . @prefix ns5: . ns5:this rdf:type foaf:Person . @prefix sioct: . rdf:type sioct:Weblog . @prefix atom: . rdf:type atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type sioct:BlogPost , atom:Entry . @prefix dc: . dc:title "Linked Data is vital to Enterprise Integration driven Agility" ; foaf:maker ns5:this ; rdfs:label "Linked Data is vital to Enterprise Integration driven Agility" . @prefix dt: . @prefix dcterms: . dcterms:created "2008-03-21T21:56:00-04:00"^^dt:dateTime ; dcterms:modified "2008-03-22T14:13:41.000002-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "7eafd544c020ca30ae647ccb3b0fb087" ; sioc:link ; sioc:content "\n John Schmidt, from Informatica, penned an interesting post titled: IT Doesn't Matter - Integration Does. Yes, integration is hard, but I do profoundly believe that what's been happening on the Web over the last 10 or so years also applies to the Enterprise, and by this I absolutely do not mean "Enterprise 2.0" since "2.0" and productive agility do not compute in my realm of discourse. large collections of RSS feeds, Wikiwords, Shared Bookmarks, Discussion Forums etc.. when disconnected at the data level (i.e. hosted in pages with no access to the "data behind") simply offer information deluge and inertia (there are only so many hours for processing opaque information sources in a given day). Enterprises fundamentally need to process information efficiently as part of a perpetual assessment of their relative competitive Strengths, Weaknesses, Opportunities, and Threats (SWOT), in existing and/or future markets. Historically, IT acquisitions have run counter intuitively to the aforementioned quest for "Ability" due to the predominance of "rip and replace" approach technology acquisition that repeatedly creates and perpetuates information silos across Application, Database, Operating System, Development Environment boundaries. The sequence of events typically occurs as follows: applications are acquired on a problem by problem basis back-end application databases are discovered once ad-hoc information views are sought by information workers back-end database disparity across applications is discovered once holistic views are sought by knowledge workers (typically domain experts). In the early to mid 90's (pre ubiquitous Web), operating system, programming language, operating system, and development framework independence inside the enterprise was technically achievable via ODBC (due to it's platform independence). That said, DBMS specific ODBC channels alone couldn't address the holistic requirements associated with Conceptual Views of disparate data sources, hence the need for Data Access Virtualization via Virtual Database Engine technology. Just as is the case on the Web today, with the emergence of the "Linked Data" meme, enterprises now have a powerful mechanism for exploiting the Data Integration benefits associated with generating Data Objects from disparate data sources, endowed with HTTP based IDs (URIs). Conceptualizing access to data exposed Databases APIs, SOA based Web Services (SOAP style Web Services), Web 2.0 APIs (REST style Web Services), XML Views of SQL Data (SQLX), pure XML etc.. is problem area addressed by RDF aware middleware (RDFizers e.g Virtuoso Sponger). Here are examples of what SQL Rows exposed as RDF Data Objects (identified using HTTP based URIs) would look like outside or behind a corporate firewall: Customer - Alfreds Futterkiste Customer Contact - Maria Anders Salesrep - Nancy Davolio Customer Orders Numbers - 11084, 11011, 11078, 11085 What's Good for the Web Goose (Personal Data Space URIs) is good for the Enterprise Gander (Enterprise Data Space URIs). Related Data Access - A Cultural or Technical Challenge? \n" ; atom:title "Linked Data is vital to Enterprise Integration driven Agility" . @prefix ns12: . sioc:has_creator ns12:this ; sioc:has_container . @prefix ns13: . sioc:links_to ns13:this . @prefix dbpedia: . sioc:links_to dbpedia:SWOT_analysis . @prefix ns15: . sioc:links_to ns15:this , dbpedia:Knowledge_worker . @prefix ns16: . sioc:links_to ns16:XML , dbpedia:Federated_database_system , dbpedia:Information_worker , , dbpedia:Domain_expert , , . @prefix ns17: . sioc:links_to ns17:this . @prefix ns18: . sioc:links_to ns18:ConverterToRdf . @prefix ns19: . sioc:links_to ns19:this . @prefix ns20: . sioc:links_to ns20:this . @prefix ns21: . sioc:links_to ns21:this . @prefix ns22: . sioc:links_to ns22:this , , dbpedia:SQL , , , dbpedia:Open_Database_Connectivity , ns1:this ; atom:source ; atom:author ns5:this ; atom:published "2008-03-22T01:56:00Z" ; atom:updated "2008-03-22T18:13:41Z" . @prefix opl: . opl:isDescribedUsing . ns12:this rdf:type sioc:User . @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 .