@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person . @prefix sioct: . rdf:type sioct:Weblog . @prefix atom: . rdf:type atom:Feed . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "Enterprise 0.0, Linked Data, and Semantic Data Web" . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "Virtuoso, Linked Data, and Linq2Rdf (Update 1)" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Entity Oriented Data Access " ; foaf:maker ns1:this ; rdfs:label "Entity Oriented Data Access " . @prefix dt: . @prefix dcterms: . dcterms:created "2008-11-03T17:32:08Z"^^dt:dateTime ; dcterms:modified "2008-11-03T22:51:48-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "9a46117853a1c0d5df479034ce78139a" ; sioc:link ; sioc:content "Recent perturbations in Data Access and Data Management technology realms are clear signs of an imminent inflection. In a nutshell, the focus of data access is moving from the "Logical Level" (what you see if you've ever looked at a DBMS schema derived from an Entity Data Model) to the "Conceptual Level" (i.e., the Entity Model becoming concrete).\n\nIn recent times I've stumbled across Master Data Management (MDM) which is all about entities that provide holistic views of enterprise data (or what I call: Context Lenses). I've also stumbled across emerging tensions in the .NET realm between Linq to Entities and Linq to SQL, where in either case the fundamental issues comes down to the optimal paths "Conceptual Level Access" over the "Logical Logical Level" when dealing with data access in the .NET realm.\n\nStrangely, the emerging realm of RDF Linked Data, MDM, and .NET's Entity Frameworks, remain strangely disconnected.\n\nAnother oddity is the obvious, but barely acknowledged, blurring of the lines between the "traditional enterprise employee" and the "individual Web netizen". The fusion between these entities is one of the most defining characteristics of how the Web is reshaping the data landscape.\n\nAt the current time, I tend to crystalize my data access world view under the moniker: YODA ("You" Oriented Data Access), based on the following:\n\n\n\nEntities are the new focal point of data access, management, and integration\n\n\n"You" are the entry point (Data Source Name) into this new realm of inter connected Entities that the Web exposes\n\n"You" the "Person" Entity is associated with many other "Things" such as "Organizations", "Other People", "Books", "Music", "Subject Matter" etc. \n\n"You" the "Person" needs Identity in this new global database, which is why "You" need to Identify "Yourself" using an an HTTP based Entity ID (aka. URI)\n\n\nWhen "You" have an ID for "Yourself" it becomes much easier for the essence of "You" to be discovered via the Web \n\n\nWhen "Others" have IDs for "Themselves" on the Web it becomes much easier for "You" to serendipitously discover or explicitly "Find" things on the Web.\n\n\nRelated\n\n\n Is LINQ to SQL truly dead?\n\n\n Virtuoso, Linked Data, and Linq2Rdf\n\n\n Enterprise 0.0, Linked Data, and the Semantic Data Web (*an old post*)\n\n\n\n" ; atom:title "Entity Oriented Data Access " . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:Linked_Data , dbpedia:Netizen . @prefix ns12: . sioc:links_to ns12:perturbation . @prefix ns13: . sioc:links_to ns13:DLINQ-Future , , dbpedia:Uniform_Resource_Identifier , dbpedia:Entity , , , , dbpedia:SQL ; atom:source ; atom:author ns1:this ; atom:published "2008-11-03T17:32:08Z" ; atom:updated "2008-11-04T03:51:48Z" . @prefix opl: . opl:isDescribedUsing . ns10: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 .