@prefix rdf: . @prefix sioct: . rdf:type sioct:Comment . @prefix atom: . rdf:type 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 sioct:BlogPost , atom:Entry . @prefix dc: . dc:title "What do people have against URLs or URIs? (Updated)" ; foaf:maker ns3:this ; rdfs:label "What do people have against URLs or URIs? (Updated)" . @prefix dt: . @prefix dcterms: . dcterms:created "2008-06-22T22:36:14Z"^^dt:dateTime ; dcterms:modified "2008-06-23T09:37:57.000003-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "77e1a372e5a79159c098a4222f9d7181" ; sioc:link ; sioc:content "Stumbled across a nice post titled: What do people have against URLs?. My answer: Everything, if they don't understand the inherent power of URLs when incorporated into the "Data Source Naming" mechanism of the Web called: URIs :-)\nURIs are simple to use i.e you simply click on them via a user agents UI. However, URLs when incorporated into Data Source Naming en route to constructing HTTP based Identifiers, that deliver HTTP based pointers to the location / address of a Resource Descriptions, another matter.\nI touched on this issue in my Linked Data Planet keynote last week, and I must say, it did set off a light.\nI believe, we can only get the broader Web community to comprehend the utility of URIs (Web Data Source Names) by exposing said utility via the Web's Universal Client (Web Browser). For instance, how do URN based Identity / Naming schemes help in a world dominated by Web Browsers that only grok "http://"? From my vantage point, the practical solution is for data providers who already have "doi", "lsid" and other Handle based Identifiers in place, to embark upon http-to-native-naming-scheme-proxying.\nIn my usual "dog-fooding" and "practice what you preach" fashion, this is exactly what we do in the new Linked Data Web extension that we've decided to reveal to the public (albeit late beta). Thus, when you use an existing browser to view pages with "lsid" or "doi" URNs, you still enjoy the utility of getting at the "Raw Linked Data Sources" that these names expose." ; atom:title "What do people have against URLs or URIs? (Updated)" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix ns11: . sioc:links_to ns11:what-do-people-have-against-urls . @prefix dbpedia: . sioc:links_to dbpedia:Linked_Data , , ; atom:source ; atom:author ns3:this ; atom:published "2008-06-22T22:36:14Z" ; atom:updated "2008-06-23T13:37:57Z" ; sioc:has_reply , , , , . @prefix opl: . opl:isDescribedUsing . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs?" . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs?" . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs?" . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs? (Updated)" . ns10:this rdf:type sioc:User . @prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:BlogPost . @prefix rdfs: . rdfs:label "Data 3.0 (a Manifesto for Platform Agnostic Structured Data) Update 5" . @prefix sioc: . sioc:links_to . rdf:type atom:Entry , sioct:Comment ; sioc:reply_of . @prefix ns5: . @prefix foaf: . ns5:this rdf:type foaf:Person ; foaf:made . rdf:type atom:Feed , sioct:Weblog ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" ; sioc:container_of ; atom:entry ; atom:contains . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs?" ; sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:What do people have against URLs or URIs?" ; sioc:reply_of . rdf:type sioct:Comment , atom:Entry ; rdfs:label "Re:What do people have against URLs or URIs?" ; sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:What do people have against URLs or URIs? (Updated)" ; sioc:reply_of . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of .