@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 sioct:BlogPost , atom:Entry ; rdfs:label "Master Data Management (MDM) & RDF based Linked Data" . rdf:type sioct:BlogPost , atom:Entry . @prefix dc: . dc:title "Cool URIs, Fish, and Wine" ; foaf:maker ns1:this ; rdfs:label "Cool URIs, Fish, and Wine" . @prefix dt: . @prefix dcterms: . dcterms:created "2008-12-12T21:41:03Z"^^dt:dateTime ; dcterms:modified "2009-01-23T17:22:00.000005-05:00"^^dt:dateTime . @prefix sioc: . sioc:id "48482593b4edca5b9801e505e9351b9b" ; sioc:link ; sioc:content "I've just read James Governor's insightful post titled: Why Applications Are Like Fish and Data is Like Wine, where he sums up the comparative value of applications (code containers) and data as follows:\n"Only one improves with age. With apologies to the originator of the phrase - \u201CHardware is like fish, operating systems are like wine.\u201D\nYes! Applications are like Fish and Data like Wine, which is basically what Linked Data is fundamentally about, especially when you inject memes such as "Cool URIs" into the mix. Remember, the essence of Linked Data is all about a Web of Linked Data Objects endowed with Identifiers that don't change i.e., they occupy one place in public (e.g. World Wide Web) or private (your corporate Intranet or Extranet) networks, keeping the data that they expose relevant (as in fresh), accessible, and usable in many forms courtesy of the data access & representation dexterity that HTTP facilitates, when incorporated into object identifiers.\n\nHere is another excerpt from his post that rings true (amongst many others):\n\n\nWhat am I talking about? Processes change, and need to change. Baking data into the application is a bad idea because the data can\u2019t then be extended in useful, and \u201Cunexpected ways\u201D. But not expecting corporate data to be used in new ways is kind of like not expecting the Spanish Inquisition. But\u2026 \u201CNOBODY expects the Spanish Inquisition! Amongst our weaponry are such diverse elements as: fear, surprise, ruthless efficiency, an almost fanatical devotion to the Pope.\u201D (sounds like Enterprise Architecture ...).\n\nRelated\n\n\n Master Data Management & RDF based Linked Data\n\n\n\n" ; atom:title "Cool URIs, Fish, and Wine" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:World_Wide_Web , dbpedia:Linked_Data , , , , , , dbpedia:Intranet , dbpedia:Extranet ; atom:source ; atom:author ns1:this ; atom:published "2008-12-12T21:41:03Z" ; atom:updated "2009-01-23T22:22:00Z" ; sioc:has_reply , , . @prefix opl: . opl:isDescribedUsing . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:Cool URIs, Fish, and Wine" . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:Cool URIs, Fish, and Wine" . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:Cool URIs, Fish, and Wine" . 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 . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:Cool URIs, Fish, and Wine" ; sioc:reply_of . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:Cool URIs, Fish, and Wine" ; sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:Cool URIs, Fish, and Wine" ; sioc:reply_of . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .